What Is RO e-Factura?
RO e-Factura is Romania's national electronic invoicing system, operated by ANAF (Agenția Națională de Administrare Fiscală — the National Agency for Fiscal Administration). It is a Continuous Transaction Controls (CTC) system, meaning every invoice must be sent to ANAF's platform for clearance before it is legally valid.
The system was initially launched in November 2021 on a voluntary basis for B2G transactions. Romania obtained a Council derogation (Council Implementing Decision EU 2023/1553) in July 2023 allowing it to mandate B2B e-invoicing — making it the first EU country to obtain such a derogation under the old pre-ViDA rules.
Romania's tax authority estimated the national VAT gap at €9.6 billion in 2020 (36.7% of expected VAT revenue — the highest in the EU). The RO e-Factura mandate is a direct response to this gap, alongside the SAF-T reporting obligation (RO e-SAF-T D406) and the e-Transport goods tracking system.
Implementation Timeline
November 2021
B2G Optional Launch
ANAF launched the RO e-Factura platform for voluntary B2G e-invoicing. Suppliers could submit XML invoices and receive clearance IDs.
July 2022
B2G Mandatory
All suppliers to Romanian public administrations were required to submit invoices through RO e-Factura. Paper or PDF invoices to public entities were no longer accepted.
January 2024
B2B Mandatory — High-Risk Products
B2B e-invoicing became mandatory for specific product categories classified as 'high fiscal risk' (HRP): alcoholic beverages, tobacco, clothing, construction materials, minerals, and agricultural products. These sectors account for ~37% of Romania's domestic trade.
July 2024
B2B Mandatory — All Domestic Transactions
All B2B transactions between Romanian VAT-registered entities must go through RO e-Factura. An XML invoice must be submitted to ANAF within 5 calendar days of the tax point. ANAF returns a clearance ID (downloadId) to the supplier.
January 2025
E-Transport Integration
The e-Transport system for tracking physical goods movements was linked to RO e-Factura. Shipments of high-risk goods must have a corresponding e-Transport declaration matching the e-invoice data.
Technical Requirements
RO e-Factura uses the CIUS-RO (Core Invoice Usage Specification for Romania), an extension of EN 16931 built on UBL 2.1 XML syntax:
Invoice Format
UBL 2.1 XML conforming to CIUS-RO. Mandatory fields include CUI/CIF (Romanian tax ID), ANAF clearance ID, and invoice type code (380 for standard, 381 for credit note).
Submission API
ANAF provides a REST API at efactura.mfinante.gov.ro. Authentication via SPV (Portalul electronic) digital certificates. OAuth 2.0 for M2M communication.
5-Day Submission Window
Invoices must be submitted to ANAF within 5 calendar days of the tax point (chargeable event). Late submission triggers penalties of RON 1,000–5,000 for small/medium entities.
Clearance Response
ANAF validates the XML, assigns a unique downloadId, and returns a signed response. The buyer retrieves the cleared invoice from ANAF's platform using the downloadId.
Archive Requirement
Both supplier and buyer must archive the original XML and ANAF's clearance response for 10 years (fiscal record retention period under Romanian law).
Penalty Regime
Non-compliance penalties: RON 5,000–10,000 for large enterprises. Repeated violations may trigger tax audit priority flags in ANAF's risk management system.
E-Transport & SAF-T
Romania's digital tax transformation goes far beyond e-invoicing. ANAF has built a three-pillar digital compliance ecosystem:
RO e-Factura — Invoice Clearance
Every B2B and B2G invoice must be cleared by ANAF before it is legally valid. The cleared XML contains an ANAF digital signature and unique ID that serves as legal proof.
E-Transport — Goods Movement Tracking
Since January 2025, high-risk goods shipments require an e-Transport declaration filed before the goods leave the warehouse. The declaration must reference the corresponding e-Factura clearance ID. ANAF uses GPS-linked UIT codes for roadside verification.
RO SAF-T (D406) — Financial Data Reporting
Large taxpayers must submit monthly SAF-T declarations to ANAF in OECD XML format. SAF-T includes general ledger, accounts receivable, accounts payable, and asset register data. Medium and small enterprises were onboarded in phases through 2025.
Together, these three systems give ANAF real-time visibility into invoices, physical goods flows, and financial records — enabling automated cross-referencing that makes VAT fraud significantly harder.
Compliance Strategy
If your business sells to or buys from Romanian entities, here's what you need:
CIUS-RO Configuration
Your e-invoicing platform must generate UBL 2.1 XML conforming to the CIUS-RO extension. This includes Romanian-specific fields like CUI/CIF tax IDs, ANAF clearance references, and correct tax category codes for Romanian VAT rates (19% standard, 9% reduced, 5% super-reduced).
5-Day SLA Automation
The 5-calendar-day submission window is tight. Manual processes won't scale. You need automated ERP-to-ANAF integration that triggers invoice submission immediately upon issuance.
Buyer-Side Download
As a buyer of Romanian goods/services, you must download cleared invoices from ANAF's platform. Your system needs to poll ANAF's API regularly for new invoices addressed to your CUI.
E-Transport Coordination
If you ship high-risk goods within Romania, your logistics team must file e-Transport declarations that cross-reference e-Factura clearance IDs before shipping.
Multi-Country Platform
Romanian e-invoicing is CTC-based (like Italy, India, Malaysia). But your Belgian, German, and French invoices use Peppol or PDP models. A platform like InvoStaq handles both architectures from a single API.
Romania + 13 More Countries. One API.
From RO e-Factura CTC clearance to Peppol BIS to Italy's SDI — InvoStaq validates, transforms, and routes invoices across every European e-invoicing architecture.