Validation rules

UBL-SR-09 — UBL rule

The seller name (BT-27) appears more than once — the supplier party may carry only one PartyLegalEntity/RegistrationName.

Rule: UBL-SR-09 — official EN 16931 / XRechnung rule
Severity: error
Business term: BT-27 — Seller name
Field in your JSON: invoice.seller.name
Detected by: tier 3 — KoSIT validator (authoritative)
Reachability: Only reachable when validating your own XML — normbill-generated documents cannot trigger it

The serializer writes invoice.seller.name as exactly one RegistrationName.

How to fix it

Keep a single cac:PartyLegalEntity/cbc:RegistrationName under cac:AccountingSupplierParty.

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

Der KoSIT-Validator lehnt die Rechnung ab, weil der Verkäufername (BT-27) mehrfach vorkommt — die Verkäuferpartei darf nur einen PartyLegalEntity/RegistrationName tragen.

So beheben Sie den Fehler

Behalten Sie genau einen cac:PartyLegalEntity/cbc:RegistrationName unter cac:AccountingSupplierParty.

Related rules

BR-06 — The seller name (BT-27) is missing or empty.
UBL-SR-08 — The invoicing period (BG-14) appears more than once — only one document-level cac:InvoicePeriod is allowed.
UBL-SR-10 — The seller trading name (BT-28) appears more than once — the supplier party may carry only one PartyName/Name.
UBL-SR-07 — A cac:BillingReference is present but the preceding invoice number (BT-25, InvoiceDocumentReference/cbc:ID)…
UBL-SR-11 — The seller legal registration identifier (BT-30) appears more than once — only one…
UBL-SR-06 — A cac:BillingReference contains more than one cac:InvoiceDocumentReference — each preceding-invoice…

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.