# BR-03: Invoice issue date (BT-2) missing

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

The invoice must state its issue date, BT-2: `cbc:IssueDate` in UBL (YYYY-MM-DD), `rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString` with `format="102"` (YYYYMMDD) 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-2
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-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-03]-An Invoice shall have an Invoice issue date (BT-2).
```

## What it checks

The invoice must state its issue date, BT-2: `cbc:IssueDate` in UBL (YYYY-MM-DD), `rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString` with `format="102"` (YYYYMMDD) in CII.

## Why invoices fail it

The date field is empty in a draft, or a CII generator writes the date in the wrong element (for example only a delivery date).

## How to fix it

Write the date the invoice is issued in BT-2, in the date format of the syntax.

## 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 CII. 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-03 and 1 other rule, as a real file with this mistake would.

| Rule | Severity | Where | Message |
|---|---|---|---|
| XSD | error | `line 11` | Element 'rsm:ExchangedDocument': Missing child element(s). Expected is ( ram:IssueDateTime ). |
| **BR-03** | error | `/rsm:CrossIndustryInvoice` | An Invoice shall have an Invoice issue date (BT-2). |

```diff
  …
      <ram:ID>2026-017</ram:ID>
      <ram:TypeCode>380</ram:TypeCode>
+     <ram:IssueDateTime>
+       <udt:DateTimeString format="102">20261020</udt:DateTimeString>
+     </ram:IssueDateTime>
    </rsm:ExchangedDocument>
    <rsm:SupplyChainTradeTransaction>
  …
```

## 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:    normalize-space(cbc:IssueDate) != ''
```

```xpath
context: /rsm:CrossIndustryInvoice
test:    normalize-space(rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString[@format='102']) != ''
```

## 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-01: Specification identifier (BT-24) missing](https://veriport.io/einvoice-rules/br-01)
- [BR-02: Invoice number (BT-1) missing](https://veriport.io/einvoice-rules/br-02)
- [BR-04: Invoice type code (BT-3) missing](https://veriport.io/einvoice-rules/br-04)
- [BR-05: Invoice currency code (BT-5) missing](https://veriport.io/einvoice-rules/br-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)
