| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4405 |
| Technical Name |
eh_account_approval |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4405 |
| Technical Name |
eh_account_approval |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Approval Workflow
Multi-step ordered approver groups with atomic step pointer (compare-and-set), re-approval on material amount change, append-only approval log.
Day in the life
A bill posts at 49,500. The approval threshold is 50,000.
The just-under-threshold detector raises a structuring flag immediately; the controller pauses the post. Investigation shows the bill was split from a 99,000 invoice the day before. The amount-change re-approval gate kicks the document back to step zero, the audit log records the rollback with the trigger amount, and the chain restarts. Manager + Director + CFO each sign off in turn through the atomic step pointer (compare-and-set so two concurrent approvers cannot skip a step). The bill posts only after the full chain completes.
Overview
What this module does, in one read.
A multi-step approval workflow for accounting documents (vendor bills, payments, journal entries). Steps are ordered; the step pointer advances atomically via compare-and-set so concurrent approvals cannot skip a step.
A material amount change after the first approval rolls the document back to step zero so the chain has to start over; the audit log records the trigger and the rollback.
Capabilities
Eight things this module gives you, with no padding.
Multi-step ordered groups
Each step has one or more groups; the step requires at least one approver from at least one of the groups.
Atomic step pointer
compare_and_set against the current step prevents concurrent approvals from skipping a step or double-advancing.
Re-approval on material change
A change to amount, partner, or other configurable fields after first approval rolls the document back to step zero.
Append-only approval log
Every action writes to the log. The log refuses unlink and refuses write on every field except comment.
Group-based ACL
Approvers are groups, not user lists.
Plays with credit limit
When eh_account_credit_limit is installed an approved invoice can override the credit-limit gate.
Multi-company aware
Policies, requests, and steps all sit under company scope.
Tested invariants
Regression tests cover the concurrent-approval race, the material-change rollback, and the delegate path.
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.
- Multi-step ordered groups (Enterprise ships single-step)
- Atomic step pointer prevents concurrent skip
- Re-approval rollback with audit reason
- Group-based ACL for approvers
- Append-only log model
- Multi-company scoping
- Approval rules are deployment-specific (no shipped catalogue)
- No external approval-chain integration (Slack, email-button)
- Activity scheduling rides standard mail.activity
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