| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 6756 |
| Technical Name |
eh_account_dynamic_reports |
| 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 | 6756 |
| Technical Name |
eh_account_dynamic_reports |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Dynamic Account Reports
Profit and Loss, Balance Sheet, Trial Balance, General Ledger, Aged Receivable and Payable, Cash Flow, Partner Ledger, Statements. One OWL viewer, currency on every cell, audit log per render.
Day in the life
P&L on a 100k-entry company in under 4 seconds.
The P&L kicks off the SQL builder against account.move.line directly (not via the ORM). Posted-only filter, period bounds, multi-company, hierarchical account.group expand/collapse all baked into the WHERE clause. The result hits the per-company cache keyed by move-version counter. Subsequent renders return from cache until the next account.move state change bumps the counter. Drill from any line to the underlying journal items preserves the report period and account filter. XLSX export completes in under 5 seconds for the 100k-entry case.
Overview
What this module does, in one read.
The financial reporting layer of the suite. Every standard accountant report is built on top of a single AbstractModel handler hierarchy and rendered through a single OWL viewer so the look and feel is uniform across the suite.
Currency symbols on every cell. Date presets cover this month, last month, this quarter, last quarter, this year, last year. Filters span companies, journals, account types, partners, accounts, analytic plans and analytic accounts. Every render writes one audit row.
Capabilities
Eight things this module gives you, with no padding.
Eight standard reports
P&L, Balance Sheet, Trial Balance, General Ledger, Aged Receivable, Aged Payable, Cash Flow (indirect), Partner Ledger.
Customer + Vendor Statements
Both sides; the customer statement also lands on the customer portal home for self-service.
Currency-aware rendering
Every monetary cell renders with the company currency symbol; the XLSX writer builds a matching Excel number-format string so the spreadsheet matches the screen cell for cell.
Comprehensive filter pane
Quick row plus advanced pane with multi-select pickers for companies, journals, account types, partners, accounts, analytic plans, analytic accounts.
Hierarchy and drill-down
Sectioned reports support unfoldable lines with caret expand/collapse and full drill-down to journal items.
Reproducible audit log
Every render including cache hits writes an audit row pointing at the source compute. An auditor can re-execute the same render later.
PDF and XLSX export
Universal PDF template with a brand footer; XLSX writer with the same currency block as the screen cell.
Multi-company aware
Every SQL build emits company scope; cache key carries the company set canonically so two scopes never collide.
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.
- Audit log row written per render including cache hits
- Customer + vendor statements both available
- Analytic plan + analytic account filters across every report
- Sectioned compute, drill-down, hierarchy
- PDF and XLSX export
- Multi-company scope
- No multi-period comparator yet (roadmap, options collected)
- No live-bank-feed integration (banking module ships statement import instead)
- Builder lives in the Pro module on top
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