RO e-Transport: repair operation and partner country

Identify which country the error describes

A transport document can mention the commercial partner, the transport organiser and the physical route. These are different roles. ETR-OP-COUNTRY refers specifically to partenerComercial/@codTara in relation to notificare/@codTipOperatiune. Changing the organiser country cannot repair that comparison. A carrier based in another country also does not automatically make the commercial partner foreign.

The fictional error pairs operation 30 with partner country DE. It is reported at line 5, at /p:eTransport[1]/p:notificare[1]/p:partenerComercial[1]/@codTara. Our passing teaching example uses RO for that partner. Establish the intended operation and the actual commercial role from the source workflow before changing either attribute. The tool cannot decide the transaction’s legal classification for the operator.

Compare the operation category deliberately

The published v2 structure distinguishes domestic, intra-EU and external-EU categories. Our independent comparison expects RO for operation 30. Operations 40 and 50 are compared with countries outside the EU. The other supported codes, 10, 12, 14, 20, 22, 24, 60 and 70, are compared with EU countries excluding Romania. These conditions are technical relationships within the selected message profile, not a statement that a particular shipment must be reported.

Country input needs an uppercase two-letter shape. The local EU comparison is independently maintained; no official country-list file is included. Greece’s GR and the documented EL representation are treated consistently for this category comparison. Country existence, historical membership at another effective date and the full official code list are outside the preflight. An unfamiliar code must therefore be investigated even if its letters have the expected shape.

Check the route and identifier role next

The route start and route end each need one representation: a border point, a customs office or a local address. Selecting two simultaneously creates an ambiguous endpoint. A local address needs county, locality and street content. The independent checks also compare border and customs representations with the operation and direction; for example, a domestic operation cannot use a border-point endpoint in this preflight.

The existence of an address or border code is never inferred from its presence. Review the route against the intended loading and unloading records. A missing street is a repairable export problem, while whether that address is geographically correct needs separate evidence. The validator does not query a map, track a vehicle or connect to a government register.

Romanian identifiers are checked as CUI values only where the shape makes that appropriate. The digit checksum cannot prove registration or ownership. Thirteen-digit identifiers and the PF marker are left for separate CNP/NIF/applicability review. The report records that condition rather than interpreting every Romanian identifier as the same kind of tax number. Foreign identifier rules remain unchecked.

Regenerate without changing unrelated data

Find the field mapping responsible for the partner country and compare it with the selected operation in your ERP. Preserve the organiser and vehicle data unless those values are independently wrong. Generate a fresh fictional export after correcting the mapping, then run the preflight again. For a batch, each readable file receives its own outcome so a malformed neighbour does not hide a country error.

Timing has its own plausibility status. Supply a reference date to compare the transport start, and optionally a future window chosen for your workflow. No statutory number of days is hard-coded. Post-outage declarations bypass the ordinary comparison and require review. Even when the country, route and date comparisons have no findings, the result remains incomplete: no UIT was issued or confirmed and legal applicability has not been established.

Primary basis and scope

MF technical publication links the v2 XSD dated 26 January 2023, Schematron v2.0.2 and v2 structure workbook. These primary sources were rechecked on 6 November 2026. The examples, diagnostic wording and partial checks here are independently written; no protected schema or assertion code is republished.

No explicit artifact licence has been established for the MF files. ANAF site conditions do not provide a blanket grant for all Ministry artifacts. Local BYO therefore requires sufficient concrete rights for the specific schema, each import and any supplied rule file. Public availability is not permission. This release bundles no official XSD, Schematron or external code-list pack.

The validator is a technical aid for Romanian transport flows, distinct from UBL DespatchAdvice and RO e-Factura. It cannot issue or confirm UIT, approve transport, determine legal applicability, connect SPV/OAuth or submit XML to ANAF. The official service and the operator’s own applicability decisions remain separate.