PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Suppliers can't send me invoices via Peppol in Odoo

Being listed in the Peppol directory is not always enough to receive invoices. This page isolates the Odoo receiving-side failures that leave inbound invoices stuck even after registration.

Inbound Peppol receiving blocker Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Odoo says you can send and receive through PeppolYour company is listed in the Peppol directorySuppliers still cannot deliver invoices to you
Likely cause

What is usually actually broken

The inbound receiving workflow is only partially enabled, or the Odoo-side server actions and receiving registration are not actually active despite the public listing.

Next steps

Do these before you resend

  1. Check the Odoo server actions and inbound Peppol actions before assuming the directory listing proves receiving is fully active.
  2. Confirm whether the company is only registered through Hermes or another limited route and whether receiving is fully enabled.
  3. Test one known supplier again only after the inbound actions and registration state are confirmed.

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.

Recent operator reports

Current public evidence for this exact failure

Odoo forum thread where inbound Peppol receiving stayed broken despite directory listing and registration email

Odoo forum · March 2026

Open source
FAQ

What people ask right before they get blocked

Does the Peppol directory listing prove I can receive invoices?

Not by itself. It proves there is public participant evidence, but it does not guarantee the Odoo receiving workflow behind it is fully active.

What should I inspect first in Odoo?

Check inbound server actions and receiving-side Peppol actions before re-registering again, especially if the issue started immediately after setup.

Operator guides

Go one level deeper before you resend

Odoo Peppol triage for Belgium

A calm, ordered checklist for Belgian Odoo users when Peppol starts failing without a clear explanation.

Read the guide
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
Related issues

Similar failure patterns worth checking

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 says 'PEPPOL is not valid' even though the customer looks registered

This exact Odoo message usually means the ERP is validating the wrong participant identity, stale evidence, or the wrong identifier scheme rather than proving the customer is truly unavailable.

Open issue page
Odoo suddenly says all customers are not on Peppol

If Odoo marks every customer as not on Peppol all at once, treat it as an environment or provider incident first, not a data-cleanup job on every partner record.

Open issue page