Romania's RO e-Factura mandate: what applies now
Romanian domestic B2B invoices have gone through ANAF's RO e-Factura system as structured UBL XML since 1 January 2024; B2C followed in 2025. Below: the dates, the format, and what a free local checker covers.
The timeline (domestic B2B and B2G)
| Date | What changes |
|---|---|
| 2022 | B2G invoices and a first set of high-fiscal-risk B2B goods go through RO e-Factura. |
| 1 Jan 2024 | Domestic B2B invoices between Romanian-established businesses must be issued as structured XML and uploaded to ANAF's system (the SPV portal or its API). |
| 2025 | B2C invoices are brought in; fines for B2C started after a no-sanction period. Check the exact date with ANAF. |
Invoices are generally to be uploaded within five working days of issue. Fines for late, missing or wrong uploads exist, but sources disagree on amounts and grace periods and they have been amended, so this page gives none. Exceptions and transition rules exist (some small or non-profit taxpayers were brought in later). This is a summary, not tax advice; confirm with your accountant or ANAF.
Which file counts, and how it travels
The invoice is a structured UBL 2.1 document that follows EN 16931 and Romania's national profile (RO_CIUS, also written CIUS-RO), uploaded to ANAF's SPV system, which validates it and the buyer retrieves it from there. A PDF emailed to the customer is not the invoice for domestic B2B sales.
Test a file before you send it
Open the checker and drop your XML. It flags totals and tax breakdowns that do not add up, a missing tax reason on a 0% or exempt line, malformed identifiers, and VAT, IBAN and BIC typos, each with a rule ID and a fix (the rule reference). For a UBL file that names CIUS-RO in BT-24 it also applies the 122 Romanian national rules (RO e-Factura v1.0.9: date format, invoice number, Bucharest sector and county codes, VAT currency, address and field length limits), each in English with a fix. It does not run ANAF's own validation, and no real ANAF verdict has been compared. No account, nothing uploaded.
No invoice yet? The e-invoice creator turns a form into UBL or CII XML and checks it. Other countries: Germany, France, Belgium, Poland, Croatia, Greece, Bulgaria, the UK, the UAE, India, Saudi Arabia, Italy, or the Portugal, EU e-invoicing mandate checker. Also: Slovakia, Lithuania, Luxembourg, Malta, Norway, Hungary, Denmark, Estonia, Latvia, Slovenia, Czech Republic, Serbia.
Common questions
When did Romania's B2B e-invoicing mandate start?
On 1 January 2024 domestic B2B invoices between Romanian-established businesses had to be issued as structured XML and uploaded to ANAF's RO e-Factura system. B2G came earlier and B2C was added in 2025. Confirm your own situation with your accountant or ANAF; this page is a summary, not advice.
Which invoice format does Romania require?
A structured UBL 2.1 invoice that conforms to the European standard EN 16931 and Romania's national profile (RO_CIUS), uploaded to ANAF's SPV system. A PDF or paper invoice is not the invoice for domestic B2B sales.
Can this checker validate a Romanian invoice?
Mostly. It reads UBL, CII, Factur-X and JSON and applies the EN 16931 arithmetic, tax breakdown, mandatory-field and identifier checks, plus VAT, IBAN and BIC typo catches, each with a rule ID and a fix. For UBL files that name CIUS-RO in BT-24 it also applies the 122 Romanian national rules (v1.0.9) in the browser. It does not run ANAF's own validation, so a clean result is an offline observation, not approval.
How do I check an invoice before sending it?
Drop the file into the checker. Nothing is uploaded: every check runs in your browser. Fix what it flags, then upload through your invoicing software or ANAF's SPV.
Open the E-invoice Preflight checker to validate your own invoice file.
More countries
Australia Austria Brazil Cyprus Finland Ireland Japan Malaysia Mexico Colombia Chile Peru Argentina Netherlands Nigeria Singapore Invoicenow Spain Sweden Switzerland Turkey Uruguay Paraguay Ecuador Indonesia Vietnam