Country deep dive
Romania rolled out RO e-Factura in stages โ starting as a voluntary channel, then becoming mandatory transaction type by transaction type. This is the full sequence, past and upcoming.
The platform opened for voluntary registration ahead of any legal mandate, giving early-adopting businesses and public bodies time to test integration.
Public contracting authorities in scope of Law 199/2020 (transposing EU Directive 2014/55/EU) must accept and process EN 16931-compliant structured invoices for public procurement above EU thresholds.
B2B e-reporting obligations begin for taxable persons established in Romania (and non-established VAT-registered entities), operating under the Government Ordinance 120/2021 framework and RO_CIUS technical specification (MF Order 1366/2021).
Romania runs a centralised clearance (CTC) model: B2B and B2G invoices must be validated and digitally sealed by ANAF via RO e-Factura before they carry legal effect. B2C reporting followed from January 2025.
Regular B2C invoices must also be reported via RO e-Factura in RO_CIUS XML format. Point-of-sale tax receipts and one-off individual transactions remain exempt.
The mandatory RO e-Invoice Register now also covers associations, foundations and non-profits not registered for VAT, individual farmers under the special agricultural regime, and sole traders identified by personal ID number (CNP).
Following a confirmed delay, small taxpayers with turnover below โฌ500,000 become fully subject to e-Factura enforcement and penalties, on the same footing as larger businesses.
Every invoice is a structured XML file โ there's no PDF or paper equivalent that carries legal weight once you're in scope.
CII XML is technically permitted by the EN 16931 standard, but UBL 2.1 is what ANAF's platform actually validates in practice โ use UBL unless you have a specific reason not to.
Invalid or inactive CUI/CIF tax IDs cause immediate rejection โ the system cross-references ANAF's live taxpayer database as part of validation, not just a formatting check.
Romanian-specific tax category codes are required for reverse-charge and simplified invoice scenarios โ generic EN 16931 codes alone won't pass Schematron validation.
Retain both the XML you submitted and ANAF's signed response/downloadId โ the government's digital seal (not your own signature) is what makes the invoice legally valid.
Romania runs a centralised clearance (CTC) model: nothing is legally an invoice until ANAF has validated and sealed it.
Track submission status through pending โ validated โ rejected. Build retry/backoff logic โ ANAF's infrastructure has known reliability issues during peak filing periods.
The 5-day clock starts from the tax point (chargeable event), not the date you get around to generating the XML โ automate submission immediately upon issuance rather than batching.
Buyers aren't passive recipients โ you're expected to actively retrieve invoices addressed to your CUI and can raise a compliance complaint if a supplier fails to issue correctly.
Before you can send or receive a single invoice, there's a one-time setup process with the central tax authority.
Get a qualified electronic signature certificate from an accredited Romanian provider. This is the credential ANAF uses to identify you โ budget time for this, as certificate issuance isn't instant.
Create your Spaศiul Privat Virtual (Virtual Private Space) account โ ANAF's secure taxpayer portal โ using your digital certificate to authenticate.
File Form 084 to formally activate RO e-Factura access for your CUI/CIF. This is the specific registration step that switches on e-invoicing capability within SPV.
If a third-party platform or accountant submits on your behalf, delegate certificate authority to them per entity. This is commonly the trickiest part of integration โ delegations must be configured individually and certificates expire, so track renewal dates.
Integrate via ANAF's REST API using OAuth 2.0 for machine-to-machine submission, or use the SPV web interface directly for lower volumes. Test thoroughly โ RO_CIUS validation is strict, and invalid CUI/CIF references cause instant rejection.
Poll for clearance status (pending/validated/rejected), track the 5-day submission clock per invoice, and maintain retry/backoff logic so invoices are submitted exactly once even if ANAF's endpoint is temporarily unavailable.
E-Factura doesn't sit alone โ two adjacent Romanian reporting regimes commonly trip up new entrants.