Validation rules
UBL-SR-35 — UBL rule
An invoice line references more than one purchase order line (BT-132) — only one OrderLineReference/LineID per line is allowed.
- Rule
UBL-SR-35— 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 order line reference; generated lines never contain cac:OrderLineReference.
How to fix it
Keep a single cac:OrderLineReference/cbc:LineID per invoice line.
UBL-SR-35 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil eine Position auf mehrere Bestellpositionen (BT-132) verweist — nur eine OrderLineReference/LineID je Position ist erlaubt.
So beheben Sie den Fehler
Behalten Sie genau eine cac:OrderLineReference/cbc:LineID je Rechnungsposition.
Related rules
UBL-SR-34— An invoice line carries more than one note (BT-127) — only one cbc:Note per cac:InvoiceLine is allowed.UBL-SR-36— An invoice line carries more than one invoicing period (BG-26) — only one cac:InvoicePeriod per line is…UBL-SR-33— A supporting document (BG-24) carries more than one description (BT-123) — only one cbc:DocumentDescription…UBL-SR-37— An item price discount (BT-147) appears more than once — only one cac:Price/cac:AllowanceCharge with one…UBL-SR-32— A VAT breakdown carries more than one exemption reason text (BT-120) — only one cbc:TaxExemptionReason per…UBL-SR-31— A document-level charge carries more than one reason text (BT-104) — only one cbc:AllowanceChargeReason per…
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.