Romania: Every Instrument at Once
Romania runs clearance e-invoicing, real-time transport tracking, a monthly standard audit file and a pre-filled VAT return, and is now building the tools to compare them against each other. No other EU country has assembled as complete a set. The work has moved from connecting to reconciling.
Country briefing · September 2026 · CFOs, Tax and Finance leads
Download Full Briefing (PDF, EN)5 working days
To transmit an invoice to RO e-Factura, for invoices issued from 1 January 2026
15%
Penalty on the value of an in-scope B2B invoice issued or received outside the system, for both parties
UIT
The transport code that must exist before high-risk or international goods move
D406
The standard audit file, filed on the VAT period and now being compared with the VAT return
Key takeaway for finance and tax leaders: in Romania the connections are built. What most companies need now is proof that the four instruments agree, before ANAF's tools prove that they do not. The question to ask this month: would our D406 for last month agree with our VAT return and with what ANAF holds in e-Factura?
Four Instruments, One Data Set
Between 2022 and 2025 Romania introduced, in quick succession, a standard audit file, clearance e-invoicing for business transactions, transport tracking for high-risk goods and all international movements, and a pre-filled VAT return. Each was a project. Together they give the tax authority the same transactions from four angles, and the authority is now testing how to compare them.
The Four Instruments
| Instrument | What it captures | Since | Model |
|---|---|---|---|
| RO e-Factura | Every B2B invoice, validated and sealed by ANAF before it is legally an invoice | 2024 | Clearance |
| RO e-Transport | Movements of high-risk goods and all international transport, before departure | 2022–24 | Pre-declaration |
| SAF-T (D406) | The ledger, partners, invoices and payments, per VAT period; assets yearly; stock on request | 2022–25 | Periodic file |
| RO e-TVA | A pre-filled VAT return built from the data the authority already holds | 2024 | Informational |
What This Means for a Finance Team
The authority knows your invoices before your VAT return does. Every B2B invoice is cleared centrally, so the return is checked against a record you cannot amend afterwards.
An invoice is in e-Factura, in D406 and behind the VAT return; the goods may be in e-Transport. Inconsistency between them is the new risk.
Missing clearance, a missing transport code or a late file is detected automatically, not by inspection.
Who Owns Which Instrument, and Where the Gaps Are
| Instrument | Usual owner | Usual gap |
|---|---|---|
| e-Factura issuing | Billing and IT | Rejections with no daily owner |
| e-Factura receiving | Accounts payable, often informally | Invoices posted from email, not the system |
| e-Transport | Logistics | No link to invoicing data |
| D406 | Tax or an external provider | Filed, but never reconciled |
RO e-Factura: The Legal Invoice Is the One ANAF Sealed
Romania operates a clearance model. The invoice is transmitted to the national system, validated, and returned with the Ministry of Finance's seal. Only that sealed XML is the legal invoice: a PDF or paper copy has no fiscal value, however identical it looks.
The invoice is produced in the national format
A Romanian specialisation of the European standard (RO CIUS), in UBL or CII.
Sent to the system within five working days of issue
Late transmission is penalised by taxpayer size.
Checked against the specification
A rejected invoice has not been issued in the eyes of the law.
ANAF seals the validated XML
And makes it available to the buyer through the national system.
Buyers download their supplier invoices from the same system
This is the inbound side of the obligation.
Why Invoices Are Rejected
| Cause | Where it is fixed |
|---|---|
| Partner tax data | Master data: wrong or missing tax identifiers and addresses |
| Tax codes and categories | Configuration: codes that carry a rate but not the right category or exemption reason |
| Units and classifications | Master data and mapping: local units, missing codes on public-sector invoices |
| Arithmetic and rounding | Billing logic: totals the specification calculates differently |
Penalties
| Failure | Penalty |
|---|---|
| Late or missing transmission | Tiered by taxpayer size: from RON 1,000 for small taxpayers up to RON 10,000 for large ones |
| In-scope B2B invoice issued or received outside the system | 15% of the invoice value, applied to both issuer and recipient |
What the 15% Rule Means for Accounts Payable
The recipient penalty is the feature most often overlooked. A company that accepts and books a supplier invoice that was never cleared is itself exposed to a penalty on the invoice value. AP has to verify that every domestic B2B supplier invoice exists in e-Factura, ideally by sourcing supplier invoices from the system itself rather than from email.
Good Practice on the Issuing Side
Transmission as part of billing, not a separate batch.
Rejections visible the same day, with an owner.
Good Practice on the Receiving Side
Supplier invoices downloaded from the system and matched.
Nothing posted that has no e-Factura record.
Invoices to public bodies must also carry procurement classification codes. Intra-EU transfers of goods are outside the system.
What Changed in 2026: Tighter in One Place, Looser in Another
Romania adjusts its rules frequently, usually through emergency ordinances. 2026 brought changes that matter to companies running SAP: one tightened the clock, one clarified scope, and one rolled part of the regime back.
Working days, not calendar days
The five-day transmission deadline now counts working days, for invoices issued from 1 January 2026. Invoices issued earlier keep the old rule.
Non-established buyers
Invoices to buyers with a Romanian VAT number but no establishment, where the supply is in Romania, must go through the system, and still be sent to the buyer by the usual route.
Most B2C removed
Invoices to individuals who give no tax number, or identify with their personal number, generally no longer have to go through the system, unless the customer has opted in (Law 88/2026).
Suppliers can deregister
Where the change removes their obligation, suppliers may ask to be removed from the relevant registers.
The B2C Rollback in Context
Consumer invoices entered the system on a mandatory basis in 2025, with penalties from mid-2025. The 2026 law removed most of that for invoices to individuals, but not all, and the treatment of mixed cases is not yet fully settled. Companies that built B2C transmission should not simply switch it off: the remaining obligations, and the voluntary register, still need handling.
And Small Businesses?
Some commentary reported a postponement of B2B e-Factura for small businesses to 1 July 2026, and the briefing found no clear Romanian legal basis beyond individuals working under their personal number. Either way, that date has now passed: treat e-Factura as applying to businesses of every size, and confirm with your adviser.
Decisions to Take
Which consumer flows still need transmission.
Whether to keep sending voluntarily for simplicity.
Risks to Avoid
Switching off a flow that is still in scope.
Treating a business customer as a consumer.
A 2026 Change Checklist
- Deadline monitoring counts working days for 2026 invoices.
- Non-established Romanian-registered buyers routed through the system.
- Consumer flows reviewed against the July rules.
- Register status reviewed where obligations fell away.
Why Frequent Change Is Itself a Risk
Each change is modest; the cumulative effect is a configuration that drifts. Deadlines counted in calendar days for some documents and working days for others, scope rules that changed mid-year, registers that can now be left: all of it needs someone who reads the ordinances and translates them into system behaviour.
Romanian rules change frequently through emergency ordinances and sources disagree on detail, including the treatment of mixed B2C cases; confirm the current position with ANAF or your tax adviser.
RO e-Transport: A Code Before the Lorry Leaves
RO e-Transport requires movements of goods to be declared before they start, producing a unique code, the UIT, that must accompany the goods. The penalties are among the harshest in any regime we cover, and they reach the goods themselves.
The Regime at a Glance
| Element | Position |
|---|---|
| Domestic scope | High-fiscal-risk goods (including produce, alcohol, clothing, footwear and steel) above weight or value thresholds |
| International scope | All international transport, since 1 January 2024 |
| When | The code is generated no more than a few days before the movement |
| Validity | Five calendar days for domestic movements; longer for intra-EU acquisitions |
| Penalties | Substantial fines for companies and drivers and, from a repeated breach, confiscation of part or all of the goods |
Why It Belongs in a Finance Briefing
Goods, quantities, values and partners: if these differ between the transport declaration and the invoice, the difference is visible.
It sits in logistics, but confiscation of goods is a balance-sheet event, not a fine.
Who generates the code, and with what data, needs to be agreed contractually.
What Good Looks Like
- Code generation triggered from the delivery or shipment in the ERP.
- The code printed on transport documents automatically.
- Validity monitored for delayed departures.
- A clear rule for which movements are in scope.
- Logistics providers' responsibilities written down.
- Declared values reconcilable with invoices.
Who Does What in a Shipment
| Party | Typical responsibility (to be confirmed contractually) |
|---|---|
| Shipper | Declares the movement and obtains the code from its own data |
| Carrier | Carries the code and the vehicle data that must match it |
| Logistics provider | Often generates declarations on the shipper's behalf, which moves the work, not the liability |
The Failure Mode
A shipment delayed beyond the code's validity, or an urgent dispatch issued outside the normal process, leaves without a valid code. The penalty applies at the roadside, not at month-end, which is why e-Transport needs an operational owner in logistics as well as a configuration in the system.
SAF-T and the Reconciliation Machine
Romania's standard audit file, D406, has been fully phased in since 2025. It is filed on the VAT period, monthly or quarterly, with the asset file yearly and stock data on request. What changed in 2025–26 is not the file but what ANAF does with it.
The D406 Files
| File | Content | Deadline |
|---|---|---|
| Periodic D406 | General ledger, partners, invoices and payments | Last day of the month after the VAT period |
| Assets | The fixed-asset register | Annually, with the financial statements |
| Stock | Inventory and movements | On request, with at least 30 days to respond |
What ANAF Has Been Building
Reconciliation pilot
A pilot with a group of companies comparing each line of the VAT return with SAF-T data, with the stated aim of pre-filling the return and eventually replacing it.
Free verification tools
A D406 validator and a D406-to-VAT-return comparison, in public testing. They run locally and send nothing to ANAF.
Pre-filled VAT return (e-TVA)
Still provided for information; the obligation to respond to compliance notifications was repealed in 2026.
Why This Matters More than Any Single Deadline
The comparison ANAF is testing is the one you should run first. Its own tools let you see your file the way ANAF will, before ANAF does.
Once the return is built from data ANAF holds, a difference becomes something you explain, not something they find.
Mapping, tax codes and partner data decide whether D406 agrees with e-Factura and the return.
What a Monthly Reconciliation Should Cover
| Comparison | What a difference suggests |
|---|---|
| Issued ↔ sealed in e-Factura | Sales not legally invoiced |
| Posted purchases ↔ e-Factura | Recipient-side penalty exposure |
| D406 ↔ VAT return | The comparison ANAF is automating |
| Transport declarations ↔ invoices | Movements and sales that do not agree |
Use ANAF's Tools Now
The validator and comparison tools are free, local and in testing this autumn. Run last quarter's D406 through them. The result is a preview of the questions the next phase of Romanian compliance will ask.
What It Means for Your SAP System
Romania is one of the few countries where both halves of SAP Document and Reporting Compliance carry weight. The electronic-document side handles e-Factura and e-Transport; the statutory reporting side produces D406. Both read the same billing, logistics and accounting documents, which is what makes the reconciliation possible, if they are designed together.
What the SAP Design Has to Cover
| Obligation | What the design has to cover |
|---|---|
| e-Factura outbound | Transmission within five working days, rejections handled daily, the sealed XML stored against the document |
| e-Factura inbound | Supplier invoices sourced from the system, matched and posted: nothing posted without a record |
| e-Transport | Codes generated from deliveries, printed on documents, validity monitored |
| D406 | Mapping, partner data and volume handled; the file reconciled before it is filed |
The Platform Question
Available on classic SAP ERP: the electronic-document framework, e-Factura and e-Transport. Requires a modern platform: the statutory reporting side, D406.
A Romanian entity on an older SAP platform therefore typically produces D406 some other way (the cloud edition, a partner product or a custom extract), which splits the obligations across tools and makes reconciliation harder. Country content and prerequisites should be confirmed with SAP for your exact release.
Where Romanian Landscapes Are Usually Weakest
Inbound invoices sourced from email rather than e-Factura.
Configured outside SAP, with its own data.
Produced by a separate tool and never compared.
Ordinance changes applied late or not at all.
Design for Change, Not for the Current Rule
Romania changes rules several times a year. Scope conditions, deadline logic and consumer handling should be held as configurable rules with an owner, not buried in custom code; otherwise every ordinance becomes a development project.
The e-TVA Signal
The pre-filled VAT return is informational today, and the duty to answer its notifications was repealed. But the direction is clear: ANAF intends to build the return from data it already holds. Every inconsistency between your systems and ANAF's record will eventually be a line you have to explain.
Five Questions for Whoever Supports Your System
- How many e-Factura rejections last month, and who cleared them?
- Can we prove every posted supplier invoice exists in e-Factura?
- Which movements generate a transport code, and who checks validity?
- How is D406 produced on our platform, and is it reconciled before filing?
- Who translates new ordinances into configuration, and how quickly?
A Health Check: Twelve Questions
Twelve questions, and what a poor answer costs. Each answer should rest on a number or a document, not on an opinion.
The Twelve Questions
| # | Question | If the answer is unclear |
|---|---|---|
| 1 | Invoices issued against invoices sealed by ANAF, last month? | Sales that do not legally exist as invoices |
| 2 | How many rejections are open, and how old? | Five working days pass quickly |
| 3 | Is every posted supplier invoice present in e-Factura? | A 15% penalty on the recipient side |
| 4 | Are deadlines counted in working days for 2026 invoices? | A configuration still on the old rule |
| 5 | Are non-established buyers' invoices transmitted? | A 2026 scope change missed |
| 6 | Which B2C flows still transmit, and why? | Either unnecessary effort or a missed obligation |
| 7 | Do all in-scope movements carry a valid transport code? | Roadside fines, and goods at risk |
| 8 | Who owns delayed shipments with expiring codes? | Goods leaving on an invalid code |
| 9 | Does D406 agree with the VAT return? | The exact difference ANAF is building tools to find |
| 10 | Have we run ANAF's own verification tools? | A free preview of the next enquiry, unused |
| 11 | Is the asset file ready ahead of the financial statements? | An annual deadline met in a rush |
| 12 | Who reads new ordinances and acts on them? | Configuration drifts behind the law |
Questions 1, 3 and 9 are the ones to fix first. The first two protect both sides of every invoice; the third is where Romanian compliance is heading next. Questions 4 to 6 concern 2026 changes that many configurations have not yet absorbed; they are quick to check and usually quick to fix.
The First Thirty Days
Count issued against sealed, and posted against present
Run ANAF's D406 tools, and check the 2026 changes in configuration
Assign owners per instrument, and agree a monthly reconciliation
What We Typically Find
Issuing well controlled; receiving barely controlled.
Cleared only when someone complains.
A B2C configuration nobody revisited after July.
Owned by logistics with no link to finance.
Filed on time but never reconciled.
No routine for reading them.
How 30 Advisory Can Help
A founder-led boutique specialised in SAP DRC & e-invoicing compliance, S/4HANA Finance optimisation and CFO/CIO strategic advisory. In Romania the connections are built; what most companies need now is proof that the four instruments agree, before ANAF's tools prove that they do not.
Reconciliation review, three weeks
e-Factura completeness on both sides, 2026 changes applied, e-Transport coverage, and D406 run through ANAF's own tools against the VAT return. Output: a quantified gap list.
Remediation
Inbound sourced from e-Factura, rejection ownership, transport codes from deliveries, D406 mapping fixed, and a monthly reconciliation built in. Output: four instruments that agree.
Run and legal change
Ordinances read and translated into configuration, changes applied in controlled windows, and the design extended to your other countries. Output: compliance that keeps up.
A Sensible First Step
Run last quarter's D406 through ANAF's free comparison tool, and count last month's supplier invoices posted without an e-Factura record. Two numbers, both available within days, and between them they show where Romanian compliance is heading for your company.
What Makes This Different
We reconcile across instruments, because each is usually owned by a different team and the risk sits between them. We start with receiving, the most exposed and least controlled part. We use the authority's own tools. And we are not your tax adviser: we work alongside the people who are.
If You Are Ahead
If both sides of e-Factura reconcile and D406 agrees with the return, the remaining work is small: a routine and an owner. We will tell you that, and keep the engagement short.
Founder-led
Finance + SAP DRC depth
Multi-country: Italy, Türkiye, Spain
Boutique agility
Sources consulted 25 September 2026: European Commission country sheet; PwC Romania, EY, KPMG and Accace alerts on e-Factura, the 2026 ordinances, Law 88/2026 and e-Transport; ANAF communications on the SAF-T pilot; Sovos and PwC on D406; vatcalc, VATupdate and Romanian practitioner commentary. SAP behaviour from the SAP Help Portal and partner commentary.
Prepared by 30 Advisory, October 2026 (status at 5 October 2026). Information only — not tax, legal or accounting advice. Romanian rules change frequently through emergency ordinances, and sources disagree on detail, including the treatment of mixed B2C cases, the dates of certain changes and the SAF-T pilot. Confirm the position for your own entity with ANAF or a qualified adviser before acting.
Not Sure What This Means for Your SAP Landscape?
We'll review your e-Factura completeness on both sides, your e-Transport coverage and your D406 against the VAT return in a 1-hour diagnostic session.
Schedule Assessment (1 hour)