Skip to content

Warning

CII-SR-315: Delivery party must not have an end point address

In short

Warning: worth checking.

CII-SR-315 means the delivery party in the file has an end point address (EndPointURIUniversalCommunication), which EN 16931 does not use for that party. It is a warning, so the file is still accepted; remove that element from the delivery party.

On this page

What it means

The delivery party (ShipToTradeParty) has a name, location identifier and address. This rule checks that it has no EndPointURIUniversalCommunication, a separate element for the address where a party receives electronic documents. In an e-invoice that address is given for the seller (BT-34) and the buyer (BT-49) only.

Why it matters

An end point address on the delivery party is not used to route the invoice; it goes to the buyer's electronic address (BT-49). The invoice is not rejected, but the element does nothing.

How to fix it

Check whether the delivery address in your software has a Peppol ID or other end point field, and clear it or stop it being exported. If the invoice should go to another recipient, change the buyer's electronic address instead. If the element keeps coming back, choose the EN 16931 profile or ask the software supplier why it is written.

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-315 still fails, and which other rules do.

Updated 6 November 2026