Skip to content

Warning

CII-SR-266: Leave out the channel code on the buyer contact's email

In short

Warning: worth checking.

CII-SR-266 means the buyer contact's email entry has a ChannelCode element, which EN 16931 does not use there. Remove the code and keep the email address. It is only a warning, so the file is still accepted.

On this page

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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-266 still fails, and which other rules do.

Updated 6 November 2026