What is RO e-Factura and when does it apply?
RO e-Factura is Romania’s national system for transmitting, storing and communicating structured XML invoices to recipients. A PDF may be convenient to read, but the original in the system is the XML file carrying the electronic seal of the Romanian Ministry of Finance.
This article is a non-exhaustive overview checked on 17 August 2026. Applicability depends on the parties, place of supply, recipient type, registers and exceptions. For a specific transaction, consult the consolidated OUG no. 120/2021, the official ANAF e-Factura page and a Romanian tax professional.
The main branches relevant to service invoices include:
| Situation | Basic rule |
|---|---|
| B2B between taxable persons established in Romania | Article 10(1) requires RO e-Factura transmission for transactions whose place of supply is Romania, subject to the exceptions in that article. |
| Supplier established in Romania and a non-established recipient registered for Romanian VAT | From 1 January 2026, Article 10(1^1) covers transactions whose place of supply is Romania, subject to its exceptions; Article 10(1^2) also requires transmission of the invoice to the recipient under Fiscal Code Article 319, without prescribing one channel in that provision. |
| B2C | Article 10^1 governs relevant transactions by suppliers established in Romania together with applicable exceptions and register rules. Law no. 88/2026 changed certain personal-identification, register and exception rules from 1 June 2026. |
B2G relationships under Articles 5–9 and other public-institution transactions under Article 9^1 are governed separately and sit outside this B2B/B2C summary. For each invoice, verify establishment, place of supply, recipient status, relevant register and applicable exception.
The wider VAT framework is also jurisdiction-sensitive. VAT Directive Articles 219a and 226 tie invoicing rules to the applicable Member State and list invoice particulars subject to specific and conditional provisions; they do not create a universal supporting-document pack.
What is the transmission deadline in 2026?
Articles 10(7) and 10^1(2^1) use a two-limb rule: the invoice must be transmitted within 5 working days of issue, but no later than 5 working days after the statutory issuance deadline in Romanian Fiscal Code Article 319(16). The time calculation follows Regulation (EEC, Euratom) no. 1182/71.
This is a system-transmission deadline, not the commercial payment term. Where the issue date or statutory deadline is uncertain for the transaction, resolve it before calculating the interval.
What does the system check before communicating the invoice?
Article 4 of OUG no. 120/2021 requires the invoice structure to follow the applicable standard, Romania’s RO_CIUS specifications and operating rules.
- If the file is structurally conforming, the Ministry of Finance applies its electronic seal and communicates it to the recipient.
- If the file is structurally non-conforming, the issuer receives a message listing the identified errors, corrects the file and resubmits it.
This check concerns structure. The seal attests receipt by the system; it does not by itself certify the substantive tax treatment, customer approval or payment.
When is the invoice communicated to the recipient?
The communication date is the date on which the invoice becomes available for the recipient to download from RO e-Factura. The date is also accessible to the issuer. The original is the XML file carrying the Ministry of Finance electronic seal.
Communication proves availability in the system. It does not mean that the customer has verified the transport service, approved the invoice in its commercial workflow or initiated payment.
What happens when the recipient has an objection?
An invoice already communicated through RO e-Factura cannot be returned inside the system. A recipient with an objection notifies the issuer, including by entering a message in RO e-Factura.
A recipient objection is different from a structural error. A structural error arises before a non-conforming file is communicated; an objection concerns an invoice that passed the structural check and was communicated.
How is a communicated invoice corrected?
Article 4(10) points corrections to Article 330 of the Romanian Fiscal Code. The corrected invoice is then transmitted through the same RO e-Factura system.
Not every commercial question automatically requires a corrective invoice. First determine whether the fiscal document changes or whether the customer needs only an explanation or supporting record.
Which fiscal particulars apply to the invoice?
Romanian Fiscal Code Article 319 distinguishes ordinary invoices, simplified invoices and conditional particulars. Depending on the transaction and invoice type, the applicable categories may include the unique number and issue date, supply date, party identifiers, service description, taxable amount, VAT rate and amount, currency and required special wording.
This is not a universal checklist for every transaction. Verify the applicable paragraphs and keep fiscal particulars separate from customer supporting documents. For transport-order, CMR/POD, reference, amount and submission-channel controls, use the road freight invoice supporting-documents checklist.
Which process confusions should you avoid?
- Assuming every transport invoice falls under the same branch without checking place of supply and party status.
- Counting five days only from issue while ignoring the limit linked to the statutory issuance deadline.
- Calling every problem a rejection instead of separating structural non-conformity, recipient objection and fiscal correction.
- Treating the seal or system communication as commercial approval or payment confirmation.
- Correcting the invoice before deciding whether the fiscal document or only its supporting pack must change.
For related transport-compliance topics, see the guides to Romania e-Transport and the UIT code and avoiding road transport fines.
Frequently asked questions
Does RO e-Factura apply to every transport invoice?
Not automatically. Applicability depends on where the parties are established, the place of supply, recipient type, relevant registers and the exceptions in OUG no. 120/2021.
What is the transmission deadline in 2026?
The invoice must be transmitted within 5 working days of issue, but no later than 5 working days after the statutory issuance deadline under the Romanian Fiscal Code.
What is the difference between a structural error and a recipient objection?
A structural error occurs before communication and requires correction and resubmission; an objection is the recipient message concerning an invoice already communicated through the system.
Does communication through RO e-Factura mean approval for payment?
No. Communication means the sealed invoice is available to the recipient in the system; it does not prove commercial approval or payment.
