ASiS + SAF-T D406 — Monthly Workflow + Automated Reconciler 2026
How to generate D406 from ASiS, the manual mapping requirements, and how the Smart Layer Reconciler reduces effort from 28h to 3h/month via automated mapping + D300/D394 cross-checks.
Mihai Istrati — CTO Azuvio · 2026-11-28 · 11 min · ERP & Integrations
Context
D406 SAF-T is a monthly requirement for all RO legal entities. ANAF (the Romanian tax authority) runs validators and anomaly analysis by cross-referencing D300/D394/e-Factura data.
What ASiS Provides Out-of-the-Box
Generation of D406 XML files including headers + master files + transactions + payments + fixed assets + stocks. Syntactic schema validation.
What Is Not Native
1. Mapping custom dimensions → ANAF analytics: if you use dimensions (cost centers, projects, locations), these require manual monthly mapping.
2. Cross-check D406 vs D300/D394/e-Factura: discrepancies trigger audits. ASiS does not perform pre-submission cross-checks.
3. ANAF Semantic Validator: 30+ rules beyond the standard schema.
4. Pre-assembled Audit Package for tax authority inspections.
Manual Cost
A Chief Accountant + assistant typically invest 24-32h/month on: mapping, cross-checking, error fixing, and package assembly.
The Solution: Smart Layer SAF-T Reconciler
1. Automated Mapping configured one-time and reused monthly.
2. Pre-submission Cross-check D406 vs D300/D394/e-Factura.
3. Semantic Validator covering 30+ ANAF specific rules.
4. ZIP Audit Package pre-assembled with drill-down capabilities + source documents.
Effort: 28h → 3h/month (-89%).
Integration with ASiS
REST API pull for accounting notes + master files. Zero modifications required in ASiS. Final D406 XML output + audit package.
See «ASiS + e-Factura».