What it means
The rule checks for ram:ContentCode inside any ram:IncludedNote directly under rsm:ExchangedDocument. It does not target ram:Content, which holds the note text (BT-22).
Why it matters
The EN 16931 CII mapping represents the note's message as text rather than through this content code. Removing the code should not remove information you still need in the note.
How to fix it
If ram:ContentCode carries information the buyer needs, express its meaning in words in ram:Content (BT-22). Remove the whole ram:ContentCode element from the note and 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
ContentCode 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-028 still fails, and which other rules do.
Related rules
- CII-SR-030 Use at most one text element per invoice note
- 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