SAF-T › DUKIntegrator D406 errors

Required element missing: "needs to appear at least 1 times"

The exact DUKIntegrator message

F: GeneralLedgerEntries (1) sectiune Journal (1) sectiune Transaction (1) sectiune TransactionLine (1)
 eroare structura: elementul 'SupplierID' ar fi trebuit sa apara de minimum 1 ori, dar apare efectiv de 0 ori

What it means

The D406 structure requires the named element at the path shown above the message, and the file does not have it (or has it fewer times than the minimum). It is a structure error (F): ANAF rejects the file.

Common causes

• CustomerID and SupplierID are missing on GeneralLedgerEntries lines – both are required even when the entry has no partner (then they are 0).
• Elements are in the wrong order: the validator reads in schema order, so an element placed lower shows up as "missing" where it was expected.
• The accounting software does not export a required field (Contact, Telephone, BankAccount in the Header, TaxInformation on lines, AccountType on accounts).

How to fix it

1. Look at the path in the F: line (e.g. "GeneralLedgerEntries … TransactionLine") – that is where the element goes.
2. Add the element in schema order; for CustomerID/SupplierID without a partner use 0.
3. If the file comes from software, ask the vendor for a version that fills the field.

<TransactionLine>
  <RecordID>1</RecordID><AccountID>4111</AccountID>
  <CustomerID>0012345674</CustomerID>
  <Description>…</Description>

<TransactionLine>
  <RecordID>1</RecordID><AccountID>4111</AccountID>
  <CustomerID>0012345674</CustomerID>
  <SupplierID>0</SupplierID>
  <Description>…</Description>

Other D406 errors

• 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"