# BR-CO-03: Tax point date and its code together

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

The VAT point date (BT-7, `cbc:TaxPointDate` / `ram:TaxPointDate`) and the VAT point date code (BT-8, `cac:InvoicePeriod/cbc:DescriptionCode` / `ram:DueDateTypeCode`) are mutually exclusive: give a date or a code, not both. 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-7, BT-8
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-CO-03 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-03]-Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive.
```

## What it checks

The VAT point date (BT-7, `cbc:TaxPointDate` / `ram:TaxPointDate`) and the VAT point date code (BT-8, `cac:InvoicePeriod/cbc:DescriptionCode` / `ram:DueDateTypeCode`) are mutually exclusive: give a date or a code, not both.

## Why invoices fail it

The generator fills both from the same setting (« VAT due on issue date »).

## How to fix it

Keep one: the date when you know it, or the code (3 issue date, 35 delivery date, 432 paid-to date) when the date follows from an event.

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

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-CO-03** | error | `/ubl:Invoice` | Value added tax point date (BT-7) and Value added tax point date code (BT-8) are mutually exclusive. |

```diff
  …
    <cbc:DueDate>2026-11-03</cbc:DueDate>
    <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
-   <cbc:TaxPointDate>2026-10-20</cbc:TaxPointDate>
    <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: /ubl:Invoice | /cn:CreditNote
test:    (exists(cbc:TaxPointDate) and not(cac:InvoicePeriod/cbc:DescriptionCode)) or (not(cbc:TaxPointDate) and exists(cac:InvoicePeriod/cbc:DescriptionCode)) or (not(cbc:TaxPointDate) and not(cac:InvoicePeriod/cbc:DescriptionCode))
```

```xpath
context: //ram:ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax
test:    ((//ram:TaxPointDate) and not(//ram:DueDateTypeCode)) or (not (//ram:TaxPointDate) and (//ram:DueDateTypeCode)) or (not (//ram:TaxPointDate) and not (//ram:DueDateTypeCode))
```

## 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-04: Line VAT category code (BT-151) missing](https://veriport.io/einvoice-rules/br-co-04)
- [BR-CO-05: Allowance reason code and text agree](https://veriport.io/einvoice-rules/br-co-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)
