Romania eInvoicing guide: RO e-Factura Rules, Deadlines, and Requirements for 2026

Luis CollVP of eInvoicing Compliance17 min read

Romania runs a clearance model. RO e-Factura is the national platform, operated by the Ministry of Finance and ANAF, Romania’s tax authority. Domestic B2B and B2G invoices pass through it to be validated and sealed, and that sealed XML is the legal invoice. B2C invoices are reported through the same platform. Businesses connect through SPV (Spațiul Privat Virtual), ANAF’s online portal, or through its API.

If you invoice in Romania, you need to know which transactions are covered, how to submit them, and what happens after submission. This guide covers the current rules, technical requirements, deadlines, and exceptions.

What is RO e-Factura?

RO e-Factura is Romania's centralized eInvoicing platform. It was established under Emergency Ordinance 120/2021 and is administered by the Ministry of Finance and ANAF.

The system uses a clearance model for B2B and B2G invoicing. You submit an invoice in a structured XML format, the platform validates it, and the Ministry of Finance applies an electronic seal. The sealed invoice then becomes available to the recipient in SPV (Spațiul Privat Virtual), ANAF's online portal.

Romania does not use Peppol for its mandatory domestic invoicing flow. There are no competing access points or separate delivery networks. All invoices covered by the mandate go through RO e-Factura. If you already route invoices over Peppol in other EU markets, none of that infrastructure carries over. Romania has one destination, reached through one government API.

The most important distinction is that the validated, electronically sealed XML is the legally recognized electronic invoice. A PDF representation alone does not satisfy the RO e-Factura requirement.

The seal is applied by the Ministry of Finance after validation, not by you, so the file with legal standing is not the one you generated. ANAF does not send it to you. It sits in SPV and you have to collect it, which makes retrieval and archiving your responsibility, not the platform’s.

Who must use RO e-Factura in Romania?

The obligation applies to taxable persons established in Romania for supplies that take place in Romania.

Since January 1, 2026, Romanian-established suppliers must also submit invoices issued to businesses that are not established in Romania but are registered for Romanian VAT, when the supply takes place in Romania.

The obligation sits with the Romanian-established supplier, not with the foreign buyer. If you hold a Romanian VAT number without an establishment, you have nothing to file yourself. Your supplier uploads the invoice to RO e-Factura but still sends it to you directly, and you only see it in the platform if you are registered in ANAF's SPV.

The rules differ depending on whether you invoice another business, a public institution, or an individual consumer.

TransactionRequirementMandatory since
B2G (business to government)Submit structured invoices through RO e-FacturaJuly 1, 2022
Domestic B2BSubmit invoices for reporting, followed by mandatory clearanceJuly 1, 2022 (high fiscal risk products); January 1, 2024 (reporting); July 1, 2024 (clearance)
B2C (business to consumer)Report issued invoices through RO e-FacturaJanuary 1, 2025
Supplies to non-established, Romanian VAT-registered businessesSubmit covered invoices through RO e-FacturaJanuary 1, 2026

The mandate excludes exports, intra-Community supplies, and fiscal receipts that meet the conditions for a simplified invoice.

What about freelancers, individuals, and farmers?

The rules for individuals conducting economic activities under their personal identification number (CNP) changed during 2026.

A requirement to register from January 15, 2026, was first postponed, then removed. Law 88/2026, promulgated on May 29, 2026 and published in Monitorul Oficial no. 459, ended the obligation for individuals identified by a CNP. Since June 1, 2026 they use RO e-Factura only if they choose to.

Farmers under the special VAT regime are exempt on the same basis. Law 88/2026 covers both groups.

Either group can opt in by registering in the Registrul RO e-Factura Opțional, and anyone already registered can ask to be removed.

In practice the exemption covers authors, journalists, translators, artists, and content creators who invoice under a CNP for copyright income.

How does RO e-Factura work?

For B2B and B2G invoices, the process follows a centralized submission and validation flow.

  1. Create the invoice. Generate a structured XML document that meets the European EN 16931 standard and Romania's national profile (CIUS-RO), using UBL 2.1.
  1. Submit it to ANAF. Upload the invoice through Spațiul Privat Virtual (SPV), ANAF's online taxpayer portal, or through an API integration.
  1. Validate the invoice. RO e-Factura checks the document against the national technical and business rules.
  1. Receive the result. If validation succeeds, the Ministry of Finance applies an electronic seal. If validation fails, the system returns errors that must be corrected.
  1. Delivery to the buyer. For B2B and B2G transactions, the recipient retrieves the sealed invoice from SPV.

