# BR-44: Line charge reason (BT-144/BT-145) missing

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

Every line charge must have a reason text (BT-144) or a UNTDID 7161 reason code (BT-145). 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-144, BT-145, BG-28
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-44 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-44]-Each Invoice line charge shall have an Invoice line charge reason or an invoice line allowance reason code.
```

```text
[BR-44]-Each Invoice line charge (BG-28) shall have an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145).
```

## What it checks

Every line charge must have a reason text (BT-144) or a UNTDID 7161 reason code (BT-145).

## Why invoices fail it

Line surcharges carry only an amount.

## How to fix it

Add a reason text or code to each line charge.

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as EN 16931 in CII. 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-44 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-44** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]/ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator` | Each Invoice line charge (BG-28) shall have an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145). |
| [BR-CO-24](/einvoice-rules/br-co-24) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]/ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator` | 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. |

```diff
  …
            </ram:ChargeIndicator>
            <ram:ActualAmount>80.00</ram:ActualAmount>
+           <ram:Reason>Expresszuschlag</ram:Reason>
          </ram:SpecifiedTradeAllowanceCharge>
          <ram:SpecifiedTradeSettlementLineMonetarySummation>
  …
```

## 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: //cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | //cac:CreditNoteLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
test:    exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)
```

```xpath
context: //ram:SpecifiedLineTradeSettlement/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-42: Line allowance reason (BT-139/BT-140) missing](https://veriport.io/einvoice-rules/br-42)
- [BR-43: Line charge amount (BT-141) missing](https://veriport.io/einvoice-rules/br-43)
- [BR-45: VAT breakdown taxable amount (BT-116) missing](https://veriport.io/einvoice-rules/br-45)
- [BR-46: VAT breakdown tax amount (BT-117) missing](https://veriport.io/einvoice-rules/br-46)
- [BR-CO-08: Line charge reason code and text agree](https://veriport.io/einvoice-rules/br-co-08)
- [BR-CO-24: Line charge without a reason](https://veriport.io/einvoice-rules/br-co-24)
- [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)
