# BR-DEC-23: More than 2 decimals in BT-131 (Invoice line net amount)

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

The invoice line net amount, BT-131 (`cac:InvoiceLine/cbc:LineExtensionAmount` in UBL, `ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount` 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-131
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DEC-23 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-23]-The allowed maximum number of decimals for the Invoice line net amount (BT-131) is 2.
```

## What it checks

The invoice line net amount, BT-131 (`cac:InvoiceLine/cbc:LineExtensionAmount` in UBL, `ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount` 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 line amount is quantity × unit price with a price of three or four decimals (1,523.4 l × 1.0789 = 1,643.59626) and is not rounded. The unit price itself may keep more decimals; the line amount may not.

## How to fix it

Round BT-131 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-23 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DEC-23** | error | `/ubl:Invoice/cac:InvoiceLine[1]` | The allowed maximum number of decimals for the Invoice line net amount (BT-131) is 2. |
| [UBL-DT-01](/einvoice-rules/ubl-dt-01) | error | `/ubl:Invoice/cac:InvoiceLine[1]/cbc:LineExtensionAmount` | Amounts shall be decimal up to two fraction digits |

```diff
  …
      <cbc:ID>1</cbc:ID>
      <cbc:InvoicedQuantity unitCode="HUR">24.00</cbc:InvoicedQuantity>
-     <cbc:LineExtensionAmount currencyID="EUR">2280.004</cbc:LineExtensionAmount>
+     <cbc:LineExtensionAmount currencyID="EUR">2280.00</cbc:LineExtensionAmount>
      <cac:Item>
        <cbc:Name>Relaunch Website, Konzeption und Umsetzung</cbc:Name>
  …
```

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

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    string-length(substring-after(ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount,'.'))<=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-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-DEC-24: More than 2 decimals in BT-136 (Invoice line allowance amount)](https://veriport.io/einvoice-rules/br-dec-24)
- [BR-DEC-25: More than 2 decimals in BT-137 (Invoice line allowance base amount)](https://veriport.io/einvoice-rules/br-dec-25)
- [BR-24: Line net amount (BT-131) missing](https://veriport.io/einvoice-rules/br-24)
- [BR-CO-10: Sum of line net amounts (BT-106) ≠ the lines](https://veriport.io/einvoice-rules/br-co-10)
- [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)
