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.
If the route is wrong, another resend only repeats the same miss. If the provider connection is broken, retries just create noise.
Use the incident evidence first: participant ID, scheme, provider message, and whether the invoice ever left the sender.
Wrong scheme selection, stale partner bindings, and copied company records often look like network failures from the ERP side.
If the recipient changed from one identifier to another, correct the partner record and regenerate the invoice before you try again.
Provider tickets move faster when you include the participant ID, the exact symptom text, the last send attempt, and what you already ruled out.
That turns a vague 'Peppol is broken' ticket into an actionable delivery incident.
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.
Open issue pagePassing XML validation is not enough. Routing, registration, and provider state can still block delivery. This page explains the gap.
Open issue pageA 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.
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 pageGuides are useful when the pattern is familiar. When the latest failure still feels fuzzy, run the analyzer with the exact provider message or XML so you can separate routing, profile, and provider-state problems.