PEPPOL-EN16931-R004
Specification identifier MUST have the value 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.
What does this rule mean?
The specification identifier (BT-24) is not the Peppol BIS Billing 3.0 identifier.
Peppol recognises its own documents by exactly this CustomizationID; another value (the XRechnung one, say) is not accepted as Peppol BIS on the network.
Official rule message (standard)
Specification identifier MUST have the value 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.
Where the rule applies
Syntax: CII · UBL
The same rule, expressed twice: UBL and CII name the same fields with different paths. Running a CII file against the UBL rules is why you get errors that mean nothing.
UBL
ubl-creditnote:CreditNote | ubl-invoice:Invoice
CII
rsm:ExchangedDocumentContext
Technical test
The rule passes when this Schematron expression holds true:
starts-with(normalize-space(ram:GuidelineSpecifiedDocumentContextParameter/ram:ID/text()), 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0')How to fix it
A missing or incorrect business entry only you can supply. Add or correct it, then re-check.
Set BT-24 to 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.
Correct the affected entry in your XML, then re-check the invoice. Validation runs locally in your browser — your file never leaves your machine.
Check an e-invoice here
Drop an XML or ZUGFeRD PDF file here. Validation runs locally in your browser against EN 16931 — your file never leaves your machine.