What it means
Inside the buyer's contact details, the email element (which holds the buyer contact email address, BT-58) also contains a CompleteNumber element. EN 16931 only uses the address itself in the email element. A phone number for the buyer contact (BT-57) has its own telephone element.
Why it matters
This is only a warning, so the file is still accepted. The number has no field in the EN 16931 data model, so the buyer's software cannot read it into anything and will probably drop it. If it was meant to be a phone number, the buyer will not see it.
How to fix it
Open the buyer's contact on the customer record in your invoicing software and check that the email field holds only an email address, with the phone number in the phone field. If you build the XML yourself, delete the CompleteNumber element from the buyer's email part. It is worth fixing when the number is a real phone number the buyer needs, or when the buyer's platform checks files strictly.
The rule as published
CompleteNumber 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-267 still fails, and which other rules do.
Related rules
- 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
- CII-SR-273 Buyer electronic address should not carry a channel code