What it means
Checks that rsm:ExchangedDocumentContext has no direct ram:SubsetSpecifiedDocumentContextParameter child, regardless of the block's contents.
Why it matters
The EN 16931 CII mapping uses the specification block rather than this separate subset block. Removing the subset block does not mean removing the specification identifier.
How to fix it
Remove ram:SubsetSpecifiedDocumentContextParameter from rsm:ExchangedDocumentContext. Keep ram:GuidelineSpecifiedDocumentContextParameter. If your software adds the subset block, ask your software supplier to omit it from 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
SubsetSpecifiedDocumentContextParameter 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-011 still fails, and which other rules do.
Related rules
- 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
- CII-SR-016 Remove the copy indicator
- CII-SR-017 Remove the Purpose element