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.
What is usually actually broken
Odoo's local participant state no longer matches the network registration data.
Do these before you resend
- Refresh the participant status in Odoo.
- Check whether the stored identifier uses the expected Belgian scheme.
- Confirm that the active company is the one registered for Peppol.
What people ask right before they get blocked
Not directly. It usually refreshes local participant trust and metadata so your ERP can resolve the partner correctly again.
Yes. Clones and restores can leave local provider bindings and participant states out of sync.
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 guideSimilar failure patterns worth checking
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.
Open issue pageAn 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.
Open issue pagePassing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.
Open issue page