Symptoms
What this usually looks like
endpointverification says 'not on Peppol'The customer appears registered in other toolsOdoo still refuses to verify the participant
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.
Likely cause
What is usually actually broken
Odoo is checking a specific scheme-plus-value pair or upstream verification route that does not match the live participant evidence you are looking at elsewhere.
Next steps
Do these before you resend
- Capture the exact identifier Odoo is verifying, not just the company name.
- Compare the verified route against the live participant scheme and value the recipient expects.
- If the mismatch only appears in Odoo, test whether the upstream verification host or resolver path is the real failure point.
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.
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 · April 2026
Open source FAQ
What people ask right before they get blocked
No. It proves the exact verification path Odoo is using is not returning a trusted match. That can still happen when the customer is registered under a different scheme or route.
Capture the exact identifier Odoo checked, the alternate live participant evidence, and whether the failure follows one route or every route.
Operator guides
Go one level deeper before you resend
A calm, ordered checklist for Belgian Odoo users when Peppol starts failing without a clear explanation.
Read the guideA short checklist that filters out the most common Belgian routing mistakes in minutes.
Read the guide Related issues
Similar failure patterns worth checking
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 pageIf 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 pageA missing directory hit does not always mean the company is absent from the network. Learn when the directory is advisory and what else to check.
Open issue page