BR-02 EN 16931 Core EU FATAL REJECTION

BR-02 — Missing Invoice Number (BT-1)

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

Rule Definition & Compliance Impact

Rule BR-02 mandates that every electronic invoice carry a unique, non-empty Invoice Number (BT-1) assigned by the seller under Article 226(2) of EU VAT Directive 2006/112/EC.

Common ERP & Exporter Root Causes

Draft invoices exported before final numbering in accounting software often leave BT-1 empty, whitespace-only, or mapped to an uninitialized database sequence.

How to Fix This Violation

Assign a finalized sequential invoice identifier in ExchangedDocument/ID (CII) or cbc:ID (UBL) before generating XML. For Romanian CIUS-RO, ensure it also contains at least one numeric digit (BR-RO-010).

Non-Compliant vs. Compliant Payload Comparison

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

REJECTED
<rsm:ExchangedDocument>
  <ram:ID>   </ram:ID>
  <ram:TypeCode>380</ram:TypeCode>
</rsm:ExchangedDocument>
COMPLIANT
<rsm:ExchangedDocument>
  <ram:ID>FV-2026-00412</ram:ID>
  <ram:TypeCode>380</ram:TypeCode>
</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></cbc:ID>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
</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:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
</Invoice>

Test Your Invoice Against This Rule Locally