The specification identifier is missing
The invoice must declare the URN of the profile it conforms to, in `ram:GuidelineSpecifiedDocumentContextParameter/ram:ID`.
This defect is fixed automatically. Test your invoice to find out whether it is affected, then apply the correction with the Pipeline Pro plan.
The message your validator prints
Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.
[BR-01]-An Invoice shall have a Specification identifier (BT-24).
Quoted from schematron-cen 1.3.16, licensed under EUPL-1.2.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
Without this URN, no validator knows which rule set to apply: the document is unusable downstream even when its content is perfect. Generators that build their XML from a template forget it often.
How to fix it
The URN can be derived from what the document actually contains. Factlint fills it in and traces the correction with its `before`, its `after` and its XPath.
XML correction example
<!-- ram:ID absent -->
<ram:ID>urn:cen.eu:en16931:2017</ram:ID>
POST /v1/fixThis defect is among those the API rewrites itself: the corrected document comes back in the response. See the endpoint