# BR-CO-04: Line VAT category code (BT-151) missing

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

Every invoice line must carry the VAT category code of the item, BT-151: `cac:Item/cac:ClassifiedTaxCategory/cbc:ID` in UBL, `ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode` 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-151, BG-25
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-04 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-04]-Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151).
```

## What it checks

Every invoice line must carry the VAT category code of the item, BT-151: `cac:Item/cac:ClassifiedTaxCategory/cbc:ID` in UBL, `ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax/ram:CategoryCode` in CII. The VAT breakdown is built from these codes.

## Why invoices fail it

Lines carry only the rate (19 %) and no category, or the category is written once at document level.

## How to fix it

Give every line its category (S standard, Z zero, E exempt, AE reverse charge, K intra-Community, G export, O not subject) and rate (BT-152).

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-04** | error | `/ubl:Invoice/cac:InvoiceLine[1]` | Each Invoice line (BG-25) shall be categorized with an Invoiced item VAT category code (BT-151). |
| [BR-S-08](/einvoice-rules/br-s-08) | error | `/ubl:Invoice/cac:TaxTotal/cac:TaxSubtotal/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). |
| [UBL-SR-48](/einvoice-rules/ubl-sr-48) | error | `/ubl:Invoice/cac:InvoiceLine[1]` | Invoice lines shall have one and only one classified tax category. |

```diff
  …
      <cac:Item>
        <cbc:Name>Relaunch Website, Konzeption und Umsetzung</cbc:Name>
+       <cac:ClassifiedTaxCategory>
+         <cbc:ID>S</cbc:ID>
+         <cbc:Percent>19.00</cbc:Percent>
+         <cac:TaxScheme>
+           <cbc:ID>VAT</cbc:ID>
+         </cac:TaxScheme>
+       </cac:ClassifiedTaxCategory>
      </cac:Item>
      <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:Item/cac:ClassifiedTaxCategory[cac:TaxScheme/(normalize-space(upper-case(cbc:ID))='VAT')]/cbc:ID)
```

```xpath
context: //ram:IncludedSupplyChainTradeLineItem
test:    (ram:SpecifiedLineTradeSettlement/ram:ApplicableTradeTax[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-CO-03: Tax point date and its code together](https://veriport.io/einvoice-rules/br-co-03)
- [BR-CO-05: Allowance reason code and text agree](https://veriport.io/einvoice-rules/br-co-05)
- [BR-CO-06: Charge reason code and text agree](https://veriport.io/einvoice-rules/br-co-06)
- [BR-16: At least one invoice line (BG-25)](https://veriport.io/einvoice-rules/br-16)
- [BR-AE-05: Category AE: wrong rate on a line](https://veriport.io/einvoice-rules/br-ae-05)
- [BR-AF-05: Category L: wrong rate on a line](https://veriport.io/einvoice-rules/br-af-05)
- [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)
