If you use the py3o reporting engine (module report_py3o from the reporting-engine OCA project) to generate your PDF invoices and you want these PDF invoices to be Factur-X invoices (i.e. a PDF invoice with an embedded XML file in CII format), this module is for you ! Factur-X is the e-invoicing standard for France and Germany (in Germany, it is also called ZUGFeRD 2.1).
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically embeds Factur-X (ZUGFeRD) XML into PDF invoices generated with the Py3o reporting engine, so your PDF invoices become compliant e-invoices.
This module connects two existing features: the Py3o reporting engine (used to design custom PDF invoices) and Factur-X e-invoicing. When you print an invoice as a PDF using a Py3o report, the module checks if the invoice is set to use the Factur-X format. If so, it automatically adds the required XML file inside the PDF, turning it into a Factur-X (also known as ZUGFeRD 2.1) invoice.
- Works only when printing a single invoice at a time.
- Only applies to reports of type 'py3o' that produce a PDF.
- The invoice must be configured to use the Factur-X format (as set by the account_invoice_facturx module).
- No new menus or screens are added; the change happens behind the scenes when generating the PDF.
- The module is installed automatically when both account_invoice_facturx and report_py3o are present.
It touches the py3o.report model and the ir.actions.report model to detect invoice reports. The result is that your Py3o-generated PDF invoices become legally compliant e-invoices without any extra manual steps.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/edi.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.