# BR-31: Document allowance amount (BT-92) missing

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

Every document-level allowance (BG-20, `cac:AllowanceCharge` with `ChargeIndicator` false in UBL, `ram:SpecifiedTradeAllowanceCharge` in the header settlement in CII) must state its amount, BT-92. 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-92, BG-20
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-31 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-31]-Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92).
```

## What it checks

Every document-level allowance (BG-20, `cac:AllowanceCharge` with `ChargeIndicator` false in UBL, `ram:SpecifiedTradeAllowanceCharge` in the header settlement in CII) must state its amount, BT-92.

## Why invoices fail it

The allowance is written as a percentage (BT-94) with no computed amount.

## How to fix it

Compute the amount (base × percentage / 100, rounded to two decimals) and write it in BT-92, keeping base and percentage if you give them.

## A failing invoice and its fix, checked

We start from our sample « allowance-and-charge », 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-31 and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-31** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge[1]/ram:ChargeIndicator` | Each Document level allowance (BG-20) shall have a Document level allowance amount (BT-92). |
| [BR-CO-11](/einvoice-rules/br-co-11) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation` | Sum of allowances on document level (BT-107) = Σ Document level allowance amount (BT-92). |
| [BR-S-08](/einvoice-rules/br-s-08) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax[1]/ram:CategoryCode` | For each different value of VAT category rate (BT-119) where the VAT category code (BT-118) is "Standard rated", the VAT category taxable amount (BT-116) in a VAT breakdown (BG-23) shall equal the sum of Invoice line net amounts (BT-131) plus the sum of document level charge amounts (BT-99) minus the sum of document level allowance amounts (BT-92) where the VAT category code (BT-151, BT-102, BT-95) is "Standard rated" and the VAT rate (BT-152, BT-103, BT-96) equals the VAT category rate (BT-119). |

```diff
  …
          <ram:CalculationPercent>3.00</ram:CalculationPercent>
          <ram:BasisAmount>1900.00</ram:BasisAmount>
+         <ram:ActualAmount>57.00</ram:ActualAmount>
          <ram:ReasonCode>95</ram:ReasonCode>
          <ram:Reason>Treuerabatt 3 %</ram:Reason>
  …
```

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

```xpath
context: //ram:ApplicableHeaderTradeSettlement/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-29: Invoicing period ends before it starts](https://veriport.io/einvoice-rules/br-29)
- [BR-30: Line period ends before it starts](https://veriport.io/einvoice-rules/br-30)
- [BR-32: Document allowance VAT category (BT-95) missing](https://veriport.io/einvoice-rules/br-32)
- [BR-33: Document allowance reason (BT-97/BT-98) missing](https://veriport.io/einvoice-rules/br-33)
- [BR-DEC-01: More than 2 decimals in BT-92 (Document level allowance amount)](https://veriport.io/einvoice-rules/br-dec-01)
- [BR-CO-11: Sum of document allowances (BT-107) ≠ allowances](https://veriport.io/einvoice-rules/br-co-11)
- [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)
