Symptoms
What this usually looks like
No directory resultCounterparty insists they are registeredDifferent answers across tools
Partner not found in the Peppol Directory
A 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.
Likely cause
What is usually actually broken
The directory is voluntary and can be incomplete, so an empty result can reflect publication gaps as well as a genuine mismatch.
Next steps
Do these before you resend
- Treat directory results as evidence, not certainty.
- Cross-check the exact participant ID and scheme.
- Escalate with provider-ready evidence rather than only a screenshot.
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.
FAQ
What people ask right before they get blocked
They may search different identifiers, cache results differently, or rely on directory publication that is not fully comprehensive.
Confirm the exact participant ID directly with the counterparty or provider before changing your ERP record.
Operator guides
Go one level deeper before you resend
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 guideA 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
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 pageThis 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 an invoice as sent while the customer sees nothing, you are usually dealing with routing, registration, or access-point issues rather than broken invoice content.
Open issue page