Business Central and Romanian Compliance: SAF-T, e-Invoice, and e-Transport Explained

If you operate a company in Romania — or you’re expanding into the Romanian market — you’ve likely heard the acronyms: SAF-T, e-Factura, e-Transport. And if you’re running Microsoft Dynamics 365 Business Central, you’ve likely asked: does standard BC handle these out of the box?

The short answer is no — and that’s where many international companies get caught off guard. Romania’s tax authority (ANAF) has executed one of the most aggressive digital compliance transformations in the European Union over the past four years. Standard Business Central, without localization, won’t keep you compliant.

This article explains what each requirement entails, who it applies to, what the timelines are, and — importantly — how to close the gap between standard Business Central and Romanian compliance. We’ll keep it practical, not panic-inducing.

---

The Big Picture: Romania’s Digital Compliance Transformation

Between 2022 and 2026, ANAF has rolled out — or is currently rolling out — a suite of mandatory electronic reporting obligations that touch virtually every transaction a Romanian company makes:

1. SAF-T (D406) — a structured XML export of your entire general ledger, sales, purchases, inventory, and assets, submitted monthly or quarterly
2. RO e-Factura (e-Invoice) — every B2B and B2C invoice must pass through ANAF’s central clearance platform before it is legally valid
3. e-Transport — a real-time declaration system for goods movement, initially for high-risk products, now covering international transport broadly
4. e-TVA — pre-filled VAT returns, cross-validated against your D406 submissions (pilot phase running through 2026)

This isn’t a theoretical future state. These obligations are live, with enforcement and penalties. And ANAF is actively cross-referencing data across systems — if your D406 doesn’t match your D300 VAT return, expect a 20-day window to explain the discrepancy.

---

SAF-T (Declarația Informativă D406)

What It Is

SAF-T stands for Standard Audit File for Tax, an OECD-defined international standard that Romania adopted under ANAF Order 1783/2021 as the Declarația Informativă D406. It’s a single XML file — validated against a strict ANAF schema — that contains a complete digital copy of your accounting records for the reporting period.

A D406 submission includes:

• General Ledger journal entries
• Sales and purchase invoices (master and transactional data)
• Payments and receipts
• Customer and supplier balances
• Inventory movements (on request)
• Fixed asset registers (annual)

That’s over 390 mandatory data fields in a single file, with a 500 MB maximum file size.

Who Must Submit, and When

Taxpayer Category	SAF-T Obligation Start
Large taxpayers	January 2022
Medium taxpayers	January 2023
Small taxpayers	January 2025
Non-resident entities with Romanian VAT registration	January 2025

Frequency depends on your VAT reporting period: monthly for monthly VAT filers, quarterly for quarterly filers. Annual asset declarations are due by the end of May of the following year. Inventory files are produced on ANAF request.

Where Standard BC Falls Short

Business Central’s global (W1) version does not produce D406-compliant XML. You need a certified Romanian localization module that:

• Maps your chart of accounts and dimensions to Romanian fiscal categories
• Applies Romanian tax posting rules (VAT posting setup, tax groups, etc.)
• Generates the D406 XML with the correct structure, validation, and electronic signature
• Handles the file split logic for datasets exceeding 500 MB

Without this module, you’re either manually assembling D406 files — a process that is error-prone and borderline impossible at any real volume — or you’re non-compliant. Neither is sustainable.

---

RO e-Factura (Electronic Invoice)

How It Works

Romania’s e-invoicing system is a clearance model: every invoice passes through ANAF’s central RO e-Factura platform via the Spațiul Privat Virtual (SPV). ANAF validates the invoice against the RO_CIUS UBL 2.1 standard (aligned with EN 16931 at the European level). Only after ANAF applies its digital seal is the invoice legally valid.

Critically, suppliers do not send invoices directly to customers. Both parties interact with the central platform.

Scope and Timeline

• B2G (business-to-government) — mandatory since mid-2020
• B2B (domestic) — mandatory since July 2024 for all businesses; SMEs (turnover under €500,000) have an extension to July 2026
• B2C — mandatory since January 2025; all consumer invoices must be reported through RO e-Factura

The submission window is 5 working days from the invoice issue date (amended from 5 calendar days under GEO 89/2025). Archiving requirement: 10 years for general documents, 25 years for capital goods. All invoices must retain the Ministry of Finance digital seal alongside the original XML.

What You Need in Business Central

Standard BC’s electronic document framework can handle Peppol BIS 3.0 and several national formats — but not the RO_CIUS UBL 2.1 profile required by ANAF. A certified e-Invoice module should:

• Generate the RO_CIUS UBL 2.1 XML for sales invoices and credit notes
• Transmit directly to ANAF SPV through the API
• Receive and process inbound purchase invoices from the platform
• Handle ANAF validation responses and error resolution
• Archive the sealed XML for the full retention period
• Support both B2B and B2C transmission from the same interface

---

e-Transport (RO e-Transport)

What It Is

The e-Transport system requires taxpayers to declare transport operations for goods moving on Romanian territory before the transport begins. ANAF issues a unique UIT code (unique transport identifier) that must accompany the goods. The system was initially targeted at high fiscal risk products (alcoholic beverages, minerals, construction materials, clothing and footwear, ferrous metals) but has since expanded to cover all international road transport.

