# BR-CO-17: VAT amount (BT-117) ≠ taxable amount × rate

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

In each VAT breakdown, the VAT amount (BT-117) must equal the taxable amount (BT-116) multiplied by the rate (BT-119) / 100, rounded to 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-116, BT-117, BT-119
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-17 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-CO-17]-VAT category tax amount (BT-117) = VAT category taxable amount (BT-116) x (VAT category rate (BT-119) / 100), rounded to two decimals.
```

## What it checks

In each VAT breakdown, the VAT amount (BT-117) must equal the taxable amount (BT-116) multiplied by the rate (BT-119) / 100, rounded to two decimals. EN 16931 computes VAT per breakdown, not per line.

## Why invoices fail it

VAT is computed on each line and the rounded line amounts are added, which differs by a cent or more from the VAT on the breakdown total; common with many lines or prices with four decimals.

## How to fix it

Compute VAT once per category and rate, on the breakdown’s taxable amount, and round that result.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-17** | error | `/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal` | VAT category tax amount (BT-117) = VAT category taxable amount (BT-116) x (VAT category rate (BT-119) / 100), rounded to two decimals. |
| [BR-S-09](/einvoice-rules/br-s-09) | error | `/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/cac:TaxCategory` | The VAT category tax amount (BT-117) in a VAT breakdown (BG-23) where VAT category code (BT-118) is "Standard rated" shall equal the VAT category taxable amount (BT-116) multiplied by the VAT category rate (BT-119). |

```diff
  …
    </cac:PaymentMeans>
    <cac:TaxTotal>
-     <cbc:TaxAmount currencyID="EUR">433.20</cbc:TaxAmount>
+     <cbc:TaxAmount currencyID="EUR">457.60</cbc:TaxAmount>
      <cac:TaxSubtotal>
        <cbc:TaxableAmount currencyID="EUR">2408.40</cbc:TaxableAmount>
-       <cbc:TaxAmount currencyID="EUR">433.20</cbc:TaxAmount>
+       <cbc:TaxAmount currencyID="EUR">457.60</cbc:TaxAmount>
        <cac:TaxCategory>
          <cbc:ID>S</cbc:ID>
  …
      <cbc:LineExtensionAmount currencyID="EUR">2408.40</cbc:LineExtensionAmount>
      <cbc:TaxExclusiveAmount currencyID="EUR">2408.40</cbc:TaxExclusiveAmount>
-     <cbc:TaxInclusiveAmount currencyID="EUR">2841.60</cbc:TaxInclusiveAmount>
-     <cbc:PayableAmount currencyID="EUR">2841.60</cbc:PayableAmount>
+     <cbc:TaxInclusiveAmount currencyID="EUR">2866.00</cbc:TaxInclusiveAmount>
+     <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:TaxTotal/cac:TaxSubtotal
test:    (round(cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/xs:decimal(cbc:Percent)) = 0 and (round(xs:decimal(cbc:TaxAmount)) = 0)) or (round(cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/xs:decimal(cbc:Percent)) != 0 and ((abs(xs:decimal(cbc:TaxAmount)) - 1 < round(abs(xs:decimal(cbc:TaxableAmount)) * (cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/xs:decimal(cbc:Percent) div 100) * 10 * 10) div 100 ) and (abs(xs:decimal(cbc:TaxAmount)) + 1 > round(abs(xs:decimal(cbc:TaxableAmount)) * (cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/xs:decimal(cbc:Percent) div 100) * 10 * 10) div 100 ))) or (not(exists(cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/xs:decimal(cbc:Percent))) and (round(xs:decimal(cbc:TaxAmount)) = 0))
```

```xpath
context: //ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax
test:    (round(.[normalize-space(upper-case(ram:TypeCode)) = 'VAT']/xs:decimal(ram:RateApplicablePercent)) = 0 and (round(xs:decimal(ram:CalculatedAmount)) = 0)) or (round(.[normalize-space(upper-case(ram:TypeCode)) = 'VAT']/xs:decimal(ram:RateApplicablePercent)) != 0 and ((abs(xs:decimal(ram:CalculatedAmount)) - 1 <= round(abs(xs:decimal(ram:BasisAmount)) * (.[normalize-space(upper-case(ram:TypeCode)) = 'VAT']/xs:decimal(ram:RateApplicablePercent) div 100) * 10 * 10) div 100 ) and (abs(xs:decimal(ram:CalculatedAmount)) + 1 >= round(abs(xs:decimal(ram:BasisAmount)) * (.[normalize-space(upper-case(ram:TypeCode)) = 'VAT']/xs:decimal(ram:RateApplicablePercent) div 100) * 10 * 10) div 100 ))) or (not(exists(.[normalize-space(upper-case(ram:TypeCode))='VAT']/xs:decimal(ram:RateApplicablePercent))) and (round(xs:decimal(ram:CalculatedAmount)) = 0))
```

## 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-CO-15: Total with VAT ≠ total without VAT + VAT](https://veriport.io/einvoice-rules/br-co-15)
- [BR-CO-16: Amount due (BT-115) does not add up](https://veriport.io/einvoice-rules/br-co-16)
- [BR-CO-18: At least one VAT breakdown (BG-23)](https://veriport.io/einvoice-rules/br-co-18)
- [BR-CO-19: Empty invoicing period (BG-14)](https://veriport.io/einvoice-rules/br-co-19)
- [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)
- [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)
