Romania e-Factura: Rules, Penalties, and the Lessons for Your Next Mandate
Romania's e-invoicing mandate has been live since July 2024 — the cleared XML is the legal invoice. Here is how RO e-Factura works, what changed in 2026, and what two years of operation teach every team facing its next country.
4 min read
Romania is not a future e-invoicing mandate — it is the live one. Domestic B2B invoices have had to clear the national RO e-Factura platform since July 2024, and since then the XML sitting in the government system is the legal invoice; the PDF in your inbox is just a picture of it. That makes Romania useful in two ways: as an onboarding checklist for anyone entering the market now, and as a preview of what “operating a mandate” feels like for everyone whose next country — like the UAE, going live in January 2027 — is still ahead.
How Romania got here
When | What became mandatory |
|---|---|
Nov 2021 | Platform launches (voluntary B2G and B2B) |
Jul 2022 | B2G — suppliers to public institutions |
Jan 2024 | B2B reporting phase (submission alongside existing invoicing) |
Jul 2024 | B2B clearance — the cleared XML is the legal invoice |
Jan 2025 | B2C reporting |
2026 | Tightened deadlines, SME enforcement, B2C scope corrections (below) |
How RO e-Factura actually works
Unlike the Peppol-based models other countries are adopting, Romania runs centralized clearance: every in-scope invoice is submitted as RO_CIUS XML (a national profile of UBL 2.1 / EN 16931) directly to the tax authority ANAF through the SPV portal (“Virtual Private Space”) or its API. ANAF validates the file and stamps it with an index number — that stamped XML is the invoice. There is no accredited-service-provider layer and no exchange network between the parties: both supplier and buyer deal with the government platform.
The operational consequences: you need SPV access before anything else (registration plus Form 084, with a qualified certificate — for foreign businesses this alone can take weeks); your ERP output has to map to RO_CIUS field by field; and your accounts-payable side must actively fetch incoming invoices from the platform — recipients retrieve them from the SPV, and after roughly 60 days they are no longer available for download. An AP process that waits for emailed PDFs is structurally broken in Romania.
What changed in 2026
Since 1 January 2026, the submission deadline is five working days from issuance (previously counted in calendar days). From 1 July 2026, enforcement fully covers small businesses under the €500,000 turnover threshold, and the B2C reporting duty was narrowed: invoices to private individuals not identified by a tax number generally no longer need to be reported, with corrections introduced by Law 88/2026. The secondary sources disagree on that law's exact scope — treat it as a flag for your Romanian tax adviser, not as settled fact from a blog (including this one).
The penalty profile — and why AP is the exposed side
Issuing a B2B invoice outside the system carries a penalty that scales with the invoice itself — widely reported at 15% of the invoice value, and it can hit both parties: the issuer for bypassing clearance, and a buyer who books an invoice that never went through the system. On top of that, a buyer who records an out-of-system invoice risks losing the VAT deduction on it, and late transmission draws tiered fixed fines (reported in the low thousands of RON, scaled by taxpayer size — the exact bands vary between sources). The pattern worth internalizing: in a clearance regime, your purchasing organization is as exposed as your billing organization. Vendor onboarding, three-way match and VAT recovery all inherit a new dependency on the government platform.
Two project shapes, not one
Entering Romania now? The onboarding project looks like the classic mandate rollout, compressed: SPV registration and certificates on the critical path (start immediately — it is the long pole for foreign entities), RO_CIUS mapping and gap analysis against your ERP's invoice data, the outbound interface, the inbound retrieval process for AP, counterparty testing, cutover. Budget real time for master data: Romanian tax IDs are validated against ANAF's live register, and inactive or mistyped IDs reject the whole invoice.
Already live? Then Romania is your best lesson in what the steady state costs: a mandate is never “done”. The 2026 changes — deadline arithmetic, SME scope, B2C corrections — each forced a regression pass through configurations that had been stable for a year. The teams that absorb this calmly have one thing in common: a named owner who watches ANAF publications and legal amendments, and a standing, repeatable way to turn each change into scoped work instead of a scramble.
Carrying the lessons to the next country
If Romania is one line in a multi-country compliance program, its real value is the template it leaves behind: the workstream structure, the master-data checks, the AP-side process, the testing approach — all reusable, even where the technical model differs (Romania's centralized clearance versus the decentralized, provider-based model the UAE mandate uses). That is exactly how we run it in Casperry: each country is a project with its own milestones, the rollout itself is a Studio blueprint cloned from the last country and adjusted for this one, incoming questions and change requests land as requests, and production incidents during hypercare are tracked as events linked to the project. Country two should never start from a blank page.
Last updated 25 October 2026. This article summarizes publicly available information about Romania's RO e-Factura regime and is not tax or legal advice. Rules, deadlines and penalty levels change and some details above are reported differently across sources; verify against ANAF publications and the underlying legal texts (including GEO 89/2025 and Law 88/2026) or with a Romanian tax adviser before acting.