e-Invoicing in Romania 2026: The Complete ANAF e-Factura Compliance Guide

What is RO e-Factura and why does it matter

RO e-Factura is the national electronic invoicing system operated by ANAF (the Romanian tax authority). Invoices are issued in a standardised XML format (RO_CIUS, based on EN 16931), submitted to the SPV (Spațiul Privat Virtual) platform, validated by ANAF, and then transmitted to the recipient.

The goal is to reduce the VAT gap, give ANAF real-time visibility into B2B transactions, and pre-fill future VAT returns. For businesses, it means every sales and purchase invoice now needs to pass through a validated digital channel before it counts as fiscally compliant.

Who must use e-Factura in 2026

As of 2026, electronic invoicing via RO e-Factura is mandatory for essentially all VAT-registered companies issuing B2B invoices to other Romanian taxpayers, as well as for B2G (business-to-government) transactions. Non-resident companies registered for VAT in Romania and issuing invoices to Romanian recipients also fall under the obligation.

B2C transactions (sales to individuals) follow a separate, gradually expanding timeline, but many companies choose to route all invoices through e-Factura regardless, simply to avoid maintaining two parallel processes.

Deadlines and penalties you need to track

Invoices must be uploaded to SPV within 5 working days of issuance (or of the date the obligation to issue the invoice arises). Late or missing submissions can result in fines that scale with company size, and — critically — an invoice that is not correctly reported through e-Factura can be challenged for VAT deduction purposes on the recipient side.

Because the rules and thresholds have evolved every year since 2022, the safest approach is not to memorise a static deadline table, but to use accounting software that is actively maintained for Romanian fiscal legislation, so submission rules update automatically.

Common e-Factura mistakes we see in audits

Most compliance issues are not about willful non-compliance — they come from process gaps: invoices issued outside the main accounting system (e.g. ad-hoc Excel or Word invoices), delays caused by manual XML generation, mismatches between the invoice series used internally and the one validated by ANAF, and missing reconciliation between SPV responses and the general ledger.

• Invoices created outside the primary accounting/ERP system and never uploaded to SPV
• XML files generated manually, with formatting errors rejected by ANAF validation
• No automated reconciliation between SPV acceptance/rejection messages and the ledger
• Credit notes and corrections not re-submitted through e-Factura
• VAT deduction claimed on supplier invoices that were never validated in SPV

How a connected accounting system simplifies e-Factura

The most reliable way to stay compliant is to issue invoices directly from the system that also runs your sales, inventory, and accounting — so the XML is generated automatically, in the correct format, and submitted to SPV without a separate manual step. OneConta, RBL's cloud accounting platform, is built around this principle: invoices generated in OneConta are formatted to RO_CIUS specifications and synced with SPV, with statuses (validated, rejected, errors) visible directly in the invoice record.

For companies running a full ERP (sales, warehouse, production, finance), the same logic applies at a larger scale — every module that creates an invoice (sales orders, returns, intercompany transfers) needs to feed the same compliant e-Factura pipeline, which is one of the reasons e-Factura readiness is now a standard requirement when implementing or migrating ERP WE.