What it means
Counts the direct ram:GuidelineSpecifiedDocumentContextParameter children of rsm:ExchangedDocumentContext and requires exactly one. This rule counts blocks, not their ID elements or identifier values.
Why it matters
This block holds the specification identifier (BT-24). The CII structure requires one specification block; CII-SR-010 separately checks the number of ID elements.
How to fix it
Inside rsm:ExchangedDocumentContext, add ram:GuidelineSpecifiedDocumentContextParameter if it is missing. If several exist, retain the block for the specification your invoice is intended to follow and remove the extras. Check its ram:ID separately and 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
GuidelineSpecifiedDocumentContextParameter must exist exactly once 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-009 still fails, and which other rules do.
Related rules
- CII-SR-010 Include exactly one specification ID
- CII-SR-011 Do not include a subset context block in the header
- CII-SR-012 Do not include a message standard block in the header
- CII-SR-013 Remove the extra document name element
- CII-SR-014 The invoice must have exactly one document type code
- CII-SR-015 Remove DateTime from the invoice date