What it means
For each ram:IncludedNote directly under rsm:ExchangedDocument, the rule counts its direct ram:Content children. Each invoice note (BG-1) may have zero or one such element for its note text (BT-22).
Why it matters
The rule limits text elements within each note, not the total number of notes. It does not establish whether a recipient will accept the file or display all its text.
How to fix it
Combine the text in the affected note into one ram:Content element and remove the extra ram:Content elements. If you split the text into separate ram:IncludedNote elements instead, check that your invoice profile permits this. Check the updated 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
Content should exist maximum 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-030 still fails, and which other rules do.
Related rules
- CII-SR-032 Remove identifiers from invoice notes
- CII-SR-033 Remove the document effective period from the invoice header
- 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