What it means
In a CII file, the seller's contact (BG-6) has fields for a name (BT-41), a phone number (BT-42) and an email address (BT-43). This rule warns when the contact also has an InstantMessagingUniversalCommunication element, such as a chat handle.
Why it matters
This is a warning, so the invoice is still accepted. The standard has no field for chat addresses, so the buyer's software will normally ignore it.
How to fix it
Remove the chat or messaging address from the seller's contact in your invoicing software, or switch off exporting it. If you edit the XML by hand, delete the InstantMessagingUniversalCommunication element inside the seller's DefinedTradeContact. The buyer can still reach you through the phone number and email address.
The rule as published
InstantMessagingUniversalCommunication 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-241 still fails, and which other rules do.
Related rules
- CII-SR-242 Seller contact should not have a note
- CII-SR-243 Seller contact should not have a nested contact person
- CII-SR-244 Seller electronic address should not have a channel code
- CII-SR-245 Seller electronic address should not have a phone number field
- CII-SR-246 No extra tax details in the seller's tax registration
- CII-SR-247 Do not use the seller's end point address element