Peppol participant lookup — how to check if a counterparty is reachable

Why lookup matters before you send

Sending a Peppol invoice is not like attaching a PDF to an email. Your Access Point must locate the recipient on the network, confirm that they can receive the document type you are sending, and route the message to their provider. If the counterparty is not discoverable, delivery fails at the network layer — often before their accounting software ever sees the invoice.

For Belgian businesses subject to structured B2B e-invoicing, a failed lookup is a practical blocker, not a minor technical detail. Checking reachability before you issue an invoice saves rework, avoids compliance gaps, and gives you time to agree on an alternative channel when Peppol is not available.

What "on Peppol" means in practice

A counterparty is on Peppol when their organisation has a registered participant identifier, published metadata in an SMP (Service Metadata Publisher), and a certified Access Point that accepts inbound traffic for at least one relevant document profile — typically Peppol BIS Billing for invoices.

Being registered is not the same as being reachable for your specific invoice. A participant may exist on the network but only publish support for purchase orders, or only in a test environment. Lookup confirms both identity and capability.

Belgian enterprise number as Peppol identifier

In Belgium, the most common Peppol addressing scheme is ISO 6523 ICD 0208, which maps to the enterprise number registered with the Crossroads Bank for Enterprises (BCE / KBO). A typical participant identifier looks like:

0208:0123456789

The ten-digit enterprise number is written without punctuation. Leading zeros matter: 0208:0403020101 is not the same identifier as 0208:403020101. When you search manually, always normalise the number to the canonical ten-digit form.

Some organisations register additional identifiers (VAT number schemes, GLN, sector-specific codes). For domestic Belgian B2B invoicing, the 0208 scheme is the default assumption — but lookup is what confirms which identifier the counterparty actually published.

Participant identifier

A scheme-qualified address on the Peppol network, such as 0208: followed by a Belgian enterprise number. It tells Access Points where to route structured documents.

The three layers: Directory, SML, and SMP

Peppol lookup can be understood as three related mechanisms:

As a business user you rarely touch SML or SMP directly. Your invoicing software or Access Point performs the technical lookup when you click send. Understanding the layers still helps you interpret errors and know when a manual directory check is worth doing.

Peppol Directory

The Peppol Directory is the practical starting point for manual verification. Search by enterprise number, company name, or country. A successful hit shows the participant identifier, supported document types, and the Access Point provider serving them.

Directory results are informative, not a legal guarantee of delivery. They reflect published SMP metadata at query time. Edge cases — very recent registrations, identifier mismatches, or environment confusion — can produce surprises at send time even when the directory looked fine yesterday.

SML and SMP in automated delivery

When your Access Point sends an invoice, it does not browse a website. It follows the Peppol routing protocol:

1. Take the recipient participant identifier (e.g. 0208:0123456789).
2. Query the SML to find which SMP hosts metadata for that identifier.
3. Query the SMP for supported document types and the recipient Access Point endpoint.
4. Deliver the UBL payload if a matching profile exists.

If step 2 or 3 returns nothing, the network treats the recipient as unreachable for that identifier and document type. That is the technical meaning behind user-facing messages such as "participant not found" or "no matching endpoint".

How to check a Belgian counterparty

Manual check (recommended before first invoice to a new customer):

1. Obtain the verified enterprise number from an official source (invoice header, KBO extract, contract).
2. Open the Peppol Directory and search using scheme 0208 and the ten-digit number.
3. Confirm that Peppol BIS Billing 3.0 (or the profile your software uses) appears among supported document types.
4. Note the Access Point provider name — useful if you need to coordinate with the counterparty's IT contact.

Check inside your invoicing tool:

Most Peppol-enabled products expose a "lookup" or "verify recipient" action that queries the same metadata your Access Point uses at send time. Prefer this when available: it mirrors production routing more closely than a one-off directory search.

Check at send time:

Even without a separate lookup step, your Access Point performs SML/SMP resolution when you transmit. Treat a failed pre-send lookup and a failed transmission the same way: the recipient is not reachable under the identifier you used.

Interpreting "not found"

"Not found" is not a single diagnosis. Common interpretations:

Truly not registered. The counterparty has never completed Peppol registration through a certified Access Point. They cannot receive structured invoices on the network until they do. See Peppol registration in Belgium for what registration involves on your own side.

Wrong identifier. A typo in the enterprise number, missing leading zero, or use of a VAT-based scheme when the counterparty registered under 0208. Re-verify the number and retry lookup before assuming they are off-network.

Registered under a different identity. Groups, branches, or shared service centres sometimes register a parent entity while you invoice a subsidiary. The directory may list the parent; your invoice may reference the child. Align the buyer reference on the invoice with the registered participant.

Wrong document type. The participant exists but their SMP does not publish the billing profile you are sending. The directory may still list them for other document types. Confirm BIS Billing support explicitly.

Propagation or environment mismatch. A registration completed minutes ago may not appear everywhere instantly. Less commonly, test and production environments are confused — a participant visible in a sandbox is invisible in production.

Inactive or de-registered metadata. Rare, but SMP entries can be withdrawn when a business changes Access Point provider. If a long-standing customer suddenly fails lookup, ask whether they migrated providers.

What to do when lookup fails

1. Confirm the enterprise number with the counterparty and retry with scheme 0208.
2. Ask whether they are Peppol-ready — many SMEs register only when their first structured invoice arrives or when their accountant prompts them.
3. Do not assume PDF by email satisfies the mandate when both parties are Belgian VAT-liable and structured exchange is required. Understand your fallback options in Sending an invoice when the client is not on Peppol.
4. Document the outcome — note the date, identifier used, and directory result. Useful for audit trails when onboarding suppliers under the 2026 obligation.

If lookup succeeds, you still need a valid structured invoice (EN 16931 / UBL). Reachability and content validity are separate gates.

Lookup in the broader Peppol workflow

Participant lookup sits between registration and transmission:

1. What is Peppol? — network fundamentals
2. Peppol Access Point — your gateway to send and receive
3. Peppol registration in Belgium — making your own organisation discoverable
4. Participant lookup — verifying counterparties before you send
5. Transmission, delivery status, and invoice responses

For Belgian businesses, treating lookup as a standard onboarding step — alongside verifying VAT details and payment terms — prevents the most common first-send failures on the network.