Validation rules
UBL-SR-24 — UBL rule
Delivery information (BG-13) appears more than once — only one cac:Delivery element is allowed.
- Rule
UBL-SR-24— official EN 16931 / XRechnung rule- Severity
- error
- Detected by
- tier 3 — KoSIT validator (authoritative)
- Reachability
- Only reachable when validating your own XML — normbill-generated documents cannot trigger it
The serializer emits at most one cac:Delivery, carrying invoice.delivery_date (BT-72).
How to fix it
Keep a single cac:Delivery. Through normbill, invoice.delivery_date produces exactly one Delivery element.
UBL-SR-24 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil die Lieferinformationen (BG-13) mehrfach vorkommen — nur ein cac:Delivery-Element ist erlaubt.
So beheben Sie den Fehler
Behalten Sie genau ein cac:Delivery. Über normbill erzeugt invoice.delivery_date genau ein Delivery-Element.
Related rules
UBL-SR-23— The tax representative VAT identifier (BT-63) appears more than once — only one PartyTaxScheme/CompanyID is…UBL-SR-25— The deliver-to party name (BT-70) appears more than once — cac:Delivery may carry only one…UBL-SR-22— The tax representative name (BT-62) appears more than once — cac:TaxRepresentativeParty may carry only one…UBL-SR-26— The payment reference (BT-83) appears more than once in a cac:PaymentMeans — only one cbc:PaymentID per…UBL-SR-21— The payee legal registration identifier (BT-61) is invalid: at most one PartyLegalEntity/CompanyID is…UBL-SR-27— A cac:PaymentMeans carries more than one cbc:PaymentMeansCode (BT-81) — each payment means states exactly…
Official sources
- XRechnung specification (KoSIT / xeinkauf.de)
- KoSIT validator on GitHub and the XRechnung validator configuration
Every 422 from the API lists the rule id, the path in your request JSON, a plain-language message and a suggested fix — see the docs overview for the report format.
Or try it live: drop any XRechnung XML on the free validator — same KoSIT-backed report, no account.