To change the vehicle in RO e-Transport, the transport organizer sends a vehicle change notification against the existing UIT code, and the code stays the same. This is the only change ANAF accepts after the transport has started: under art. 4 of Order 1.337/1.268/2024, every other field closes the moment the vehicle is set in motion. Before departure, the vehicle can also be changed as part of a normal correction, along with anything else.
What you can change, and when
| Moment | Vehicle | Everything else | UIT code |
|---|---|---|---|
| Before departure, inside the 3-day window | Changeable by correction | Changeable | Kept |
| After departure | Changeable by the transport organizer | Closed | Kept |
| After arrival | Closed | Closed | Kept, confirmed |
The asymmetry is deliberate. A transport in motion is a fact the tax authority can check on the road, so the goods, the weight, the value and the route are frozen — but a truck can break down, and the system has to survive that without invalidating a legitimate transport. Which movements need a declaration at all, and under which thresholds, is set out in the RO e-Transport overview.
Who sends it
The transport organizer sends the vehicle change. Not the importer, not the supplier, not the accountant who filed the original declaration — unless one of them happens to hold that role as well.
This trips up companies where the declarant and the transport organizer are different legal entities, which is the normal case for hired transport. A Romanian importer files the declaration; a Polish carrier is the transport organizer; the truck fails outside Arad on a Sunday. The importer cannot fix it from the office, however fast it reacts. The notification has to come from the carrier’s side.
Settle that before the first shipment. Who holds the transport organizer role, who has access to send lifecycle messages, and which phone number is reachable at three in the morning are the questions that decide how a breakdown ends. The role map is in the guide on who must declare in RO e-Transport.
The sequence for a breakdown
The order of operations is what protects the load.
- Secure the vehicle and the goods. Nothing is sent from the roadside before the truck is safe.
- Identify the replacement vehicle, with its plates and, where relevant, the trailer plates.
- Have the transport organizer send the vehicle change against the existing UIT code, before the goods move again.
- Confirm the message was accepted. A notification that fails validation leaves the declaration describing the broken truck.
- Tranship and continue, with the same code in the new cab.
Step 3 before step 5 is the part that gets reversed under pressure. Moving the goods first and notifying afterwards leaves a window — sometimes hours — in which the goods travel against a declaration naming a vehicle that is sitting on a hard shoulder somewhere else. A check inside that window finds a mismatch between the road and the declaration, and the fine for that is a separate exposure from the fine for no declaration at all. Both are covered in the guide on RO e-Transport fines and appeals.
The clock does not stop for a breakdown
A vehicle change does not extend the UIT code. Validity still runs 5 calendar days from the declared start date, or 15 for intra-community acquisitions and the operations named in art. 2 pt. 9 letters g) and j) of OUG 41/2022.
A two-day repair inside a five-day window is absorbed. A two-day repair on day four is not: the transport will finish outside the validity, and under art. 3 para. 18 of Order 1.337/1.268/2024 a transport not completed within the validity period is invalidated and needs a new UIT code. At that point the vehicle change is the wrong message. The right one is a fresh declaration for the remaining movement, with a new code, sent before the goods move again. The arithmetic of the two periods is in the guide on UIT code validity and deadlines.
So a breakdown asks two questions, in this order. Will the transport still finish inside the validity? If yes, change the vehicle. If no, redeclare.
A worked example: relay across two countries
A Hungarian forwarder moves 22 tonnes of steel from Budapest to a site near Brașov. Declared start date Tuesday, intra-community supply, declared by the Hungarian supplier. The forwarder is the transport organizer.
- Tuesday, 05:00. Departure on the declared tractor unit and trailer. Code issued Monday, status confirmed as accepted.
- Tuesday, 15:00. Cooling system failure near Nădlac. The truck is parked at a service area.
- Tuesday, 16:20. The forwarder arranges a replacement tractor unit, keeping the same trailer.
- Tuesday, 16:45. The forwarder, as transport organizer, sends the vehicle change with the new tractor plates against the same UIT code. Acceptance confirmed.
- Tuesday, 17:30. The trailer is coupled to the new unit and the transport continues, carrying the original code.
- Wednesday, 11:00. Delivered, inside the 5-day validity. Confirmation sent.
Had the failure happened on Saturday, with the validity ending Saturday night, the forwarder would have redeclared rather than changed the vehicle, and the site would have received goods under a second UIT code.
Where the standard advice fails
“Just send a correction.” After departure, a correction is not available. The vehicle change is a distinct message, restricted to the transport organizer, and it is the only door still open.
“We will update it when the truck arrives.” The declaration has to match the road while the goods are on it. A notification sent after delivery documents a mismatch rather than preventing one.
“The plates are close enough.” Inspectors compare the declared plates with the vehicle in front of them. A trailer swapped in a yard and never notified produces the same mismatch as a different truck.
“The driver needs a new code.” The driver needs the code that was issued at the start. A vehicle change never produces a second code — the mechanics of what does and does not produce a new code are in the guide on correcting, deleting and confirming a UIT declaration.
“Only the carrier is exposed here.” The vehicle mismatch is the transport organizer’s exposure, but the goods belong to somebody else, and confiscation of the countervalue is a sanction measured against the shipment. The declarant has an interest in the notification being sent, even though it cannot send it.
Sources: OUG 41/2022 on legislatie.just.ro; ANAF’s RO e-Transport guide (2025); technical information on mfinante.gov.ro; Order ANAF/AVR 1.337/1.268/2024, Official Gazette 597 of 27 June 2024.
Frequently asked questions
Can I change the vehicle after the transport has started?
Yes. The vehicle is the only element that can still be changed once the transport is under way. Under art. 4 of Order 1.337/1.268/2024, after the vehicle has been set in motion the transport organizer may change the vehicle, keeping the same UIT code. Every other field is closed from the moment of departure.
Who sends the vehicle change to ANAF?
The transport organizer — the party carriers usually call the transporter. It is the role ANAF holds responsible for the vehicle used in the transport, and it is the only party that may send the change after departure. The declarant who filed the original declaration cannot send it unless it is also the transport organizer for that movement.
Does changing the vehicle give me a new UIT code?
No. The UIT code stays the same. A vehicle change is a lifecycle notification against the existing code, not a new declaration. The driver of the replacement truck carries the same code the first driver had. Expecting a new 16-digit number after the change means waiting for something the system does not send.
The truck broke down. What do I do first?
Arrange the replacement vehicle, then have the transport organizer send the vehicle change with the new plates before the goods move again. The order matters: transhipping onto a truck whose plates are not on the declaration leaves the goods travelling against a declaration that describes a different vehicle, which is what a roadside check finds.
What if only the trailer changes?
Send the change with the correct plates as they will be at the check. The declaration identifies the vehicle used for the transport, and an inspector compares what is on the road with what was declared. A swapped trailer that is not reflected in the declaration produces the same mismatch as a swapped tractor unit.
Can I change the vehicle before departure instead?
Yes, and it is simpler. Before the vehicle is set in motion, and within the 3 calendar days before the declared start date, the whole declaration can be corrected while keeping the UIT code — vehicle included. The restricted, organizer-only vehicle change applies after departure, when nothing else is open any more.
How many times can the vehicle be changed on one UIT code?
The procedure does not set a limit. What matters is that the declaration matches the vehicle actually carrying the goods at any moment of the journey, so each replacement is notified as it happens. A long relay with two changes needs two notifications, each sent before the goods move on the new vehicle.
