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

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

1. Why This Rule Triggers (Diagnostic Message)

Taken individually, the reason (BT-104) and the reason code (BT-105) on the document level charge at charges[0] are both optional terms — which is why this constraint exists separately from BR-38: it is the co-occurrence rule that forbids the one combination the cardinalities allow, namely neither. Supplying both is explicitly permitted and is usually the better answer, since the code is what a receiving system can act on automatically and the text is what a person reads.

2. How to Fix BR-CO-22

Add charges[0].reason, charges[0].reasonCode, or both. If no UNCL 7161 code fits what you are charging for, omit the code and write the reason as free text — the list has no "other" entry, and inventing a code fails BR-CL-20.

3. Valid Code / Payload Example

"reason": "Freight service", "reasonCode": "FC"