WizPro + SAF-T D406 — How to generate correctly and what to check (2026 Guide)
Operational guide for generating SAF-T D406 in WizPro: configuration, validation, frequencies, common errors, and how to avoid penalties from ANAF (the Romanian tax authority).
Ionut Mihaescu — Full Stack Developer Azuvio · 2026-05-25 · 9 min · ERP & Integrations
Context
SAF-T D406 (Standard Audit File for Tax) has been mandatory in Romania since 2022 for large companies, 2023 for medium-sized ones, and 2025 for small entities. WizPro natively generates the SAF-T XML file.
Reporting Frequencies
Large companies (>500 employees): Monthly
Medium companies (50-500): Monthly since 2023
Small companies (<50): Annually from 2025, monthly from 2026 (verify exact deadline with the tax authority)
Mandatory modules: Master Files + General Ledger + Source Documents
Generation steps in WizPro
1. Initial configuration (one-time):
Settings → SAF-T → account structure configuration (mapping WizPro account → SAF-T account)
Map VAT types → ANAF codes
Map units of measure → UN/ECE nomenclature
Map countries → ISO 3166 codes
2. Periodic generation:
Modules → SAF-T → select period (month / year)
Select modules (Master + GL + Source Documents)
XML Generation (can take 30 min - 4h for high-volume companies)
Automatic structural validation
Export .xml file
3. Upload to the tax authority portal (SPV):
Login to SPV with digital certificate
Section D406 → upload XML
Receipt confirmation (registration number)
Top 8 common errors
1. Unconfigured accounts in mapping — any WizPro account appearing in the GL must be mapped to SAF-T. Missing mappings = blocking error.
2. Inconsistent opening balances — the SAF-T opening balance must match the closing balance of the previous month. Discrepancies trigger audits.
3. Documents without series numbers — every source document (invoice, reception note, consumption voucher) must have a unique number.
4. Invalid Client/Supplier VAT ID — verify all partner VAT IDs before generation.
5. Inconsistent VAT codes — the same transaction type must utilize the same VAT code consistently.
6. Incomplete addresses — all partners in Master Files must have a full address.
7. Transactions without source documents — every accounting entry must reference a source document.
8. Special characters in descriptions — ensure correct XML escaping (ampersands and quotes must be encoded as XML entities).
Recommended monthly workflow
Day 1-3 post-month close: Internal pre-validation using the WizPro "SAF-T check" report
Day 5: Generate draft SAF-T, verify totals vs. trial balance
Day 8-10: Final generation + SPV upload
Tax Authority Deadline: The 25th day of the following month (verify the exact deadline for your company type)
Statutory Penalties
Non-reporting: 1,000-5,000 RON / month
Incomplete/erroneous reporting: 500-2,500 RON / file
Recurrence: Increased penalties + scheduled tax audit
WizPro Limitations for SAF-T
1. Generation performance — for companies with over 100k transactions/month, generation can take 4-8 hours.
2. Lack of tax authority pre-validation — WizPro validates structurally but not against the most recent official ANAF schema updates.
3. Audit trail for differences — if you re-generate SAF-T for a previously reported month, differences are not automatically documented.
Smart Layer for SAF-T
Azuvio Document Hub + Compliance connects to WizPro and provides:
Pre-validation against the weekly-updated tax authority schema
Incremental generation (differences only) for re-reporting
Full SAF-T version audit trail per month
CFO Dashboard with real-time reporting status
Discord/email alerts 5 days before the deadline
See "WizPro Limitations - When do you need a Smart Layer?".
Conclusion
WizPro covers SAF-T for standard mid-market companies. For high volumes or companies with zero appetite for penalty risks, a Smart Layer adds essential robustness.
See also "WizPro + e-Invoicing" for the complete tax compliance package.