What it means
In the buyer contact's email entry, the ChannelCode element must be absent. That element is a code for the kind of communication channel. The email address (BT-58) is carried in the URIID element of the entry, and the position already says it is an email. The same restriction applies in the CII rules for XRechnung, NLCIUS and the French CTC rules.
Why it matters
This is a warning, so the file is still accepted. The recipient's software reads the email address from URIID and ignores the channel code, so nothing changes for the buyer. Fix it if you want a file with no warnings, or if the recipient asks for one.
How to fix it
Your software adds the code by itself, so look for an export setting such as EN 16931 output or standard contact details, and use it. You cannot normally clear the code from the customer record. If you edit the XML yourself, delete ChannelCode inside the buyer contact's EmailURIUniversalCommunication and leave the URIID with the address.
The rule as published
ChannelCode should not be present 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-266 still fails, and which other rules do.
Related rules
- CII-SR-267 Buyer contact email should hold only the address, not a number
- CII-SR-268 Leave the telex number out of the buyer's contact details
- CII-SR-269 Leave the VoIP address out of the buyer's contact details
- CII-SR-270 Leave the instant messaging address out of the buyer's contact
- CII-SR-271 Do not attach a note to the buyer's contact details
- CII-SR-272 Do not add a separate contact person block to the buyer contact