What it means
Checks every element anywhere in the XML whose name ends in DocumentContextParameter and flags any direct ram:SpecifiedDocumentVersion child. The XPath is not restricted to the document header.
Why it matters
These EN 16931 CII rules do not use this version element in context parameter blocks. The block's identifier is separate and should not be removed as part of this correction.
How to fix it
Find the affected context parameter block and remove its direct ram:SpecifiedDocumentVersion child. Leave its ram:ID unchanged. If your software generates the extra element, ask your software supplier to correct the CII export, then recheck the file.
Once the file is corrected, check it again for free: Validate an invoice against EN 16931
Or fix the invoice in a form and download the corrected file, for 1 credit: Fix a rejected e-invoice
The rule as published
SpecifiedDocumentVersion should not be present Where this rule applies
| Rule set | Version |
|---|---|
| EN 16931 (CII) | 1.3.17 |
| XRechnung 3.0 (CII) | 3.0.2 |
| NLCIUS (CII) | 1.0.3.13 |
| France CTC (CII) | 1.4.0-04 |
Check your file
Drop your e-invoice to see whether CII-SR-05 still fails, and which other rules do.
Related rules
- CII-SR-006 Do not include a BIM context block in the header
- CII-SR-007 Do not include a scenario context block in the header
- CII-SR-008 Do not include an application context block in the header
- CII-SR-009 Use exactly one specification identifier block
- CII-SR-010 Include exactly one specification ID
- CII-SR-011 Do not include a subset context block in the header