BR-01 EN 16931 Core EU FATAL REJECTION
BR-01 — Missing Specification Identifier (BT-24)
Rule Definition & Compliance Impact
Rule BR-01 requires every EN 16931 electronic invoice to declare a non-empty Specification Identifier (BT-24) so receiving portals know which semantic profile and CIUS Schematron rules apply.
Common ERP & Exporter Root Causes
Custom ERP XML exporters often omit CustomizationID in UBL or GuidelineSpecifiedDocumentContextParameter/ID in CII, or output internal ERP template names instead of an official CEN URN.
How to Fix This Violation
Populate BT-24 with the exact URN required by your target profile: urn:cen.eu:en16931:2017 for core EN 16931 / Factur-X EN16931, the KoSIT XRechnung URN for Germany, or the ANAF CIUS-RO 1.0.1 URN for Romania.
Non-Compliant vs. Compliant Payload Comparison
UN/CEFACT CII D16B (Factur-X / ZUGFeRD)
REJECTED
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameter>
<ram:ID></ram:ID>
</ram:GuidelineSpecifiedDocumentContextParameter>
</rsm:ExchangedDocumentContext> COMPLIANT
<rsm:ExchangedDocumentContext>
<ram:GuidelineSpecifiedDocumentContextParameter>
<ram:ID>urn:cen.eu:en16931:2017</ram:ID>
</ram:GuidelineSpecifiedDocumentContextParameter>
</rsm:ExchangedDocumentContext>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">
<!-- Missing cbc:CustomizationID (BT-24) -->
<cbc:ID>INV-2026-001</cbc:ID>
</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:CustomizationID>urn:cen.eu:en16931:2017</cbc:CustomizationID>
<cbc:ID>INV-2026-001</cbc:ID>
</Invoice>