Validation rules

UBL-CR-001 — UBL rule

The document contains ext:UBLExtensions. Extensions are valid UBL but not part of the EN 16931 core model — receivers are free to ignore their content (embedded signatures included).

Rule
UBL-CR-001 — official EN 16931 / XRechnung rule
Severity
warning
Detected by
tier 3 — KoSIT validator (authoritative)
Reachability
Only reachable when validating your own XML — normbill-generated documents cannot trigger it

normbill's serializer never emits UBL extensions.

How to fix it

Remove the UBLExtensions block, or keep it only if your receiver explicitly supports it.

UBL-CR-001 auf Deutsch — was bedeutet der Fehler?

Der KoSIT-Validator meldet eine Warnung, weil das Dokument ext:UBLExtensions enthält. Extensions sind gültiges UBL, gehören aber nicht zum Kernmodell der EN 16931 — Empfänger dürfen ihren Inhalt (auch eingebettete Signaturen) ignorieren.

So beheben Sie den Fehler

Entfernen Sie den UBLExtensions-Block — oder behalten Sie ihn nur, wenn Ihr Empfänger ihn ausdrücklich unterstützt.

Related rules

  • UBL-CR-002 — cbc:UBLVersionID is present with a value other than 2.1. EN 16931 invoices are UBL 2.1 — omit the element or…
  • UBL-CR-006 — cbc:IssueTime is present. The EN 16931 core model works with dates only (BT-2) — a time of day is not part…
  • UBL-CR-561 — An invoice line contains cac:TaxTotal. In EN 16931 VAT is broken down at document level only (BG-23) — lines…
  • UBL-CR-646 — An invoice line contains cac:SubInvoiceLine. XRechnung prohibits sub-invoice lines — the KoSIT validator…

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.