| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4585 |
| Technical Name |
eh_account_budget_pro |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4585 |
| Technical Name |
eh_account_budget_pro |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Multi Version Budget Pro
Multi-version budgets with per-account lines, optional analytic dimension, monthly auto-split, prior-year seed.
Day in the life
Q3 forecast vs. budget. Marketing is 47% over.
The variance compute runs in batch SQL across all 200 budget lines: budgeted vs actual vs committed (encumbrance from open POs) vs available. The Marketing line shows 47% overrun; the encumbrance column reveals two open POs that would push the line further negative. The overrun_policy = block setting on the budget refuses the next PO confirm until availability returns to non-negative. The variance commenter (via eh_account_ai_agent) writes the close-pack headline: 'Period total overran by 12.2% driven by Marketing +47% and Salaries +10%.'
Overview
What this module does, in one read.
A real budget tool for finance teams. Budgets are versioned (v1, v2, scenario A, scenario B); lines are per account with an optional analytic account; views include list, form, graph, and pivot so the executive read is one click.
Two productivity actions: split lines monthly to prorate annual figures across calendar-month slices; seed from prior year to read the previous twelve months and write one budget line per contributing account.
Capabilities
Eight things this module gives you, with no padding.
Multi-version
Versions live alongside one another; comparison across versions is one click on the pivot view.
Optional analytic
A line can carry an analytic account; actuals are weighted by the percentage allocated to that account in the source journal item.
Split lines monthly
A productivity action replaces each line with calendar-month slices, prorating the budgeted amount across the slices it overlaps.
Seed from prior year
Reads the company prior twelve months of posted income and expense and writes one budget line per contributing account at the prior-period absolute balance.
Batch actuals
A single SQL pass computes actuals for every line.
Graph plus pivot
Pivot defaults to row=account, column=period_from:month; graph defaults to bar with three measures (budgeted, actual, variance).
Per-cron savepoint
The actuals-refresh cron iterates budgets under a per-record savepoint; one bad budget never freezes the queue.
Multi-company aware
Budgets, lines, and views all sit under company scope.
Compared
How this module stacks up.
Workflow
Configure once. Operate. Audit. Report.
Four steps, the same across every ERP Heritage module so a finance team learns the suite once.
Configure
Settings > Accounting > ERP Heritage. Multi-company, multi-currency, journals, accounts. One-time setup, persisted on the company record.
Operate
The user works inside the standard Odoo accounting flow. The module surfaces only the controls relevant to its scope.
Audit
Every action that changes accounting state writes an audit row. The audit log is append-only at the framework level.
Report
Reports flow through the same reproducible audit pipeline, with cache invalidation by per-company move version.
Why Heritage
Where this module leads, where it matches, what we are honest about.
- Optional analytic dimension on every budget line
- Split-monthly + prior-year seed productivity actions
- Batch actuals via single SQL pass
- Multi-version budgets
- Graph + pivot views
- Per-cron savepoint
- No statistical revenue forecast yet (lives in Reports Pro)
- No what-if scenario modelling beyond version compare
- Analytic plans are inherited from the upstream analytic module
The full ERP Heritage Accounting Suite (26 modules)
Engineering
Ten engineering rules we hold ourselves to.
No silent fallbacks.Missing config, missing accounts, malformed input each surface explicit messages naming the bad field.
Tests cover the bug, not just the feature.Every defect found in review has a regression test attached to the fix, kept in the repository.
Plain Python where possible.Algorithms that do not need the ORM live under tools/ with unit tests that run without Odoo.
Atomic counters via SQL.Concurrent counters use UPDATE col = col + 1, never read-modify-write loops.
Per-record savepoints in cron loops.A single bad record never freezes the batch; failing rows are recorded, the rest of the batch keeps moving.
Schema-first XML output.PAIN.001 and PAIN.008 generators target the published namespace; tests parse output back and assert structure.
ValidationError versus UserError.Constraint failures raise ValidationError; action failures raise UserError with a remedy.
Privilege groups, not direct upstream references.ACL CSVs reference suite-specific groups; the post-migration script promotes upstream-only users.
Append-only audit logs.Approval log, override log, reconciliation audit, mandate amendment log all override write and unlink at the model level.
Originality from public spec.Every standard implementation is built from the published technical specification, not from another vendor codebase.
The standard we hold: every shipped capability is original code from a public technical specification, with regression tests, with a documented engineering rule for the invariant the code preserves, and with no vendor names in code or user-facing docs. From the suite contributing process
Frequently asked questions
Honest answers to the questions a buyer asks.
Does this run on Odoo 19 Community?
Yes. Every module is built and tested against Odoo 19 Community. No Enterprise dependency anywhere in the stack.
What is the licence?
LGPL-3, the same licence as Odoo Community. You can read the source, modify it, and ship it inside your own Odoo deployment without restriction.
Will this conflict with another accounting addon I already use?
Probably not. The modules add new models in their own namespace (eh.*) and inherit standard models without overriding behaviour silently. If your existing addon also extends the same standard model, ordinary Odoo inheritance rules apply.
Are the engineering principles documented?
Yes. The contributing process and ten engineering rules are kept in the repository so a reviewer can verify the code holds itself to them.
Is there a test suite?
Yes. Every module ships its own integration tests; the engine module ships a full unit test suite for the SQL builder, cache, and report orchestrator.
How do I get support?
Reach the team via info@erpheritage.com.au. Training, deployment, and custom extension work is handled by ERP Heritage directly.
Built by ERP Heritage
ERP Heritage builds enterprise-grade accounting software for the Odoo community. Our suite covers the operational accounting cycle end to end: invoice intake, posting, reconciliation, reporting, period close, payment runs, customer portal, multi-step approvals, and year-end. Every module ships with explicit licensing posture, documented engineering principles, comprehensive tests, and a clear differentiation story.
Ready to deploy?
Install this module, run the test suite, and inspect the structured audit log. For training, deployment, or a custom extension, reach our team.
Talk to ERP Heritage about Odoo implementation, customisation, training, or support.
End-to-end engagement across the Odoo platform: implementation, customisation, reimplementation, functional and technical training, ongoing support, integration planning, and scoped extensions. One team, one response within a business day.
Please log in to comment on this module