SAF-T

DUKIntegrator errors for D406 (Romanian SAF-T): meaning and fixes

The messages DUKIntegrator gives when you validate the Romanian SAF-T return (D406), explained: what they mean, why they happen and what to change in the XML. The examples are real outputs of ANAF's validator (kit of 16 Feb 2026).

• 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
• Wrong element order or misplaced section
• "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"