# BR-24: Line net amount (BT-131) missing

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

Every line must state its net amount, BT-131: `cbc:LineExtensionAmount` of the line in UBL, `ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount` 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-131, BG-25
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-24 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-24]-Each Invoice line (BG-25) shall have an Invoice line net amount (BT-131).
```

## What it checks

Every line must state its net amount, BT-131: `cbc:LineExtensionAmount` of the line in UBL, `ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount` in CII.

## Why invoices fail it

Only the unit price and quantity are written, leaving the receiver to multiply.

## How to fix it

Write the line net amount: quantity × net price (per base quantity), minus line allowances, plus line charges, rounded to two decimals.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| [BR-CO-10](/einvoice-rules/br-co-10) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation` | Sum of Invoice line net amount (BT-106) = Σ Invoice line net amount (BT-131). |
| **BR-24** | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItem[1]` | Each Invoice line (BG-25) shall have an Invoice line net amount (BT-131). |
| [BR-S-08](/einvoice-rules/br-s-08) | error | `/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/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:ApplicableTradeTax>
          <ram:SpecifiedTradeSettlementLineMonetarySummation>
-           
+           <ram:LineTotalAmount>2280.00</ram:LineTotalAmount>
          </ram:SpecifiedTradeSettlementLineMonetarySummation>
        </ram:SpecifiedLineTradeSettlement>
  …
```

## 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:    exists(cbc:LineExtensionAmount)
```

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    (ram:SpecifiedLineTradeSettlement/ram:SpecifiedTradeSettlementLineMonetarySummation/ram:LineTotalAmount)
```

## 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-22: Invoiced quantity (BT-129) missing](https://veriport.io/einvoice-rules/br-22)
- [BR-23: Unit of measure code (BT-130) missing](https://veriport.io/einvoice-rules/br-23)
- [BR-25: Item name (BT-153) missing](https://veriport.io/einvoice-rules/br-25)
- [BR-26: Item net price (BT-146) missing](https://veriport.io/einvoice-rules/br-26)
- [BR-DEC-23: More than 2 decimals in BT-131 (Invoice line net amount)](https://veriport.io/einvoice-rules/br-dec-23)
- [BR-CO-04: Line VAT category code (BT-151) missing](https://veriport.io/einvoice-rules/br-co-04)
- [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)
