Compliance · Country Mandates
Romania RO e-Factura: Scope, Deadlines and CNP Rules
Sources checked: 15 November 2026. Romanian e-Factura obligations depend on taxpayer status, transaction, invoice type and statutory exceptions. Check the current consolidated law and ANAF procedure for the specific case.
What RO e-Factura covers
RO e-Factura is Romania’s national system for transmitting structured invoices. The rules have expanded in stages across B2B, B2G and domestic B2C situations; “every invoice must be submitted” is not an accurate scope test. Confirm where the supply takes place, the parties’ status, the document type and any statutory exception. The consolidated OUG 120/2021 includes a domestic B2C transmission obligation from 1 January 2025, with statutory exceptions such as qualifying fiscal receipts.
Transmission deadline from 1 January 2026
For invoices covered by the system, Article 10(7) sets a deadline of five working days from the invoice’s issue date, but no later than five working days from the legal deadline for issuing that invoice. The consolidated law refers to the working-day calculation rules in Regulation (EEC, Euratom) No 1182/71. Confirm both the transaction’s scope and the date calculation before relying on a due date.
Current rule for providers identified by CNP
As amended from 1 June 2026, Article 10^10 of OUG 120/2021 says that providers who identify fiscally by their personal numeric code (CNP) are not required to meet the specific system obligations listed there. They may opt into RO e-Factura; if they do, they must join the optional register, with registration taking effect from the first day of the following month. This is a rule for that defined identification category. Do not assume it applies to every individual, sole trader or transaction without checking the person’s fiscal status and the current ANAF procedure.
What a compliant workflow involves
- Determine whether the supplier, customer, transaction and document fall within the current statutory scope.
- Use the current ANAF technical specifications and schemas. Generic UBL 2.1 is not automatically a valid RO e-Factura payload.
- Apply the five-working-day deadline only after confirming the applicable issuance rule and calculation.
- Use the official system’s authentication, submission, validation, retrieval and response workflow.
- Retain the structured invoice and system response, and check current correction and exception procedures.
InvoiceConvertor does not generate CIUS-RO files, validate invoices against ANAF rules or submit invoices to ANAF. A generic UBL or CII export is not an RO e-Factura invoice.
Official sources
- Consolidated OUG 120/2021 (Portal Legislativ)
- Law 88/2026 (Portal Legislativ)
- OUG 89/2025 (ANAF-hosted official text)
- ANAF notice on the five-working-day transmission deadline
- ANAF RO e-Factura portal and technical resources
Frequently asked questions
What is the RO e-Factura transmission deadline in 2026?
For covered invoices, the deadline is five working days from issue, but no later than five working days from the legal invoice-issuance deadline. Verify the transaction’s scope and calculate the days under the applicable statutory rules.
Are providers identified by CNP required to use RO e-Factura?
Under Article 10^10 of OUG 120/2021, as amended from 1 June 2026, providers who identify fiscally by CNP are not required to meet the specific obligations listed there. They may opt in and must register in the optional register if they do. Check current ANAF procedures and the person’s exact status.
Does a generic UBL invoice meet RO e-Factura requirements?
No. A generic UBL or CII export is not automatically a valid CIUS-RO payload. Use the current ANAF technical specification and validation process.