Validation rules

UBL-SR-44 — UBL rule

The document carries more than one distinct cbc:PaymentID value — the payment reference (BT-83) must be unique; the same value may be repeated on multiple payment means.

Rule: UBL-SR-44 — official EN 16931 / XRechnung rule
Severity: error
Business term: BT-83 — Remittance information
Field in your JSON: invoice.payment.reference
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 PaymentID, from invoice.payment.reference.

How to fix it

Use one payment reference for the whole invoice; repeat the identical value if several PaymentMeans need it.

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

Der KoSIT-Validator lehnt die Rechnung ab, weil das Dokument mehrere unterschiedliche cbc:PaymentID-Werte trägt — der Verwendungszweck (BT-83) muss eindeutig sein; derselbe Wert darf auf mehreren Zahlungswegen wiederholt werden.

So beheben Sie den Fehler

Verwenden Sie einen Verwendungszweck für die gesamte Rechnung; wiederholen Sie bei mehreren PaymentMeans denselben Wert.

Related rules

UBL-SR-26 — The payment reference (BT-83) appears more than once in a cac:PaymentMeans — only one cbc:PaymentID per…
UBL-SR-43 — A schemeID attribute is set on an AdditionalDocumentReference/cbc:ID that is not an invoiced-object…
UBL-SR-45 — The payment due date inside cac:PaymentMeans appears more than once — cbc:PaymentDueDate is allowed at most…
UBL-SR-42 — The supplier party carries more than two cac:PartyTaxScheme elements — at most two are allowed: the VAT…
UBL-SR-46 — The payment means text (BT-82, the name attribute on cbc:PaymentMeansCode) appears more than once in the…
UBL-SR-47 — Several cac:PaymentMeans elements carry different cbc:PaymentMeansCode values — when the code (BT-81) is…

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.