Validation rules
UBL-SR-17 — UBL rule
The buyer legal registration identifier (BT-47) appears more than once — only one PartyLegalEntity/CompanyID is allowed.
- Rule
UBL-SR-17— 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 buyer legal registration identifier; the serializer never emits this CompanyID.
How to fix it
Keep a single cbc:CompanyID inside the customer's cac:PartyLegalEntity.
UBL-SR-17 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil die Registernummer des Käufers (BT-47) mehrfach vorkommt — nur eine PartyLegalEntity/CompanyID ist erlaubt.
So beheben Sie den Fehler
Behalten Sie genau eine cbc:CompanyID in der cac:PartyLegalEntity des Käufers.
Related rules
UBL-SR-16— The buyer identifier (BT-46) appears more than once — the customer party may carry only one…UBL-SR-18— The buyer VAT identifier (BT-48) appears more than once — only one PartyTaxScheme with TaxScheme/ID 'VAT'…UBL-SR-15— The buyer name (BT-44) appears more than once — the customer party may carry only one…UBL-SR-19— The payee name (BT-59) is invalid: cac:PayeeParty may carry at most one PartyName/Name, and it must differ…UBL-SR-14— The seller's additional legal information (BT-33) appears more than once — only one…UBL-SR-20— The payee identifier (BT-60) is invalid: cac:PayeeParty may carry at most one PartyIdentification/ID (SEPA…
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.