Analytic Dynamic Full Cost
This module extends analytic accounting with a dynamic full-cost calculation based on productive and reproductive analytic plan branches.
It includes the classification of analytic plans as productive, reproductive, or not analyzed.
Functional Purpose
In many organisations, part of the activity is directly productive while another part corresponds to reproductive or supporting activity such as administration, coordination, infrastructure, shared services, or delivery management.
Reproductive activity has associated analytic weight. This module distributes that weight across productive branches in each analytic dimension and stores the resulting full-cost amount on analytic lines, producing a more realistic and traceable analytic cost structure.
How Full Cost Is Determined
The cost of the reproductive plans is spread over the productive ones, proportionally to their base lines: their expenses or their revenue, depending on the company weight basis (see below). Billing ten times more, or spending ten times more, means bearing ten times more of the reproductive cost.
For each company and reference date, the module:
Selects the computation window according to the company settings.
Computes, for each analytic plan, the amount of its base lines and the net cost of all its lines (expenses minus revenue), using the analytic account field that corresponds to that plan dimension.
At each productive plan, computes a rate: the net cost of its reproductive child branches divided by the base lines of its productive branch. When a productive plan has no base lines below it, its reproductive cost goes up to the parent level.
Adds the rates of the plan and all its ancestors.
Stores the resulting multiplier on the analytic plan: 1 + rate when the base lines are expenses (the cost grows), 1 - rate when they are revenue (the margin shrinks).
For each analytic line, the module stores its full-cost amount:
lines linked to reproductive plans: 0.0, whatever their sign, because their whole balance is redistributed over productive branches;
base lines of productive plans: amount * product(plan_full_cost_multipliers);
any other line: its original amount.
The full-cost amounts of the analysed lines therefore add up to their original amounts: the reproductive cost is moved, never created nor lost.
Plans marked as Not Analyzed and every descendant below them are completely excluded from the computation. Their analytic lines keep their original amount. When an analytic line also has productive accounts in other dimensions, only the not-analyzed dimensions are ignored.
Configurable Time Window
The company parameter Full Cost Period controls the default look-back window used to calculate plan weights. The default is the two-year window. When the period is set to rolling, Full Cost Window (Days) defines the number of days to look back.
Examples:
Two-year window: full cost based on the same date two years earlier.
Three-year window: full cost based on the same date three years earlier.
Rolling window = 180 days: full cost based on the last six months.
Current fiscal year: full cost based on the fiscal year of the reference date, from its first day. Every line of the year is valued with the same multipliers, so the full cost of the year adds up to its amount.
Weight Basis
The company setting Full Cost Weight Basis defines the base lines, which both weight the productive plans and carry the reproductive cost:
Expenses: analytic lines with negative amount. The reproductive cost is added to the expenses of the productive plans.
Revenue: analytic lines with positive amount. The reproductive cost is deducted from the revenue of the productive plans, as a percentage of their billing.
Recalculation
A daily cron recomputes recent analytic lines.
A wizard allows recomputing multipliers and analytic line full-cost amounts for a company, useful when:
the full-cost window is changed,
analytic entries are backdated,
productive or reproductive weights change significantly.
Operational recalculation only updates analytic lines inside the current full-cost window. Lines outside that window keep their latest calculated full_cost_amount. This is intentional: once an entry falls outside the active calculation window, its operational value is treated as a stable historical result instead of being continuously rewritten by later cost structures. For historical analysis at another date, use the historical full-cost report; it calculates the applicable window and ratios on the fly without changing stored analytic lines.
Typical Use Cases
Project costing
Cooperative / social economy organisations
Internal rate validation
Management accounting / controlling
Forecasting and budgeting
Table of contents
Usage
1. Configure Analytic Plans
Each analytic plan can be marked as:
Productive: activity that receives full-cost allocation.
Reproductive: supporting activity whose weight must be spread.
Not Analyzed: activity excluded from full-cost analysis together with all descendants.
To configure:
Go to Accounting -> Configuration -> Analytic Accounting -> Analytic Plans.
Open a plan.
Set Full Cost Role to Productive, Reproductive, or Not Analyzed.
Analytic lines derive their full-cost role from the analyzed analytic accounts set on the line. In Odoo’s multidimensional analytic model, each root analytic plan has its own account field; dimensions marked as Not Analyzed are ignored.
2. Configure Company Full-Cost Settings
Go to Accounting -> Configuration -> Settings, in the Analytics block (with the analytic accounting enabled), and set for the current company:
Full Cost Period
Full Cost Window (Days) (only for the rolling window)
Full Cost Weight Basis
The block also links to the recompute wizard.
The window determines which analytic lines are considered when recomputing plan weights. The weight basis determines whether those weights come from expenses or revenue.
3. Recompute Multipliers and Amounts
Use Accounting -> Analytic Accounting -> Recompute analytic full cost.
Select:
Company
Whether analytic lines should also be recomputed
The wizard recomputes the current plan multipliers using today’s date and the company window configuration. If line recomputation is enabled, it then updates full_cost_amount only on analytic lines inside the current full-cost window.
Analytic lines outside the current window keep their latest calculated full_cost_amount. This avoids continuously rewriting old operational analytic figures when today’s cost structure changes. To analyse another date or an old period, use the historical full-cost report, which calculates the relevant window and ratios on the fly without updating stored analytic lines.
4. Reporting
Use Accounting -> Reporting -> Historical Full-Cost Analysis to select an analysis date. The report calculates the window and multipliers on the fly for that date; it does not store historical ratios.
You can also analyse current full cost in analytic reporting views by using:
full_cost_amount
full_cost_role
This allows reporting at analytic account and full-cost role level.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Quim Rebull <quim.rebull@coopdevs.org>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/account-analytic project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-account-analytic-dynamic-full-cost 18.0.1.1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1.tar.gz | 40.5 kB | Without provenance | Details for odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1-py3-none-any.whl |
Total release size: 101.3 kB
Release files / odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1.tar.gz
| Download URL | odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1.tar.gz |
|---|---|
| Size | 40.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa539e59cfdcf2a815259e7329f75b2fe5fc94b3968dce1607d5ddf8d56ffae1
|
|
BLAKE2b-256 checksum How to use checksums |
9c6355ae6ce8718b728aa03f2c6fae7a2a71a42389d755dcdf3c82f906a31382
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1-py3-none-any.whl
| Download URL | odoo_addon_account_analytic_dynamic_full_cost-18.0.1.1.0.1-py3-none-any.whl |
|---|---|
| Size | 60.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f6864aae44e83b634b22761c5cc168dd572d8cd9a004b4cb3a5813c14877df30
|
|
BLAKE2b-256 checksum How to use checksums |
24d0cb40f623f729f292e6b7d7d34c402b4fd14d8c21c8582759490211bb83c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for odoo-addon-account-analytic-dynamic-full-cost 18.0.1.1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.