Validation rules

UBL-SR-33 — UBL rule

A supporting document (BG-24) carries more than one description (BT-123) — only one cbc:DocumentDescription per cac:AdditionalDocumentReference is allowed.

Rule
UBL-SR-33 — 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 one DocumentDescription per supporting document, from invoice.supporting_documents[i].description.

How to fix it

Keep a single DocumentDescription per AdditionalDocumentReference.

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

Der KoSIT-Validator lehnt die Rechnung ab, weil eine rechnungsbegründende Unterlage (BG-24) mehrere Beschreibungen (BT-123) trägt — nur eine cbc:DocumentDescription je AdditionalDocumentReference ist erlaubt.

So beheben Sie den Fehler

Behalten Sie genau eine DocumentDescription je AdditionalDocumentReference.

Related rules

  • UBL-SR-32 — A VAT breakdown carries more than one exemption reason text (BT-120) — only one cbc:TaxExemptionReason per…
  • UBL-SR-34 — An invoice line carries more than one note (BT-127) — only one cbc:Note per cac:InvoiceLine is allowed.
  • UBL-SR-31 — A document-level charge carries more than one reason text (BT-104) — only one cbc:AllowanceChargeReason per…
  • UBL-SR-35 — An invoice line references more than one purchase order line (BT-132) — only one OrderLineReference/LineID…
  • UBL-SR-30 — A document-level allowance carries more than one reason text (BT-97) — only one cbc:AllowanceChargeReason…
  • UBL-SR-36 — An invoice line carries more than one invoicing period (BG-26) — only one cac:InvoicePeriod per line 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.

Spotted something?

Bug, missing feature, wrong validation result — tell us. The page you're on is attached automatically; email optional.