Validation rules
UBL-SR-40 — UBL rule
The buyer trading name (BT-45) appears more than once — the customer party may carry only one PartyName/Name.
- Rule
UBL-SR-40— 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 separate buyer trading name; generated XML never contains a buyer cac:PartyName.
How to fix it
Keep a single cac:PartyName/cbc:Name under the customer party.
UBL-SR-40 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil der Handelsname des Käufers (BT-45) mehrfach vorkommt — nur ein PartyName/Name ist bei der Käuferpartei erlaubt.
So beheben Sie den Fehler
Behalten Sie genau einen cac:PartyName/cbc:Name bei der Käuferpartei.
Related rules
UBL-SR-39— The project reference (BT-11) appears more than once — only one cac:ProjectReference with one cbc:ID is…UBL-SR-42— The supplier party carries more than two cac:PartyTaxScheme elements — at most two are allowed: the VAT…UBL-SR-37— An item price discount (BT-147) appears more than once — only one cac:Price/cac:AllowanceCharge with one…UBL-SR-43— A schemeID attribute is set on an AdditionalDocumentReference/cbc:ID that is not an invoiced-object…UBL-SR-36— An invoice line carries more than one invoicing period (BG-26) — only one cac:InvoicePeriod per line is…UBL-SR-44— The document carries more than one distinct cbc:PaymentID value — the payment reference (BT-83) must be…
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.