Account Analytic Parent Plan Restrict
This module extends the analytic account hierarchy introduced by the account_analytic_parent module. It forces every account in a parent/child tree to belong to the same analytic plan, so a hierarchy can never belong to more than one plan.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Prevents an analytic account from being linked to a parent or child that belongs to a different analytic plan, keeping each hierarchy inside one plan.
This module adds a consistency rule to analytic accounts. When a user saves an analytic account, Odoo checks the account's analytic plan against the plan of its parent and against the plans of its children.
- If the account has a parent whose analytic plan is different, saving is blocked with a message naming both the account and its parent.
- If any child account belongs to a different analytic plan than the account being saved, saving is also blocked, and the message lists the offending children.
The rule is enforced automatically whenever the plan or the parent is set or changed, so users cannot build a hierarchy that spans more than one analytic plan. It applies to the account.analytic.account model, which is the same model used for analytic accounts throughout Accounting. No new menus, screens, buttons, reports or scheduled jobs are added; the only visible change is the validation error shown when an inconsistent hierarchy is saved.
Depends on
Models and fields (1)
- account.analytic.account · extends an existing model
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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/account-analytic.
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.