What it means
Within each header trade agreement, the check counts ram:AdditionalReferencedDocument blocks whose ram:TypeCode equals 50. It allows zero or one. It counts blocks, not distinct reference values, and excludes blocks with other type codes.
Why it matters
BT-17 provides a single tender or lot reference for the invoice. Repeating its reference block does not fit that structure.
How to fix it
Check the tender or lot reference your buyer supplied. Under ram:ApplicableHeaderTradeAgreement, keep the appropriate ram:AdditionalReferencedDocument with ram:TypeCode 50 and remove the extra type 50 blocks. Do not change a type code merely to avoid the warning. 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 50 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-457 still fails, and which other rules do.
Related rules
- CII-SR-458 Give the invoiced object identifier only once
- 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