Partner Category Multi Company Account
Ensure multi-company check in Matching partner categories.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a multi-company check to the partner categories used in reconciliation models, so a reconciliation rule cannot mix partner categories from different companies.
This module is a small technical extension that reinforces company separation in accounting reconciliation rules.
In Odoo, a reconciliation model (the rule used to automatically match bank statement lines with accounts and partners) can be linked to partner categories. This module adds a company consistency check on that link: the partner categories selected in a reconciliation model must belong to the same company as the reconciliation model itself.
- It extends the
account.reconcile.modelmodel. - It applies the company check to the
company_idfield of that model. - It works together with the
partner_category_multi_companymodule, which is what makes partner categories company-specific.
There are no new menus, screens, buttons or reports. Users keep working in the existing reconciliation model configuration screen; the only visible effect is that Odoo will refuse to save a rule that combines partner categories from another company. This prevents cross-company data leaks and keeps accounting rules correctly scoped per company.
The module installs automatically when its dependencies are present, so no manual setup is required.
Depends on
Models and fields (1)
- account.reconcile.model · extends an existing modelcompany_id
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/multi-company.
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.