Validation rules

BR-CO-24 — EN 16931 rule

An invoice line charge (BG-28) carries neither a reason text (BT-144) nor a reason code (BT-145) — at least one is required.

Rule
BR-CO-24 — official EN 16931 / XRechnung rule
Severity
error
Business term
BT-144
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-44 at tier 1.

How to fix it

Set the line charge's reason or a UNCL 7161 reason_code.

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

Ein Positionszuschlag (BG-28) trägt weder einen Grundtext (BT-144) noch einen Grundcode (BT-145) — mindestens eines ist Pflicht.

So beheben Sie den Fehler

Setzen Sie reason des Positionszuschlags oder einen UNCL-7161-reason_code. normbill meldet denselben Befund bereits vorab als BR-44.

Related rules

  • BR-44 — A line-level charge must state what it is for (BT-144/BT-145).
  • BR-CO-25 — An amount is due but neither a due date (BT-9) nor payment terms (BT-20) are present.
  • 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-26 — The seller carries none of: VAT identifier (BT-31), legal registration identifier (BT-30) or seller…
  • BR-CO-22 — A document-level charge (BG-21) carries neither a reason text (BT-104) nor a reason code (BT-105) — at least…
  • BR-CO-21 — A document-level allowance (BG-20) carries neither a reason text (BT-97) nor a reason code (BT-98) — at…

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.