# BR-CL-06: VAT point date code (BT-8) not allowed

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

The VAT point date code, BT-8, must be one of the UNTDID 2005 codes EN 16931 allows: 3 (invoice issue date), 35 (delivery date) or 432 (paid-to date). 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-06 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-06]-Value added tax point date code MUST be coded using a restriction of UNTDID 2005.
```

```text
[BR-CL-06]-Value added tax point date code MUST be coded using a restriction of UNTDID 2475.
```

## What it checks

The VAT point date code, BT-8, must be one of the UNTDID 2005 codes EN 16931 allows: 3 (invoice issue date), 35 (delivery date) or 432 (paid-to date). In CII the codes are 5, 29 and 72 of UNTDID 2475.

## Why invoices fail it

Another date code (137 document date) is copied from a generic list.

## How to fix it

Use 3, 35 or 432 in UBL (5, 29, 72 in CII), or give the date itself in BT-7 instead.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CL-06** | error | `/ubl:Invoice/cac:InvoicePeriod/cbc:DescriptionCode` | Value added tax point date code MUST be coded using a restriction of UNTDID 2005. |

```diff
  …
      <cbc:StartDate>2026-10-01</cbc:StartDate>
      <cbc:EndDate>2026-10-31</cbc:EndDate>
-     <cbc:DescriptionCode>137</cbc:DescriptionCode>
+     <cbc:DescriptionCode>3</cbc:DescriptionCode>
    </cac:InvoicePeriod>
    <cac:AccountingSupplierParty>
  …
```

## 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:InvoicePeriod/cbc:DescriptionCode
test:    ((not(contains(normalize-space(.), ' ')) and contains(' 3 35 432 ', concat(' ', normalize-space(.), ' '))))
```

```xpath
context: ram:DueDateTypeCode
test:    ((not(contains(normalize-space(.), ' ')) and contains(' 5 29 72 ', 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-04: Invoice currency code (BT-5) not ISO 4217](https://veriport.io/einvoice-rules/br-cl-04)
- [BR-CL-05: VAT accounting currency (BT-6) not ISO 4217](https://veriport.io/einvoice-rules/br-cl-05)
- [BR-CL-07: Object identifier scheme (BT-18-1) not UNTDID 1153](https://veriport.io/einvoice-rules/br-cl-07)
- [BR-CL-08: Note subject code (BT-21) not UNCL 4451](https://veriport.io/einvoice-rules/br-cl-08)
- [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)
