PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Odoo Peppol is using the wrong company binding

Multi-company setups, duplicates, and restored databases can leave Odoo pointing at the wrong Belgian participant even when the invoice itself looks fine.

Odoo multi-company drift Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Wrong company sendsAfter restore Peppol behaves strangelyDifferent Belgian IDs appear across records
Likely cause

What is usually actually broken

The active company record, provider binding, or participant identity drifted after a clone, restore, or multi-company change.

Next steps

Do these before you resend

  1. Confirm which legal entity is active in Odoo at send time.
  2. Compare the bound identifier in Odoo with the participant you expect on the network.
  3. Re-authorize or refresh the binding before retrying sends.

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

Can this happen without an XML validation error?

Yes. The exported XML can still look correct while the provider binding points to the wrong company context.

What usually changed before this started?

Database restores, company duplication, and environment changes are common triggers.

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
When to resend a Peppol invoice and when to escalate

A 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

Odoo Error 201: 'Your company is already registered on another Access Point' and sender-only fallback

This exact Odoo Peppol message usually appears after a restore, duplicate database, or half-reset receiving setup. The result is a blocked receiving registration and a sender-only fallback that still does not restore the real workflow.

Open issue page
Odoo Peppol broke after a database restore or clone

Restores and cloned environments often leave Odoo Peppol bindings out of sync. This page isolates the exact symptoms that usually follow and how to recover cleanly.

Open issue page
Odoo Peppol is using the commercial company or mother company instead of the branch

Branch setups and commercial-company relationships can send Peppol traffic through the wrong legal entity. This page isolates the exact binding problem and how to correct it.

Open issue page