Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| BR-03 | Fatal (error) | ubl:Invoice |
| Series reference: BR-03 | Schematron ID: ibr-003 | ||
Classification
Transaction Data — The invoice issue date is a transaction-level date field generated at the point of invoice creation by the seller's system.
What the Rule Is Checking
BR-03 requires that every invoice contains a non-empty cbc:IssueDate element at the invoice header level. This is BT-2 in the PINT-AE data model — the Invoice issue date. The element must be present and must contain a valid date in ISO 8601 format (YYYY-MM-DD). The rule fails fatally if the element is absent or empty.
BT-2 is the date on which the invoice is issued by the seller. It is distinct from the supply date (BT-7, the tax point date) and the due date (BT-9). In many cases these three dates are the same, but where they differ — for example, in a services invoice issued after the service is delivered — each must be populated independently.
Why This Rule Exists
Under UAE VAT law, the tax point (and therefore the VAT accounting period) is determined by the earlier of the invoice date or the date of payment. The invoice date (BT-2) anchors the entire VAT position of the transaction. Without it, neither the seller nor the FTA can determine which VAT return period the transaction falls into.
MD No. 243 of 2025 and the UAE VAT regulations require that the invoice date be included as a mandatory field. The UAE e-invoicing system also applies the 14-day issuance rule (Article 65 of the UAE VAT Decree-Law): an invoice must be issued within 14 days of the date of supply. BT-2 is the field against which this deadline is verified. An absent or incorrect BT-2 makes the 14-day compliance check impossible.
Standard / Code List
BT-2 must be formatted as ISO 8601 date: YYYY-MM-DD. Time components and timezone offsets are not included in the cbc:IssueDate element (time belongs in cbc:IssueTime if required). The date must be a real calendar date — schematron validators will reject values like 2027-02-30.
UAE Data Example
PASSES ✓
<cbc:IssueDate>2027-01-15</cbc:IssueDate>
FAILS ✗ — Element absent:
<!-- No cbc:IssueDate present -->
FAILS ✗ — Wrong date format (DD/MM/YYYY):
<cbc:IssueDate>15/01/2027</cbc:IssueDate>
FAILS ✗ — Empty element:
<cbc:IssueDate></cbc:IssueDate>
FAILS ✗ — Datetime instead of date:
<cbc:IssueDate>2027-01-15T00:00:00</cbc:IssueDate>What Your ERP / IT Team Must Ensure
- The ERP-to-UBL mapping must extract the invoice creation date (not the posting date or the accounting date) and format it strictly as YYYY-MM-DD — many ERP systems output dates in locale-specific formats that will fail BR-03.
- Where ERP systems store datetime values in UTC, the date component must be derived in UAE local time (UTC+4), not UTC — an invoice posted at 11:00 PM UTC on 14 January is an invoice dated 15 January in UAE time.
- The 14-day issuance rule must be enforced upstream: the mapping layer should validate that BT-2 is no more than 14 days after BT-7 (tax point date) before transmission to the ASP.
- Batch invoice runs that use a single issue date for a group of invoices created over multiple days must assign individual BT-2 values per invoice — a single batch date does not comply with the 14-day rule for invoices whose supply date precedes the batch run date.
Related Rules
BR-02 (Invoice number), BR-04 (Invoice type code), UAE E-Invoicing 14-Day Rule