SAF-T › D406 checks beyond ANAF

Journal entry dated outside the reported period

How it shows in our report

SAFT-GL-05 · Transaction VZ-1 · 2026-09 / 2026-10-15

What it means

Period / PeriodYear and TransactionDate of every entry must fall within Header/SelectionCriteria.

Why it matters

ANAF uses D406 for risk analysis and compares it with the VAT return (D300) and D394. Mismatches like this do not block filing, but can lead to compliance letters or requests for clarification.

Common causes

• Next-month entries included because of a filter on posting date rather than document date.
• Month-end closing posted in period 13.

How to fix it

1. Export by the same date the month's trial balance uses; closing entries go in month 12.

Other D406 checks

• D406 trial balance does not balance (total debit ≠ total credit)
• Closing balance differs from opening balance + movements in D406
• Account used in entries but not declared in GeneralLedgerAccounts
• Unbalanced journal entry in D406 (debit ≠ credit)
• Wrong NumberOfEntries, TotalDebit or TotalCredit in GeneralLedgerEntries
• Customer or supplier used in entries but not declared in MasterFiles
• Customer / supplier balances do not add up to account 4111 / 401
• Invoice NetTotal differs from the sum of its lines
• Invoice GrossTotal differs from NetTotal + VAT
• VAT differs from base × rate in D406
• Wrong NumberOfEntries / TotalDebit / TotalCredit in SalesInvoices or PurchaseInvoices
• Invoice in SourceDocuments without a journal entry
• Unknown VAT tax code in D406
• VAT rate does not match the tax code
• VAT rate of 19%, 9% or 5% in D406 after 1 August 2025
• Tax code used on lines but missing from TaxTable
• RON amount differs from currency × rate (Amount ≠ CurrencyAmount × ExchangeRate)
• Period 13 or a month outside 1–12 in D406
• Quarterly D406 for a single month (HeaderComment T vs period)
• CUI with a wrong check digit in D406 (company or partner)
• IBAN with wrong check digits in D406

ANAF validator messages →