The platform returns a validation response of ok or nok, together with the sealed invoice or the errors. ANAF usually answers within a few minutes, but not instantly, so your integration has to wait for the decision rather than treat a successful upload as a cleared invoice.

Can you send invoices directly to customers?

For transactions subject to mandatory B2B clearance, RO e-Factura is the official delivery channel. You may send a PDF copy to your customer for convenience, but it does not replace the validated XML made available through the platform.

For B2C transactions, the arrangement is different. You report the invoice to RO e-Factura and continue delivering it to the consumer through your usual channel.

Submission deadlines

As of January 1, 2026, you must transmit covered invoices to RO e-Factura within 5 working days of issuance, and no later than 5 working days after the statutory invoice-issuance deadline.

Previously, the transmission deadline was 5 calendar days.

Under Article 319(16) of the Fiscal Code (Law 227/2015), you must issue the invoice by the 15th day of the month following the taxable event.

For example, an invoice issued on a Monday must reach RO e-Factura by the following Monday. The count starts the day after issuance and skips weekends, so Tuesday to Friday are days one to four and the next Monday is day five. A Romanian public holiday inside that window pushes the deadline out by a further working day.

The same transmission period applies to B2C invoices that must be reported.

B2C invoicing and the bon fiscal distinction

Since January 1, 2025, Romanian-established taxpayers have been required to report B2C invoices through RO e-Factura.

However,** the obligation depends on whether you issue an invoice (factură), not simply whether you make a retail sale.

What is the difference between a factură and a bon fiscal?

A factură is an invoice. A bon fiscal is the receipt a fiscal cash register prints at the till.

A fiscal receipt that meets the legal requirements of a simplified invoice is excluded from the RO e-Factura submission obligation. Its transaction data is handled through the fiscal cash register reporting system.

If you issue a separate B2C invoice for a transaction, that invoice falls within the RO e-Factura reporting requirement.

For example:

  • A customer purchases an item in a store and receives only a qualifying fiscal receipt. The receipt is not separately transmitted through RO e-Factura.
  • A consumer requests an invoice for the purchase. The business issues the invoice and reports it through RO e-Factura.
  • An online service provider issues invoices to individual consumers. Those invoices must be reported, even though the consumers do not receive them through SPV.

The B2C reporting mandate does not require consumers to register for SPV.

Do you need the consumer's CNP?

Romanian invoices may identify an individual consumer using their CNP.

If you do not have the consumer's CNP, fill the buyer identifier with thirteen zeros (0000000000000). This allows you to report covered B2C invoices without collecting a personal identification number from every customer.

eInvoicing formats and field requirements

RO e-Factura accepts structured XML invoices based on the European eInvoicing standard EN 16931.

The supported formats include:

  • UBL 2.1: Universal Business Language, using the Romanian CIUS-RO profile.
  • CII D16B: Cross-Industry Invoice, another structured format under the European standard, accepted for B2G and B2B.

Romania applies its own national validation rules, commonly referred to as BR-RO, in addition to the European requirements. An invoice that is valid under a general European XML schema can still fail Romanian validation if it does not meet these national rules.

Romania-specific invoice requirements

These rules apply however you file. SPV is an upload channel, not an authoring tool: it accepts a finished XML file, so the fields are yours to get right whether you submit by hand or through an ERP, billing platform, or API.

Field or ruleRequirement
Invoice typeSupported codes include 380 (commercial invoice), 381 (credit note), 384 (corrective invoice), 389 (self-billing), and 751 (accounting purposes)
Invoice numberMust contain at least one digit
Foreign currencyVAT amounts must also be expressed in Romanian lei (RON)
County codesRomanian addresses use ISO 3166-2 county identifiers
Bucharest addressesThe city field carries the sector, Sector 1 to Sector 6, not the city name. The county code is RO-B
Monetary precisionAmounts take at most 2 decimal places
Attachments3 MB in total

These details matter because an otherwise complete invoice can be rejected for a formatting or data-validation error. Before going live, test your invoice output against ANAF's current XML schemas and validation rules, rather than relying only on the general EN 16931 specification.

Credit notes, corrective invoices and self-billing

Once RO e-Factura has validated and sealed an invoice, you cannot simply delete or cancel the original document from the system.

To correct it, issue another document that references the original invoice. The relevant document types include:

  • Credit note (381): Used to reduce or reverse previously invoiced amounts.
  • Corrective invoice (384): Used to correct information in an earlier invoice.

