What it means
Checks that rsm:ExchangedDocumentContext has no direct ram:ScenarioSpecifiedDocumentContextParameter child, regardless of its contents.
Why it matters
The EN 16931 CII mapping does not use this scenario block. It is separate from the specification block required by CII-SR-009.
How to fix it
Remove ram:ScenarioSpecifiedDocumentContextParameter from rsm:ExchangedDocumentContext. Leave ram:GuidelineSpecifiedDocumentContextParameter in place. If your software adds the scenario block, 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
ScenarioSpecifiedDocumentContextParameter 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-007 still fails, and which other rules do.
Related rules
- 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
- CII-SR-012 Do not include a message standard block in the header
- CII-SR-013 Remove the extra document name element