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

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

1. Why This Rule Triggers (Diagnostic Message)

The reason (BT-144) and the reason code (BT-145) on the invoice line charge at lines[0].charges[0] are individually optional terms, and this constraint — separate from BR-44, 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-24

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

3. Valid Code / Payload Example

"reason": "Handling", "reasonCode": "SH"