Account EDI Additional Documents
This module extends account_edi_ubl_cii to import all attachments included in UBL invoices, not only PDF files.
During the import process, additional documents provided by the supplier (e.g. XLSX, CSV, images) are extracted from the UBL payload and linked to the generated vendor bill.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0When a supplier sends a UBL electronic invoice, this module also imports the extra files attached to it (spreadsheets, images, CSV) and stores them on the created vendor bill, not just the PDF.
This module changes how Odoo reads supplier electronic invoices in UBL format. Normally only the PDF copy is kept; with this module, other files embedded in the same electronic document are also saved as attachments on the vendor bill.
- Supported extra file types are PDF, ODS and XLSX spreadsheets, JPEG and PNG images, and CSV files.
- PDF files are skipped by this module because they are already handled by the standard import.
- Each imported file is named after the identifier given in the electronic document, with the correct file extension added.
- The files are attached directly to the vendor bill (
account.move) that Odoo creates from the import.
It works in the background during the standard import of UBL invoices; there is no new menu, button or report. The module extends the shared electronic invoicing logic (account.edi.common) and relies on the account_edi_ubl_cii module. If a file type is not in the supported list, or if the document has no embedded file content, it is simply ignored.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 16.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.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.