PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

No valid Peppol ID found for a Belgian customer

This usually means the customer is registered under a different identifier or not fully published. Here is how to separate a real absence from a lookup mismatch.

Failed partner onboarding Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Partner is not on PeppolNo valid Peppol IDCounterparty says they are registered
Likely cause

What is usually actually broken

The lookup used the wrong scheme, wrong value, or a stale registration signal.

Next steps

Do these before you resend

  1. Check both enterprise-number and VAT-number variants.
  2. Confirm the company is meant to receive through Peppol and not only send.
  3. Use live directory evidence before changing the ERP record.

The fastest path from this page is a prefilled diagnosis. It opens the analyzer with this exact issue pattern already loaded and immediately prepares the EUR 9 fix-pack preview when the route looks blocked or risky.

Open prefilled diagnosis See the fix pack
Direct help

Buy the rescue kit for this exact issue

If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.

FAQ

What people ask right before they get blocked

Does a missing directory result prove they are not on Peppol?

No. Directory publication can be incomplete, so a missing result is evidence, not certainty.

What should I ask the counterparty for?

Ask for the exact participant identifier they expect you to use, including the scheme and value.

Operator guides

Go one level deeper before you resend

Belgium Peppol routing checklist before you contact support

A short checklist that filters out the most common Belgian routing mistakes in minutes.

Read the guide
What to do when VIES is inconclusive

VIES helps validate EU VAT numbers, but it can be slow or unavailable. This guide explains how to proceed safely when that happens.

Read the guide
Related issues

Similar failure patterns worth checking

My customer has a GLN in Odoo, but I still get 'no valid Peppol ID'

A stored GLN or alternate identifier does not guarantee Odoo will resolve the exact Peppol participant the recipient expects. This page shows where the mismatch happens.

Open issue page
Recipient is on Peppol, but Odoo still says no valid Peppol ID

This contradiction usually means Odoo has the wrong identifier, wrong scheme, or stale participant evidence. This page breaks down the mismatch clearly.

Open issue page
0208 vs 9925 in Belgium: which Peppol ID should you use?

Belgian Peppol delivery often fails because the counterparty is stored with the wrong identifier scheme. This page explains when 0208 and 9925 diverge and what to verify first.

Open issue page