SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BT-139, BT-140

BR-CO-23 — E-Invoice Validation Rule & Fix

Fixture ID: lineAllowanceEmpty · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:AllowanceCharge[1]/cbc:AllowanceChargeReasonCode

1. Why This Rule Triggers (Diagnostic Message)

The reason (BT-139) and the reason code (BT-140) on the invoice line allowance at lines[0].allowances[0] are individually optional terms, and this constraint — separate from BR-42, which is the cardinality rule on the group — is what rules out the one combination those cardinalities would otherwise permit: neither present. Supplying both is allowed and preferable, because the code is machine-actionable and the text is what a person reads.

2. How to Fix BR-CO-23

Add lines[0].allowances[0].reason, lines[0].allowances[0].reasonCode, or both. Where no UNCL 5189 code describes what you are deducting, omit the code entirely and use free text — the lists have no "other" entry, and an invented code fails BR-CL-19.

3. Valid Code / Payload Example

"reason": "Special agreement", "reasonCode": "100"
Test & Validate XML / JSON in Live SchemaGuard Validator →