# BR-37: Document charge VAT category (BT-102) missing

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

Every document-level charge must carry a VAT category code, BT-102, since a charge (freight, packaging) is itself a taxable supply that lands in a VAT breakdown. 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-102, BG-21
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-37 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-37]-Each Document level charge (BG-21) shall have a Document level charge VAT category code (BT-102).
```

## What it checks

Every document-level charge must carry a VAT category code, BT-102, since a charge (freight, packaging) is itself a taxable supply that lands in a VAT breakdown.

## Why invoices fail it

Freight or packing is added as a charge without tax information.

## How to fix it

Give the charge the VAT category and rate (BT-103) that apply to it, usually those of the main supply.

## A failing invoice and its fix, checked

We start from our sample « allowance-and-charge », 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-37 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-37** | error | `/ubl:Invoice/cac:AllowanceCharge[3]` | Each Document level charge (BG-21) shall have a Document level charge VAT category code (BT-102). |
| [BR-S-08](/einvoice-rules/br-s-08) | error | `/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal[1]/cac:TaxCategory` | 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
  …
      <cbc:AllowanceChargeReason>Versand</cbc:AllowanceChargeReason>
      <cbc:Amount currencyID="EUR">24.90</cbc:Amount>
+     <cac:TaxCategory>
+       <cbc:ID>S</cbc:ID>
+       <cbc:Percent>19.00</cbc:Percent>
+       <cac:TaxScheme>
+         <cbc:ID>VAT</cbc:ID>
+       </cac:TaxScheme>
+     </cac:TaxCategory>
    </cac:AllowanceCharge>
    <cac:TaxTotal>
  …
```

## 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: /ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator = true()] | /cn:CreditNote/cac:AllowanceCharge[cbc:ChargeIndicator = true()]
test:    exists(cac:TaxCategory[cac:TaxScheme/normalize-space(upper-case(cbc:ID))='VAT']/cbc:ID)
```

```xpath
context: //ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge/ram:ChargeIndicator[udt:Indicator='true']
test:    (../ram:CategoryTradeTax[upper-case(ram:TypeCode) = 'VAT']/ram:CategoryCode)
```

## 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-33: Document allowance reason (BT-97/BT-98) missing](https://veriport.io/einvoice-rules/br-33)
- [BR-36: Document charge amount (BT-99) missing](https://veriport.io/einvoice-rules/br-36)
- [BR-38: Document charge reason (BT-104/BT-105) missing](https://veriport.io/einvoice-rules/br-38)
- [BR-41: Line allowance amount (BT-136) missing](https://veriport.io/einvoice-rules/br-41)
- [BR-AE-07: Category AE: wrong rate on a charge](https://veriport.io/einvoice-rules/br-ae-07)
- [BR-AF-07: Category L: wrong rate on a charge](https://veriport.io/einvoice-rules/br-af-07)
- [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)
