Validation rules

BR-CO-05 — EN 16931 rule

The document-level allowance reason code (BT-98) and reason text (BT-97) should describe the same type of allowance.

Rule: BR-CO-05 — 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 pinned Schematron implements this as an always-true assertion (semantic agreement between code and free text cannot be machine-checked), so the validator never reports it in practice.

How to fix it

Align the allowance's reason and reason_code so they describe the same thing.

BR-CO-05 auf Deutsch — was bedeutet der Fehler?

Der Code des Nachlassgrundes (BT-98) und der Grundtext (BT-97) sollen denselben Nachlasstyp beschreiben. Die amtliche Schematron-Implementierung prüft dies faktisch nicht (Always-true-Assertion).

So beheben Sie den Fehler

Bringen Sie reason und reason_code des Nachlasses inhaltlich in Übereinstimmung.

Related rules

BR-CO-04 — An invoice line is not categorized with a VAT category code (BT-151).
BR-CO-06 — The document-level charge reason code (BT-105) and reason text (BT-104) should describe the same type of…
BR-CO-03 — The VAT point date (BT-7) and the VAT point date code (BT-8) are mutually exclusive — an invoice may carry…
BR-CO-07 — An invoice line allowance reason code (BT-140) and reason text (BT-139) should describe the same type of…
BR-CO-08 — An invoice line charge reason code (BT-145) and reason text (BT-144) should describe the same type of charge.
BR-CO-09 — A VAT identifier (seller BT-31, buyer BT-48, or tax representative BT-63) does not start with an ISO 3166-1…

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.