# BR-CL-18: Line VAT category code not UNTDID 5305

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

The VAT category code of an invoice line, BT-151 (`cac:ClassifiedTaxCategory/cbc:ID` in UBL, `ram:ApplicableTradeTax/ram:CategoryCode` in CII), must be one of S, Z, E, AE, K, G, O, L, M, B. 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
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CL-18 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-CL-18]-Invoice tax categories MUST be coded using UNCL5305 code list
```

```text
[BR-CL-18]-Invoice tax categories MUST be coded using UNCL 5305 code list
```

## What it checks

The VAT category code of an invoice line, BT-151 (`cac:ClassifiedTaxCategory/cbc:ID` in UBL, `ram:ApplicableTradeTax/ram:CategoryCode` in CII), must be one of S, Z, E, AE, K, G, O, L, M, B.

## Why invoices fail it

The line carries a rate or an internal tax key instead of the category.

## How to fix it

Map the internal tax key to the category letter and write the rate in 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-CL-18 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| [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). |
| **BR-CL-18** | error | `/ubl:Invoice/cac:InvoiceLine[1]/cac:Item/cac:ClassifiedTaxCategory/cbc:ID` | Invoice tax categories MUST be coded using UNCL5305 code list |

```diff
  …
        <cbc:Name>Relaunch Website, Konzeption und Umsetzung</cbc:Name>
        <cac:ClassifiedTaxCategory>
-         <cbc:ID>VAT19</cbc:ID>
+         <cbc:ID>S</cbc:ID>
          <cbc:Percent>19.00</cbc:Percent>
          <cac:TaxScheme>
  …
```

## 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:ClassifiedTaxCategory/cbc:ID
test:    ( ( not(contains(normalize-space(.),' ')) and contains( ' AE L M E S Z G O K B ',concat(' ',normalize-space(.),' ') ) ) )
```

```xpath
context: ram:ApplicableTradeTax/ram:CategoryCode
test:    ((not(contains(normalize-space(.), ' ')) and contains(' AE L M E S Z G O K B ', concat(' ', normalize-space(.), ' '))))
```

## 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-CL-16: Payment means code (BT-81) not UNTDID 4461](https://veriport.io/einvoice-rules/br-cl-16)
- [BR-CL-17: VAT category code not UNTDID 5305](https://veriport.io/einvoice-rules/br-cl-17)
- [BR-CL-19: Allowance reason code not UNTDID 5189](https://veriport.io/einvoice-rules/br-cl-19)
- [BR-CL-20: Charge reason code not UNTDID 7161](https://veriport.io/einvoice-rules/br-cl-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)
