To check a UIT code, you ask ANAF what happened to the declaration behind it. The code itself tells you almost nothing. It is 16 digits with a check digit, so a mistyped code can be spotted, but a perfectly formed code can belong to a declaration ANAF rejected minutes after issuing it. The answer that matters comes from the status of the message you submitted to the RO e-Transport system.
Why a UIT code issued is not a declaration accepted
The system validates in two stages, at different moments. The first runs on upload and checks the structure of the XML file; if it passes, ANAF returns the UIT code immediately. The second checks the content rules and runs afterwards, with its result available through a separate status call.
Between submission and that status answer, a correct declaration and one that will be rejected look identical. Both have a code. The steps from form to code are set out in the guide on how to get a UIT code in Romania.
How to check a UIT code: the four possible answers
| What you see | What it means | What to do |
|---|---|---|
| UIT code issued, no status answer yet | structure passed, content is being validated | ask again in a few seconds |
| Status: accepted | the declaration is registered and live | send the code to the driver, watch the validity |
| Content errors listed | the declaration is rejected | correct and submit again |
| XML with errors, not taken over by the system | the declaration never entered the system | fix the file, submit as a new declaration |
The last row is the one that misleads. The wording sounds like an intermediate state, but it is a rejection: the message was not registered, so it cannot become accepted later. Anyone reading it as “processing” polls for days about a declaration ANAF has no record of.
There is a fifth case, less common. When a status answer contains something you do not recognise, the most expensive possible reading is to treat it as success. An unknown status means the declaration is still open. Ask again.
How often to ask, and for how long
There is no legal deadline for querying status. There is a deadline for how long the answers exist.
Sixty days is not a setting to tune. It is the window in which you still have something to reconcile your records against. Beyond it, there is nothing at ANAF left to compare, and the only proof that you declared a shipment in March is the copy you kept. Evidence gets downloaded continuously, not on the day of an inspection.
One operational detail shows up only at volume: the ANAF environment goes down occasionally, and a failed query is not a verdict. A call that errors means you do not know, not that the declaration was rejected. Retry it, and keep failed calls visibly separate from real answers.
Checking in the Virtual Private Space, and where it stops
Messages exchanged with RO e-Transport can be consulted in the Virtual Private Space, for the tax number you hold rights over. For a few transports a month, that is enough. What is needed to get there is covered in the guide on declaring in the SPV.
The method breaks at volume for three reasons. Every declaration has its own status message, so manual checking grows in step with your shipments. A check done once does not stay true, because a correction sent later has its own separate answer. And the 60-day window keeps running whether anyone looked or not.
What a status check cannot tell you
The status says whether the declaration was accepted. It does not say whether it was true.
A declaration carrying the wrong goods, the wrong operation type or the wrong partner can be accepted without objection, because the system checks the format of tax numbers rather than the reality inside the truck. Acceptance closes a procedural question, not a factual one.
That also marks the honest limit of any application, this one included. What can be guaranteed is that the message was sent, that the answer was read and stored, and that nothing was fabricated along the way. Acceptance cannot be guaranteed by anyone, and false codes are not obtainable by any route: there are two environments, test and production, and both belong to ANAF.
Official sources: ANAF’s RO e-Transport guide (2025) and the Ministry of Finance technical information page, which documents the services and their responses.
Frequently asked questions
How do I check whether a UIT code is valid?
By querying the status of the message you sent, not by inspecting the code. A UIT code is 16 digits with a check digit, so you can tell whether it was typed correctly, but a correctly formed code can belong to a rejected declaration. The only reliable answer comes from ANAF's status service for the message that carried your declaration.
What does it mean if I have the code but no accepted status?
It means you passed the first validation stage, not the second. ANAF returns the UIT code after checking the structure of the submitted file. The content rules run afterwards and can still reject the declaration. Until a final status answer arrives, the code exists but the declaration is under validation. Ask again rather than assuming either outcome.
What does XML with errors, not taken over by the system mean?
It is a rejection, not a pending state. The declaration never entered ANAF's system, so it cannot become accepted later. Treated as processing, it leads to endless polling for a declaration that does not exist. Fix the cause, then send a new declaration, which receives its own UIT code. The original attempt leaves no live code behind.
How long can I check a UIT code with ANAF?
Sixty days. Under Joint Order ANAF/AVR 1.337/1.268/2024, art. 6, ANAF keeps the responses to your messages, including the signed XML and the errors, for 60 days. After that the evidence exists only where you saved it, so download your records continuously rather than when an inspection or a dispute asks for them.
Can I check a UIT code in the Virtual Private Space?
Yes, the messages exchanged with RO e-Transport can be consulted in the Virtual Private Space for the tax number you hold rights over. Manual checking works for a handful of transports a month. It scales badly, because every declaration has its own status message, every correction has its own answer, and the 60-day window runs whether you looked or not.
