Validation rules

UBL-SR-29 — UBL rule

The SEPA creditor identifier (BT-90) appears more than once — only one PartyIdentification/ID with schemeID 'SEPA' is allowed in the whole document.

Rule: UBL-SR-29 — 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 serializer emits at most one schemeID SEPA PartyIdentification, from invoice.payment.creditor_id.

How to fix it

Keep a single party identification with schemeID SEPA (the bank-assigned creditor reference).

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

Der KoSIT-Validator lehnt die Rechnung ab, weil die SEPA-Gläubiger-ID (BT-90) mehrfach vorkommt — im gesamten Dokument ist nur eine PartyIdentification/ID mit schemeID „SEPA“ erlaubt.

So beheben Sie den Fehler

Behalten Sie genau eine Parteikennung mit schemeID SEPA (die Gläubiger-ID der Bank).

Related rules

UBL-SR-28 — The direct-debit mandate reference (BT-89) appears more than once — only one PaymentMandate/cbc:ID per…
UBL-SR-30 — A document-level allowance carries more than one reason text (BT-97) — only one cbc:AllowanceChargeReason…
UBL-SR-27 — A cac:PaymentMeans carries more than one cbc:PaymentMeansCode (BT-81) — each payment means states exactly…
UBL-SR-31 — A document-level charge carries more than one reason text (BT-104) — only one cbc:AllowanceChargeReason per…
UBL-SR-26 — The payment reference (BT-83) appears more than once in a cac:PaymentMeans — only one cbc:PaymentID per…
UBL-SR-32 — A VAT breakdown carries more than one exemption reason text (BT-120) — only one cbc:TaxExemptionReason 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.