Key Dates

• July 2022: mandatory for declared high-risk goods
• January 2025: scope expanded to all international transport; penalties enforced
• Penalties for non-compliance: fines up to 50,000 RON for legal entities, plus potential confiscation of goods valued above 10,000 RON

The Integration Challenge

If your Business Central deployment handles logistics — purchase receipts, sales shipments, transfer orders between warehouses — you need the e-Transport module to:

• Detect transport operations in BC (inbound, outbound, transfers) that trigger e-Transport obligations
• Generate the XML declaration with correct goods classification and transport data
• Submit to ANAF SPV and retrieve the UIT code
• Store the UIT code on the relevant BC documents for audit purposes

Manual UIT generation is feasible at a handful of shipments per month. At any real volume, automation isn’t optional — it’s the difference between running your logistics and running a compliance department.

---

Additional Compliance Modules Worth Knowing

Romanian fiscal compliance doesn’t end with SAF-T, e-Factura, and e-Transport. Depending on your industry, you’re likely to need:

• Romanian Localization Package — the foundation. Adapts Business Central to Romanian fiscal and accounting regulations: chart of accounts, VAT posting, journals, and statutory reports. Without this, none of the other modules work correctly.
• Retail Fiscalization — if you operate POS in Romania, you must connect fiscal cash registers to ANAF in real time. For LS Central and Business Central POS scenarios, this requires a certified fiscalization module that communicates with approved fiscal devices.
• ANAF Partner Check — a practical protection module that lets you query ANAF’s database for VAT status, registration validity, and partner details. Running this check on new customers and vendors reduces the risk of unknowingly transacting with invalid VAT-registered entities.
• E-Waste / Green Tax — Romania imposes an environmental contribution on electronics. If you import, distribute, or sell electronic products, you need reporting and calculation automation.

All of the above are available as ready-made, certified modules from Vanguard 360 — built from real implementation experience and refined across dozens of client projects.

---

Why This Matters for Your Business

Here’s the thing: Romanian compliance is not a “nice to have” layer you can defer until after go-live. It is a must-operate layer, and it has to work from the moment you issue your first Romanian invoice or file your first tax declaration.

Companies that treat it as an afterthought end up with:

• Manual, spreadsheet-based compliance processes that eat hours every month
• Inconsistent data between their ERP and what ANAF receives
• Penalties for late or incorrect submissions
• Audits triggered by mismatches between D406 and e-Factura declarations

The right approach is to build compliance into the implementation from the start. A proper Business Central implementation for Romania integrates the localization and compliance modules during the solution design phase — not as a post-go-live patch.

---

Getting It Right

Romania’s compliance landscape will continue to evolve. The D406-to-D300 cross-validation pilot running through 2026 is just the beginning. The EU’s VAT in the Digital Age (ViDA) directive will bring additional reporting obligations across all member states in the coming years.

The best time to get compliant was when the regulations launched. The second-best time is now — before ANAF’s automated reconciliation systems flag your company for review.

If you’re evaluating Business Central for a Romanian operation, or you’re already on BC and need to close the compliance gap, we’d be happy to talk through your specific situation. Book a free discovery call — no obligation, no pitch. Just honest advice from a team that has done this dozens of times.

---

FAQ: Romanian Compliance & Business Central

Does standard Business Central work for Romanian companies?

Standard Business Central does not include Romanian localization. You need certified modules for SAF-T (D406), RO e-Factura, e-Transport, and fiscalization. Without them, you’re not compliant with ANAF requirements — and penalties apply.

What is the SAF-T D406 deadline for my company?

Large taxpayers have been obligated since January 2022. Medium since January 2023. Small taxpayers and non-resident entities with Romanian VAT registration since January 2025. If you’re operating in Romania today, you’re almost certainly already obligated.

How much do Romanian compliance modules cost?

Individual modules typically start at €2,000–5,000 for license + implementation, with the full compliance suite running €8,000–15,000 for a standard mid-market deployment. Annual maintenance adds 15–20%. Compare that against penalties: late SAF-T submissions can trigger fines of €1,000–€5,000 per filing.

Can I file SAF-T and e-Factura manually without BC automation?

Technically yes — for a handful of invoices and one legal entity. At any real transaction volume, manual filing creates a compliance department, not a finance team. Automation is the difference between running your business and running a compliance operation.

What about e-Transport reporting — who needs it?

Romania’s e-Transport system applies to international goods transport, high fiscal risk products, and goods entering/leaving Romania. If your BC handles purchase receipts, sales shipments, or transfer orders across borders, you need it. The UIT code generated by ANAF must be stored on your transport documents.

Will more compliance requirements come?

Yes. The D406-to-D300 cross-validation pilot runs through 2026. The EU’s ViDA (VAT in the Digital Age) directive will add reporting obligations across all member states. And ANAF continues tightening enforcement. This isn’t a one-time compliance project — it’s an ongoing operational layer.

---

Vanguard 360 Solutions is a Microsoft Dynamics 365 Business Central partner and LS Retail Gold Partner based in Sibiu, Romania. We serve clients across Europe, the UK, UAE, and Saudi Arabia, with ready-made, certified modules for Romanian SAF-T, e-Invoice, e-Transport, fiscalization, and localization.