NextUp ERP and SAF-T D406 in 2026: Native Export, Top 8 Errors, and Automation
NextUp ERP provides a native cloud-based SAF-T D406 module. How the export works, common errors to avoid, and how a Smart Layer can reduce monthly processing time to under 5 minutes.
Bogdan Minoiu — Founder Azuvio · 2026-08-28 · 10 min · Reglementări
SAF-T D406 — What needs to be reported
SAF-T (Standard Audit File for Tax) is the OECD standardized XML format adopted by ANAF (the Romanian tax authority) for the D406 monthly reporting. The structure includes: accounting ledgers, journals, chart of accounts, customers, suppliers, stock movements, fixed assets, invoices, and payments.
Deadline: The last day of the month following the reporting period.
Obligation: All large companies (since 2022), medium companies (since 2023), and small companies (from 2025).
Status in NextUp ERP
NextUp delivers a native SAF-T D406 module included in the subscription (or as a symbolic cost add-on, depending on the plan). The cloud advantage: updates to the ANAF (tax authority) schema are delivered transparently.
Functionality:
Automatic extraction of the 13 mandatory sections from the NextUp database
XML generation according to the current tax authority schema
Pre-export validation (checking accounts, VAT IDs, tax codes)
Final export for upload to the tax authority portal (SPV)
Top 8 SAF-T Errors that occur in NextUp
1. Outdated Chart of Accounts — Users keeping old accounts that haven't been remapped.
2. Invalid Customer/Supplier VAT IDs — Data entered manually without validation.
3. Invalid VAT Code per Operation — Incorrect mapping for atypical cases.
4. Stock Movements Not Reconciled with Balance — Discrepancies between inventory and accounting.
5. Invoices Missing the Unique Tax Authority Key — e-Invoicing files missing the official SPV ID.
6. Fixed Assets — Missing Depreciation Data — Optional fields left blank.
7. Analytical Sub-accounts Not Covered — SAF-T requires a maximum of 4 levels.
8. Special Characters and Diacritics — Strict UTF-8 encoding is required.
Manual Workflow with NextUp (without Smart Layer)
1. Export SAF-T from the NextUp module (5-10 min)
2. Excel verification of the 13 sections (1-2 hours)
3. Manual correction of accounts, VAT IDs, and tax codes (1-3 hours)
4. Re-export and validation on the tax authority portal (30 min)
5. Correcting reported errors (1-2 hours)
6. Final submission + archiving (15 min)
Total: 4-7 hours/month of accounting work (better than desktop ERPs, but still significant).
Workflow with Azuvio Smart Layer
1. Smart Layer runs automatically on the last day of the month (cron)
2. Extracts data from NextUp via API
3. Validates against 23+ internal rules (exceeding native validation)
4. Automatically corrects what is possible (account mapping, VAT ID formatting, character cleaning)
5. Generates final XML and validates against the tax authority schema
6. Sends an alert to the accountant for approval and final click
Total: <5 minutes, only for verification and the final click.
Cost-Benefit Analysis
| Element | Manual with NextUp | With Smart Layer |
|---------|--------------------|------------------|
| Monthly Accounting Time | 4-7 hours | <5 minutes |
| Time Cost (50€/h) | 200-350€/month | <5€/month |
| Risk of Fines (Errors) | Medium | Very Low |
| Annual Azuvio SAF-T Cost | — | Included in Smart Layer |
Net Savings: ~2,500-4,200€/year on SAF-T alone for a medium-sized company.
Conclusion
The native NextUp module for SAF-T D406 works well and covers most cases. For mid-market companies with high transaction volumes, the Azuvio Smart Layer reduces monthly time from hours to minutes and eliminates the risk of rejection. For very small companies, the native module is sufficient.