EH HR Lawsuit
Track legal cases through a configurable, audited workflow from filing to closure.
Why this module
EH HR Lawsuit
A register, not a law firm
This is a disciplined case register on a shared engine. It records what a case is, who it concerns, where it is filed, what is claimed, and what state it sits in. It does not pretend to be litigation management software.
Every change is captured
State changes and edits to the case fields are written to an append-only, sha256 hash-chained audit log that can be verified end to end. When a case is contested, you can show exactly who changed what and when.
Owns no workflow code of its own
States, transitions and the audit trail come from the EH HR Platform engine, so behaviour is consistent with the rest of the suite and the case workflow can be reconfigured without touching this module's code.
Day in the life
From filing to closure in one register
An HR officer logs a new case as Draft. The system stamps it with an auto reference like LAW/2026/00042 and records who created it. The officer opens the case, moves it to court when a hearing is set, then closes it or dismisses it from open. Each step is gated to the HR officer group, written to the chatter, and appended to the hash-chained audit log. Closed and dismissed are final, so the record cannot be quietly reopened or re-routed. A second company in the same database sees none of this: the case belongs to one company and stays there.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Closed and dismissed are marked terminal in the workflow definition. The engine refuses any further transition from a final state, even one a misconfigured definition might declare, so a settled or dismissed case cannot be silently reopened.
Each audit row stores the sha256 of the previous row plus its own fields. Any edit that does not recompute the entire downstream chain is caught by verify_chain(), which walks the log forward and returns the first broken row.
The hash chain is serial by nature. Appends take a transaction-scoped Postgres advisory lock (pg_advisory_xact_lock), so two concurrent writes cannot read the same tail and fork the chain. The lock releases automatically on commit or rollback.
company_id is required and defaults to the active company. A write that moves a case into a company the user does not belong to is rejected, even under sudo, unless an explicit audited override context is set, and the elevation is itself written to the audit log with every affected record id.
Case references are drawn from a per-year sequence only when the name is still 'New', so importing or duplicating records does not consume or overwrite an existing reference, with a safe LAW/AUTO fallback if the sequence is missing.
Where the engine routes a gated transition to approvers, the real submitter is captured before the engine elevates to sudo, so the user who fired the transition cannot later approve their own request even if they hold an approver group.
What is inside
Built to do the job, end to end.
- Case model. eh.hr.lawsuit with title, optional employee link (ondelete restrict so a tracked employee cannot be deleted out from under a case), case type of labour, civil, criminal or other, court or tribunal name, filed date, amount claimed and a free-text description, ordered newest filed first.
- Configurable workflow. A draft to open to in court to closed path, plus a dismiss transition from open. States, order and the allowed transitions live in the workflow definition data and are resolved at runtime, so the flow can be reconfigured without code changes.
- Hash-chained audit trail. An append-only audit log captures create, write and unlink events for the tracked fields with before and after snapshots, each row chained by sha256 and verifiable via verify_chain(), independent of the chatter.
- Access and menus. Read and write for HR admin, officer and manager groups, with unlink reserved to admin. Transitions are gated to the HR officer group. A Lawsuits menu sits under the platform records section, visible to officers.
- Status form and chatter. A statusbar form with stage-aware buttons (Open Case, To Court, Close, Dismiss) that appear only in the valid source state, plus full mail.thread chatter and field tracking on state, employee, case type, filed date and amount.
- Tests. Post-install tests cover auto-numbered defaults, the optional-employee case, the full draft to closed path, and the dismiss-from-open path, run on real Odoo 18.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a case register and workflow tracker, not full litigation or matter-management software. It does not manage documents or evidence beyond standard chatter attachments, and ships no document templates.
- There is no hearing-date scheduling, no reminders, and no scheduled jobs. Dates such as the filed date are recorded fields, not calendar events, and the module ships no cron.
- There is no financial integration. Amount claimed is an informational figure only, with no reserves, provisions, journal entries or accounting links.
- The platform engine supports approval-gated transitions, but the lawsuit workflow ships with direct, group-gated transitions rather than a wired approval chain. Approval routing would need configuration.
- It does not produce legal reporting, dashboards or analytics out of the box beyond the standard list, form and search views.
- It owns no workflow or audit code of its own. It depends on eh_hr_core, eh_hr_compat and eh_hr_engine_workflow, which must be installed.
odoo legal case tracking, odoo lawsuit management, hr litigation register odoo, employee legal case odoo, labour dispute tracking, court case workflow odoo, case audit trail, multi company hr odoo, odoo 18 hr legal, fair work claim tracking, employment law case management, tamper evident audit log
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Please log in to comment on this module