What it means
Within each header trade agreement, the check counts ram:SellerTradeParty/ram:URIUniversalCommunication elements. Zero or one passes this rule. Two blocks fail even if they contain the same address. The rule does not check the address itself.
Why it matters
The CII mapping provides at most one communication block here for the seller's electronic address. The count does not establish whether that address can be reached.
How to fix it
Check the seller's electronic address, such as the Peppol ID you intend to use. Keep it in one ram:URIUniversalCommunication under ram:SellerTradeParty and remove duplicate or unwanted blocks. If you are unsure which address to use, confirm it with your Peppol access point or e-invoicing platform. 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
SellerTradeParty URIUniversalCommunication 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-459 still fails, and which other rules do.
Related rules
- 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
- CII-SR-465 Choose a person or department for the seller contact