Skip to content

Warning

CII-SR-363: Do not give the payee an end point address

In short

Warning: worth checking.

CII-SR-363 means the payee block holds an EndPointURIUniversalCommunication, an end point address for the payee, which EN 16931 does not use. Delete it and keep the electronic addresses in the seller and buyer blocks.

On this page

What it means

The payee block (PayeeTradeParty) has an EndPointURIUniversalCommunication element, an address where messages for the payee could be delivered. EN 16931 has no such address for the payee. Its electronic addresses are those of the seller (BT-34) and the buyer (BT-49).

Why it matters

The file is still accepted, because this is a warning. Delivery of the invoice follows the buyer's electronic address (BT-49), so the payee's end point is never used. Remove it to keep the file within the standard and to avoid confusing whoever reads the XML.

How to fix it

Delete the EndPointURIUniversalCommunication element from the payee block. Check that the Peppol ID or other electronic address of the buyer is in the buyer block. If a Peppol ID was entered on the payee in your software, move it to the right party or remove it.

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
Rule text from phive-rules 4.6.4.

Check your file

Drop your e-invoice to see whether CII-SR-363 still fails, and which other rules do.

Updated 6 November 2026