What it means
Within each header trade agreement, the check counts ram:AdditionalReferencedDocument blocks whose ram:TypeCode equals 130. It allows zero or one, even when repeated blocks contain the same identifier. References with other type codes are not counted.
Why it matters
BT-18 identifies the object the invoice relates to, such as a subscription or meter. The CII mapping provides at most one header reference block for this identifier.
How to fix it
Check which identifier should identify the object you are billing. Under ram:ApplicableHeaderTradeAgreement, keep the appropriate ram:AdditionalReferencedDocument with ram:TypeCode 130 and remove the extra type 130 blocks. If you need several identifiers, agree with your buyer which belongs in this field. Export and recheck your 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
IssuerAssignedID with TypeCode 130 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-458 still fails, and which other rules do.
Related rules
- CII-SR-459 Give the seller's electronic address only once
- CII-SR-460 Give the buyer's electronic address only once
- CII-SR-461 Give the VAT point date only once
- CII-SR-462 Use a consistent VAT point date code
- CII-SR-463 Each discount or charge must say which it is
- CII-SR-464 Remove the payer's bank block