What it means
The buyer party (BG-7) contains an EndPointURIUniversalCommunication element, a second way of stating where the buyer receives messages. EN 16931 gives the buyer's electronic address (BT-49) only in the URIUniversalCommunication element.
Why it matters
This is only a warning, so the file is still accepted. If the address is given only in this element, software that reads the file by EN 16931 will not find a buyer electronic address. That matters if the buyer or their e-invoicing platform expects it.
How to fix it
In your invoicing software, check the e-invoice or electronic address field on the customer record. It should be written as the buyer's electronic address with its scheme, not as an end point. If you build the XML yourself, move the address into URIUniversalCommunication, in the URIID element with a schemeID, and delete the end point element.
The rule as published
EndPointURIUniversalCommunication 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-276 still fails, and which other rules do.
Related rules
- CII-SR-277 Do not embed a logo for the buyer
- CII-SR-278 Do not name a sales agent in the invoice header
- CII-SR-279 Do not name a buyer requisitioner in the invoice header
- CII-SR-280 Do not name the buyer's accountant in the invoice header
- CII-SR-281 Do not name the seller's accountant in the invoice header
- CII-SR-282 Do not name a tax representative for the buyer