What it means
When a charge gives a reason code, on the whole invoice (BT-105) or on a line (BT-145), it must be a code from UNTDID 7161, for example FC for freight, ABL for packaging or SAA for shipping and handling.
Why it matters
Codes are read by software, not by people. A value outside the agreed code list cannot be interpreted, so the recipient's system rejects the invoice even when the value looks sensible to a person.
How to fix it
Choose the reason code from the list in your invoicing software, or leave the code out and describe the charge in words instead. Discount codes from UNTDID 5189 such as 95 are not valid for charges. In the XML the code goes in cbc:AllowanceChargeReasonCode (UBL) or ram:ReasonCode (CII).
The rule as published
Coded charge reasons MUST belong to the UNCL 7161 code list Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (UBL) | 1.3.17 |
| EN 16931 (UBL credit note) | 1.3.17 |
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (UBL) | 3.0.2 |
| XRechnung 3.0 (UBL credit note) | 3.0.2 |
| XRechnung 3.0 (CII) | 3.0.2 |
| Peppol BIS Billing 3.0 (invoice) | 2026.5 |
| Peppol BIS Billing 3.0 (credit note) | 2026.5 |
| SI-UBL 2.0 / NLCIUS (invoice) | 2.0.3.13 |
| SI-UBL 2.0 / NLCIUS (credit note) | 2.0.3.13 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (UBL invoice) | 1.4.0-04 |
| France CTC (UBL credit note) | 1.4.0-04 |
| France CTC (CII) | 1.4.0-04 |
| CIUS-RO UBL Invoice 1.0.9 | 1.0.9 |
| CIUS-RO UBL Credit Note 1.0.9 | 1.0.9 |
Check your file
Drop your e-invoice to see whether BR-CL-20 still fails, and which other rules do.
Related rules
- BR-CL-21 The item standard identifier scheme must come from ISO 6523
- BR-CL-22 VAT exemption reason codes must come from the VATEX list
- BR-CL-23 Units of measure must come from UN/ECE Recommendation 20 or 21
- BR-CL-24 Attachments must be PDF, PNG, JPEG, CSV, XLSX or ODS
- BR-CL-25 Electronic address schemes must come from the EAS list
- BR-CL-26 The delivery location scheme must come from ISO 6523