| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 8235 |
| Technical Name |
eh_account_dynamic_reports_pro |
| 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 | 8235 |
| Technical Name |
eh_account_dynamic_reports_pro |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Dynamic Reports Pro
Drag-and-drop custom report builder, scheduled email delivery, multi-period forecasting, saved views.
Day in the life
Friday morning. Five report packs scheduled across the org.
The custom report builder defines five report variants for different audiences: Board P&L, Treasury cash position, Sales receivables, Operations cost centres, Group consolidated TB. Each has its own filter set saved as a named view. Five email-delivery schedules fire at 9 AM Friday. The forecast engine runs a multi-period projection on the budgets module. All five reports auto-export and email; the recipients open the PDF before the standup.
Overview
What this module does, in one read.
The pro extension. Builds on the standard Dynamic Account Reports engine so the OWL viewer, PDF template, XLSX writer, and audit log all flow through the same hot path.
Builder produces deterministic output from a definition; scheduler sends the rendered PDF or XLSX on a cadence; forecaster fits Holt-Winters or linear trend or simple moving average to a published series.
Capabilities
Eight things this module gives you, with no padding.
Custom report builder
Define rows, formulas, account roll-ups, and grouping in a form. The builder produces a report the user can run, schedule, save, and export like any standard report.
Scheduled delivery
A cron renders the report on cadence and emails it to recipients. Per-record savepoint isolates a single bad delivery from freezing the queue.
Multi-period forecasting
Plain-Python Holt-Winters plus linear trend plus simple moving average. The choice of method degrades by series length, never silently to the global mean.
Saved views per user
Save the current filter pane, give it a name, optionally share with the company. Saved views are isolated by company and user as appropriate.
Safe formula evaluator
Whitelist AST walk plus restricted evaluator. No exec, no import, no attribute access; only literals, arithmetic, and named line lookups.
Forecast as comparison
Forecast results render alongside actuals with the same comparator infrastructure used by period comparison in the base reports.
Versioned schedule history
Each scheduled delivery records the run as an audit row pointing at the source compute, so an auditor can re-execute the exact email that landed in the inbox.
Multi-company aware
Every builder, every saved view, every schedule lives under company scope; record rules enforce isolation at the framework level.
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.
- Plain-Python Holt-Winters that degrades by series length, not silently
- Builder formula evaluator with whitelist AST walk
- Scheduled deliveries land as audit rows
- Saved views per user with optional sharing
- Cron-driven scheduling
- Builder rows / formulas / roll-ups
- Forecast accuracy bounded by published methods, not a deep-learning model
- Builder is form-driven, not WYSIWYG
- Statistical forecasting is opt-in per scenario, not always-on
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