What it means
The rule checks that rsm:ExchangedDocument has no direct ram:EffectiveSpecifiedPeriod child. It does not check the invoicing period (BG-14).
Why it matters
A document's effective period is not necessarily the period covered by the invoice. The EN 16931 CII mapping does not use this header element.
How to fix it
Remove the whole ram:EffectiveSpecifiedPeriod element from rsm:ExchangedDocument. If the dates describe the period the invoice covers, record them in the invoicing period (BG-14), using start date BT-73 and end date BT-74 as applicable. Do not put document validity dates there unless they genuinely describe that period. Check the file again.
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
EffectiveSpecifiedPeriod 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-033 still fails, and which other rules do.
Related rules
- CII-SR-034 Remove the separate issuer section from the invoice header
- CII-SR-035 Remove description codes from the line document section
- CII-SR-036 Remove parent line identifiers
- CII-SR-037 Remove line status codes
- CII-SR-038 Remove line status reason codes
- CII-SR-039 Use at most one note per invoice line