What it means
The buyer's contact details contain a TelexUniversalCommunication element. EN 16931 describes the buyer contact with a name (BT-56), a telephone number (BT-57) and an email address (BT-58), so a telex element should not be there. The check fails as soon as the element is in the file, whatever it contains.
Why it matters
This is only a warning, so the file is still accepted. Telex is not part of the EN 16931 data model, so the buyer's software has no field to read it into and the number will probably be lost. No amount or VAT figure depends on it.
How to fix it
Look for a telex or other extra communication field on the buyer's contact in your invoicing software and clear it, or switch off exporting it. If the number is one the buyer should ring, enter it in the normal phone field instead. It is worth acting on when the buyer needs that number or their platform is strict. Otherwise removing it simply keeps the file clean.
The rule as published
TelexUniversalCommunication 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-268 still fails, and which other rules do.
Related rules
- 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
- CII-SR-273 Buyer electronic address should not carry a channel code
- CII-SR-274 Buyer electronic address should not carry a number