Guide
e-Factura in 2026: the complete guide for businesses in Romania
What RO e-Factura is, who must use it, the 5-working-day deadline, the fines, the steps in ANAF's SPV portal and what changed in 2026.
- by
- Echipa VITT
- Updated
- 16
- min read
e-Factura (officially RO e-Factura) is the Romanian Ministry of Finance’s national system through which businesses in Romania submit invoices as structured XML files, which are validated automatically and, between businesses, delivered to the buyer through ANAF’s online portal. It has been mandatory for invoices to contracting authorities since 2022, between businesses since 2024 and to private individuals since 2025. Since 1 January 2026, every invoice must be submitted within 5 working days of being issued.
This guide explains who is covered, the deadlines, the fines and the practical steps, with the legal basis for each rule. The rules changed several times in 2025 and 2026; everything below reflects the position on the date shown as last updated.
A few Romanian terms recur: ANAF (Agenția Națională de Administrare Fiscală, the tax authority), SPV (Spațiul Privat Virtual, ANAF’s online portal), CUI (cod unic de înregistrare, the company tax ID), CNP (cod numeric personal, the personal identification number), OUG (ordonanță de urgență, a government emergency ordinance) and the Codul fiscal (Fiscal Code, Law 227/2015).
What e-Factura is
The system is governed by OUG 120/2021, published in Official Journal no. 960 of 7 October 2021 and amended many times since. The law defines an electronic invoice as one “issued, transmitted and received in a structured electronic XML format” (art. 2(1)(a)). A PDF, even one signed electronically, is not an electronic invoice in this sense.
The system does three things: it receives the invoice from the issuer, checks that it follows the required structure and, if it does, applies the Ministry of Finance’s electronic seal and makes it available to the buyer. Otherwise, the issuer receives a message listing the errors (art. 4(4)–(5)).
| Element | What it means |
|---|---|
| EN 16931 | The European standard for electronic invoices: the business terms (BT) and business rules (BR). |
| XML syntax | UBL 2.1 (Invoice and CreditNote messages) or UN/CEFACT CII. Most software uses UBL. |
| CIUS-RO | The Romanian specification approved by Minister of Finance Order 1366/2021: BR-RO rules, maximum lengths, code lists. |
| Validation rules | The schematron files published by the Ministry of Finance; at the time of writing, version 1.0.9 applies, in force since 5 June 2024. |
| Ministry of Finance seal | Applied only to valid invoices; it attests that the system received them. |
Which document is the original invoice
The original electronic invoice is the XML file accompanied by the Ministry of Finance’s electronic seal (art. 4(6) of OUG 120/2021). Since 1 July 2024, between taxable persons established in Romania only invoices that meet the conditions of OUG 120/2021 count as invoices (Fiscal Code, art. 319(1¹)). A PDF sent by email, or one rendered from the XML, is only a visual copy.
An invoice is deemed delivered to the buyer on the date it becomes available for download in the system (art. 4(7)). The buyer cannot send it back through the system; if they object, they tell the issuer, including through a message in RO e-Factura (art. 4(8)–(9)).
For invoices to private individuals (B2C), submission works as reporting: the customer still receives the invoice in the usual way, on paper or electronically (art. 10¹(4)).
Who must use e-Factura
The obligation applies to taxable persons established in Romania, whether or not they are registered for VAT: limited companies (SRL), sole traders (PFA), individual and family businesses, and the liberal professions. Company size and the VAT exemption threshold make no difference.
| Relationship | Since | What it involves | Legal basis |
|---|---|---|---|
| B2G: invoices under public procurement contracts | 1 July 2022 | The invoice is issued and submitted only through the system; since 2025 it must include CPV codes | Law 139/2022, art. II; OUG 120/2021, art. 4(2¹) |
| B2B: between businesses established in Romania | 1 January 2024 (reporting); 1 July 2024 (the invoice travels only through the system) | The buyer receives the invoice from SPV | OUG 120/2021, art. 10(1); Law 296/2023 |
| Other public institutions | 1 January 2024 (reporting); 1 July 2024 (the invoice travels only through the system) | The B2G rules apply: the invoice is issued and submitted only through the system | Law 296/2023, art. LIX(2); OUG 120/2021, art. 9¹ |
| B2C: to private individuals | 1 January 2025 | You submit the invoice and still give it to the customer as before | OUG 120/2021, art. 10¹ |
| Foreign businesses registered for VAT in Romania | 1 January 2026 | You submit the invoice and also send it to the customer in the usual way | OUG 120/2021, art. 10(1¹)–(1²) |
Invoices to private individuals
A sale to an individual counts as B2C when the customer gives no tax ID or chooses to identify with their CNP. Where there is no ID at all, you enter a code made of thirteen zeros instead (art. 10¹(3)). You are not required to ask for the customer’s CNP. The exception is an individual enrolled in the optional RO e-Factura register: the sale is then not B2C, and the invoice reaches them through the system (art. 10¹(3)–(4), as amended by Law 88/2026).
Fiscal receipts (bonuri fiscale) that meet the conditions of a simplified invoice are not submitted (Fiscal Code, art. 319(12), (13) and (21)). If you issue an invoice, however small the amount, you submit it.
Foreign businesses
- As suppliers: businesses not established in Romania but registered for VAT there have reported their B2B invoices for supplies taking place in Romania since 1 January 2024 (Law 296/2023, art. LIX(3)), and also send them to customers in the usual way. They may opt to use the system in full.
- As customers: since 1 January 2026, Romanian suppliers also submit the invoices they issue to these businesses.
- Not submitted: invoices to customers that are neither established nor VAT-registered in Romania, exports, and intra-Community supplies where the customer provides a VAT number from another member state.
Who is exempt, at the time of writing
- People who invoice under a CNP rather than a CUI, for example individuals earning copyright income or renting rooms to tourists. Since 1 June 2026 they are no longer obliged to use the system and may opt in through the optional RO e-Factura register (art. 10¹⁰, as amended by Law 88/2026). Sole traders (PFA) and individual and family businesses have a CUI, so they remain covered.
- Individual farmers under the special scheme in art. 315¹ of the Fiscal Code (art. 10⁷). Their suppliers submit invoices to them through the system only if they have joined the optional register.
- Cultural institutes and centres of other states operating in Romania under intergovernmental agreements (art. 10⁵).
- Invoices for operations outside the scope of VAT for which the Fiscal Code does not require an invoice (art. 10³).
Associations, foundations, political parties and religious organisations not registered for VAT were exempt only for invoices issued between 1 July 2024 and 30 June 2025. Since 1 July 2025, those carrying out economic activities must join the mandatory RO e-Factura register (art. 10⁶). If such a customer asks you for an invoice, check the register on anaf.ro.
The submission deadline
An invoice must be submitted within 5 working days of its issue date, and no later than 5 working days after the legal deadline for issuing it under art. 319(16) of the Fiscal Code, which is the 15th day of the month after the chargeable event (usually the supply) or after the month in which an advance was received. The rule is in art. 10(7) for B2B and art. 10¹(2¹) for B2C, as amended by OUG 89/2025. The period is counted under Regulation (EEC, Euratom) No 1182/71: the issue day itself is not counted, and Saturdays, Sundays and Romanian public holidays are not working days.
| Period | Submission deadline |
|---|---|
| 1 January – 30 June 2024 | 5 working days (Law 296/2023, art. LIX) |
| 1 July 2024 – 31 December 2025 | 5 calendar days (OUG 115/2023, art. LXVII; OUG 69/2024) |
| From 1 January 2026 | 5 working days, for B2B and B2C |
Example. For an invoice issued on Friday 27 November 2026, Monday 30 November (St Andrew’s Day) and Tuesday 1 December (National Day) are public holidays. The working days that count are 2, 3, 4, 7 and 8 December, so the deadline is the end of Tuesday 8 December 2026.
The period runs from the date printed on the invoice. An invoice issued today with an earlier date may already be late when you submit it.
Fines
Penalties are set out in art. 13¹ and 13² of OUG 120/2021. Large and medium taxpayer status is the classification assigned by ANAF; micro-enterprises and other small businesses fall under “other legal persons”.
| Offence | Fine | Legal basis |
|---|---|---|
| Late B2B submission, for one or more invoices whose deadline falls in the same month | large taxpayers: 5,000–10,000 lei; medium: 2,500–5,000 lei; other legal persons and individuals: 1,000–2,500 lei | art. 13²(1)(c) and (3) |
| B2C invoices not submitted on time, from 1 July 2025, with the same monthly rule | same amounts | art. 13²(1)(d) and (3) |
| The issuer does not send a B2B invoice through the system | 15% of the invoice’s total value | art. 13²(1)(a) and (2) |
| The buyer receives and books a B2B invoice that did not go through the system | 15% of the invoice’s total value | art. 13²(1)(b) and (2) |
| Enforcement bodies fail to submit invoices | 5,000–10,000 lei per invoice | art. 13²(1)(e) and (3¹) |
| A public institution pays a B2G invoice that did not go through the system | 500–1,000 lei | art. 13¹ |
For late submission, one fine covers all invoices whose deadline falls in the same calendar month; it is not charged per invoice. The 15% fine is the most expensive and hits both sides, so as a buyer, do not book a B2B invoice that reached you only by email or on paper.
How it works, step by step
- Access to SPV. The company registers in ANAF’s online portal with a qualified digital certificate: the company’s own, its legal representative’s, or that of an authorised person such as its accountant. Invoicing software connects to the system through ANAF’s web services, after an authorisation made with the same certificate.
- Issuing the invoice and generating the XML. Your invoicing software generates the XML file. Without software, you can use the Ministry of Finance’s free web form. Supporting documents (contract, estimate, work report) are embedded in the XML, up to 3 MB in total.
- Validating before you send. Check the XML with the validator and the CIUS-RO rules published by the Ministry of Finance. An error caught here saves you a rejection and a resubmission; the deadline runs from the issue date either way.
- Uploading. You send the XML from SPV (Factura electronică, then Trimitere factură) or directly from your software. The system replies with an upload index (index de încărcare), the number you use to track the invoice.
- Processing. While it is checked, the invoice shows as “în prelucrare” (processing). Then you get one of two answers: ok, when the invoice is valid, receives the Ministry of Finance seal and reaches the buyer; or nok, when errors were found: you download the list of errors and the invoice does not reach the buyer. A file that cannot be taken in at all is refused with the message “XML cu erori nepreluat de sistem”.
- Downloading the response. For an accepted invoice you download an archive with the original XML and the Ministry of Finance’s signature. This is the original invoice.
- Archiving. Files and error messages stay in SPV for 60 days from publication; after that, ANAF archives them and releases them on request. Accounting records and supporting documents must be kept for 5 years, counted from 1 July of the year after the financial year ends (Accounting Law 82/1991, art. 25, as amended by Law 36/2023), so keep the XML with its signature, not just the PDF.
If RO e-Factura is out of service for at least 24 hours, the obligation to submit B2B and B2G invoices is suspended until it is restored; you issue the invoice under the usual rules and submit it afterwards (OUG 115/2023, art. LXXI). The text does not mention B2C invoices; submit those too once the system is back. Outages are published on anaf.ro and mfinante.gov.ro.
Received invoices and VAT deduction
Invoices from suppliers appear in SPV in the message list, as received invoices. You download them together with the Ministry of Finance signature; the Ministry offers a free application to verify the signature and another that turns the XML into a readable PDF.
To deduct VAT, the Fiscal Code requires an invoice issued under art. 319 (art. 299(1)(a)), and between businesses established in Romania only an invoice submitted through RO e-Factura meets that condition (art. 319(1¹)). In practice:
- download received invoices at least once a week, well within the 60 days; ANAF can repost documents that were not downloaded, on request;
- if a Romanian supplier sends you a B2B invoice only by email, ask them to submit it to the system before you book it;
- for supplies paid on the spot, if the invoice does not reach you through the system in time, you can notify ANAF (art. 10⁹ of OUG 120/2021);
- if an invoice is wrong, you cannot reject it in the system: you write to the supplier, and the supplier corrects it.
Data from e-Factura also feeds RO e-TVA, the pre-filled VAT return that ANAF makes available in SPV.
Corrections: rejected invoices, reversals and credit notes
A rejected invoice is not considered submitted and has not reached the customer. You fix the errors and submit it again (art. 4(5) of OUG 120/2021), normally with the same number and date and without a reversal. The 5-working-day deadline keeps running from the issue date.
An accepted invoice can no longer be cancelled. An invoice delivered to the buyer is corrected under art. 330(1)(b) of the Fiscal Code, and the correcting document also goes through e-Factura (art. 4(10) of OUG 120/2021). The Ministry of Finance’s guide to invoice type codes describes the options:
| Code (BT-3) | Document | How it is filled in |
|---|---|---|
| 380 | Invoice, including the reversal invoice (storno) | For a reversal: negative quantities and amounts, while the unit price (BT-146) stays positive; reference to the original invoice in BT-25 and BT-26 |
| 381 | Credit note | Positive amounts, in a separate XML structure (CreditNote) |
| 384 | Corrective invoice | The reference to the original invoice is mandatory; it can carry the old values as negatives and the correct ones as positives |
| 389 | Self-billed invoice | Issued by the buyer on the supplier’s behalf, under a prior agreement |
| 751 | Information invoice for accounting purposes | For example, an invoice requested later for fiscal receipts |
An advance invoice has no separate code in RO e-Factura: it is submitted as a 380. Two situations need care:
- The buyer’s CUI is wrong. The invoice went to another company’s SPV, so a correction on that invoice would not reach the real buyer. In practice you issue a reversal against the wrong CUI and a new invoice to the correct one (Fiscal Code, art. 330(1)(b)).
- You submitted the same invoice twice. Any difference in the XML, even a space, makes the second upload a new invoice that cannot be cancelled. The guide recommends a “technical reversal” (storno tehnic): the original invoice number followed by the letter S (for example TX623S), the duplicate’s upload index in BT-25, its upload date in BT-26 and, in BT-22, the note “Storno tehnic a facturii” with the series, number, date and upload index.
The VAT rate is the one in force when the chargeable event occurred (Fiscal Code, art. 291(4)). Since 1 August 2025 the standard rate is 21% and the single reduced rate is 11% (Law 141/2025), but a reversal of a July 2025 supply is, as a rule, still made at 19%.
Common validation errors
ANAF’s error messages quote the code of the rule that failed. The most frequent:
| Rule | What to check |
|---|---|
| BR-RO-110 | The county is coded in ISO 3166-2:RO (for example RO-CJ, RO-B), not written as text. |
| BR-RO-100 | In Bucharest, the city is SECTOR1 … SECTOR6. |
| BR-RO-080, BR-RO-090 | Street and city are filled in for both seller and buyer. |
| BR-RO-120 | The buyer has a CUI or VAT number; for individuals, a CNP or the thirteen zeros. |
| BR-RO-030, BR-53 | On foreign-currency invoices, the VAT accounting currency (BT-6) is RON and the VAT total is also given in lei (BT-111). |
| BR-RO-020 | The invoice type is one of 380, 381, 384, 389 and 751. |
| Maximum lengths (BR-RO-L…) | Item names have at most 100 characters, an invoice note at most 300, an address line at most 150. |
| BR-CO-15, BR-S-08, BR-S-09 | Totals and the VAT for each rate add up, with amounts of at most two decimals. |
| BR-CO-25 | If an amount remains payable, the invoice has a due date (BT-9) or payment terms (BT-20). |
| cvc-… errors | The XML breaks the UBL schema, for example element order; the schema is checked before the business rules. |
Beyond validation, the costliest mistakes are organisational: a B2B invoice sent to the customer only by email, received invoices left undownloaded for 60 days, the belief that a sole trader or a business not registered for VAT is exempt, and incomplete partner data (address, county, CUI) that causes rejection after rejection.
Recent changes
| Date | Change | Legal act |
|---|---|---|
| 1 July 2022 | B2G mandatory; also in 2022, B2B for goods with high fiscal risk | Law 139/2022; OUG 130/2021 |
| 1 January 2024 | B2B reporting becomes mandatory, within 5 working days; non-resident businesses registered for VAT report their B2B invoices | Law 296/2023 |
| 1 June 2024 | The period without fines for late submission ends, after being extended to 31 May 2024 | OUG 30/2024, art. III (amending Law 296/2023, art. LIX(8)) |
| 1 July 2024 | In B2B, the invoice is only the XML in the system; the 15% fine; a 5-calendar-day deadline; B2C optional | Law 296/2023; OUG 115/2023; OUG 69/2024 |
| 1 January 2025 | B2C mandatory; fiscal receipts that serve as simplified invoices are not submitted | OUG 69/2024; OUG 138/2024 |
| 1 July 2025 | Fines for B2C; the exemption for associations, parties and religious organisations not registered for VAT ends | OUG 69/2024 |
| 1 August 2025 | VAT rates: 21% standard, 11% reduced | Law 141/2025 |
| 1 January 2026 | 5-working-day deadline for B2B and B2C; invoices to non-resident businesses registered for VAT are submitted | OUG 89/2025 |
| 15 January 2026 | Suppliers who invoice under a CNP must be enrolled in the mandatory RO e-Factura register; OG 6/2026, published on 30 January, relieves them of the obligation until 1 June 2026 | OUG 89/2025, art. X point 5 and art. XI; OG 6/2026, art. IX |
| 1 June 2026 | Suppliers invoicing under a CNP, farmers under the special scheme and foreign cultural institutes are no longer obliged | Law 88/2026 |
At EU level, mandatory B2B e-invoicing was authorised by Council Implementing Decision (EU) 2023/1553, as a derogation from Articles 218 and 232 of the VAT Directive. The ViDA package (Directive (EU) 2025/516) allows member states to require electronic invoicing for domestic transactions and introduces, from 1 July 2030, electronic invoicing and digital reporting for B2B supplies between member states. For changes made after the update date, check the e-Factura sections of anaf.ro and mfinante.gov.ro.
How VITT helps
VITT is a Romanian invoicing and business-management platform, built in Romania for Romanian legislation. For e-Factura, it:
- validates each invoice’s XML against the EN 16931 and CIUS-RO rules before sending it to SPV;
- submits the invoice to e-Factura and tracks its status (pending, submitted, accepted, rejected, failed), separately from the invoice’s own status and its payment status;
- synchronises received invoices from SPV and imports e-Factura archives or XML files;
- fills in customer details from ANAF data when you enter a CUI, and issues reversal invoices, advance invoices and invoices in EUR with VAT in lei at the BNR (National Bank of Romania) exchange rate;
- lets you prepare invoices from Claude or ChatGPT too, over MCP; by default, invoices created that way wait for your approval in VITT before they go to SPV, and the data the assistant reads reaches its provider, for example Anthropic or OpenAI (VITT in Claude and ChatGPT).
See the Invoicing and e-Factura page for details.
Questions
Is a PDF sent by email a valid invoice between two Romanian businesses?
No. Since 1 July 2024, between taxable persons established in Romania only invoices that go through RO e-Factura count as invoices (Fiscal Code, art. 319(1¹)). The original is the XML file with the Ministry of Finance's electronic seal; a PDF is only a visual copy.
How long do I have to submit an invoice to e-Factura?
5 working days from the issue date, and no later than 5 working days after the legal deadline for issuing the invoice, which is the 15th of the month after the chargeable event, usually the supply. The rule applies to B2B and B2C invoices from 1 January 2026; the issue day itself is not counted.
Do invoices to private individuals have to go through e-Factura?
Yes, since 1 January 2025, except fiscal receipts that serve as simplified invoices. If the customer gives no tax ID, you enter thirteen zeros instead of the CNP, and you still hand the invoice to the customer on paper or electronically.
What should I do if ANAF rejects my invoice?
An invoice rejected at validation is not considered submitted and does not reach the customer. Fix the errors listed in ANAF's message and submit it again; the 5-working-day deadline keeps running from the issue date, so check the response the same day.
Can I cancel an invoice that ANAF has accepted?
No. An invoice delivered to the buyer cannot be cancelled (Fiscal Code, art. 330(1)(b)). You correct it with a reversal invoice (storno), a credit note or a corrective invoice, also submitted through e-Factura.
I am a sole trader (PFA) and not VAT-registered. Do I have to use e-Factura?
Yes. The obligation applies to taxable persons established in Romania whether or not they are VAT-registered, and a PFA is identified by a company tax ID (CUI). The exemption from 1 June 2026 covers only those who invoice under a CNP.
How long can I download invoices from SPV?
60 days from publication in the system; after that, ANAF archives them and releases them on request. Download the XML with its signature and keep it for 5 years, counted from 1 July of the year after the financial year ends.
What happens if RO e-Factura is down?
If the system is out of service for at least 24 hours, the obligation to submit B2B and B2G invoices is suspended until it is restored. You issue the invoice under the usual rules and submit it to the system afterwards (OUG 115/2023, art. LXXI); the text does not mention B2C invoices, so submit those too once the system is back.
Sources
- 01 OUG 120/2021 on the RO e-Factura national system, Legislative Portal · Romanian Ministry of Justice, Legislative Portal
- 02 OUG 120/2021, text as published in Official Journal no. 960 of 7 October 2021 · ANAF
- 03 Law 139/2022 approving OUG 120/2021 (B2G from 1 July 2022) · ANAF
- 04 Law 296/2023, art. LIX and LXV (Official Journal no. 977 of 27 October 2023) · ANAF
- 05 OUG 115/2023, art. LXVII, LXVIII and LXXI · ANAF
- 06 OUG 30/2024, art. III (no-fine period extended to 31 May 2024) · ANAF
- 07 OUG 69/2024 (B2C, RO e-Factura registers, fines) · ANAF
- 08 OUG 138/2024, art. I · ANAF
- 09 OUG 89/2025, art. X–XI (Official Journal no. 1203 of 24 December 2025) · ANAF
- 10 Changes made to OUG 120/2021 by OUG 89/2025 (in Romanian) · ANAF, Brașov Regional Directorate
- 11 OG 6/2026, art. IX (Official Journal no. 77 of 30 January 2026) · ANAF
- 12 Law 88/2026, art. III–IV (Official Journal no. 459 of 29 May 2026) · ANAF
- 13 Romanian Fiscal Code (Law 227/2015), consolidated: art. 291, 299, 319, 330 · ANAF
- 14 Guide to using the RO e-Factura national system (in Romanian) · ANAF
- 15 Guide to invoice type codes, version 2.9 (in Romanian) · Romanian Ministry of Finance (published on anaf.ro)
- 16 RO e-Factura technical information: validators, CIUS-RO schematron, web services · Romanian Ministry of Finance
- 17 Law 36/2023 amending Accounting Law 82/1991 (art. 25: the 5-year retention period) · ANAF
- 18 Main changes to VAT rates under Law 141/2025 (in Romanian) · ANAF
- 19 Council Implementing Decision (EU) 2023/1553 authorising Romania to derogate from Articles 218 and 232 of the VAT Directive · EUR-Lex
This guide is for information only and is not a substitute for tax or legal advice. VITT is not affiliated with ANAF.