The correction follows Romanian invoicing rules and goes through RO e-Factura like any other covered invoice.

Negative line amounts are allowed. A corrective invoice can therefore carry both increases and decreases to the original, instead of forcing you to split a mixed correction across two documents.

Self-billing is allowed. The buyer issues the invoice in the supplier's name, using invoice type code 389. The resulting invoice follows the same RO e-Factura rules as any other covered transaction.

Can a buyer reject an invoice in RO e-Factura?

RO e-Factura does not provide a buyer acceptance or rejection workflow comparable to systems that require the recipient to formally approve an invoice.

The platform's validation status indicates whether the document meets the technical and business rules.

If the buyer disputes the amount, goods, services, or other details, the parties must resolve the issue directly. Any required correction is then handled through the appropriate invoice document.

Do you need a certified eInvoicing provider in Romania?

Romania does not operate a separate ANAF certification scheme for commercial eInvoicing service providers. You can use the public SPV portal or connect through the RO e-Factura API, either directly or through a third-party provider. A provider does not need a Romanian entity: any company can connect through the public API with a qualified eIDAS certificate, once each customer authorizes it in SPV.

API access uses a qualified digital certificate and ANAF's authorization procedure. The certificate belongs to a natural person, who authorizes the provider in SPV to act for the taxpayer's tax number (CIF). That authorization lasts a year and has to be renewed, and a lapse stops sending and receiving at the same time.

The taxpayer does not need to apply an electronic signature to each invoice as part of the normal RO e-Factura clearance process. The Ministry of Finance applies its electronic seal after validation.

Nothing here forces you to use a provider. Building it yourself is reasonable if you issue a low volume from a single Romanian entity and have someone who can hold the qualified certificate and keep the integration current.

A provider earns its place when:

  • You need continuous retrieval. Nothing arrives on its own, in either direction. The invoices your suppliers sent you and the sealed copies of the invoices you sent both sit in SPV for 60 days until something collects them.
  • Validation rules change. ANAF updates its schemas, and a rejection you catch late turns into a missed 5 working day deadline and a fine.
  • You file in more than one country. One provider covering every mandate beats building and maintaining a separate pipeline for each country's format.

When choosing a provider, check that it handles Romanian XML generation, validation, submission, error handling, invoice retrieval, and authorization for each of your legal entities.

Retrieval and archiving

RO e-Factura makes validated invoice XML files and associated system messages available for download for 60 days. After that, ANAF archives the files and you have to request a copy. That request is manual and handled case by case, so it is not a step you want sitting in the path of a month-end close or an audit.

This does not mean that window should be your company's document retention policy. Keep your invoices and supporting records for as long as Romania's accounting and tax rules require.

Retrieval runs in both directions. You collect the invoices your suppliers sent you, and you collect the sealed version of the invoices you sent, because the copy your own system generated has no legal standing. At any volume, both need to be automated rather than left to someone remembering. ANAF explains the process in its RO e-Factura user guide.

What happens if RO e-Factura is unavailable?

If the platform is unavailable for at least 24 hours, the obligation to transmit pauses until the service resumes.

Qualifying outages are announced on the ANAF and Ministry of Finance websites. Check there before assuming your deadline is suspended.

You should distinguish an officially recognized platform outage from a failure in your own software or internet connection.

Penalties

Two different failures carry two different penalties. Sending a covered invoice late, meaning outside the 5 working day window, draws a fixed fine that depends on your taxpayer size. Issuing or booking a covered B2B invoice outside RO e-Factura altogether draws 15% of the invoice value.

ViolationPenalty
Late transmission, large taxpayersRON 5,000–10,000
Late transmission, medium taxpayersRON 2,500–5,000
Late transmission, other taxpayersRON 1,000–2,500
Issuing a covered B2B invoice outside the mandatory system15% of the total invoice value
Receiving and recording a covered B2B invoice outside the mandatory system15% of the total invoice value

These penalties are established under Article 13² of OUG 120/2021, as amended.

The late-transmission fine applies once per calendar month, covering every invoice whose deadline fell in that month, not once per late invoice. It also covers B2C reporting failures.

The 15% penalties cover B2B clearance violations. They are separate from the fixed fines for late transmission.

A buyer that records an invoice from outside the system also risks losing the VAT deduction.

Romania's other tax reporting systems

Romania operates several electronic tax reporting systems. They serve different purposes and may apply to the same business.

