Analytic Budget Dashboard
This module compares the budgets of account_budget_oca with the actual analytic amounts, month by month, over the whole analytic plan hierarchy.
Plan budgets are envelopes
With account_budget_analytic_plan, a budget line can target an analytic plan instead of an analytic account, for instance when the revenue expected from a business line is known before its projects are. Such a budget line is an envelope: the budget lines on the analytic accounts and on the subplans below it, in the same budget and budgetary position, identify part of it instead of adding up. The rest of the envelope shows as a Pending to identify item of the plan.
So the budget of a plan is its envelope (or the sum of its content when it has none) and nothing is counted twice. As projects get sold and budgeted, their budget moves from the pending item to their account and the total of the plan does not change. When the identified budget exceeds the envelope, the pending item becomes negative.
Budget and actual amounts
The budget lines are spread over the months of their period in proportion to their days, as their theoretical amount.
The actual amounts are the analytic lines counted by the analytic reports (see the personnel cost source of account_analytic_dashboard), classified by the budgetary positions of each budget: an analytic line belongs to the position holding its financial account, or to no position.
Revenue and expenses follow the sign of the budget lines and of the analytic lines.
Within a budget, the budgetary positions cannot share financial accounts, or the actual amounts would be counted twice. Different budgets can use different positions.
Reports
Accounting > Reporting > Budget vs Actual: a pivot with the plan hierarchy down to the budget items in rows, and the budget, actual and deviation of each budget in columns.
Dashboards > Budget: key figures against the budget, budget and actual by month, by line (first level of the project plan, with the revenue pending to identify) and by budgetary position. Filter it by budget: the figures of several budgets add up, and the dashboard warns about it.
Table of contents
Usage
Define the budgetary positions, for instance one for the sales accounts and one for every group of expense accounts.
Create a budget and add its lines: on an analytic plan for the envelopes of the business lines, and on analytic accounts for the projects already known. Revenue is positive and expenses are negative.
As new projects are known, add budget lines on their analytic accounts: they are taken from the envelope of their plan.
Review Accounting > Reporting > Budget vs Actual or the Budget dashboard, filtered by budget.
The dashboard is generated by tools/build_dashboard.py: to change its layout, edit the script and run it again to update data/files/budget_dashboard.json.
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@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-budgeting 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-budget-analytic-dashboard 18.0.1.0.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_budget_analytic_dashboard-18.0.1.0.0.1.tar.gz | 31.9 kB | Without provenance | Details for odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1-py3-none-any.whl |
Total release size: 76.6 kB
Release files / odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1.tar.gz
| Download URL | odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1.tar.gz |
|---|---|
| Size | 31.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db8674ddbd0a0f2f0eac2ff2fea843941e56d43e6925ac165e3c16b73b2fabd9
|
|
BLAKE2b-256 checksum How to use checksums |
9e6e0b8f04766d55e97160cbd1b327cb2cf5e457b7060cb06f2939bd85fd570a
|
| 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_budget_analytic_dashboard-18.0.1.0.0.1-py3-none-any.whl
| Download URL | odoo_addon_account_budget_analytic_dashboard-18.0.1.0.0.1-py3-none-any.whl |
|---|---|
| Size | 44.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34719e9fd8d1df543c59f23f87b7c2b048f9da6091f304feaf532be3a4cc6bf2
|
|
BLAKE2b-256 checksum How to use checksums |
e3d6d37c932fb63fcb1d65c16ccbb02e4c835d134bcf6227d19ce8fbabb8fc26
|
| 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-budget-analytic-dashboard 18.0.1.0.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.