PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Why a valid invoice can still fail on Peppol

Passing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.

Validation passed but delivery failed Belgium-first Self-serve remediation
Symptoms

What this usually looks like

No schema errorNetwork failure or no deliveryConfusing provider messages
Likely cause

What is usually actually broken

The delivery problem sits outside the XML payload itself.

Next steps

Do these before you resend

  1. Separate document issues from routing issues.
  2. Check participant lookup evidence and provider symptoms together.
  3. Use the analyzer before escalating to support.

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

What is the missing layer after XML validation?

Participant resolution, network capability, provider state, and access-point configuration all sit outside basic XML validity.

Why does this matter commercially?

Teams lose hours escalating the wrong failure class when a route problem gets mistaken for a document problem.

Operator guides

Go one level deeper before you resend

When to resend a Peppol invoice and when to escalate

A fast decision guide for operators who need to know whether the next step is a resend, a partner-record fix, or a provider ticket.

Read the guide
Fixing missing Peppol profile fields before delivery fails

A practical guide for missing CustomizationID, profile markers, and other export-level metadata that leave XML looking valid but unusable in Peppol workflows.

Read the guide
Related issues

Similar failure patterns worth checking

Missing CustomizationID in a Peppol invoice

A Peppol invoice can contain the business data and still fail because the export is missing the profile marker tools expect to classify it correctly.

Open issue page
Odoo endpointverification says 'not on Peppol' for a customer that is registered

If Odoo's endpointverification flow says a customer is not on Peppol while other evidence shows they are, the mismatch is usually in the exact route Odoo is verifying rather than in the customer's existence.

Open issue page
Odoo Peppol is using the commercial company or mother company instead of the branch

Branch setups and commercial-company relationships can send Peppol traffic through the wrong legal entity. This page isolates the exact binding problem and how to correct it.

Open issue page