SAF-T › DUKIntegrator D406 errors
Wrong element order or misplaced section
What it means
The D406 schema fixes the order of elements. An element placed before one that should precede it produces order or "missing element" messages.
Common causes
- The software writes fields in a different order than the schema (e.g. AccountDescription before AccountID).
How to fix it
- Reorder following the schema; order matters even when all elements are present.
- Note: DUKIntegrator often does not say "wrong order" but "element X needs to appear at least 1 times" – for an element that exists but comes later. If the "missing" element is in the file, the problem is the order (example below).
How it usually shows up in DUKIntegrator:
F: MasterFiles (1) sectiune GeneralLedgerAccounts (1) sectiune Account (1) sectiune AccountDescription (1) eroare structura: elementul 'AccountID' ar fi trebuit sa apara de minimum 1 ori, dar apare efectiv de 0 ori
Wrong
<Account><AccountDescription>Clienti</AccountDescription><AccountID>4111</AccountID>…
Correct
<Account><AccountID>4111</AccountID><AccountDescription>Clienti</AccountDescription>…
Check your D406 file before filing it
We run ANAF's validator for your period plus the checks ANAF only does after filing: trial balance, balances, ledger totals, VAT, CUIs and IBANs. One free check per day.
Check a SAF-T fileOther D406 errors
- Required element missing: "needs to appear at least 1 times"
- Required group missing: "the group needs to appear at least 1 times"
- Element repeated too often: "exceeded the maximum allowed number of occurrences"
- "unknown element … in namesapace": element not in the schema
- Missing or incorrect namespace on AuditFile
- "the value … is not in the list": code not in the ANAF nomenclature
- "the value … is out of the given interval"
- "decimal number does not match the pattern 16.2": too many decimals
- "wrong decimal number" / "wrong integer number": bad number format
- "wrong date (format: yyyy-mm-dd)"
- "string longer than N characters": text too long
- "Fatal parsing error": the XML cannot be read
- "not allowed content in or after the element …"
- "CustomerID cannot be 0 (zero)" in MasterFiles
- "Invalid format for CustomerID …": wrong partner ID format
- "CustomerID and SupplierID cannot both be 0" on payments
- "Invalid format for RegistrationNumber" / "invalid CIF"
- "Invalid format for IBANNumber …"
- "The account ID … must be in the chart of accounts"
- "Amount (RON) … differs from CurrencyAmount x ExchangeRate"
- "The return type … does not match the declared period"
- "For country RO the region code … is not in the list"
- "The Name element was filled … use CustomerID!"
- "For PaymentMechanism … the PaymentMethod value … is not allowed"
- "Wrong reporting period" / "wrong year-month parameter"
- "The first part of a return must contain at least one MasterFiles section"
- "TotalSegmentsInSequence should be greater than SegmentIndex"
- "MovementPostingTime must be HH:mm"