Symptoms
What this usually looks like
Directory result is unclearTooling disagreesRegistration may be real but uncertain
Peppol Directory inconclusive: what it means before you resend
An inconclusive directory result is not a green light and not a final rejection. This page explains how to handle the gray zone without wasting retries.
Likely cause
What is usually actually broken
The lookup source is incomplete, stale, or temporarily unavailable, so you do not yet have enough evidence to trust the result.
Next steps
Do these before you resend
- Pause the resend and treat the lookup as advisory.
- Confirm the full scheme-plus-value pair you expect to use.
- Escalate with evidence if the provider and live lookup disagree.
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
No. It means the lookup did not give you enough confidence to treat the answer as final.
Bring the exact participant ID, the lookup result, and the last provider symptom so support can separate route problems from source-system issues.
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 VIES cannot confirm the Belgian VAT number you used for an e-invoice workflow, you need to separate a real format problem from a temporary upstream gap.
Open issue pageIf 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 page