Validation rules
UBL-SR-05 — UBL rule
Payment terms (BT-20) appear more than once — across all cac:PaymentTerms elements only a single cbc:Note is allowed.
- Rule
UBL-SR-05— official EN 16931 / XRechnung rule- Severity
- error
- Business term
BT-20— Payment terms- Field in your JSON
invoice.payment.terms- 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.payment.terms as exactly one cac:PaymentTerms/cbc:Note.
How to fix it
Merge your payment terms into one cac:PaymentTerms/cbc:Note. Through normbill, invoice.payment.terms is a single string.
UBL-SR-05 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil die Zahlungsbedingungen (BT-20) mehrfach vorkommen — über alle cac:PaymentTerms hinweg ist nur eine cbc:Note erlaubt.
So beheben Sie den Fehler
Fassen Sie die Zahlungsbedingungen in einer cac:PaymentTerms/cbc:Note zusammen. Über normbill ist invoice.payment.terms ein einzelner String.
Related rules
BR-DE-18— A payment-terms line starting with # is not a valid Skonto segment — XRechnung requires the exact format…UBL-SR-04— The invoiced-object identifier (BT-18) appears more than once — only one cac:AdditionalDocumentReference…UBL-SR-06— A cac:BillingReference contains more than one cac:InvoiceDocumentReference — each preceding-invoice…UBL-SR-03— The despatch advice reference (BT-16) appears more than once — only one cac:DespatchDocumentReference with…UBL-SR-07— A cac:BillingReference is present but the preceding invoice number (BT-25, InvoiceDocumentReference/cbc:ID)…UBL-SR-02— The receiving advice reference (BT-15) appears more than once — only one cac:ReceiptDocumentReference with…
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.