Account Edi Ubl Cii Purchase Match Product Packaging
This module provides a fallback mechanism to recover the Unit of Measure (UoM) and product packaging during purchase line reconciliation of vendor bills imported from UBL/CII files.
It is a glue module between:
- Account Edi Ubl Cii Purchase Match
- Account EDI UBL move line uom and packaging By UNECE
auto_awesome What this module does
AI-generated from the code · Odoo 16.0When vendor bills are imported from UBL/CII electronic files, this module helps Odoo recover the correct unit of measure and product packaging on invoice lines by using the UNECE codes found in the file.
This is a technical bridge module that works behind the scenes during the import of electronic vendor bills (UBL/CII format). It does not add any new menu, screen or button.
What it changes: - When an invoice line is matched to a product, if the line carries a UNECE unit code from the electronic file, the module tries to fill in the product packaging information on that line. - If packaging cannot be determined, it then tries to fill in the unit of measure instead. - After packaging information is filled in, the line quantity is recalculated so that the quantities stay consistent with the packaging.
Which areas it touches:
- account.move.line (invoice lines) through the product assignment logic.
- The UBL 2.0 electronic document import logic (account.edi.xml.ubl_20).
It relies on two other modules: one that matches invoice lines with purchase orders, and one that reads UNECE unit and packaging codes from the electronic file. No scheduled actions, emails or access rules are added by this module.
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.