Guide
Markdown exportValidate Odoo invoice exports
Use validation output to distinguish missing Odoo master data from conversion-time review fixes.
Export expectations
Check Odoo invoice exports and localization modules for EN 16931 field completeness before sending.
Validate the XML attached from the Odoo send flow or Peppol flow; the PDF and the posted invoice can look correct while EDI fields are still missing.
Export signals to inspect
Odoo documentation exposes e-invoicing format selection on the customer accounting tab and lists Peppol BIS Billing 3.0, XRechnung CIUS, and NLCIUS among supported send formats. Validate the selected contact format and endpoint data first.
Validation checklist
Use these points as the practical checks for this section.
- Confirm the customer e-invoicing format is explicitly set when the recipient needs XRechnung rather than default PDF/email behavior.
- Verify Peppol EAS code and endpoint number with the contact before treating a routing failure as an XML failure.
- If Studio extra Peppol fields are used, validate that their technical names populate the exported XML, not only the Odoo form.
Export triage table
| Symptom | Likely field or rule | Export-side fix |
|---|---|---|
| Odoo sends a PDF/email but no XRechnung XML is attached. | Recipient format setup | Set the customer e-invoicing format to XRechnung CIUS or Peppol BIS before using Send. |
| Peppol send fails before validator output is available. | EAS / endpoint identifier | Validate EAS code and endpoint number separately from XML content errors. |
Common validation failures
Localization setup often controls whether VAT exemption reasons, reverse-charge details, and buyer identifiers are present.
Validation workflow after export
Use validation output to distinguish missing Odoo master data from conversion-time review fixes.