🇷🇴 OasisPro · Romania e-Factura · ANAF · RO_CIUS · EU eInvoicing Gateway
Romania e-Factura.
Mandatory since 2024. Still catching foreign businesses out.
Romania e-Factura has been mandatory for all B2B transactions since July 2024 and B2C since January 2025, making Romania one of the most comprehensively mandated eInvoicing regimes in the EU. Yet two years into full enforcement, Romania e-Factura still generates a steady stream of rejected invoices, VAT deduction disputes, and penalty exposure for foreign businesses with Romanian operations. The reasons are consistent, avoidable, and explained in this guide.
Romania operates a clearance model like Italy: every invoice passes through the ANAF tax authority platform before it is legally valid.
The received XML in the SPV system is the legal invoice, not the PDF your ERP produces.
That single fact drives most of the compliance failures. This guide covers how the system works, the four mistakes foreign businesses keep making, and how any ERP connects through one gateway.
In Romania, the XML in the SPV is the legal invoice. Your ERP's PDF is not. Everything about Romania e-Factura compliance follows from that one fact.
The Romanian buyer's right to deduct VAT depends on the invoice existing in the ANAF system. A supplier who fails to submit correctly has not merely missed an administrative step. They have issued an invoice their customer cannot legally use. That is why Romanian customers escalate supplier non-compliance faster than in almost any other EU regime, and why getting the connection right matters commercially as well as legally.
How Romania e-Factura works: the ANAF clearance model
Romania e-Factura operates through the SPV (Spatiul Privat Virtual), the taxpayer portal operated by ANAF.
Invoices are generated in the RO_CIUS format, submitted to the SPV, validated by ANAF, and stamped with an official electronic seal and index number.
RO_CIUS is the Romanian Core Invoice Usage Specification, built on the European EN 16931 standard in UBL 2.1 syntax with Romanian-specific business rules layered on top.
It is closer to the pan-European formats than Italy's FatturaPA, but the Romanian business rules still require country-specific mapping from ERP data.
The Ministry of Finance e-Factura portal publishes the RO_CIUS specifications, validation rules, and system updates.
The validation rules have been updated repeatedly since launch, which is a recurring source of rejection for businesses with static integrations.
The 4 reasons foreign businesses still get Romania e-Factura wrong
Treating the PDF as the invoice
Finance teams accustomed to PDF invoicing continue sending PDFs to Romanian customers and treat SPV submission as an afterthought. In Romania the validated XML is the legal invoice. A PDF without a corresponding validated XML in the SPV leaves the customer unable to deduct VAT and the supplier exposed to penalties.
Missing the 5 working day submission window
Invoices must reach the e-Factura system within 5 working days of issue. Businesses running batch exports or manual uploads routinely breach this window during month-end peaks, holidays, and staff absence. Fines scale with taxpayer size and repeat with each late invoice.
Static integrations that fall behind validation rule updates
ANAF has updated RO_CIUS validation rules multiple times since 2024. Integrations built once and never maintained start generating rejections when rules change. Without a provider tracking Romanian updates, each ANAF change becomes an emergency IT project.
No systematic monitoring of ANAF responses
Submission is not the end of the process. ANAF validation can reject an invoice after submission, and the seal and index number confirm legal validity. Businesses that submit without monitoring responses discover rejected invoices weeks later, usually when the customer's accounts payable team refuses payment.
Romanian customers escalate supplier e-Factura failures faster than in any other EU regime, because their VAT deduction depends on your compliance.
In PDF-era invoicing, a supplier compliance failure was the supplier's problem. Under Romania e-Factura, your failure to submit a valid XML directly blocks your customer's VAT recovery. That converts a compliance issue into a commercial dispute, payment holds, and in recurring cases, supplier delisting. Getting the connection right protects the trading relationship, not just the penalty position.
Romania e-Factura compliance is not a tax team problem. It is an order-to-cash problem that determines whether your Romanian customers can pay you.
Romania e-Factura and the rest of the EU: why a per-country approach breaks down
Romania is one mandate among many.
A business trading across the EU now faces Italy SDI, Romania e-Factura, Poland KSeF, Belgium Peppol, France's reform going live in September 2026, Germany phasing in issuance obligations, and Spain's VeriFactu regime.
Each mandate has its own format, its own submission model, its own deadlines, and its own update cadence.
Building and maintaining a separate point integration for each one is the expensive path that most businesses started down and are now abandoning.
The gateway approach replaces per-country integrations with one connection. Your ERP sends invoice data once.
The gateway generates RO_CIUS for Romania, FatturaPA for Italy, the KSeF format for Poland, and the correct format for every other destination.
It then handles submission, validation responses, and mandate updates for all of them.
The OasisPro EU eInvoicing Gateway covers Romania e-Factura through the same connection as every other EU mandate.
RO_CIUS generation, SPV submission, ANAF response monitoring, the 5 working day deadline handled automatically, and validation rule updates included in the service. One connection from SAP, Oracle, Odoo, IFS Cloud, Dynamics, NetSuite, or any other ERP covers Romania and the rest of the EU at the most affordable rates in the market.
Read about the OasisPro EU eInvoicing GatewayWhat to do if your Romania e-Factura setup is manual, fragile, or failing
- Audit your rejection and late-submission history. Pull the last six months of SPV submissions. Count rejections, late submissions, and unresolved responses. Most businesses are surprised by what the data shows once someone actually looks.
- Stop relying on manual SPV uploads. Manual portal upload does not scale and does not survive staff absence. Automated submission through a gateway removes the human dependency from the 5 day window.
- Check who is tracking ANAF rule updates for you. If the answer is nobody, your next validation rule change becomes your next rejection wave. A maintained gateway makes ANAF updates the provider's job, not yours.
- Consolidate Romania into your EU-wide approach. If you are solving Romania in isolation while France, Germany, and Spain mandates land around you, you are building the per-country integration estate that the gateway model exists to replace.
Romania e-Factura handled. Along with every other EU mandate. One connection.
Talk to OasisPro about your Romanian invoicing footprint. We will review your current submission process, identify your rejection and deadline risks, and show you what one gateway connection covers across Romania and the rest of the EU.
What is Romania e-Factura?
Romania e-Factura is the mandatory national electronic invoicing system operated by ANAF, the Romanian tax authority. Invoices are generated in the RO_CIUS structured XML format, submitted through the SPV platform, validated by ANAF, and stamped with an official seal and index number. The validated XML is the legal invoice. The mandate has covered all B2B transactions since July 2024 and B2C since January 2025.
Does Romania e-Factura apply to foreign businesses?
Yes, for businesses established in Romania or registered for Romanian VAT in respect of transactions subject to Romanian invoicing rules. Foreign businesses with Romanian subsidiaries, branches, or VAT registrations should assess their position. Even where the formal obligation sits with a Romanian entity in the group, the ERP and invoicing infrastructure serving that entity must support RO_CIUS generation and SPV submission.
What format does Romania e-Factura require?
Romania requires the RO_CIUS format, the Romanian Core Invoice Usage Specification based on the European EN 16931 standard in UBL 2.1 syntax with Romanian business rules applied. Invoices are submitted as XML to the ANAF SPV platform. ANAF has updated the validation rules repeatedly since launch, so integrations must be maintained against current specifications to avoid rejections.
What are the deadlines and penalties for Romania e-Factura?
Invoices must be submitted to the e-Factura system within 5 working days of issue. Late or missing submissions attract fines scaled by taxpayer size, applied per invoice. Because the validated XML in the SPV is the legal invoice for VAT deduction, non-compliance also blocks the buyer's VAT recovery, which converts compliance failures into commercial disputes with Romanian customers.
Romania e-Factura. Fully mandatory. Fully covered by one gateway connection.
Romania was among the first EU countries to reach full B2B and B2C eInvoicing coverage, and its clearance model shows where the rest of the EU is heading under ViDA.
Businesses that connect through the OasisPro EU eInvoicing Gateway handle Romania the same way they handle every other mandate: one connection, automated submission, response monitoring, and updates included.
Talk to us about your Romanian operations.