D406 (SAF-T) - the standard fiscal control file
D406 is the declaration through which the company transmits the SAF-T (Standard Audit File for Tax) file to ANAF - a standardized XML file that holds, in a single structure, almost all of the period’s accounting and operational records. It is mandatory and submitted periodically (monthly or quarterly, depending on company size; assets are reported annually). Unlike a “summary” declaration, SAF-T is the app’s most comprehensive report: it touches almost every module.
What the file contains
Section titled “What the file contains”SAF-T has several sections, which the app builds from the corresponding modules:
- Header - the company and period data.
- MasterFiles (the nomenclatures):
- The chart of accounts with opening and closing balances per account.
- Customers and suppliers with their balances.
- The tax table (VAT rates), the units of measure, the products.
- The asset register (fixed assets).
- GeneralLedgerEntries - the accounting notes (journals) in the period.
- SourceDocuments - the source documents: sales invoices, purchase invoices, payments and, annually, asset transactions.
Where the data comes from (why it is the most integrated report)
Section titled “Where the data comes from (why it is the most integrated report)”SAF-T draws from all modules at once:
| Section | Source in the app |
|---|---|
| Header / company | the company data |
| Chart of accounts + balances | Accounting (the account register) |
| Customers / suppliers + balances | Partners |
| Taxes, units of measure, products | nomenclatures + Inventory |
| Assets | the Assets module |
| Accounting notes (journals) | the Centralizers (9 journals: cash, bank, partners, expenses, sales, assets, stock…) |
| Sales / purchase invoices, payments | Sales / Purchases + Financial |
The internal chart of accounts is mapped to the SAF-T form, and VAT codes are translated to the ANAF nomenclature. Because it depends on the structure of every module, any change in a source module (a new field on partners, assets, stock) can affect the export - which is why on the new platform this contract must be pinned with regression tests (see the gap register, A3).
How to use it
Section titled “How to use it”From the menu: Fiscal Declarations > Declarația D406 - SAF-T.
- Choose the type (monthly, quarterly or annual) and the period + year.
- Assets are included only on the annual declaration (a tick available on annual).
- Press Generate, then Download: you get the XML file (
D406_{CIF}_{year}_{period}.xml), which you submit to ANAF.
As with D394, submission stays manual (upload on the ANAF portal). Generating SAF-T is a heavy operation (it reads all modules), so on large volumes it can take a while.
What the accountant sees
Section titled “What the accountant sees”- SAF-T is not filled in by hand: it is a projection of the chart of accounts, the notes generated by the centralizers, and the source documents. Corrections are made at the source.
- Amounts are formatted with a
.decimal separator and two decimals, per the ANAF requirement.
Known limitations / to confirm (new platform)
Section titled “Known limitations / to confirm (new platform)”- Movement of goods (MovementOfGoods) is not exported at present - the section exists in the file but is empty. To confirm whether the target customer has stock that ANAF requires reported here.
- No automatic validation against the XSD schema before download and no direct upload to ANAF; the file is checked/uploaded manually (e.g. via DUK Integrator).
- The targeted SAF-T schema version must be confirmed and kept current (ANAF updates the official schema periodically).
- Some secondary nomenclatures (movement types, analysis types, owners) are currently partial. All of these are new-platform items, alongside pinning the data contract with tests (A3).