Validation rules
UBL-SR-43 — UBL rule
A schemeID attribute is set on an AdditionalDocumentReference/cbc:ID that is not an invoiced-object reference — the scheme is only allowed together with DocumentTypeCode 130 (or 50 in credit notes).
- Rule
UBL-SR-43— 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 additional document references; generated XML never contains this construct.
How to fix it
Remove the schemeID attribute, or add cbc:DocumentTypeCode 130 to mark the reference as the invoiced object (BT-18).
UBL-SR-43 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil ein schemeID-Attribut auf einer AdditionalDocumentReference/cbc:ID gesetzt ist, die keine Objektkennung ist — das Schema ist nur zusammen mit DocumentTypeCode 130 (bzw. 50 bei Gutschriften) erlaubt.
So beheben Sie den Fehler
Entfernen Sie das schemeID-Attribut — oder ergänzen Sie cbc:DocumentTypeCode 130, um die Referenz als Objektkennung (BT-18) zu kennzeichnen.
Related rules
UBL-SR-42— The supplier party carries more than two cac:PartyTaxScheme elements — at most two are allowed: the VAT…UBL-SR-44— The document carries more than one distinct cbc:PaymentID value — the payment reference (BT-83) must be…UBL-SR-45— The payment due date inside cac:PaymentMeans appears more than once — cbc:PaymentDueDate is allowed at most…UBL-SR-40— The buyer trading name (BT-45) appears more than once — the customer party may carry only one PartyName/Name.UBL-SR-46— The payment means text (BT-82, the name attribute on cbc:PaymentMeansCode) appears more than once in the…UBL-SR-39— The project reference (BT-11) appears more than once — only one cac:ProjectReference with one cbc:ID 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.