Validation rules

BR-CL-10 — EN 16931 rule

The scheme of a party identifier (BT-29/BT-46 schemeID) is not part of the ISO/IEC 6523 ICD list.

Rule: BR-CL-10 — official EN 16931 / XRechnung rule
Severity: error
Detected by: tier 3 — KoSIT validator (authoritative)
Reachability: Not expressible through the normbill invoice model — documented for completeness

The serializer emits party identifiers (BT-29/BT-46 from seller.id / buyer.id) without a schemeID attribute, so the ICD membership check can never fire on generated documents. Fatal in the primary CIUS scenario (only the Extension scenario downgrades it).

How to fix it

Use an ISO 6523 ICD value (e.g. "0088" for GLN) as the schemeID, or drop the attribute; only the seller identifier may additionally use "SEPA".

BR-CL-10 auf Deutsch — was bedeutet der Fehler?

Das Schemakennzeichen einer Parteikennung (BT-29/BT-46, schemeID) stammt nicht aus der ISO/IEC-6523-ICD-Liste. Das normbill-Datenmodell kennt keine Parteikennungen; die gepinnte KoSIT-Konfiguration stuft die Regel zudem nur als Information ein, und die normbill-API filtert solche Meldungen aus dem Report.

So beheben Sie den Fehler

Verwenden Sie einen ICD-Code (z. B. "0088" für GLN) als schemeID — oder entfernen Sie das Attribut. Nur die Verkäuferkennung darf zusätzlich "SEPA" verwenden.

Related rules

BR-CL-11 — The scheme of a legal registration identifier (BT-30/BT-47 schemeID) is not part of the ISO/IEC 6523 ICD list.
BR-CL-08 — An invoice note (BT-22) starts with a #...# prefix whose subject code (BT-21) is not part of UNTDID 4451.
BR-CL-07 — The scheme of an invoiced-object identifier (BT-18 schemeID) is not a UNTDID 1153 code.
BR-CL-13 — The list identifier of an item classification (BT-158 listID) is not a UNTDID 7143 code.
BR-CL-14 — A country code in the invoice is not an ISO 3166-1 alpha-2 code.
BR-CL-06 — The VAT point date code (BT-8) is not one of the UNTDID 2005 codes EN 16931 permits (3, 35 or 432).

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.