
ÜTS Application Rejection and Objection: Reasons and Solutions
Why is an ÜTS application rejected? Barcode and document mismatch, Turkish product name, product images, signature verification, the class and document business rule; objection and reapplication.
Your application came back from ÜTS with a negative decision, and all you have is a single sentence of reasoning. The first reflex is to correct the same record and send it again; yet the Manual defines a separate route that has to be used before reapplying, and that route has its own formal requirements. A request that does not meet the requirement is not assessed at all.
This page separates two questions: under which provisions an application ends negatively, and what is done after a negative decision. We give the reasons for rejection not by guesswork but through the paragraphs of the Manual that make something mandatory or state expressly that the application will end negatively. We give no estimate of frequency, rate or duration; the source contains none.
The source is the Manual on Registration Procedures of Medical Devices in the Product Tracking System (Tıbbi Cihazların Ürün Takip Sistemine Kayıt Süreçlerine İlişkin Kılavuz). The device and document registration flow itself is a separate subject; here only the points where the decision comes out negative are covered.
A negative decision in ÜTS is not of one kind
In everyday speech the word "rejection" is used to cover every negative outcome, but the Manual distinguishes three different outcomes. Article 39(16) of the Manual, when defining a negative decision given by the Agency on one or more of the notifications in a document application, says in parentheses "any 'Rejection' ('Ret') or 'Revision' ('Revizyon') decision". Paragraph 17 of the same article regulates a third outcome, the giving of a 3-day update period ("Request Update", "Güncelleme İste"), under a separate heading. Article 40(9) of the Manual repeats the same dual definition for device applications.
This distinction matters in practice, because the path to follow differs in each of the three: in a rejection or revision decision, reapplication comes into play, whereas in the update period the action is taken on the existing application. Read the name of the decision correctly before taking the action that suits the decision that came.
There is a fourth outcome, and it is not even counted as a decision: the application not being examined at all. Article 39(14) of the Manual says that applications that do not reach "Under Review" ("İncelemede") status cannot be assessed by the Agency's review expert; Article 40(5)(g) and Article 40(6)(ç) of the Manual repeat the same sentence for device applications. An application that has not been signed or whose fee has not been paid has not been rejected; it has not been made.
A barcode that is not identical to the technical document has a direct consequence
The most frequently repeated sanction provision of the Manual is in the barcode field, and it is written separately for each regulatory scope.
On the MDR side, sub-point (3) of Article 27(2)(b) of the Manual says that the barcode assigned to the device under standards such as GS1, HIBCC, ICCBBA or IFA must be entered into ÜTS exactly as it is, without any change. Sub-point (4) of the same point ties the consequence: for a device record whose barcode is not entered into ÜTS as it appears in the technical documents (label/sales packaging, EU declaration of conformity, EU certificate and similar), the device application made under Article 40 of the Manual ends negatively.
The same sanction exists in other scopes. Sub-point (4) of Article 25(2)(b) of the Manual brings the same result for the primary product number of devices under the old regulations, and sub-point (4) of point (ç) of the same paragraph for the secondary product number. Sub-point (4) of Article 28(4)(b) of the Manual sets up the same provision for the system and procedure pack record under the MDR, sub-point (4) of Article 29(10)(b) for the custom-made medical device record, and sub-point (4) of Article 30(2)(b) for the device record under the IVDR.
In practice, what trips people up on this article is usually not bad faith but form: dropping a leading zero, adding a space, removing a separator character, or entering the sales packaging barcode in place of the unit packaging barcode. Sub-point (5) of Article 27(2)(b) of the Manual also says that the format of the UDI-DI number must comply with the barcode assignment rules set by the organisation that assigned it; the consistency between the barcode and the reference number is also checked.
If the product name is not in Turkish and does not match the label, the application is rejected
The second area with many rejections is the product name, and here the Manual uses the verb "is rejected" directly. Sub-point (5) of Article 27(2)(f) of the Manual says that the specific expressions identifying the device in the product name or trade name will be written in Turkish in a way that a unique user can distinguish them; that, although on the label of devices of foreign manufacturers the name may be given in a foreign language or in several languages, the name must be entered in Turkish in this section. Sub-point (6) of the same point writes the consequence: the application for a device whose product name or trade name does not state what the device is, from which it cannot be understood what the device is, which is incomplete, which is not in Turkish, or which is not entered into the system so as to match what is shown on the label, is rejected.
The same provision is repeated in other scopes: sub-point (4) of Article 25(2)(e) of the Manual, Article 28(4)(f) of the Manual, Article 29(10)(d) of the Manual and Article 30(2)(f) of the Manual bring the same result.
The Manual defines some flexibility here, and not knowing it leads to unnecessary translation. Sub-point (7) of Article 27(2)(f) of the Manual says that the product name may consist of specialised terms accepted internationally, and that in that case whether the name is in Turkish will not be taken into account; sub-point (8) says that, for devices intended for professional use, the name may consist of symbols and abbreviations accepted internationally or scientifically; and sub-point (9) says that the branded, commercialised or registered parts of the trade names of devices cannot be translated into Turkish, so whether these parts are in Turkish will not be taken into account. That is, you are not expected to translate the brand; you are expected to write in Turkish the part that describes what the device is.
Product images are checked more strictly than expected
The image field is, by its nature, one that is assumed to be "done once uploaded" but has an express sanction. Sub-point (8) of Article 27(6)(a) of the Manual says that the product image will be uploaded with the extension jpeg, jpg, pdf or png, not exceeding the maximum file size stated in ÜTS, and that the application will end negatively if images that are unclear or unreadable are uploaded. The same provision is repeated in sub-point (8) of Article 25(6)(a) of the Manual, in Article 28(9)(a) of the Manual, in sub-point (4) of Article 29(14)(a) of the Manual and in sub-point (8) of Article 30(6)(a) of the Manual.
The content rules are tied to the same point. Sub-point (3) of Article 27(6)(a) of the Manual says that only photographs and technical drawings of the relevant device will be uploaded to this field, and that images of other devices will never be uploaded, even if they belong to similar devices; sub-point (4) says that the catalogue itself, or an image containing more than one device that makes the device hard to understand, will not be uploaded; sub-point (5) says that an image of the package or packaging alone is not sufficient and that a photograph or technical drawing of the device must also be uploaded. Sub-point (7) of the same point says that at most 10 images can be uploaded to this field, and sub-point (9) says that file names must be given in a way that describes the device and the image, and that commercial extensions and expressions such as "WhatsApp" must not appear in image names.
This last one is often skipped because it does not sound convincing when heard as a reason for rejection. Do not upload an image that came from a phone as it is; change the file name.
On the document side, rejection mostly comes from signature verification
The harshest provision in document notifications concerns electronic signature verification, and here the Manual says "is not accepted". Sub-point (1) of Article 8(1)(c) of the Manual makes it mandatory, so that the e-signature of an e-apostilled document can be verified, to upload to ÜTS the original of the document issued digitally by the issuing authority or downloaded from that authority's website; sub-point (2) requires that the e-signature of the authority that carried out the apostille procedure can be validly verified; and sub-point (3) says that e-apostille-certified documents whose e-signature cannot be verified because the original was not uploaded or for other reasons, and documents with an invalid e-signature, will not be accepted.
Article 8(1)(ç) of the same article sets up the same structure for certificates issued and signed electronically by the notified body: sub-point (1) makes uploading the original to ÜTS mandatory, sub-point (2) requires that the e-signature of the notified body official who electronically signed the certificate can be verified, and sub-point (3) says that documents with an e-signature that cannot be verified or is invalid will not be accepted.
The most common mistake here comes from a technical habit: uploading a screenshot of an e-signed pdf, or a printed and scanned version of it. This breaks the signature; the document looks the same visually but cannot be verified, and it is not accepted.
Who the signatory is and whether the name in the document matches is a separate reason for rejection
In e-signed document applications of domestic manufacturer firms, the owner of the signature is also checked. Sub-point (1) of Article 13(1)(ç) of the Manual says that an e-signed document is checked automatically by the system and that ÜTS allows a document application only if the document is electronically signed by the firm's "Responsible Manager" ("Mesul Müdür") or "Signatory" ("İmza Yetkilisi"). Sub-point (2) of the same point makes it mandatory that, if the name and surname of the signing official are written in the document itself, this name matches the name and surname of the registered official who electronically signed the document. Article 16(1)(ç) of the Manual and Article 9(2)(a) of the Manual repeat the same requirement for the system and procedure pack declaration and for the certificate undertaking.
There is also a general accuracy requirement concerning the content of the document. Article 19(4) of the Manual makes it mandatory that all the information in the intended purpose form or declaration is correct and valid; Article 19(2)(d) of the same article says that the document will be uploaded without any change made to it and with a wet signature or an e-signature.
A mismatch between class and document business rule blocks the record from the start
Some reasons for rejection arise not at the time of application but on the registration screen. Sub-point (1) of Article 27(5)(a) of the Manual says that selecting the document field in ÜTS is a mandatory field; sub-point (2) says that the documents to be added, according to the appropriate one of the document business rules in Article 66 of the Manual in line with the risk class of the device, will be selected from among the documents in registered status in ÜTS as a result of the application made under Article 39; and sub-point (3) makes it mandatory that the class of the device has been selected on the registration screen before the document selection.
Sub-point (3) of Article 27(5)(c) of the Manual makes it mandatory to select, from the document field, the documents relating to the relevant device and Basic UDI-DI before selecting the Basic UDI-DI. Sub-point (5) of the same point makes it mandatory that the Basic UDI-DI information of the device is present in EU certificates of the types "EU Technical Documentation Certificate", "EU Type-Examination Certificate" and "EU Product Verification Certificate", and sub-point (6) makes it mandatory that the Basic UDI-DI information is present in the device's EU declaration of conformity. If the Basic UDI-DI is not in the document, the problem is not in ÜTS but in the document.
The invalidation of documents by a class change is also regulated. Article 43(11) of the Manual says that, if as a result of updating the "Class" data field the documents linked to the device records become inconsistent with the device class, revision data will be given to the devices with the relevant barcode.
A rejection that comes after a positive decision: certificate query
It is wrong to assume that the process has ended because the document reached "Registered" status. Article 39(18) of the Manual says that, where an application contains document notifications of the types mentioned in Articles 6 and 7 of the Manual and the assessment ends positively, the validity and currency of the certificates that have reached registered status will be queried by the Agency through the notified body that issued the certificate or the competent authority that authorised that body.
The query has two outcomes. Point (a) of the same paragraph says that a 45-day revision procedure will be applied to certificates found not to be current, and that, as an exception, only for EU certificates under the MDR and IVDR, and only for certificates revised because of an extension of product scope, a 120-day extension procedure will be applied instead of the 45-day revision. Point (b) of the same paragraph says that a direct rejection procedure will be applied to certificates found to be invalid for reasons other than having lapsed, and that, for documents found to be forged or tampered with, a market surveillance and inspection process will also be started after the rejection. Both points add that these procedures will be carried out for all certificates registered in ÜTS with the same document number that are not current.
This means: when a certificate lapses, what is affected is not only that application but all records tied to that document number.
Transition period and free sale certificate applications have their own reasons for rejection
Transition period applications carry a separate set of sanctions. Article 46(15) of the Manual says that attaching the text of an agreement with the notified body or audit plans to the application in place of the document mentioned in paragraph 6 of the same article will not be accepted. Paragraph 16 of the same article says that the application will end negatively if it is made contrary to the provisions of the article, if the requested evidence documents are attached incomplete or wrong, or if documents different from those requested are attached. Paragraph 17 says that the application will end negatively if the evidence documents attached to the application are not confirmed by the manufacturer or the notified body, or if the relevant party notifies that the document is not current or valid; and paragraph 18 says that a transition period request can be made for only a single document in an application, and that if there is more than one document in the petition, the application will not be taken into assessment and will end negatively.
The sequence requirement is also a reason for rejection. Article 47(2)(a) of the Manual makes it mandatory, for an MDR transition period to be defined for custom-made medical devices, that an application is made in EBS under Article 46 of the Manual before applying in ÜTS and that the Agency permits the extension; it writes that, if this is not done, the ÜTS application will be rejected. On the IVDR side, Article 50(2)(a) and Article 50(3)(a) of the Manual set up the same order and say that a document registration or update application made without an EBS application will be rejected. Article 49(7) of the Manual says that applications made to the Agency within this scope without a petition will not be accepted.
In free sale certificate applications, rejection arises from the status of the device. Article 42(2)(ı) of the Manual says that all devices in the file must be in "Registered" status in ÜTS and that, if devices in "Rejected" ("Reddedildi") or "Unique Product Exists in the System" ("Sistemde Tekil Ürün Var") status are included in the application, the application will be rejected by the Agency. Sub-point (3) of Article 42(3)(ç) of the Manual repeats the same rule for devices of manufacturers whose EU authorised representative is established in Turkey.
The objection route: the "Submit Request" screen and the citation requirement
If you have received a negative decision and think the decision is contrary to the legislation, the Manual defines a separate route before reapplication. Article 39(16) of the Manual sets up this route for document applications: before reapplying for the relevant notification or notifications, the firm can request re-evaluation of the decision by using the "Submit Request" ("Talep Bildir") screen in ÜTS, selecting "Medical Device Document and Product Registration Procedures" ("Tıbbi Cihaz Belge ve Ürün Kayıt İşlemleri") as the "Request Area" and entering the relevant Document Application Number in the "Medical Device/Document Application Number" ("Tıbbi Cihaz/Belge Başvuru Numarası") field. The same paragraph states expressly that the purpose is to have the decision corrected, without a reapplication, for an application that was assessed wrongly.
The request has two formal requirements, and both are strict. The same paragraph requires that the request cite the legislation and the provisions of the Manual relating to the matter objected to, and says that requests in which the application number is not entered and requests that do not cite will not be taken into assessment. The same paragraph also says that the Agency will not be held responsible for applications that are sent for review by reapplying, without correction through the request.
Article 39(17) of the Manual sets up the same route for the 3-day update period decision, and Article 40(9) of the Manual for device applications. On the device side, the Device Application Number is entered in the "Medical Device/Document Application Number" field; the formal requirements and the consequence of not being taken into assessment are the same.
The practical rule that follows is this: the sentence "we find the decision wrong" is not in itself a request. If you have not written in the request which article, which paragraph and which point was violated, the request will not be read at all.
How to choose between correcting and reapplying and objecting
The Manual leaves both routes open but ties a consequence to the choice between them. The last sentence of Article 39(16) of the Manual says that the Agency will not be held responsible for applications sent for review by reapplying without correction through the request. So where the error really is yours, the right move is to correct the record and reapply; where you think the decision is wrong, the request route has to be used first.
In practice, the distinction is made like this: if the reason rests on a provision that the Manual expressly ties to a consequence, correct it without objecting. A barcode that does not match the technical document, a product name that is not in Turkish, an unreadable image, a document whose e-signature cannot be verified and a certificate without a Basic UDI-DI are reasons of this kind; all of them are given above with their articles. If the reason does not rest on such a provision, write exactly this in your objection request: which provision was applied and why that provision does not fit this record.
When reapplying, do not forget the structural limits of an application either. Article 39(15) of the Manual says that a document application will contain at most 5 document notifications; Article 40(5)(ğ) of the Manual says that device applications will contain at most 500 notifications, and Article 40(6)(d) that custom-made medical device and system and procedure pack applications will contain at most 5 notifications. Paragraph 7 of the same article says that, under the old regulations, an application can be made only for devices linked to the same GMDN code, and paragraph 8 says that, under the new regulations (except custom-made medical devices), an application can be made only for devices linked to the same Basic UDI-DI code. Correcting the rejected items and putting them all into one big application is the easiest way to a second negative outcome.
A negative decision is also possible on the firm registration side
Rejection does not occur only on the product and document side. Article 5(4) of the Manual says that, where a firm registration application of the general partnership firm type ends with a negative decision, the physical application documents sent to the Agency will be returned to the applicant firm with a cover letter, while the originals of the physical documents of firms whose registration ends positively are not returned but kept in the Agency's archive.
Data correction requests can also be rejected. Article 43(10) of the Manual says that, if the imported product data change request is not found appropriate as a result of the Agency's assessment, the request will be rejected with its reasons and will move to "Rejected" ("Reddedildi") status in ÜTS. Paragraph 9 of the same article says that requests found appropriate move to "Accepted" ("Kabul Edildi") status and that the change is corrected automatically in all device records of the relevant firms.
What we do after a rejection, and what we cannot do
Within medical device ÜTS registration consultancy, our concrete output after a negative decision is this:
Reason breakdown: We determine whether the decision that arrived is a "Rejection", a "Revision" under Article 39(16) of the Manual, or an update period under paragraph 17, and write the path for each separately.
Provision mapping: We tie the reason to the paragraph that has an express sanction in the Manual; for the barcode, Article 27(2)(b); for the product name, point (f) of the same paragraph; for the image, Article 27(6)(a); we show the counterparts one by one.
Pre-check list: Before a new application, we compare the barcode, product name, image, document set, class and Basic UDI-DI fields against the mandatory provisions of the relevant articles.
Objection text: We prepare the "Submit Request" in the form required by Article 39(16) and (17) and Article 40(9) of the Manual, with the application number and the article citations.
Certificate monitoring: Under Article 39(18) of the Manual, we follow the currency of your registered certificates and work out in advance which records revision and extension procedures will affect.
Application splitting plan: We divide the reapplication into groups according to the limits on the number of notifications and on code integrity in Article 39(15) and Article 40(5) and (6) of the Manual.
What we cannot do is also clear. We do not promise that a decision will change; Article 39(14) of the Manual leaves the assessment to the Agency's review expert, and the Manual contains no guarantee as to the outcome of the request. Nor do we say how long an objection will take to conclude; there is no such period in the source. We do not close a gap in a document by producing a document: the certificate is issued by the notified body and the declaration of conformity by the manufacturer, and the Basic UDI-DI information required in sub-points (5) and (6) of Article 27(5)(c) of the Manual can be added to the document only by the issuing party. There is also no way to make a rejected certificate valid again from inside ÜTS.
The way of working is as follows: the firm defines a user authorisation for us from its own ÜTS firm page, we prepare the corrected records and the request text with the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") authorisation, and the person who electronically signs the reapplication remains the firm's signatory.
