What it means
A charge on an invoice line (BG-28) has neither a reason in words (BT-144) nor a reason code (BT-145).
Why it matters
Without a reason the recipient cannot tell what the extra amount on the line is for.
How to fix it
On that line, add a short reason such as "Packing", a code from the UNTDID 7161 list, or both.
The rule as published
Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both. Business terms: BG-28, BT-144, BT-145
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 |
| Factur-X 1.09 BASIC | 1.0.9-2 |
| Factur-X 1.09 EN 16931 | 1.0.9-2 |
| ZUGFeRD 2.5 BASIC | 2.5.2 |
| ZUGFeRD 2.5 EN 16931 | 2.5.2 |
| 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-CO-24 still fails, and which other rules do.
Related rules
- BR-FXEXT-BR-44 Each charge on an invoice line needs a reason
- BR-CO-08 Line charge reason code and text must match
- BR-43 Amount of a line charge is required
- BR-RO-L1023 Charge reason on a line: 100 characters at most
- BR-CO-25 A positive amount due needs a due date or payment terms
- BR-CO-26 The seller must be identifiable