# BR-15: Amount due for payment (BT-115) missing

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

The totals must include BT-115, the amount due for payment: `cac:LegalMonetaryTotal/cbc:PayableAmount` in UBL, `ram:DuePayableAmount` in CII. 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-115
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-15 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-15]-An Invoice shall have the Amount due for payment (BT-115).
```

## What it checks

The totals must include BT-115, the amount due for payment: `cac:LegalMonetaryTotal/cbc:PayableAmount` in UBL, `ram:DuePayableAmount` in CII.

## Why invoices fail it

A credit note or a fully prepaid invoice is exported without an amount due instead of with 0.00.

## How to fix it

Always write BT-115, 0.00 when nothing is due; BR-CO-16 checks it against BT-112, BT-113 and BT-114.

## 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-15 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-15** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation` | An Invoice shall have the Amount due for payment (BT-115). |
| [BR-CO-16](/einvoice-rules/br-co-16) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation` | Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114). |

```diff
  …
          <ram:TaxTotalAmount currencyID="EUR">457.60</ram:TaxTotalAmount>
          <ram:GrandTotalAmount>2866.00</ram:GrandTotalAmount>
+         <ram:DuePayableAmount>2866.00</ram:DuePayableAmount>
        </ram:SpecifiedTradeSettlementHeaderMonetarySummation>
      </ram:ApplicableHeaderTradeSettlement>
  …
```

## 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:LegalMonetaryTotal
test:    exists(cbc:PayableAmount)
```

```xpath
context: //ram:SpecifiedTradeSettlementHeaderMonetarySummation
test:    (ram:DuePayableAmount)
```

## 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-13: Total without VAT (BT-109) missing](https://veriport.io/einvoice-rules/br-13)
- [BR-14: Total with VAT (BT-112) missing](https://veriport.io/einvoice-rules/br-14)
- [BR-16: At least one invoice line (BG-25)](https://veriport.io/einvoice-rules/br-16)
- [BR-17: Payee name (BT-59) when a payee is given](https://veriport.io/einvoice-rules/br-17)
- [BR-DEC-18: More than 2 decimals in BT-115 (Amount due for payment)](https://veriport.io/einvoice-rules/br-dec-18)
- [BR-DE-18: Skonto in payment terms (BT-20) malformed](https://veriport.io/einvoice-rules/br-de-18)
- [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)
