Validation rules
BR-CO-22 — EN 16931 rule
A document-level charge (BG-21) carries neither a reason text (BT-104) nor a reason code (BT-105) — at least one is required.
- Rule
BR-CO-22— official EN 16931 / XRechnung rule- Severity
- error
- Business term
BT-104- Detected by
- tier 1 — normbill pre-flight (also in the playground)
- Reachability
- Triggerable from your request JSON (generate & validate)
normbill's pre-flight reports the equivalent finding as BR-38 at tier 1.
How to fix it
Set the charge's reason (e.g. "Versandkosten") or a UNCL 7161 reason_code.
BR-CO-22 auf Deutsch — was bedeutet der Fehler?
Ein Zuschlag auf Dokumentebene (BG-21) trägt weder einen Grundtext (BT-104) noch einen Grundcode (BT-105) — mindestens eines ist Pflicht.
So beheben Sie den Fehler
Setzen Sie reason des Zuschlags (z. B. "Versandkosten") oder einen UNCL-7161-reason_code. normbill meldet denselben Befund bereits vorab als BR-38.
Related rules
BR-38— A document-level charge must state what it is for (BT-104/BT-105).BR-CO-21— A document-level allowance (BG-20) carries neither a reason text (BT-97) nor a reason code (BT-98) — at…BR-CO-23— An invoice line allowance (BG-27) carries neither a reason text (BT-139) nor a reason code (BT-140) — at…BR-CO-20— An invoice line period (BG-26) is present but carries neither a start date (BT-134) nor an end date (BT-135).BR-CO-24— An invoice line charge (BG-28) carries neither a reason text (BT-144) nor a reason code (BT-145) — at least…BR-CO-25— An amount is due but neither a due date (BT-9) nor payment terms (BT-20) are present.
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.