PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Odoo says Peppol sent the invoice, but the customer never received it

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.

Blocked Odoo send flow Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Sent status in OdooCustomer has no invoiceNo obvious XML validation error
Likely cause

What is usually actually broken

The invoice left Odoo, but the target participant resolution or delivery handoff failed downstream.

Next steps

Do these before you resend

  1. Verify the recipient identifier outside the ERP.
  2. Compare the Odoo company binding with the recipient's live publication.
  3. Use the analyzer to decide whether the issue is routing or provider-side.

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.

Recent operator reports

Current public evidence for this exact failure

Belgium operators reporting invoices marked as sent but not received in Odoo

r/Odoo · March 2026

Open source
FAQ

What people ask right before they get blocked

Does this mean my XML is broken?

Usually not. If Odoo shows sent status, the more common problem is participant resolution, publication mismatch, or downstream provider state.

Should I resend immediately?

Not before confirming the participant identity and provider state. Blind retries can create noise without fixing the route.

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

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