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

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.

Open issue page
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.

Open issue page
Why a valid invoice can still fail on Peppol

Passing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.

Open issue page