| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 8894 |
| Technical Name |
eh_account_dashboard |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 8894 |
| Technical Name |
eh_account_dashboard |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Financial Dashboard
Live cash, AR, AP, period revenue and net plus optional approvals, collections, budget tiles.
Day in the life
9:00 AM. CFO opens one screen and reads the financial pulse.
Cash position at 1.2M (sparkline trends 30 days down). Receivables at 380k with 12% over 60 days. Payables at 290k. Period revenue at 950k, expense at 620k, net 330k (delta -8% vs. prior period). Pending approvals: 4. Active collections cases: 18. Budget overruns: 2. Open close runs: 1. FX revaluation pending: 0. One screen, one truth. Drill into any tile preserves the period context (period revenue drill goes to the period's posted entries, not all-time). The 9 KPIs render in under 2 seconds via parameterised SQL.
Overview
What this module does, in one read.
A financial dashboard for Odoo 19 Community. Live tiles for cash position, AR total, AP total, period revenue and net P&L; optional integration tiles for approvals queue depth, collections in-progress, and budget variance.
The dashboard reuses the same SQL builder and the same audit pipeline as the dynamic reports, so the numbers on the dashboard match the numbers on the trial balance to the cent.
Capabilities
Eight things this module gives you, with no padding.
Cash position tile
Live aggregate over cash and bank journals; multi-currency aware via the company functional currency.
AR + AP totals + overdue
One SQL pass each; the overdue figure uses configurable cut-offs.
Period revenue and net
Reuses the report engine compute so the dashboard matches the trial balance.
Optional approvals tile
When eh_account_approval is installed the queue depth surfaces on the dashboard.
Optional collections tile
When eh_account_collections is installed the in-progress count surfaces.
Optional budget tile
When eh_account_budget_pro is installed the headline variance surfaces.
One record per (user, company)
The dashboard model is per user per company so each operator has their own scope.
Brand footer
The dashboard finishes with the same brand line as the rest of the suite for visual consistency.
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.
- Tiles match the trial balance to the cent (same SQL builder)
- Optional integration tiles auto-light when other modules install
- Per (user, company) scoping for personal tiles
- Live cash / AR / AP / period revenue tiles
- Currency-aware aggregation
- Multi-company scoping
- No drag-and-drop tile editor (fixed tile layout for now)
- Optional integration tiles depend on the other modules being installed
- No external embedding
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