# BR-CL-01: Invoice type code not in UNTDID 1001

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

The invoice type code (BT-3) must be one of the UNTDID 1001 codes that EN 16931 lists for invoices and credit notes (380, 381, 383, 384, 386, 389, 751, 875, 876, 877 and others). 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-01 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-01]-The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001.
```

## What it checks

The invoice type code (BT-3) must be one of the UNTDID 1001 codes that EN 16931 lists for invoices and credit notes (380, 381, 383, 384, 386, 389, 751, 875, 876, 877 and others).

## Why invoices fail it

An internal document type (« RE », « GS »), a code for another document (an order 220) or a typo is written in BT-3.

## How to fix it

Map document types to UNTDID 1001: 380 invoice, 381 credit note, 384 corrected invoice, 386 prepayment invoice, 326 partial invoice.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CL-01** | error | `/ubl:Invoice/cbc:InvoiceTypeCode` | The document type code MUST be coded by the invoice and credit note related code lists of UNTDID 1001. |

```diff
  …
    <cbc:IssueDate>2026-10-20</cbc:IssueDate>
    <cbc:DueDate>2026-11-03</cbc:DueDate>
-   <cbc:InvoiceTypeCode>220</cbc:InvoiceTypeCode>
+   <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
    <cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
    <cbc:BuyerReference>EK-2026-0345</cbc:BuyerReference>
  …
```

## 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: cbc:InvoiceTypeCode | cbc:CreditNoteTypeCode
test:    (self::cbc:InvoiceTypeCode and ((not(contains(normalize-space(.), ' ')) and contains(' 71 80 81 82 84 102 130 202 203 204 211 218 219 295 325 326 331 380 382 383 384 385 386 387 388 389 390 393 394 395 456 457 471 472 473 500 501 527 553 575 623 633 751 780 817 870 875 876 877 935 ', concat(' ', normalize-space(.), ' '))))) or (self::cbc:CreditNoteTypeCode and ((not(contains(normalize-space(.), ' ')) and contains(' 81 83 261 262 296 308 381 396 420 458 502 503 532 ', concat(' ', normalize-space(.), ' ')))))
```

```xpath
context: rsm:ExchangedDocument/ram:TypeCode
test:    ((not(contains(normalize-space(.), ' ')) and contains(' 71 80 81 82 83 84 102 130 202 203 204 211 218 219 261 262 295 296 308 325 326 331 380 381 382 383 384 385 386 387 388 389 390 393 394 395 396 420 456 457 458 471 472 473 500 501 502 503 527 532 553 575 623 633 751 780 817 870 875 876 877 935 ', 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-03: Amount currencyID not an ISO 4217 code](https://veriport.io/einvoice-rules/br-cl-03)
- [BR-CL-04: Invoice currency code (BT-5) not ISO 4217](https://veriport.io/einvoice-rules/br-cl-04)
- [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)
