Compliance · 🇷🇴 Romania Live mandate

Romania — RO e-Factura mandatory clearance

RO e-Factura mandatory clearance universal since July 2024 — regulator: Agenția Națională de Administrare Fiscală (ANAF). Facts last refreshed: 2026-05-05.

Coverage model

Flowie operates a registered Peppol Access Point in this jurisdiction directly where we hold national accreditation, or via a vetted local partner registered with the in-country regulator where on-the-ground presence is required (KSeF, SDI intermediario, ZATCA service-provider, etc.). Either way, you call the same POST /v1/documents/send.

TL;DR

Romania's RO e-Factura is a clearance system: every B2B invoice is submitted to ANAF, validated, and a signed PDF copy is returned before legal delivery.
Universal B2B since 1 July 2024.
Format: UBL or CII with the Romanian RO_CIUS.
Plus: SAF-T (D406) monthly reporting for large taxpayers (extended to all by 2026).

Deadlines

Date	Who	What
2022-07-01	High-fiscal-risk products (B2B)	RO e-Factura mandatory for selected sectors.
2024-01-01	All B2B reporting (5-day window)	Reporting obligation universal.
2024-07-01	All B2B clearance	Full clearance — invoices invalid without ANAF acceptance.
2025-01-01	B2C extension	RO e-Factura extended to B2C invoices.
2026-01-01	All taxpayers SAF-T	D406 monthly reporting universal.

Background

Romania's mandate is structurally the same as Italy's SDI: clearance, not just reporting. The difference is speed of rollout — Romania went universal in 18 months, the most aggressive timeline in the EU. Flowie's ANAF integration handles certificate-based authentication, UBL conversion, and clearance polling transparently.

Format profile

RO_CIUS on top of UBL 2.1 or CII.
SAF-T (D406) for tax reporting.
Romanian CUI: RO + 2-10 digits.

Required fields

seller.taxId.cuistringrequired

Romanian fiscal code (CUI), with or without RO prefix.
buyer.taxId.cuistringrequired for B2B

Buyer CUI.

Public sector (B2G)

Hub	Peppol identifier scheme	Lookup
RO e-Factura (ANAF)	`RO-CUI-<cui>`	https://efactura.mfinante.ro

RO e-Factura covers public and private alike — single clearance entry point.

B2B reporting / clearance

RO e-Factura — Clearance + signed PDF return; invoice not legally valid until ANAF accepts.

Lifecycle status	Reported as
`issued`	Submitted; ANAF returns signed XML.
`rejected`	Schema or business-rule failure.
`cancelled`	Cancellation message.

Error codes

Code	Meaning	Fix
`RO-EFACT-101`	CUI not registered with RO e-Factura.	Verify the buyer is registered in the ANAF directory.
`RO-EFACT-205`	Schema validation failure.	Inspect `error.details`.

Testing in sandbox

What you want to test	How
RO e-Factura happy path	Seller CUI `RO12345678`, buyer CUI `RO87654321`; sandbox returns signed XML.
Force ANAF rejection	`simulateCompliance: "reject_RO_EFACT_101"`.

FAQ

How long does ANAF take to clear?

Typically < 30 seconds, occasionally up to a few minutes during peaks. Flowie's /v1/documents/send blocks until clearance returns; if you need async, use ?waitFor=submitted.

References

Primary sources (government / regulator / standards body):

EU Commission · eInvoicing in Romania — Pan-EU reference factsheet.
ANAF · National Tax Administration Agency — Tax authority — RO e-Factura mandate.
ANAF · SPV Virtual Private Space — Mandatory communication channel for e-Factura.
Ministry of Finance Romania — Finance ministry — Law 199/2020 transposition.

Industry analyses (vendor trackers — useful for cross-referencing):

ecosio · Romania ANAF RO e-Factura — Industry analysis — clearance model details.