EN16931 1.3.16 · UBL / CII · Severity: ERROR
An Invoice shall have a Specification identifier (BT-24)
Every EN16931 invoice must declare the specification identifier (BT-24) of the semantic profile it follows.
- Rule ID & Severity
BR-01· ERROR- Standard & Scope
- EN16931 1.3.16 · UBL / CII
- XPath Condition
exists(cbc:CustomizationID)- Target XML Path
cbc:CustomizationID
Find the source field
cbc:CustomizationID
Match namespace URI and element name, not a particular prefix spelling. The validator reports the full expanded-name source path when the published rule supplies a location.
Common causes
- The UBL or CII export omitted CustomizationID / GuidelineSpecifiedDocumentContextParameter.
- An internal ERP schema identifier was used instead of the official EN16931 URN.
Invalid and corrected fragments
<!-- CustomizationID missing -->
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
Include the exact CustomizationID URN required by the recipient profile (EN16931, XRechnung 3.0, or Peppol BIS 3.0).
Open BR-01 in en16931-validator →
Verify the whole document
These are fragments, not complete invoices. The exact rule is exercised by synthetic mutation tests against the stated package. Correcting one field does not prove conformance; run the full selected validator again. Published messages and severity remain authoritative.
Explanation record: 2026-10-14 · Local WebAssembly / SaxonJS validation. No invoice-derived report is published as a search page.