SAF-T RomaniaD406 MandatoryLast reviewed January 2026

SAF-T in Romania: the D406 explained

Romania mandates SAF-T through the D406 declaration, phased by taxpayer size. The D406 file covers GL transactions, customer/supplier data, invoices, payments, and goods movements. It must be submitted monthly or quarterly depending on the reporting period.

The mandate

D406 SAF-T — Romanian Standard Audit File

Who must file

All taxpayers in Romania, phased by size category.

How it works

Accounting system generates D406 SAF-T XML → submitted to ANAF monthly/quarterly → ANAF validates and cross-references with RO eFactura data.

Key dates for Romania

  1. Jan 2022
    Large taxpayers: D406 mandatory
  2. Jan 2023
    Mid-sized taxpayers: D406 mandatory
  3. Jan 2025
    Small taxpayers: D406 mandatory (phased)

What the file contains

Romania's D406 SAF-T is comprehensive, covering five data sections: general ledger master data, GL transactions, customer/supplier information, invoices (sales and purchases), payments, and goods/asset movements. The file is submitted monthly (for monthly VAT filers) or quarterly. ANAF cross-references D406 data with RO eFactura submissions, creating a powerful audit framework.

What your ERP has to deliver

ERP systems must generate D406-compliant XML covering all five data sections. The Romanian chart of accounts mapping is required. Integration between D406 SAF-T and RO eFactura data must be consistent. Systems must handle the phased rollout — different entities may have different go-live dates based on their size classification.

The data flow, step by step

Accounting System
D406 SAF-T XML (5 sections)
ANAF submission
ANAF validation
Cross-reference with RO eFactura
Automated discrepancy detection.

Practical insights

  • Romania's D406 is one of the most data-rich SAF-T implementations, covering GL, invoices, payments, and goods movements in a single file. The breadth of data required means ERP systems must provide comprehensive data extraction across multiple modules.
  • The cross-reference between D406 SAF-T and RO eFactura is a critical compliance intersection. Invoice data reported through eFactura must be consistent with the same invoices in D406. This creates a double-validation challenge for companies operating both systems.
  • The phased rollout by taxpayer size means that companies with multiple Romanian entities may have different compliance timelines. Centralized compliance management across entities is important.
  • ANAF's automated analysis of D406 data is becoming increasingly sophisticated. The combination of real-time eFactura data and periodic SAF-T data gives ANAF a comprehensive view that makes discrepancies highly visible.

Common pitfalls

  • Inconsistencies between D406 SAF-T invoice data and RO eFactura submissions — ANAF's cross-referencing makes this a high-risk area.
  • Incomplete goods movement data in D406, especially for companies with complex logistics operations.
  • Not mapping to the Romanian chart of accounts correctly, particularly for foreign-owned subsidiaries using group-level GL structures.

Linked obligations in Romania

E-Invoicing (RO eFactura): D406 and eFactura data must be consistent. ANAF cross-references both.
eTransport: Goods movement data in D406 should align with eTransport declarations for monitored goods.

How Taxera approaches SAF-T in Romania

The same way in every country: from your ERP to the authority, without spreadsheets in the middle.

Straight from your ERP

Taxera extracts exactly the fields required, from your live transactions. No manual exports or uploads.

Checked before it leaves

Files are validated against the schema and cross-checked against your source data and filed returns before submission.

Changes tracked for you

When the rules or the file format change, we track it and update the platform. You do not rebuild mappings.

Book a demo

SAF-T Romania: questions, answered

Official sources

More SAF-T guides