Romania e-Factura: SAP Integration Guide

Romania e-Factura is a live, enforced clearance system: in-scope invoices must be submitted as XML to ANAF’s RO e-Factura platform, and the rules have changed several times a year since launch. SAP teams need a controlled way to generate, validate, submit, and monitor invoice data while preserving traceability to source documents — and a process for absorbing rule changes.

How should SAP teams implement Romania e-Factura?

SAP teams should implement Romania e-Factura by confirming document scope, source data, ANAF connectivity, authentication, response handling, corrections and operational monitoring before choosing the integration path. SAP DRC, an SAP-native add-on or another approved architecture should be selected only after verifying the exact system release and scenario coverage.

Executive Summary

Mandate name	Romania RO e-Factura
Current status (as of July 2026)	B2B e-invoicing mandatory since July 2024 for transactions with a Romanian place of supply; B2C reporting mandatory since January 2025; simplified invoices in scope since January 2025 (except fiscal cash register receipts).
Submission deadline	Five working days from invoice issuance, but no later than five working days after the statutory invoice-issuance deadline, for both B2B and B2C transmissions under OUG 89/2025.
Recent scope changes	From 1 January 2026, Romanian-established taxable suppliers must transmit invoices for Romanian-place-of-supply transactions to non-established customers registered for Romanian VAT, subject to statutory exceptions; this does not create a general issuance duty for every foreign VAT registrant. Law 88/2026 made use optional from 1 June 2026 for CNP-identifying economic operators and the other specifically listed categories.
Business risk	For an invoice exchanged outside RO e-Factura between in-scope established B2B parties, the issuer and recipient can each face a fine equal to 15% of the invoice value. Late-transmission offences use separate taxpayer-category fine bands.
SAP impact	SD billing, FI invoices, tax codes, master data, XML generation (RO_CIUS), submission workflow, and response handling.
Recommended next step	Review SAP invoice scenarios against the current scope and confirm the 5-working-day submission workflow is monitored.

What Is the Requirement?

Invoices are prepared in Romania’s RO_CIUS XML format (based on EN 16931) and uploaded to the RO e-Factura platform, which validates each file and applies an electronic seal; the sealed XML is the legally valid invoice for in-scope B2B transactions. Buyers retrieve invoices from the platform rather than relying on what arrives by e-mail. Romania pairs this with the related RO e-Transport regime for goods movements, which draws on the same SAP logistics data.

Business Impact for Finance and Tax Teams

Finance teams need timely, accurate invoice processing and visibility into rejected or incomplete records inside the 5-working-day window. Tax teams need assurance that reported data matches SAP source documents — and, given how often the scope has moved (2024, 2025, and twice in 2026), someone must own regulatory-watch for Romania specifically.

How This Impacts Your SAP Environment

• Billing and accounting data must be mapped to the RO_CIUS invoice structure, including simplified invoice scenarios.
• Customer and tax master data must be complete enough for validation, including the cases affected by the 2026 scope changes.
• Submission results, seal confirmations, and errors need process ownership within the deadline window.
• AP processes should retrieve and reconcile the platform-sealed invoices, not just supplier-sent copies.

How S4FN Supports Romania e-Factura Compliance

S4FN can review SAP source data, XML mapping, validation workflow, authority communication assumptions, and response handling. Related reading: Romania RO e-Transport from an SAP perspective and Romania SAF-T D406 readiness.

Official sources

• Romanian legislation portal — RO e-Factura legal framework
• Romanian legislation portal — Law 88/2026

Regulatory content verified: 10 July 2026.

Verified on: 10 July 2026. Confirm the current legal scope, authority technical package and SAP-supported scenario before implementation.