| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 2866 |
| Technical Name |
eh_account_base |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 2866 |
| Technical Name |
eh_account_base |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Accounting Suite Base
Reproducible report audit log. Move-version cache. Parameterised SQL builder. The shared engine that powers every other module in the ERP Heritage accounting suite.
Day in the life
An auditor asks: who ran the P&L on May 4 with which filters?
The reproducible report audit log has the answer in one query. Every render is recorded as an eh.account.report.execution row: who, when, parameters used, runtime, and a SHA-256 hash of the rendered output. The auditor re-runs from the stored options snapshot and gets a byte-identical result. The per-company eh_move_version counter bumps on every account.move state change, so cached report results are served on cache hit and recomputed the moment the underlying ledger changes. No stale numbers; no missing audit trail.
Overview
What this module does, in one read.
eh_account_base is the engine. It auto-installs as a dependency of any ERP Heritage accounting module so you do not need to install it manually.
It ships three core capabilities the rest of the suite relies on: a structured report execution audit log; a precise cache invalidation pipeline based on a per-company move version counter; and a multi-company aware SQL builder used on the hot path of every report.
Capabilities
Eight things this module gives you, with no padding.
Reproducible audit log
Every report render writes an eh.account.report.execution row with options snapshot, user, runtime, and a SHA-256 of the result. Re-run the exact report from any audit row on demand.
Move-version cache
A per-company move version counter is incremented atomically on every account.move post or unlink. Cache lookups carry the counter so a hit means no posting since the cached payload was generated.
Parameterised SQL builder
A fluent query composer that emits multi-company scoped SQL, accepts analytic plan and account filters, and never interpolates user input into raw SQL.
Privilege groups
Three groups (User, Manager, Auditor) so a deployment can grant suite access to one cohort without granting standard accounting access.
Originator constraint check
res.company gains an eh_move_version field maintained by SQL UPDATE; nothing in the suite reads or writes it directly except the cache infrastructure.
Currency-aware payloads
Report payloads carry a currency block per scope so monetary values render with the correct symbol and decimal places in PDF, XLSX, and the OWL viewer.
Auto-install on dependency
Listed in the manifest of every other EH module so it appears once when the user installs any of them, never twice.
No vendor lock-in
No activation key, no online phone-home, no opaque server. The whole codebase is on disk and inspectable.
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.
- Reproducible report audit log per render
- Cache invalidation by atomic move-version counter
- Privilege-group ACL separation from upstream
- Multi-company scoping on every report query
- Currency rendering on every monetary cell
- Standard Odoo ORM and chatter idioms
- Does not ship reports itself (those land in the dynamic-reports modules)
- No UI of its own beyond the audit log list
- Engine module: depend on it from your own EH-style addons
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