| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3844 |
| Technical Name |
eh_account_close_workflow |
| 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 | 3844 |
| Technical Name |
eh_account_close_workflow |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Period Close Workflow
Ordered period-close checklist with sign-off chain and re-mark guard.
Day in the life
Month-end close: 38 tasks, 4 preparers, 1 controller.
The reusable checklist instantiates 38 tasks against the new run. Preparer A checks off bank reconciliations; Preparer B clears AR aging; Preparer C confirms accruals; Preparer D reconciles intercompany. The progress bar moves in real time. Two tasks are marked blocked with reasons; the request-approval transition refuses while required tasks are still pending. SoD enforces preparer != reviewer != approver. Once approved, the run is closed and read-only, but the audit trail (prepared_by, reviewed_by, approved_by + timestamps) is preserved if anyone needs to reopen.
Overview
What this module does, in one read.
A close-the-month workflow for finance teams. The closing tasks are listed in dependency order; each task has an owner and a sign-off; the workflow refuses to mark a task complete out of order.
A single shared checklist replaces the per-analyst spreadsheet that lives outside the system; the audit log captures every transition.
Capabilities
Eight things this module gives you, with no padding.
Ordered checklist
Tasks have a sequence; the workflow refuses to advance to a later task while a predecessor is incomplete unless explicitly overridden.
Sign-off per task
Each task records the signer, the time, and an optional comment. The sign-off is append-only at the framework level.
Re-mark guard
Re-marking a signed-off task is rejected with a UserError naming the task; an explicit override action is required.
Per-company instance
A close instance is per company per period; the workflow is templated per company so deployments encode their own steps.
Status surface
A small dashboard counter surfaces in the financial dashboard module if installed.
Plays with year-end
The year-end closing module schedules itself as a final task on the close workflow when both modules are installed.
Audit on every step
Every advance, every sign-off, every override is recorded; the audit log refuses write and unlink.
Multi-company aware
Templates and instances live under company scope; record rules enforce per-company isolation.
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.
- Re-mark guard with explicit override action
- Append-only sign-off at the framework level
- Per-company templated instances
- Ordered task dependency
- Activity-driven sign-off chain
- Multi-company isolation
- Templates are deployment-specific (no shipped catalogue)
- No external evidence-attachment workflow yet
- 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