Merlin ERP and SAF-T D406 in 2026: Tax Authority Reporting, Top 8 Errors, and Automation
SAF-T D406 reporting is mandatory for all large and medium-sized companies. Learn how Merlin ERP exports SAF-T data, which errors occur most frequently, and how a Smart Layer can reduce monthly processing time from 6-10 hours to under 5 minutes.
Bogdan Minoiu — Founder Azuvio · 2026-08-12 · 10 min · Reglementări
SAF-T D406 — What you need to report
SAF-T (Standard Audit File for Tax) is the OECD standardized XML format adopted by ANAF (the Romanian tax authority) for monthly D406 reporting. The structure includes: accounting ledgers, journals, chart of accounts, customers, suppliers, stock movements, fixed assets, invoices, and payments.
Deadline: By the last day of the month following the reporting period.
Obligation: All large companies (since 2022), medium-sized companies (since 2023), and small companies (starting 2025).
Status in Merlin ERP
Prodigy Software has released an official SAF-T D406 module available as an add-on. It allows the automatic extraction of the 13 mandatory sections from the Merlin database, generating the XML according to the tax authority schema and exporting it.
Cost: €1,800-3,500 initially (per implementation) + €600/year maintenance.
Top 8 Frequent SAF-T Errors
1. Outdated Chart of Accounts — Merlin allows custom accounts that are not present in the official tax authority nomenclature.
2. Invalid Customer/Supplier VAT IDs — Missing country prefixes or failed checksum validation.
3. Invalid VAT Codes per Transaction — Incorrect mapping between Merlin and the official Tax Authority Operation Codes.
4. Stock Movements Not Reconciled with Balance Sheet — Discrepancies between the inventory management module and accounting.
5. Invoices Missing the Unique Tax Authority Key — e-Invoicing files without the official ID returned by the government portal (SPV).
6. Fixed Assets — Missing Depreciation Data — The Merlin module does not populate all required fields.
7. Unsupported Analytical Sub-accounts — SAF-T requires a maximum of 4 levels; some Merlin installations use more.
8. Special Characters and Diacritics — The XML requires strict UTF-8 encoding.
Typical Manual Workflow (Without Automation)
1. Export SAF-T from the Merlin module (10-15 min)
2. Excel verification of all 13 sections (1-2 hours)
3. Manual correction of accounts, VAT IDs, and VAT codes (2-4 hours)
4. Re-export and validation on the tax authority portal (30 min)
5. Correction of flagged errors (1-2 hours)
6. Final submission + archiving (15 min)
Total: 6-10 hours/month of manual labor for the accountant.
Workflow with Azuvio Smart Layer
1. Smart Layer runs automatically on the last day of the month (cron)
2. Extracts data from Merlin via API
3. Validates the 8 points above + 15 additional internal rules
4. Automatically corrects what is possible (account mapping, VAT ID formatting, encoding)
5. Generates final XML and validates against the tax authority schema
6. Sends an alert to the accountant for final approval + submission
Total: <5 minutes, only for verification and the final click.
Cost-Benefit Analysis
| Element | Manual | With Smart Layer |
|---------|--------|----------------|
| Monthly Accountant Time | 6-10 hours | <5 minutes |
| Time Cost (€50/h) | €300-500/month | <€5/month |
| Risk of Fines (Errors) | Medium-High | Very Low |
| Annual SAF-T Azuvio Cost | — | Included in Smart Layer |
Net Savings: €3,500-6,000/year on SAF-T alone for a medium-sized company.
Conclusion
The Prodigy SAF-T module works, but it leaves significant manual labor to the accountant. The Azuvio Smart Layer reduces monthly time to under 5 minutes through automated validation and correction. For companies with high transaction volumes, SAF-T automation pays for itself in 2-3 months.