What it means
Within a line's ram:SpecifiedTradeProduct, this rule checks that no item attribute (BG-32), represented by ram:ApplicableProductCharacteristic, contains a ram:ValueCode child. It prohibits this element, not codes written as text in ram:Value.
Why it matters
The EN 16931 CII mapping represents an item attribute value (BT-161) through ram:Value rather than a separate coded value element. This warning alone does not establish whether the invoice will be accepted.
How to fix it
Put the information into the affected attribute's single ram:Value element. Use a description the buyer can understand, keeping a useful code alongside it if needed. Remove ram:ValueCode from the same ram:ApplicableProductCharacteristic. If you do not need the attribute, remove the whole characteristic instead. 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
ValueCode 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-073 still fails, and which other rules do.
Related rules
- CII-SR-074 Write item attribute dates as text
- CII-SR-075 Write yes or no attributes as text
- CII-SR-076 Leave out the content type code on item attributes
- CII-SR-077 Leave out binary files attached to item attributes
- CII-SR-078 Leave out conditions attached to item attributes
- CII-SR-079 Leave out referenced standards on item attributes