End-of-Service / Gratuity Settlement

This is a build-to-order engagement with a typical 2-4 week lead time from the point your gratuity rules are confirmed. After purchase we run a short scoping call to lock the labor-law equation, slabs and wage basis with your HR/legal team, then build, install and configure the module on your Odoo instance and validate it against sample leaver cases before go-live. It is not an instant download — you are commissioning a purpose-built module that ECOSIRE builds and deploys for you.

Your quote includes a defined post-go-live support window (typically 30-90 days) covering bug fixes, configuration questions and rule adjustments. You also receive the full module source, so your own team can maintain it. When labor law changes or you upgrade Odoo, ECOSIRE offers ongoing support and version-migration engagements so the module keeps working correctly across Odoo 17, 18 and 19.

Both. The module is built as a standard custom addon and targets Odoo 17, 18 and 19 on either Community or Enterprise. It integrates with your existing HR (hr.employee, contracts) and time-off data. If a specific feature depends on an Enterprise app in your environment, we confirm that during scoping so there are no surprises at install.

Yes — that is the point of build-to-order. Country-law presets for GCC, Pakistan, India and others ship as a starting point, but the equation, service slabs, daily-wage basis, capping, eligibility gates and resignation-versus-termination reduction factors are all configurable data we tune to your jurisdiction and your company policy during scoping. If your rules are unusual, we model them explicitly rather than forcing a generic template.

Gratuity is a stored compute field driven by @api.depends on the employee's join date, last working day, contract wage and leave balance, so it recalculates automatically when any input changes. The final settlement consolidates gratuity plus leave encashment, pending salary and notice pay, minus loans and advances. Every recomputation and applied rule is logged in the record chatter, a QWeb PDF statement documents the breakdown line-by-line, and the payable posts to accounting — a full, auditable trail from input to journal entry.

Yes. Because it is native Odoo, settlements are available over the standard XML-RPC and JSON-RPC APIs. If you run an external HRIS or an automated offboarding workflow, we can expose endpoints so a settlement is created and read programmatically. We scope any such integration during the build so security and record rules still apply to API access.

The labor law(s) and jurisdiction(s) you operate in, your written gratuity and end-of-service policy (slabs, wage basis, resignation/termination treatment, leave-encashment valuation), a few real or sample leaver cases to validate against, and access to your Odoo instance. We handle the rest — scoping, building, installing, configuring, documenting and training your team.