Validation rules
UBL-SR-42 — UBL rule
The supplier party carries more than two cac:PartyTaxScheme elements — at most two are allowed: the VAT identifier (BT-31) and the tax registration (BT-32).
- Rule
UBL-SR-42— 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 two: one VAT scheme (invoice.seller.vat_id) and one FC scheme (invoice.seller.tax_number).
How to fix it
Keep at most two PartyTaxScheme elements on the seller: one with TaxScheme/ID 'VAT', one with a non-VAT scheme.
UBL-SR-42 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil die Verkäuferpartei mehr als zwei cac:PartyTaxScheme-Elemente trägt — erlaubt sind höchstens zwei: die USt-IdNr. (BT-31) und die Steuernummer (BT-32).
So beheben Sie den Fehler
Behalten Sie höchstens zwei PartyTaxScheme beim Verkäufer: eines mit TaxScheme/ID „VAT“, eines mit einem Nicht-VAT-Schema.
Related rules
UBL-SR-43— A schemeID attribute is set on an AdditionalDocumentReference/cbc:ID that is not an invoiced-object…UBL-SR-40— The buyer trading name (BT-45) appears more than once — the customer party may carry only one PartyName/Name.UBL-SR-44— The document carries more than one distinct cbc:PaymentID value — the payment reference (BT-83) must be…UBL-SR-39— The project reference (BT-11) appears more than once — only one cac:ProjectReference with one cbc:ID is…UBL-SR-45— The payment due date inside cac:PaymentMeans appears more than once — cbc:PaymentDueDate is allowed at most…UBL-SR-46— The payment means text (BT-82, the name attribute on cbc:PaymentMeansCode) appears more than once in the…
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.