Validation rules
UBL-SR-10 — UBL rule
The seller trading name (BT-28) appears more than once — the supplier party may carry only one PartyName/Name.
- Rule
UBL-SR-10— 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 trading name; generated XML never contains a seller cac:PartyName.
How to fix it
Keep a single cac:PartyName/cbc:Name under the supplier party.
UBL-SR-10 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil der Handelsname des Verkäufers (BT-28) mehrfach vorkommt — nur ein PartyName/Name ist erlaubt.
So beheben Sie den Fehler
Behalten Sie genau einen cac:PartyName/cbc:Name bei der Verkäuferpartei.
Related rules
UBL-SR-09— The seller name (BT-27) appears more than once — the supplier party may carry only one…UBL-SR-11— The seller legal registration identifier (BT-30) appears more than once — only one…UBL-SR-08— The invoicing period (BG-14) appears more than once — only one document-level cac:InvoicePeriod is allowed.UBL-SR-12— The seller VAT identifier (BT-31) appears more than once — only one PartyTaxScheme with TaxScheme/ID 'VAT'…UBL-SR-07— A cac:BillingReference is present but the preceding invoice number (BT-25, InvoiceDocumentReference/cbc:ID)…UBL-SR-13— The seller tax registration identifier (BT-32) appears more than once — only one non-VAT PartyTaxScheme may…
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.