What it means
For every item attribute (BG-32) in a line's product details, the test counts its ram:Value children and requires exactly one. It checks the number of elements, not whether their text is empty or contains several details.
Why it matters
The CII mapping gives each item attribute one text value element for BT-161. A missing or repeated value element fails this fatal check, but that result does not establish what a recipient will do with the file.
How to fix it
For each ram:ApplicableProductCharacteristic you keep, provide one ram:Value containing the appropriate attribute value. If several details belong together, put them in that single text element. If they describe different attributes, use separate characteristics, each with its own name in ram:Description and value in ram:Value. Remove any unwanted characteristic as a whole and 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
Value 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-072 still fails, and which other rules do.
Related rules
- CII-SR-073 Leave out the value code on item attributes
- 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