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.
The company is still bound for receiving on another access-point state or stale Odoo environment, so the current instance cannot take over the registration cleanly.
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.
If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.
r/Odoo · March 2025
Open sourceOdoo forum · April 2026
Open sourceNot if the real goal is full receiving and sending from the intended Odoo environment. Sender-only fallback usually means the registration conflict is still unresolved.
Because the old environment can keep a stale access-point relationship, credentials, or receiving registration that the new database cannot safely overwrite.
A calm, ordered checklist for Belgian Odoo users when Peppol starts failing without a clear explanation.
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 guideRestores 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 pageMulti-company setups, duplicates, and restored databases can leave Odoo pointing at the wrong Belgian participant even when the invoice itself looks fine.
Open issue pageAn invalid request signature is usually a provider credential or environment problem, especially after database copies or restores.
Open issue page