What it means
Within each header trade agreement, the check counts ram:BuyerTradeParty/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 buyer's electronic address. The count does not check delivery or establish a rejection outcome.
How to fix it
Confirm which electronic address your buyer uses for e-invoices. Keep that address in one ram:URIUniversalCommunication under ram:BuyerTradeParty and remove duplicate or unwanted blocks. 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
BuyerTradeParty 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-460 still fails, and which other rules do.
Related rules
- 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
- CII-SR-466 Choose a person or department for the buyer contact