Validation rules

UBL-SR-51 — UBL rule

An address carries more than one cac:AddressLine — only one additional address line (line 3) is allowed per postal address.

Rule
UBL-SR-51 — 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 address model has no third address line; generated addresses never contain cac:AddressLine.

How to fix it

Keep at most one AddressLine per address; the first two lines belong in cbc:StreetName and cbc:AdditionalStreetName.

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

Der KoSIT-Validator lehnt die Rechnung ab, weil eine Anschrift mehrere cac:AddressLine-Elemente trägt — nur eine zusätzliche Adresszeile (Zeile 3) je Anschrift ist erlaubt.

So beheben Sie den Fehler

Behalten Sie höchstens eine AddressLine je Anschrift; die ersten beiden Zeilen gehören in cbc:StreetName und cbc:AdditionalStreetName.

Related rules

  • UBL-SR-50 — An item carries more than one description (BT-154) — only one cbc:Description per cac:Item is allowed.
  • UBL-SR-52 — An invoice line carries more than one cac:DocumentReference — the line-level invoiced-object identifier…
  • UBL-SR-49 — The tax point date code (BT-8) appears more than once — only one cac:InvoicePeriod/cbc:DescriptionCode is…
  • UBL-SR-53 — A cac:PartyTaxScheme states a TaxScheme/ID but no cbc:CompanyID — the identifier itself (e.g. the VAT…
  • UBL-SR-48 — An invoice line does not have exactly one cac:ClassifiedTaxCategory — every line states its VAT category…
  • UBL-SR-54 — More than one payment card account (BG-18) is present — cac:PaymentMeans/cac:CardAccount is allowed at most…

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.