UNB Entity and Account Verification in UTS

1. Key takeaways

Before a single product entry can be created in ÜTS, the entity standing behind that entry must be recognised by the system. This article addresses that precondition: how the entity side of ÜTS works, which provisions govern it, and why the choice of account type must be settled long before any product submission is attempted. A registration project that begins with product data almost always has to loop back: the system rejects entries that lack a recognised account holder, and the delay is measured in weeks rather than days. Establishing the entity first, and confirming its permissions in writing, is therefore the cheapest sequencing decision available.

• Product-side actions in ÜTS presuppose entity-side actions: without a recognised entity identity, no product entry can be established. The legal chain is Madde 34 (ÜTS obligations) plus Madde 11 (foreign manufacturers must appoint an authorised representative) plus Madde 13 (importer obligations).
• Foreign manufacturers cannot bypass the local carrier. Under paragraph 1 of Madde 11, where the manufacturer has no establishment in Turkey or in an EU Member State, the device may be placed on the market only once an authorised representative has been appointed.
• Account types — manufacturer, authorised representative, importer, distributor, healthcare institution — correspond to different reporting permissions. This difference should be confirmed at the account-opening stage, not discovered when a product submission fails for lack of authority.
• System-side identifiers such as UNB and UBB belong to the operative layer, and their specific generation rules and field definitions are governed by the TİTCK guide; this article makes no specific assertions about numbering rules (practical estimate).

2. Legal basis

The provisions gathered here form the statutory skeleton of the entity side: one article creates the ÜTS duty, two articles govern who may lawfully bring goods into the market and under what identity, and one article requires registration ahead of notified body involvement. The operative guide then fills in the procedural detail that the Regulation deliberately leaves to the Kurum. Because the operative layer carries the procedural detail, keep the two layers identified separately in the compliance file: a change to the guide never changes the statutory duty, but it can change everything about how that duty is performed day to day.

3. Expert insights

Insight one: the core of the ÜTS entity layer is the question of who bears legal responsibility. What the system records is not merely a name but an obligated subject within the meaning of Madde 34. Hanging the account on the name of an unrelated local company amounts to letting a party that owes none of the reporting duties hold the reporting rights — and the moment a traceability event occurs, the mismatch between responsibility and authority is exposed at once. Auditors, authorities and trading partners all read the entity record as a statement of accountability, so the entity named in ÜTS must be the entity that genuinely discharges the duties attached to that role. Naming conventions matter here as well: the entity record, the notarised appointment chain and the signatories on internal procedures should all point to the same legal person, so that a reviewer moving between documents never encounters an unexplained discrepancy.

Insight two: Madde 11 and Madde 13 are two different gateways. The authorised representative solves the question of the foreign manufacturer’s lawful identity; the importer solves the question of how the goods physically enter the market. They may be different entities or the same entity, but the sources of their obligations differ. Many enterprises treat having an importer as a reason for not needing an authorised representative — under Turkish law that reasoning does not hold. The two roles answer different provisions, carry different duties and are examined separately during any regulatory check, which is precisely why both must be assessed on their own terms before market entry. Clarifying the division in writing at the outset costs little and removes an argument that otherwise resurfaces during audits and renewals.

Insight three: registration under Madde 31 precedes the notified body application, and precedes ÜTS product-side operations as well. The Regulation expressly requires that projects requiring notified body involvement complete registration before submitting the application. Combined with Madde 34, the practical sequence is: first determine the legal carrier → complete Madde 31 registration and obtain the SRN → establish the ÜTS entity → create the product entry. Reversing any step in this order produces rework, because the later steps validate against the outputs of the earlier ones. Each step consumes the output of the one before it, so compressing the schedule by overlapping them usually trades a small saving for a large rework risk.

4. Practical recommendations

• Complete the role determination before the contract is signed: authorised representative versus importer versus one entity serving both roles.
• Before opening the account, produce a written checklist reconciling the account type, the scope of reporting permissions and the actual business needs.
• Treat the notarisation chain of the authorised representative’s appointment documents (notarisation and Turkish translation) as a mandatory item in the account-opening file, and confirm the receiving requirements with the local partner in advance (practical estimate).

5. Verification checklist

• □ The foreign manufacturer has appointed an authorised representative in Turkey (or the EU) (Madde 11, paragraph 1).
• □ The importer’s identity and obligations have been clarified (Madde 13).
• □ Registration under Madde 31 has been completed before the notified body application, and the SRN has been retained.
• □ The ÜTS account type and reporting permissions have been checked in writing.
• □ The operative numbering rules have been reconciled against the guide of 2026-05-13 (V4.0) (practical estimate items subject to the TİTCK reply).

Regulatory information verified to 29 October 2026. The provisions listed in this article were checked against the original text on the Turkish legislative information system (MevzuatNo 38657); field definitions for items such as system accounts and numbering rules, for which no official original text was obtained, are handled as a practical estimate.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, authorised representative and local testing support for the Turkish market. Our team prepares CE/UTS-compliant documentation, and supports post-market vigilance obligations. Business enquiries: info@grzanglobal.com