# BR-41: Line allowance amount (BT-136) missing

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

Every allowance on an invoice line (BG-27, `cac:AllowanceCharge` inside `cac:InvoiceLine` with indicator false, `ram:SpecifiedTradeAllowanceCharge` in the line settlement in CII) must state its amount, BT-136. 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-136, BG-27
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-41 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-41]-Each Invoice line allowance (BG-27) shall have an Invoice line allowance amount (BT-136).
```

## What it checks

Every allowance on an invoice line (BG-27, `cac:AllowanceCharge` inside `cac:InvoiceLine` with indicator false, `ram:SpecifiedTradeAllowanceCharge` in the line settlement in CII) must state its amount, BT-136.

## Why invoices fail it

A line discount is written as a percentage only.

## How to fix it

Compute the line allowance amount and write it in BT-136; it reduces the line net amount (BT-131).

## 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-41.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-41** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]/ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator` | Each Invoice line allowance (BG-27) shall have an Invoice line allowance amount (BT-136). |

```diff
  …
              <udt:Indicator>false</udt:Indicator>
            </ram:ChargeIndicator>
+           <ram:ActualAmount>80.00</ram:ActualAmount>
            <ram:Reason>Rabatt</ram:Reason>
          </ram:SpecifiedTradeAllowanceCharge>
  …
```

## 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 = false()] | //cac:CreditNoteLine/cac:AllowanceCharge[cbc:ChargeIndicator = false()]
test:    exists(cbc:Amount)
```

```xpath
context: //ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator[udt:Indicator = 'false']
test:    (../ram:ActualAmount)
```

## 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-37: Document charge VAT category (BT-102) missing](https://veriport.io/einvoice-rules/br-37)
- [BR-38: Document charge reason (BT-104/BT-105) missing](https://veriport.io/einvoice-rules/br-38)
- [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-DEC-24: More than 2 decimals in BT-136 (Invoice line allowance amount)](https://veriport.io/einvoice-rules/br-dec-24)
- [BR-CO-23: Line allowance without a reason](https://veriport.io/einvoice-rules/br-co-23)
- [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)
