e-Transport in WinMENTOR: getting the UIT code from an invoice or delivery note, step by step

RO e-Transport is the ANAF system through which you declare, before the vehicle leaves, road transports of high-fiscal-risk goods and international transports of goods. Each transport receives a UIT code that must accompany the goods. A missing code or wrong data is fined and, in serious cases, the value of the goods is confiscated. In WinMENTOR the declaration is generated straight from the invoice or delivery note, with no retyping. This guide follows the producer’s documentation (revision 3, 23 January 2025) and our implementation experience.

The guide describes the WinMENTOR ENTERPRISE flow, which the documentation is written for. In WinMENTOR CLASSIC the steps are the same, with minor menu differences. If you need it configured, our e-Transport implementation takes about 3 hours.

Which goods are in scope

The system applies to road transports of high-fiscal-risk goods, set by order of the ANAF president, by CN code:

Since 2024 the system also covers international transports of goods, whatever the category: imports, exports, intra-community acquisitions and supplies. The declaration is made by the Romanian company that is party to the transaction. The thresholds above which a transport becomes declarable, by value, gross weight and vehicle tonnage, are set in WinMENTOR in the constants below.

Step 1: Preparing the program

1. WinMENTOR updated. From version 24.091, communication with ANAF runs only on version 2 of the e-Transport system, and the WMDecl interface was redesigned.
2. WMDecl.exe copied from the kit next to the program executable.
3. The TR_CONFIG structures, shipped with the documentation, copied into the directory set in the export constant.
4. ANAF token. The same token serial as for e-Invoicing is used; if you already have it, nothing more to do. Alternatively, the classic electronic signature.
5. Access rights in WinMService → Administrare → Categorii de utilizatori: Acces la E-transport pe documente and Acces la detalii livrare E-transport pe documente.

Step 2: The e-Transport constants

With a local directory, the other users get the message “XML generat în altă locație… Nu poți vizualiza transmisia” when submitting.

Step 3: Items

For every item that will be declared:

• Name and international unit of measure, the same as for SAF-T;
• the Risc fiscal ridicat (high fiscal risk) tick on all products in the categories above;
• Customs code, mandatory for everything going through e-Transport;
• Mass, i.e. net weight;
• Gross weight, in the Mod depozitare form, Masa-Kg column, for every unit of measure used on documents.

If you do not know the gross weight per item, you can enter the total gross weight on the document, in the details form; the program spreads it proportionally over the lines.

Step 4: Partners

Mandatory: name, tax ID, address. Mind the country and the Stat comunitar European (EU member state) tick: Romania must not have it. A wrong tick causes validation errors when uploading to SPV. If you do not choose a carrier from the register, the XML takes your own company’s data.

Step 5: The E-Transport Details form

The eTransport button is available on: purchase invoices, import receipts, purchase delivery notes, delivery notes awaiting invoice, inter-warehouse transfers, sales invoices, sales delivery notes, dispatches to branches. On the document to declare you fill in:

1. Tip scop operațiune (purpose), from the list shown according to the partner’s country and the transaction type: domestic, intra-community acquisition or supply, import, export.
2. Detalii E-Transport: loading and unloading place types (with border crossing point and customs office where applicable), town and street (filled in automatically from the current branch or the partner’s address, to be corrected if different), the carrier, the vehicle number in capital letters and digits only, no spaces, the transport date and, optionally, the total gross weight.

A document cannot carry both positive and negative quantities if it has a purpose set; make two separate documents.

The large document views get two new columns: UIT and E-Transport, with a tick on documents that meet the declaration conditions by the thresholds in the constants. From Coloane suplimentare VIEW you can also show the UIT status.

Step 6: Obtaining the UIT code

Pressing the eTransport button generates the XML, uploads and validates it. The XML is saved in the export directory, per company and month.

Button colours:

• blue: the submitted XML has errors; correct the document, regenerate and resend;
• yellow: the UIT is in WAIT status, final validation not passed yet;
• green: filed without errors, status OK.

Important: the UIT appears after the first, structural validation, but becomes valid only at status OK, after ANAF’s second validation. There are cases where the second validation returns an error and the UIT obtained initially is not good. Press the eTransport button on the document or the status button in WMDecl until you see OK, before the goods leave.

For several documents at once: in the Listare și transmisie prin e-mail form select the documents by e-Transport status (incomplete, finalised, can be finalised), fill in the date and vehicle for all selected documents from the DataET and AutoET column headers, then press UIT in the column header. You get a success or error message per document.

Step 7: What you do after obtaining the UIT

From WMDecl you have every operation the system provides:

In WMDecl you see the environment the UIT was obtained on, the upload ID, the transport or confirmation date, the status button and the remarks field for confirmations.

Special cases

Intra-community acquisitions or imports with services included in the goods’ value (freight, insurance): select the service items in the constant Articole de tip serviciu încadrate la achiziții intracomunitare de bunuri; their value is spread over the stock items in the declaration.

Purchase delivery note in month N, receipt in month N+1: add the delivery note unposted, obtain the UIT, move the document to the next month and only then post it.

Import treated as an intra-community acquisition: the partner with the tax ID of the country of origin and an extra invoicing and delivery address in the town where customs clearance takes place; on the import invoice choose the type Import bunuri și servicii and the address with the customs town, so you can select the border crossing point.

AWB as transport document: the document extension DOC_ET, with separate remarks in OBS_ET.

Return delivery note: loading and unloading place types are filled in as for a purchase delivery note with positive quantities; at generation the program swaps them automatically.

Common errors

• Validation failed because of the partner’s country: the Stat comunitar European tick set wrongly, including on Romania.
• Vehicle number refused: contains spaces, hyphens or lowercase letters.
• Document will not save: positive and negative quantities on the same document with a purpose set.
• Other users cannot submit: the export directory is local, not on the server.
• UIT obtained, then error: ANAF’s second validation failed; do not leave with the goods until status OK.
• Vehicle cannot be declared: the previous GPS transport was not confirmed.

Checklist

• Current version, WMDecl.exe and TR_CONFIG in place
• ANAF token, the same as for e-Invoicing
• Constants: environment, export directory on the server, thresholds, default purpose
• Items with high-risk tick, customs code, international unit, net and gross weight
• Partners with the correct country, no EU tick on Romania
• Test declaration in Testare, then switch to Producție and regenerate
• The person in charge trained to watch for status OK and to confirm transports

---

Want e-Transport configured right the first time? Request a free audit: we check the items, partners and constants and make the first declaration together. See also the licence and implementation estimate in the configurator.