| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 3436 |
| Technical Name |
eh_account_year_end |
| 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 | 3436 |
| Technical Name |
eh_account_year_end |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
ERP Heritage · Odoo Accounting Suite
Year-End Closing
Year-end closing wizard with computed P&L breakdown, balanced closing entry to retained earnings, optional reversal, optional fiscal-year lock.
Day in the life
31 December. Year-end close on a single button.
The year-end run computes net income across income + expense accounts up to year-end. The closing entry transfers net to retained earnings. The reversal entry goes on January 1 to start the new fiscal year. The fiscalyear_lock_date bumps to year-end so backdated entries cannot post. The audit log preserves who ran the close, with which parameters, and the SHA-256 of the closing entry. Re-running on a closed year is refused.
Overview
What this module does, in one read.
A year-end close routine for finance teams that need more than a manual journal. The wizard reads the income and expense balances over the fiscal year, computes the breakdown to retained earnings, posts a single balanced closing entry.
The closing entry is balanced by construction. The reversal path issues the symmetric reversal so reporting against the new year starts from a clean slate without losing the previous-year audit trail.
Capabilities
Nine things this module gives you, with no padding.
Computed breakdown
Income and expense balances over the fiscal year are read from posted journal entries; the wizard surfaces the breakdown so the operator approves it before posting.
Balanced closing entry
A single entry credits net income to retained earnings and zeros every income and expense account.
Optional reversal
The reversal action issues the symmetric reversal; the audit log records both entries with linkage so an auditor can trace the pair.
Fiscal-year lock
Optionally advance the fiscal-year lock date so subsequent posting against the closed year is blocked except by an authorised override.
One run per year
A unique constraint enforces one closing run per fiscal year per company; the wizard refuses a second run unless the first is reversed.
Per-company aware
The wizard reads the company calendar from the company record; runs across companies require explicit re-runs per company.
Audit log per run
Every run is recorded with the closing entry id, the user, the time, and the breakdown.
Plays with the close workflow
When eh_account_close_workflow is installed, the year-end run schedules itself as a final task on the close checklist.
Optional automation of closing
A scheduled cron can run the closing entry on a configured fiscal year end date. Manual review remains the default; automation is opt-in per company.
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.
- Computed breakdown with operator review before post
- Symmetric reversal with audit linkage
- Optional fiscal-year lock advance
- Closing entry to retained earnings
- One run per (company, fiscal year)
- Audit log per run
- No multi-year reroll (one year at a time)
- Closing date is the fiscal year-end on the company record
- Reversal is intentional; no automatic period reopening
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