Skip to main content

Compliance questions

Yes. Taxable persons established in Romania must send their domestic invoices to RO e-Factura. It is mandatory for invoices to public bodies (B2G) since July 2022 and for invoices to businesses (B2B) since July 2024. Invoices to consumers (B2C) must be reported since January 2025.
No. RO e-Factura is a national clearance platform that the Ministry of Finance and ANAF run. Every domestic invoice goes to this one platform through its API or through SPV. There is no Peppol directory and no network of access points in the domestic flow.
5 working days from the issue date, since 1 January 2026. Before that date, the deadline was 5 calendar days. The supplier must issue the invoice by the 15th of the month after the supply.
Yes, when the supplier issues an invoice to the consumer. The supplier reports the invoice to RO e-Factura and gives it to the consumer in the usual way. A fiscal cash register receipt (bon fiscal) that meets the conditions of a simplified invoice does not go to RO e-Factura.
A B2C invoice (factură) is an invoice that the supplier issues to a consumer. The supplier reports it to RO e-Factura and gives it to the consumer. A bon fiscal is a receipt from a fiscal cash register, under OUG 28/1999. Its data reaches ANAF through the cash register, not through RO e-Factura. A bon fiscal that meets the conditions of a simplified invoice does not go to RO e-Factura.
Exports and intra-Community supplies are out of scope. Qualifying fiscal cash register receipts are also out of scope. Since January 2026, invoices to buyers that are registered for VAT in Romania but not established there are in scope.
No. Romania has no certification scheme for e-invoicing providers. A provider uses a qualified certificate for electronic signature. Each business authorizes the provider in SPV to act for its tax number (CIF).
A late transmission costs RON 1,000 to 10,000, based on the size of the taxpayer. An invoice issued outside the system costs the supplier 15% of its value. A buyer that books an invoice from outside the system also pays 15% of its value and cannot deduct the VAT.

Invoicing questions

Romania
UBL 2.1 in the Romanian profile of EN 16931, called CIUS-RO (version 1.0.1). RO e-Factura also accepts CII (D16B). The platform checks the invoice against the EN 16931 rules and the national BR-RO rules.
No. The legal invoice is the XML file that the Ministry of Finance seals after validation. A PDF has no legal value, but you can give one to your customer as a readable copy.
You cannot cancel a sealed invoice. Issue a credit note (type 381) or a corrective invoice (type 384) that references the original invoice.
No. The platform statuses show only whether the invoice passed validation. The buyer settles a dispute directly with the supplier, and the supplier corrects the invoice with a new document.
Since 1 August 2025, the standard rate is 21% and the reduced rate is 11%. If an invoice is in another currency, the VAT amounts must also show in RON.
For 60 days. After that, ANAF archives the files, and a copy is available only on request. Keep your own copy of each sealed invoice.
Yes. The buyer issues the invoice in the supplier’s name, with type code 389.
RO e-Factura
Invoices that declare the ro-efactura-v1 addon: standard invoices (380), invoices for accounting purposes (751, with the accounting tag), self-billed invoices (389, with the self-billed tag), credit notes (381) and corrective invoices (384).
Usually a few minutes. After the upload, the Send e-Factura XML to ANAF step waits and checks the upload status until ANAF answers ok or nok. The job finishes when ANAF has decided.
When ANAF accepts the invoice, Invopop attaches the official XML returned by ANAF to the invoice entry as anaf-efactura.xml, next to the generated efactura.xml. The archive is also kept in Invopop’s database.
The job fails with the errors ANAF returned. Correct the invoice and run the workflow again; a rejected invoice can be sent again.
No. Invopop never uploads an accepted invoice twice. To change an accepted invoice, issue a credit note or a corrective invoice that references it.
Invopop picks the ANAF upload options from the invoice itself. An invoice to a customer without a tax ID goes to the B2C endpoint, and a self-billed invoice is uploaded with the customer’s CIF and flagged as autofactura. No workflow configuration is needed.

Registering supplier questions

A Romanian tax ID (CIF) and a qualified digital certificate of a person with access to the company’s SPV (Spațiul Privat Virtual) as legal representative or authorized person. The certificate holder opens the registration link, accepts the terms and authorizes Invopop on ANAF’s site. Invopop never sees or stores the certificate.
Yes. An accountant or representative with SPV rights for several companies can use the same certificate for all of them, but each company is a separate party in Invopop. Run the registration workflow and complete the authorization once per party.
Yes. If you register parties for your own customers, fetch the terms with GET /apps/gov-ro/v1/entry/{silo_entry_id}/terms, show them in your own interface and record your customer’s acceptance with POST on the same path. The response carries the ANAF link to send to the certificate holder. See the white label registration flow.
Invopop records the acceptance together with the exact terms accepted and when, whether they were accepted on the registration page or through the API. Nothing is stored on the party entry. The terms are accepted on every registration, including a renewal.
Common reasons:
  • Wrong certificate: the certificate chosen in the browser does not belong to a person with SPV rights for the company’s CIF.
  • SPV rights missing: the certificate holder is not registered in SPV as legal representative or authorized person of the company.
  • Party not Romanian: the party’s tax_id country must be RO.
  • Terms not accepted: the ANAF authorization only goes through once the terms have been accepted.
  • Registration expired: the terms of a registration can only be accepted while it is open. One left unaccepted for 32 days shows registration expired, register the party again: run the registration workflow again and use the new link.
After fixing the cause, open the same registration link again.
The page shown at the end of the authorization tells whether it succeeded, and shows the error otherwise. The workflow error logs in the Invopop Console have more detail.
One year. Invopop renews access automatically during that year, after which the party has to complete the registration again. Notifications before the deadline are in development and will soon be supported through the app configuration.
Yes. In an Invopop sandbox workspace, every call goes to ANAF’s test environment, so invoices sent there have no fiscal value. The registration still uses a real digital certificate, since ANAF authenticates the same way in both environments.
Run the RO unregister party workflow on the party. It removes the ANAF authorization from Invopop and unsubscribes the party from periodic sync. To receive again, run the registration workflow again.

Receiving questions

Invoices other companies issued to the registered party and that ANAF made available in its SPV, from the moment the party completed registration. Invoices received before registration are not imported.
No. The RO sync received invoices workflow creates one import job per received invoice, using the workflow set as Import Workflow in its Receive all new invoices from RO e-Factura step. Don’t run the import workflow directly.
Each sync picks up from where the last successful one finished, so no invoice is missed. ANAF keeps messages for 60 days, so a party that stops syncing for longer loses the older ones.
The ANAF archive is kept in Invopop’s database, and a new invoice entry is created in the silo with the invoice converted to GOBL. The workflow then sets the folder and state, typically Invoices · Expenses and Registered.

Participate in our community

Ask and answer questions about Romania’s regulation →