# BR-03

Source: https://xmlvalid.com/rules/BR-03

> An Invoice shall have an Invoice issue date (BT-2).

- Level: error
- Rule sets: EN 16931 rules (UBL) 1.3.17, EN 16931 rules 1.3.16 (UBL), EXTENDED-CTC-FR rules (UBL) 1.4.0.04
- Context: `/ubl:Invoice | /cn:CreditNote`
- Test: `normalize-space(cbc:IssueDate) != ''`

> An Invoice shall have an Invoice issue date (BT-2).

- Level: error
- Rule sets: EN 16931 rules (CII) 1.3.17, EN 16931 rules 1.3.16 (CII), EXTENDED-CTC-FR rules (CII) 1.4.0.04
- Context: `/rsm:CrossIndustryInvoice`
- Test: `normalize-space(rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString[@format='102']) != ''`

> An Invoice shall have an Invoice issue date (BT-2).

- Level: error
- Rule sets: Romanian RO e-Factura rules (UBL) 1.0.9
- Context: `/ubl:Invoice | /cn:CreditNote`
- Test: `(cbc:IssueDate) !=''`

> An Invoice shall have an Invoice issue date (BT-2).

- Level: error
- Rule sets: Factur-X BASIC WL rules 1.09, Factur-X EN 16931 rules 1.09.2, Factur-X EXTENDED rules 1.09.2
- Context: `/rsm:CrossIndustryInvoice`
- Test: `(rsm:ExchangedDocument/ram:IssueDateTime/udt:DateTimeString[@format='102']!='')`

## Why it fails

- The issue date in `cbc:IssueDate` (`ram:IssueDateTime` in CII) is missing or empty.

## How to fix it

- Add the issue date (BT-2). UBL writes it as `2026-10-16`; CII as `<udt:DateTimeString format="102">20261016</udt:DateTimeString>`.

Validate a document against these rules: https://xmlvalid.com/validate
