Validation rules

UBL-SR-25 — UBL rule

The deliver-to party name (BT-70) appears more than once — cac:Delivery may carry only one DeliveryParty/PartyName/Name.

Rule: UBL-SR-25 — 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 normbill invoice model has no deliver-to party; generated Delivery elements only carry the delivery date.

How to fix it

Keep a single deliver-to party name inside cac:Delivery.

UBL-SR-25 auf Deutsch — was bedeutet der Fehler?

Der KoSIT-Validator lehnt die Rechnung ab, weil der Name des Warenempfängers (BT-70) mehrfach vorkommt — cac:Delivery darf nur einen DeliveryParty/PartyName/Name tragen.

So beheben Sie den Fehler

Behalten Sie genau einen Warenempfänger-Namen innerhalb von cac:Delivery.

Related rules

UBL-SR-24 — Delivery information (BG-13) appears more than once — only one cac:Delivery element is allowed.
UBL-SR-26 — The payment reference (BT-83) appears more than once in a cac:PaymentMeans — only one cbc:PaymentID per…
UBL-SR-23 — The tax representative VAT identifier (BT-63) appears more than once — only one PartyTaxScheme/CompanyID is…
UBL-SR-27 — A cac:PaymentMeans carries more than one cbc:PaymentMeansCode (BT-81) — each payment means states exactly…
UBL-SR-22 — The tax representative name (BT-62) appears more than once — cac:TaxRepresentativeParty may carry only one…
UBL-SR-28 — The direct-debit mandate reference (BT-89) appears more than once — only one PaymentMandate/cbc:ID per…

Official sources

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.