In Peppol e-invoicing, the Endpoint ID is how the network knows where to deliver an invoice. It consists of two parts: a scheme ID (which type of identifier) and the identifier value itself.

Every business registered on the Peppol network has an Endpoint ID. When you send a Peppol invoice, the sender's Access Point looks up the receiver's Endpoint ID in the SMP (Service Metadata Publisher) to find their Access Point and deliver the document.

Structure

Endpoint ID = Scheme ID + Identifier Value

Examples:

  • Belgian business: scheme 0208 + KBO/BCE number 0123456789
  • Dutch business: scheme 0106 + KvK number 12345678
  • German business: scheme 9930 + USt-IdNr DE123456789

In UBL XML

The Endpoint ID appears in both sender and receiver party elements:

<!-- Seller endpoint -->
<cac:EndpointID schemeID="0208">0123456789</cac:EndpointID>

<!-- Buyer endpoint -->
<cac:EndpointID schemeID="0106">12345678</cac:EndpointID>

Registration

Endpoint IDs are registered through your Peppol Access Point provider. The Access Point registers your business in the SMP, making you discoverable on the network.

Common Issues

Missing endpoint ID — every Peppol invoice must include the buyer's Endpoint ID. If your ERP doesn't have the buyer's Peppol registration details, the invoice can't be routed.

Wrong scheme ID — using scheme 9930 (German VAT) for a Belgian business that should use 0208 (KBO/BCE) will cause routing failures.

In the XML

UBL (Peppol BIS, XRechnung UBL)
<cbc:EndpointID schemeID="0208">0123456789</cbc:EndpointID>
CII (ZUGFeRD, Factur-X, XRechnung CII)
<ram:URIID schemeID="0208">0123456789</ram:URIID>