Romania RO e-Transport for SAP: UIT and GPS Guide

Romania’s RO e-Transport system, run by ANAF, monitors road freight in near real time: qualifying transports must be declared before the goods move, and each declaration receives a UIT code that travels with the shipment. For SAP teams, the obligation affects logistics data, shipment controls, XML/reporting workflow, and the ability to trace each transport notification back to source documents.

Compliance Summary

Area	Status (as of July 2026)
Mandate	Romania RO e-Transport
Authority	ANAF (National Agency for Fiscal Administration)
Scope	Domestic transports of high-fiscal-risk goods (per Order 802/2022) and all international transports (imports, exports, intra-Community) regardless of goods type — when the vehicle is at least 2.5 t and the load exceeds 500 kg or RON 10,000
Core requirement	Declare within the statutory window and obtain the UIT code. The code must be held and presented, physically or electronically, together with the document accompanying the goods; it is not itself the transport document
Enforcement	Offences and sanctions differ by duty and responsible party. Under the consolidated ordinance, fines for legal persons can range from RON 20,000 to 100,000 for specified offences; separate driver fines and potential confiscation rules also apply
Primary SAP impact	Logistics documents, business partner data, goods characteristics, route/location data, XML generation, and reporting status monitoring

What Is RO e-Transport?

RO e-Transport is Romania’s road freight monitoring layer, complementing RO e-Factura and Romania SAF-T: e-Factura sees the invoice, e-Transport sees the goods moving. Businesses in scope declare the shipment (parties, goods, weights, values, vehicle, route) before transport starts; the platform validates the declaration and returns the UIT code. The UIT is valid for a limited period around the declared transport, so late trucks and rescheduled shipments are compliance events, not just logistics ones.

Key Data Required for Reporting

Data group	Typical SAP source
Sender and recipient details	Customer/vendor master data, partner functions, tax identifiers
Goods characteristics	Material master, delivery item, quantity, weight, tariff classification, value
Transport details	Delivery, shipment, route, carrier, vehicle registration, loading/unloading location
Reporting payload	Mapped XML based on ANAF requirements
UIT status	Response handling, validity window monitoring, and operational follow-up

UIT Timing, Validity, GPS and Exceptions

• Declaration window: data may be declared up to three calendar days before the declared start date, but no later than the applicable border-entry, import or vehicle-movement event.
• Validity: a UIT code is generally valid for five calendar days, or 15 calendar days for intra-Community acquisitions and specified transit/non-transfer cases. Use after expiry is prohibited.
• Vehicle changes: vehicle identification must be updated within the UIT validity period when it changes, before the vehicle moves again.
• GPS: the road carrier must transfer current vehicle-position data throughout the monitored route. The driver starts the positioning device before the Romanian leg and stops it only after declared delivery or exit.
• System outage: specified declaration/update duties are suspended during an officially published outage and must be completed by the end of the next working day after restoration.
• Exceptions: defined categories include certain diplomatic, defence/security, EMCS excise and postal-parcel transports; facts must be checked against the current consolidated text.

Business Impact for SAP Finance and Logistics Teams

• Transport cannot be treated as only a logistics task: the declaration depends on accurate commercial, goods, and movement data before the truck leaves.
• UIT code tracking is operational: the code must reach the carrier by the applicable statutory event and be presented with the document accompanying the goods, and its validity window must match reality.
• Master data gaps create fine risk: missing tax identifiers, tariff classifications, weights, or location details surface at roadside checks, not in month-end reports.
• Exception handling needs ownership: rejected submissions or changed shipments should be routed back to the correct SAP process owner in time to re-declare.

SAP Readiness Checklist

1. Confirm which transport scenarios are in scope: high-fiscal-risk goods domestically, and all international flows above the thresholds.
2. Map the SAP source documents used for deliveries, shipments, and goods movement.
3. Review master data completeness for business partners, materials, carriers, and locations.
4. Define XML payload mapping and validation checks, including weight/value threshold logic.
5. Confirm how UIT codes, validity windows, and reporting errors will be stored and monitored in SAP-aligned workflows.

Primary Source and Verification

Verified on: 10 July 2026. Check the consolidated ordinance, current implementing procedure, threshold order and ANAF technical documentation for the specific transport.

• Romania Legislative Portal — consolidated Emergency Ordinance 41/2022