The issue catalog is deliberately narrow: it targets the phrases people search when the send is already failing.
Belgian 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 identifier