Validation rules
UBL-SR-08 — UBL rule
The invoicing period (BG-14) appears more than once — only one document-level cac:InvoicePeriod is allowed.
- Rule
UBL-SR-08— 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 document-level InvoicePeriod, from invoice.invoicing_period.
How to fix it
Keep a single cac:InvoicePeriod at document level; per-line periods belong inside the invoice lines (BG-26).
UBL-SR-08 auf Deutsch — was bedeutet der Fehler?
Der KoSIT-Validator lehnt die Rechnung ab, weil der Abrechnungszeitraum (BG-14) mehrfach vorkommt — nur ein cac:InvoicePeriod auf Dokumentebene ist erlaubt.
So beheben Sie den Fehler
Behalten Sie genau eine cac:InvoicePeriod auf Dokumentebene; Zeiträume je Position gehören in die Rechnungsposition (BG-26).
Related rules
UBL-SR-07— A cac:BillingReference is present but the preceding invoice number (BT-25, InvoiceDocumentReference/cbc:ID)…UBL-SR-09— The seller name (BT-27) appears more than once — the supplier party may carry only one…UBL-SR-06— A cac:BillingReference contains more than one cac:InvoiceDocumentReference — each preceding-invoice…UBL-SR-10— The seller trading name (BT-28) appears more than once — the supplier party may carry only one PartyName/Name.UBL-SR-05— Payment terms (BT-20) appear more than once — across all cac:PaymentTerms elements only a single cbc:Note is…UBL-SR-11— The seller legal registration identifier (BT-30) appears more than once — only one…
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.