Specification identifier is missing
What it means
Every EN 16931 invoice must declare which specification it follows (BT-24). Without it a receiver cannot know which rule set to validate against, so the document is untrustworthy even if every other field is correct.
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
Insert the specification identifier. For a Peppol document this is the Peppol customization string; for plain EN 16931 it is 'urn:cen.eu:en16931:2017'.
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