# BR-28: Item gross price (BT-148) negative

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

When given, the item gross price, BT-148, must not be negative: `cac:Price/cac:AllowanceCharge/cbc:BaseAmount` in UBL, `ram:GrossPriceProductTradePrice/ram:ChargeAmount` 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-148
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-28 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-28]-The Item gross price (BT-148) shall NOT be negative.
```

## What it checks

When given, the item gross price, BT-148, must not be negative: `cac:Price/cac:AllowanceCharge/cbc:BaseAmount` in UBL, `ram:GrossPriceProductTradePrice/ram:ChargeAmount` in CII.

## Why invoices fail it

A price rebate is mapped as a negative gross price instead of a price allowance.

## How to fix it

Write the list price as a positive gross price and the rebate as the price allowance (BT-147); the net price is gross minus rebate.

## 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-28.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-28** | error | `/ubl:Invoice/cac:InvoiceLine[1]` | The Item gross price (BT-148) shall NOT be negative. |

```diff
  …
          <cbc:ChargeIndicator>false</cbc:ChargeIndicator>
          <cbc:Amount currencyID="EUR">5.00</cbc:Amount>
-         <cbc:BaseAmount currencyID="EUR">-100.00</cbc:BaseAmount>
+         <cbc:BaseAmount currencyID="EUR">100.00</cbc:BaseAmount>
        </cac:AllowanceCharge>
      </cac:Price>
  …
```

## 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:    (cac:Price/cac:AllowanceCharge/cbc:BaseAmount) >= 0 or not(exists(cac:Price/cac:AllowanceCharge/cbc:BaseAmount))
```

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    (ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:ChargeAmount >= 0) or not(ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:ChargeAmount)
```

## 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-26: Item net price (BT-146) missing](https://veriport.io/einvoice-rules/br-26)
- [BR-27: Item net price (BT-146) negative](https://veriport.io/einvoice-rules/br-27)
- [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)
- [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)
