What it means
The buyer's contact details contain an InstantMessagingUniversalCommunication element, a chat or messenger address. EN 16931 gives the buyer contact only a name (BT-56), a telephone number (BT-57) and an email address (BT-58), so this element should not be there.
Why it matters
This is only a warning, so the file is still accepted. A chat address has no field in the EN 16931 data model, so the buyer's software will not read it into anything and it will probably be lost.
How to fix it
Check the buyer's contact on the customer record in your invoicing software and clear any chat or messenger field, or switch off exporting it. The name, telephone number and email address are the details that travel with the invoice. If your file is a ZUGFeRD or Factur-X PDF, the XML is inside it, so make the change in the software that creates the PDF.
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-270 still fails, and which other rules do.
Related rules
- 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
- CII-SR-273 Buyer electronic address should not carry a channel code
- CII-SR-274 Buyer electronic address should not carry a number
- CII-SR-275 Buyer VAT number should not carry extra tax registration details
- CII-SR-276 Give the buyer's electronic address in the standard element only