PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

What Odoo means by 'Revalidate IDs' in Peppol

The revalidation prompt usually signals stale participant metadata or a registration mismatch. This page shows what to refresh before you resend.

Odoo maintenance and trust issues Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Revalidate IDs buttonParticipant status out of syncPeppol verification drift after setup
Likely cause

What is usually actually broken

Odoo's local participant state no longer matches the network registration data.

Next steps

Do these before you resend

  1. Refresh the participant status in Odoo.
  2. Check whether the stored identifier uses the expected Belgian scheme.
  3. Confirm that the active company is the one registered for Peppol.

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

Does revalidating IDs change the invoice?

Not directly. It usually refreshes local participant trust and metadata so your ERP can resolve the partner correctly again.

Can this happen after restoring a database?

Yes. Clones and restores can leave local provider bindings and participant states out of sync.

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
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