Validation rules

BR-CL-08 — EN 16931 rule

An invoice note (BT-22) starts with a #...# prefix whose subject code (BT-21) is not part of UNTDID 4451.

Rule: BR-CL-08 — official EN 16931 / XRechnung rule
Severity: error
Business term: BT-22 — Invoice note
Field in your JSON: invoice.notes
Detected by: tier 3 — KoSIT validator (authoritative)
Reachability: Triggerable from your request JSON (generate & validate)

The UBL binding embeds the note subject code as a #CODE# prefix inside cbc:Note. invoice.notes entries are free text and serialized verbatim, so a note that begins with an unknown three-letter code between two hashes triggers this rule.

How to fix it

Remove the leading #CODE# prefix from the entry in invoice.notes, or use a valid UNTDID 4451 code such as "#AAI#" (general information).

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

Eine Rechnungsnotiz (BT-22) beginnt mit einem "#...#"-Präfix, dessen Betreff-Code (BT-21) nicht in der UNTDID 4451 enthalten ist. In der UBL-Syntax wird der Notiz-Betreff als Präfix in cbc:Note codiert — eine Freitext-Notiz, die zufällig mit einem unbekannten Drei-Zeichen-Code zwischen zwei Rauten beginnt, führt zur Ablehnung durch den KoSIT-Validator.

So beheben Sie den Fehler

Entfernen Sie das führende "#CODE#"-Präfix aus dem Eintrag in invoice.notes — oder verwenden Sie einen gültigen UNTDID-4451-Code, z. B. "#AAI#" für allgemeine Informationen.

Related rules

BR-CL-07 — The scheme of an invoiced-object identifier (BT-18 schemeID) is not a UNTDID 1153 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).
BR-CL-10 — The scheme of a party identifier (BT-29/BT-46 schemeID) is not part of the ISO/IEC 6523 ICD list.
BR-CL-05 — The VAT accounting currency code (BT-6) is not part of ISO 4217.
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-04 — The invoice currency code (BT-5) is not part of ISO 4217.

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.