PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Wrong endpoint scheme in a Belgian Peppol invoice

The invoice can look structurally valid and still fail because the participant scheme does not match the recipient's published routing identity.

Endpoint-level routing mismatch Belgium-first Self-serve remediation
Symptoms

What this usually looks like

EndpointID is presentInvoice validates elsewhereRecipient still unreachable
Likely cause

What is usually actually broken

The value is real, but the scheme and identity pair do not match the recipient's live publication.

Next steps

Do these before you resend

  1. Check the Peppol participant as a full scheme-plus-value pair.
  2. Look for 0208/9925 mismatches first.
  3. Regenerate the invoice once the partner record is corrected.
Run the analyzer See the fix pack
FAQ

What people ask right before they get blocked

Can a wrong scheme still pass XML validation?

Yes. The XML can be structurally valid while still routing to the wrong participant identity.

What should I store in my ERP?

Store the same scheme-plus-value pair that the recipient expects you to resolve on the network.

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
Related issues

Similar failure patterns worth checking

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
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