BR-03fatal

How to fix BR-03

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

What this rule checks

The invoice issue date (BT-2, mapped to cbc:IssueDate) records when the invoice was created and is legally required in virtually all jurisdictions. It determines tax point dates, payment due dates, and reporting periods. The date must follow the YYYY-MM-DD format as specified by ISO 8601.

Referenced business terms

This rule references the following EN 16931 business term. Click through for the full definition, the UBL XPath and the cardinality.

How to fix it

Add a cbc:IssueDate element at the Invoice root level in YYYY-MM-DD format.

Common causes

  • The cbc:IssueDate element is missing entirely.
  • The date is in a non-ISO format such as DD/MM/YYYY or MM-DD-YYYY.
  • The element is present but empty.
  • The date value is invalid (e.g. 2024-02-30).

Example: before (broken)

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ID>INV-2024-001</cbc:ID>
  <!-- cbc:IssueDate is missing -->
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
</Invoice>

Example: after (fixed)

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ID>INV-2024-001</cbc:ID>
  <cbc:IssueDate>2024-01-15</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
</Invoice>

Related rules

Validate your invoice

Upload your corrected invoice to check it passes BR-03 and all other EN 16931 and Peppol BIS 3.0 rules. Free, instant, no signup.