Romania · RO e-Factura: e-invoice formats and rules
Use this page to choose the Romania · RO e-Factura check, identify the fixed package and follow diagnostic examples before sending an invoice to its recipient.
Formats and syntax
The Romanian implementation uses structured invoice data and national CIUS-RO requirements, rather than a PDF-only invoice. XSDHub supports UBL 2.1 Invoice and CreditNote in this country package. The Romanian Ministry of Finance technical resources describe the national syntax and artefacts, while ANAF explains using the exchange system. Other syntaxes described by a receiving system should not be mistaken for additional support in this particular XSDHub validator.
Rules XSDHub applies
The Romanian path pins ANAF EN16931/CIUS-RO artefacts 1.0.9 with the CIUS-RO:1.0.1 customization identifier. It checks UBL structure against the schema and then runs the fixed national business-rule transformation. This is separate from uploading a document into SPV and receiving the authority’s response. A locally passing result cannot confirm that an ANAF signature or download package exists, that the sender has access, or that the legal reporting deadline was met.
Who this affects
ANAF’s usage guide distinguishes B2G, where a supplier invoices a contracting authority, from B2B transactions between economic operators. Its 2026 communication describes further scope changes and reporting rules. Use those official materials to determine the position of the supplier, customer and place of supply. Domestic consumer reporting is a separate question; the B2B label on a software screen does not settle the applicability of every RO e-Factura obligation.
Common errors to investigate
- BR-RO-001: customization — Compare the customization identifier with the national profile before investigating unrelated European rules.
- BR-RO-020_1: national field rule — Follow the field-specific example in the Romanian guide and correct the producing system’s mapping.
- BR-S-08: taxable base — Reconcile VAT-category totals with their lines and adjustments instead of correcting only the final amount.
| Check | XSDHub coverage |
|---|---|
| XML structure and fixed rules | UBL 2.1 + ANAF EN16931/CIUS-RO 1.0.9; CIUS-RO:1.0.1 |
| Certification and legal acceptance | Not provided |
| Government portal submission | Not provided |
| Peppol | Not supported yet |
Working with the result
Choose the Romanian validator for a Romanian profile, preserve the exported XML and review the first failing layer. Repair missing national identifiers before chasing arithmetic symptoms in later messages. Run a fresh export through the same pinned package after correction. The examples link to existing explanations, without claiming to rank the errors of real Romanian users. Continue separately with official ANAF transmission, download and evidence-retention procedures.