SAF-T › DUKIntegrator D406 errors
"Fatal parsing error": the XML cannot be read
The exact DUKIntegrator message
F: MasterFiles (1) sectiune Customers (1) sectiune Customer (1) sectiune CompanyStructure (1) sectiune Name (1) eroare: Eroare fatala de parsare: '… The entity name must immediately follow the '&' in the entity reference.'
What it means
The file is not well-formed XML, so the validator stops at the first problem character (line and column are in the message).
Common causes
- An unescaped & in names ("Ion & Fiii SRL") – it must be &.
- < and > characters in text.
- File saved in an encoding other than UTF-8, or truncated during export.
How to fix it
- Open the file at the line/column from the message and replace & with &, < with <, > with >.
- Save as UTF-8.
Wrong
<Name>EXEMPLU & CUMPARATOR SRL</Name>
Correct
<Name>EXEMPLU & CUMPARATOR SRL</Name>
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
- Wrong element order or misplaced section
- "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"