# BR-DEC-18: More than 2 decimals in BT-115 (Amount due for payment)

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

The amount due for payment, BT-115 (`cac:LegalMonetaryTotal/cbc:PayableAmount` in UBL, `ram:DuePayableAmount` in CII), may have at most two decimals. 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-DEC-18 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-DEC-18]-The allowed maximum number of decimals for the Amount due for payment (BT-115) is 2.
```

## What it checks

The amount due for payment, BT-115 (`cac:LegalMonetaryTotal/cbc:PayableAmount` in UBL, `ram:DuePayableAmount` in CII), may have at most two decimals. EN 16931 amounts are in the currency’s cents; only prices (BT-146, BT-148) and quantities may carry more.

## Why invoices fail it

The amount due is derived from unrounded totals.

## How to fix it

Round BT-115 to two decimals (commercial rounding, half away from zero) before writing it, and compute every total that depends on it from the rounded value.

## 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 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-DEC-18 and 2 other rules, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-CO-16](/einvoice-rules/br-co-16) | error | `/ubl:Invoice/cac:LegalMonetaryTotal` | Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114). |
| **BR-DEC-18** | error | `/ubl:Invoice/cac:LegalMonetaryTotal` | The allowed maximum number of decimals for the Amount due for payment (BT-115) is 2. |
| [UBL-DT-01](/einvoice-rules/ubl-dt-01) | error | `/ubl:Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount` | Amounts shall be decimal up to two fraction digits |

```diff
  …
      <cbc:TaxExclusiveAmount currencyID="EUR">2408.40</cbc:TaxExclusiveAmount>
      <cbc:TaxInclusiveAmount currencyID="EUR">2866.00</cbc:TaxInclusiveAmount>
-     <cbc:PayableAmount currencyID="EUR">2866.004</cbc:PayableAmount>
+     <cbc:PayableAmount currencyID="EUR">2866.00</cbc:PayableAmount>
    </cac:LegalMonetaryTotal>
    <cac:InvoiceLine>
  …
```

## 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:    string-length(substring-after(cbc:PayableAmount,'.'))<=2
```

```xpath
context: //ram:SpecifiedTradeSettlementHeaderMonetarySummation
test:    string-length(substring-after(ram:DuePayableAmount,'.'))<=2
```

## 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-DEC-16: More than 2 decimals in BT-113 (Paid amount)](https://veriport.io/einvoice-rules/br-dec-16)
- [BR-DEC-17: More than 2 decimals in BT-114 (Rounding amount)](https://veriport.io/einvoice-rules/br-dec-17)
- [BR-DEC-19: More than 2 decimals in BT-116 (VAT category taxable amount)](https://veriport.io/einvoice-rules/br-dec-19)
- [BR-DEC-20: More than 2 decimals in BT-117 (VAT category tax amount)](https://veriport.io/einvoice-rules/br-dec-20)
- [BR-15: Amount due for payment (BT-115) missing](https://veriport.io/einvoice-rules/br-15)
- [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)
