# BR-CO-22: Document charge without a reason

Source: https://veriport.io/einvoice-rules/br-co-22 (published 2026-11-17)

Each document-level charge (BG-21) must contain a reason text (BT-104), a reason code (BT-105), or both. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [EN 16931 business rules](/einvoice-rules/en16931), CEN EN 16931 validation artefacts 1.3.16
- **Severity:** error
- **Business terms:** BT-104, BT-105, BG-21
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-22 is a rule of the EN 16931 business rules (CEN validation artefacts 1.3.16) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-CO-22]-Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.
```

## What it checks

Each document-level charge (BG-21) must contain a reason text (BT-104), a reason code (BT-105), or both. Same requirement as BR-38.

## Why invoices fail it

Charges are written as bare amounts.

## How to fix it

Add a reason text or a UNTDID 7161 code to each document-level charge.

## A failing invoice and its fix, checked

We start from our sample « allowance-and-charge », written by our own generator as EN 16931 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-CO-22 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-38](/einvoice-rules/br-38) | error | `/ubl:Invoice/cac:AllowanceCharge[3]` | Each Document level charge (BG-21) shall have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105). |
| **BR-CO-22** | error | `/ubl:Invoice/cac:AllowanceCharge[3]` | Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both. |

```diff
  …
    <cac:AllowanceCharge>
      <cbc:ChargeIndicator>true</cbc:ChargeIndicator>
+     <cbc:AllowanceChargeReasonCode>FC</cbc:AllowanceChargeReasonCode>
+     <cbc:AllowanceChargeReason>Versand</cbc:AllowanceChargeReason>
      <cbc:Amount currencyID="EUR">24.90</cbc:Amount>
      <cac:TaxCategory>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from CEN EN 16931 validation artefacts 1.3.16. An `assert` fails when its test is false.

Text and test: © CEN/TC 434, EN 16931 validation artefacts, EUPL 1.2. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
test:    exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)
```

```xpath
context: //ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator[udt:Indicator='true']
test:    (../ram:Reason) or (../ram:ReasonCode)
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-CO-20: Empty line period (BG-26)](https://veriport.io/einvoice-rules/br-co-20)
- [BR-CO-21: Document allowance without a reason](https://veriport.io/einvoice-rules/br-co-21)
- [BR-CO-23: Line allowance without a reason](https://veriport.io/einvoice-rules/br-co-23)
- [BR-CO-24: Line charge without a reason](https://veriport.io/einvoice-rules/br-co-24)
- [BR-38: Document charge reason (BT-104/BT-105) missing](https://veriport.io/einvoice-rules/br-38)
- [BR-36: Document charge amount (BT-99) missing](https://veriport.io/einvoice-rules/br-36)
- [All EN 16931 business rules](https://veriport.io/einvoice-rules/en16931)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- EN 16931 validation artefacts 1.3.16 (UBL and CII schematron, the business rules BR-*) — https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.16 (2026-10-28)
- EN 16931 validation artefacts: licence, European Union Public Licence (EUPL) v1.2 (LICENSE.txt, the README « License » section and the release notes of validation-1.3.16) — https://github.com/ConnectingEurope/eInvoicing-EN16931/blob/master/LICENSE.txt (2026-11-17)