SAF-T (D406)

Romania's Standard Audit File for Tax (SAF-T) requires taxpayers in scope to submit structured accounting data through declaration D406.

Large taxpayers started in 2022 and medium taxpayers followed. Small taxpayers came into scope on January 1, 2025, with a grace period of six months for a first monthly report, or three months for a first quarterly one.

PFA, individual and family enterprises, liberal professions, and non-profits on simplified accounting are excluded, under ANAF Order 407/2025.

SAF-T does not replace invoice submission through RO e-Factura.

RO e-Transport

RO e-Transport monitors certain road movements of goods and uses a unique transport identification code (UIT). It is separate from RO e-Factura. Submitting an invoice does not automatically fulfill a transport reporting obligation.

RO e-TVA

RO e-TVA uses information available to ANAF, including e-invoice data and other tax records, to prepare pre-filled VAT return information. It is a separate VAT administration process and does not replace your obligation to submit invoices through RO e-Factura.

Romania's eInvoicing timeline

Romania has expanded the mandate in stages since 2021, and the lead times have been short. The five working day deadline that applied from January 1, 2026 was published on December 24, 2025. The CNP obligation was announced, postponed, then removed. Assume the current rules are the current rules, not the settled ones.

DateChange
October 2021OUG 120/2021 establishes the framework for RO e-Factura
July 1, 2022Mandatory B2G eInvoicing begins. B2B becomes mandatory for high fiscal risk products only
January 1, 2024Mandatory domestic B2B invoice reporting begins
July 1, 2024Full B2B clearance and delivery through RO e-Factura becomes mandatory
January 1, 2025Mandatory B2C invoice reporting begins; SAF-T rollout expands to small taxpayers
July 1, 2025Penalties for failure to report covered B2C invoices take effect
August 1, 2025VAT rates change to 21% standard and 11% reduced
January 1, 2026Transmission deadline changes to 5 working days; additional transactions involving non-established Romanian VAT-registered buyers come into scope
January 2026The CNP registration requirement is postponed
June 1, 2026Law 88/2026 removes the obligation for CNP-identified individuals and special-regime farmers. Both may opt in
July 1, 2030EU digital reporting under ViDA starts for intra-EU transactions

How Invopop helps with eInvoicing in Romania

Invopop extends coverage to Romania for B2B, B2G, and B2C through RO e-Factura.

When issuing, Invopop converts your invoice to CIUS-RO in UBL 2.1, checks it against ANAF's schematron before upload, and files it with RO e-Factura. The sealed XML ANAF returns comes back attached to the invoice, so you hold the legal version and not just the one you generated.

For receiving, invoices are synced from SPV and converted to GOBL, ready for your system to book. Receiving handles both UBL and CII so every invoice can be imported, and invoices are kept for as long as you need.

Each supplier needs to register once with Invopop, using its Romanian CIF. The person who holds the company's SPV certificate opens a registration link, accepts the terms, and authorizes Invopop on ANAF's own site. The certificate never leaves its owner, and Invopop never sees or stores it. Invopop renews access to ANAF automatically. You only need to renew the registration once a year, as ANAF requires.

You can run the whole flow in a sandbox workspace first, where everything goes to ANAF's test environment and has no fiscal value.

To get started, read the documentation or contact our team if you need help.

Frequently asked questions about Romania eInvocing

Yes. RO e-Factura is mandatory for domestic B2B and B2G invoices, and B2C invoices must be reported through the platform. Exports, intra-Community supplies, and qualifying fiscal receipts are out of scope.

No. For transactions covered by mandatory clearance, the legally recognized electronic invoice is the validated and sealed XML document transmitted through RO e-Factura. You can send a PDF copy for convenience, but it does not replace the official electronic invoice.

Since January 1, 2026, the deadline is 5 working days from the invoice issue date, and no later than 5 working days after the statutory issuance deadline. The previous requirement was 5 calendar days.

It depends on your Romanian establishment, VAT registration, and transactions. Since January 2026, Romanian-established suppliers must also submit invoices issued to non-established buyers registered for Romanian VAT. Assess your own obligations rather than assuming a Romanian VAT number creates the same ones as a local establishment.

You need a Romanian tax number (CIF) and a qualified digital certificate held by someone with SPV rights for the company, as legal representative or authorized person. From there you can file through ANAF's SPV portal or authorize a provider to connect through the API. Individuals identified by a CNP are no longer obliged to register, but can opt in through the Registrul RO e-Factura Opțional.

Keep reading