The issue catalog is deliberately narrow: it targets the phrases people search when the send is already failing.
If Odoo marks an invoice as sent while the customer sees nothing, you are usually dealing with routing, registration, or access-point issues rather than broken invoice content.
Diagnose Odoo deliveryThis 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.
Fix the access-point conflictThis 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.
Diagnose the exact validity errorIf 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.
Triage the global lookup failureBeing listed in the Peppol directory is not always enough to receive invoices. This page isolates the Odoo receiving-side failures that leave inbound invoices stuck even after registration.
Check the receiving setupBelgian zero-VAT or exempt invoices can still fail Peppol export when the tax category and exemption metadata do not line up with what the connector expects.
Check the zero-VAT send blockerBelgian Peppol delivery often fails because the counterparty is stored with the wrong identifier scheme. This page explains when 0208 and 9925 diverge and what to verify first.
Check a Belgian participant nowIf Odoo marks an invoice as sent while the customer sees nothing, you are usually dealing with routing, registration, or access-point issues rather than broken invoice content.
Diagnose Odoo deliveryThe revalidation prompt usually signals stale participant metadata or a registration mismatch. This page shows what to refresh before you resend.
Refresh the right identifiersThis usually means the customer is registered under a different identifier or not fully published. Here is how to separate a real absence from a lookup mismatch.
Validate the counterpartyA 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.
Compare directory evidenceThe invoice can look structurally valid and still fail because the participant scheme does not match the recipient's published routing identity.
Check endpoint structureAn invalid request signature is usually a provider credential or environment problem, especially after database copies or restores.
Triage the signature failurePassing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.
See the missing layerGerman XRechnung flows commonly reject invoices missing the buyer reference. Learn how to spot the issue fast and avoid another failed submission.
Check XRechnung fieldsIf you hit BR-CO-10, the invoice totals do not reconcile. This page translates the rule into practical bookkeeping and ERP checks.
Translate BR-CO-10A Peppol invoice can contain the business data and still fail because the export is missing the profile marker tools expect to classify it correctly.
Check profile metadataAn 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.
Review the lookup evidenceIf VIES cannot confirm the Belgian VAT number you used for an e-invoice workflow, you need to separate a real format problem from a temporary upstream gap.
Check the VAT evidenceMulti-company setups, duplicates, and restored databases can leave Odoo pointing at the wrong Belgian participant even when the invoice itself looks fine.
Check the company bindingRounding logic that looks harmless in the ERP can still produce totals that fail e-invoice validation. This page isolates the most common pattern.
Check the totals logicA stored GLN or alternate identifier does not guarantee Odoo will resolve the exact Peppol participant the recipient expects. This page shows where the mismatch happens.
Compare the stored identifierIf the invoice has business lines and totals but no EndpointID, the document still cannot route over Peppol. This page explains the exact failure and what to fix first.
Check the missing EndpointIDRestores 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.
Triage the restored environmentThis 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.
Fix the access-point conflictThis contradiction usually means Odoo has the wrong identifier, wrong scheme, or stale participant evidence. This page breaks down the mismatch clearly.
Compare Odoo against the live participantAn inconclusive VIES result is a gray zone, not a clean pass and not a final rejection. This page shows how to proceed without overcorrecting.
Review the inconclusive VAT resultThis is a precise invoice arithmetic failure, not vague validator fog. The page shows what causes it and which ERP fields to inspect first.
Check the payable amount mismatchThis 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.
Diagnose the exact validity errorIf 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.
Triage the global lookup failureBranch 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.
Check the branch-versus-parent bindingIf 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.
Compare the verification routeWhen Odoo or the verification path fails on the upstream ISO6523 resolver host, it looks like every customer is wrong even though the real problem is infrastructure or resolver state.
Triage the DNS failureBelgian zero-VAT or exempt invoices can still fail Peppol export when the tax category and exemption metadata do not line up with what the connector expects.
Check the zero-VAT send blockerOdoo may let you combine Belgian VAT and roerende voorheffing logic on one line, but the Peppol UBL export can still fail when that tax structure does not map cleanly to one invoice item.
Check the VAT and RV conflictBeing listed in the Peppol directory is not always enough to receive invoices. This page isolates the Odoo receiving-side failures that leave inbound invoices stuck even after registration.
Check the receiving setup