Specification identifier is not the Peppol value
What it means
The specification identifier (BT-24) tells the receiver which rule set the document claims to follow. Peppol requires one exact string; a document carrying only the plain EN 16931 identifier is a valid EN 16931 invoice but will be rejected by a Peppol receiver. This is the single most common reason a technically correct invoice fails Peppol validation.
Can it be fixed automatically?
Nothing about your business is needed to fix this — the correct value is a constant, a code list entry, or is already present in the document.
This one can be repaired automatically. The API applies the fix, re-validates, and reports exactly what changed with before and after values.
How to fix it
Set CustomizationID to 'urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0'.
Where it applies
| CII | /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext/ram:GuidelineSpecifiedDocumentContextParameter/ram:ID |
|---|---|
| UBL | /Invoice/cbc:CustomizationID |
Check your own invoice
curl -X POST https://einvoice.mgsoft.sk/v1/validate \
-H 'Content-Type: application/xml' \
--data-binary @invoice.xml