BR-03 EN 16931 Core EU FATAL REJECTION

BR-03 — Missing or Malformed Invoice Issue Date (BT-2)

Affected EN 16931 Terms:
BT-2
Normative Specification: CEN EN 16931-1:2017 Clause 6.5 (BR-03) Official specification ↗

Rule Definition & Compliance Impact

Rule BR-03 requires every electronic invoice to specify an Invoice Issue Date (BT-2) formatted strictly as YYYYMMDD (format='102') in UN/CEFACT CII or YYYY-MM-DD in OASIS UBL.

Common ERP & Exporter Root Causes

Spreadsheets and regional accounting tools frequently serialize dates in DD/MM/YYYY or DD.MM.YYYY format, or omit format='102' on udt:DateTimeString in CII.

How to Fix This Violation

Format BT-2 as 8-digit YYYYMMDD with attribute format='102' in CII (ExchangedDocument/IssueDateTime), or ISO 8601 YYYY-MM-DD without timezone offsets in UBL (cbc:IssueDate).

Non-Compliant vs. Compliant Payload Comparison

UN/CEFACT CII D16B (Factur-X / ZUGFeRD)

REJECTED
<rsm:ExchangedDocument>
  <ram:ID>FV-2026-00412</ram:ID>
  <ram:IssueDateTime>
    <udt:DateTimeString format="102">17/11/2026</udt:DateTimeString>
  </ram:IssueDateTime>
</rsm:ExchangedDocument>
COMPLIANT
<rsm:ExchangedDocument>
  <ram:ID>FV-2026-00412</ram:ID>
  <ram:IssueDateTime>
    <udt:DateTimeString format="102">20261117</udt:DateTimeString>
  </ram:IssueDateTime>
</rsm:ExchangedDocument>

OASIS UBL 2.1 (XRechnung / Peppol / RO e-Factura)

REJECTED
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:ID>FV-2026-00412</cbc:ID>
  <!-- Missing or localized DD.MM.YYYY date -->
  <cbc:IssueDate>17.11.2026</cbc:IssueDate>
</Invoice>
COMPLIANT
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:ID>FV-2026-00412</cbc:ID>
  <cbc:IssueDate>2026-11-17</cbc:IssueDate>
</Invoice>

Test Your Invoice Against This Rule Locally