Validation rules
UBL-SR-46 — UBL rule
The payment means text (BT-82, the name attribute on cbc:PaymentMeansCode) appears more than once in the document.
- Rule
UBL-SR-46— 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 payment means text; the serializer never sets the name attribute.
How to fix it
Set the name attribute on at most one PaymentMeansCode.
UBL-SR-46 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil der Zahlungsweg-Text (BT-82, das name-Attribut auf cbc:PaymentMeansCode) mehrfach vorkommt.
So beheben Sie den Fehler
Setzen Sie das name-Attribut auf höchstens einem PaymentMeansCode.
Related rules
UBL-SR-45— The payment due date inside cac:PaymentMeans appears more than once — cbc:PaymentDueDate is allowed at most…UBL-SR-47— Several cac:PaymentMeans elements carry different cbc:PaymentMeansCode values — when the code (BT-81) is…UBL-SR-44— The document carries more than one distinct cbc:PaymentID value — the payment reference (BT-83) must be…UBL-SR-48— An invoice line does not have exactly one cac:ClassifiedTaxCategory — every line states its VAT category…UBL-SR-43— A schemeID attribute is set on an AdditionalDocumentReference/cbc:ID that is not an invoiced-object…UBL-SR-49— The tax point date code (BT-8) appears more than once — only one cac:InvoicePeriod/cbc:DescriptionCode is…
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.