SAF-T Romania 2026: The D406 Reporting Guide for Companies
Alongside e-Factura, Romania's SAF-T (Standard Audit File for Tax) regime — submitted to ANAF as the D406 informative declaration — is one of the most demanding compliance requirements for finance teams. Since its phased rollout began with large taxpayers in 2022, ANAF has progressively extended the obligation to medium and small companies, and by 2026 most VAT-registered businesses in Romania are expected to be in scope. Unlike e-Factura, which covers individual invoices, SAF-T requires a structured export of your entire accounting dataset — general ledger, invoices, fixed assets, inventory movements and more — in a standardised XML format. This guide explains what SAF-T/D406 is, who must file it, what it covers, and how a connected ERP or accounting platform turns a periodic compliance burden into an automated export.
What is SAF-T and the D406 declaration
SAF-T (Standard Audit File for Tax) is an OECD-designed standard for exporting accounting data in a structured, machine-readable format so tax authorities can review it without requesting ad-hoc reports. In Romania, ANAF implemented its own SAF-T schema and requires it to be submitted as the D406 informative declaration.
D406 is far broader than a single invoice or VAT return: it packages general ledger entries, customer and supplier master data, sales and purchase invoices, payments, and fixed assets — plus, for companies that hold stock, inventory movements and balances — into one structured XML file per reporting period.
Who must file SAF-T (D406) in 2026, and from when
ANAF rolled out the D406 obligation in stages based on taxpayer size: large taxpayers were first in scope from January 2022, medium taxpayers followed from January 2023, and the obligation has progressively extended to small taxpayers and non-resident companies registered for VAT in Romania. By 2026, the large majority of active VAT payers in Romania fall under some SAF-T filing obligation.
Because the exact start date depends on a company's taxpayer category as assigned by ANAF — and these categories can change — the safest way to confirm your filing obligation and first reporting period is to check your company's status directly with ANAF or with your accountant, and to make sure your accounting software is configured for D406 from that date rather than retrofitted afterwards.
What goes into a D406 file and how often it is submitted
A D406 file is built around several standard sections:
- General ledger — chart of accounts and journal entries
- Master data — customers, suppliers and product/service records
- Sales and purchase invoices, plus payments
- Fixed assets register (typically reported annually)
- Inventory — stock movements and balances, where required
Common SAF-T challenges we see
Most SAF-T problems are structural rather than about the underlying accounting being wrong:
- Chart of accounts not mapped to ANAF's standard SAF-T account codes, causing validation errors
- Master data — customer/supplier tax IDs and addresses — incomplete or inconsistent across modules
- Manual exports built in spreadsheets that no longer match the live general ledger by filing time
- Inventory and fixed assets tracked outside the core accounting system, requiring extra reconciliation before each SAF-T period
- No automated check between what was filed in D406 and what was reported via e-Factura or the VAT return for the same period
How a connected ERP/accounting system automates D406
The practical fix mirrors e-Factura: generate SAF-T directly from the system of record. OneConta maps its chart of accounts to ANAF's SAF-T codes by default and can export a validated D406 XML for a given period directly from the general ledger, customer/supplier records and invoice history — without rebuilding a spreadsheet each period.
For companies running ERP WE, the same general ledger, inventory, and fixed asset registers that support day-to-day operations are the source for SAF-T — so as long as postings (sales, purchases, stock movements, asset additions and disposals) are recorded as they happen, the D406 export reflects them automatically, and your e-Factura, VAT return and SAF-T figures stay consistent with each other.
Frequently asked questions
Is SAF-T (D406) mandatory for all companies in Romania in 2026?
ANAF introduced D406 in stages by taxpayer size — large taxpayers from 2022, medium from 2023, with the obligation progressively extended to small taxpayers and non-resident VAT payers since. By 2026 most VAT-registered companies fall under some SAF-T obligation, but the exact start date depends on your taxpayer category — confirm your specific filing start date with ANAF or your accountant.
How is SAF-T (D406) different from e-Factura?
e-Factura validates and transmits individual B2B/B2G invoices in near real time. SAF-T (D406) is a periodic, much broader export of your accounting data — general ledger, master data, invoices, fixed assets and inventory — submitted as a single structured XML file for a reporting period.
What happens if a D406 file fails ANAF validation or is filed late?
A rejected or late SAF-T submission is treated as non-compliance, similar to a missed VAT return, and can result in fines. Because D406 files are large and structurally strict, the most common cause of rejection is a chart of accounts or master data that hasn't been mapped to ANAF's SAF-T codes — which is why generating the file directly from accounting software configured for SAF-T is strongly preferable to manual exports.