示意预览Automate end-of-service gratuity and final settlements in Odoo with configurable equations per labor law.
Built, installed and supported by ECOSIRE.
什么是 End-of-Service / Gratuity Settlement？
Automate end-of-service gratuity and final settlements in Odoo with configurable equations per labor law. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Processing a leaver in Odoo out-of-the-box means a spreadsheet, a lawyer's memo, and a lot of manual arithmetic — pro-rating years of service, applying resignation-versus-termination reductions, and reconciling leave encashment and outstanding dues by hand. Every mistake is a compliance and cashflow risk.
The ECOSIRE End-of-Service / Gratuity Settlement module removes that manual work. It is a purpose-built Odoo application that plugs into your existing HR and Payroll data and computes each employee's gratuity and final settlement from a configurable, auditable equation that mirrors the labor law you operate under — GCC (UAE, KSA, Qatar, Oman, Bahrain, Kuwait), Pakistan, India and beyond.
This is a BUILD-TO-ORDER engagement, not an off-the-shelf apps.odoo.com download. After purchase, ECOSIRE scopes your gratuity rules with your HR/legal team, then builds, installs and configures the module on your Odoo 17, 18 or 19 instance (Community or Enterprise) with a typical one working week lead time. You receive the full source, documentation and a support window — you own it outright.
Under the hood it is idiomatic Odoo. A dedicated models.Model for the settlement holds stored, compute fields (@api.depends on service dates, contract wage and leave balances) so the gratuity figure recalculates the instant an input changes. Rules are data, not hard-code: service-length slabs, daily-wage basis (basic vs. gross), capping, and resignation reduction factors are all configurable records you can edit without a developer. Country-law presets ship as loadable data. Access is governed by ir.model.access.csv plus record rules so only HR and Finance see settlements, and every calculation is captured in the chatter for audit. A QWeb report generates a signed-off settlement statement PDF, and the figures post through to accounting so the payable lands in your books automatically.
你得到什么
- The complete, installable Odoo module source (custom addon with __manifest__.py, models, views, security and data files) targeting your Odoo 17, 18 or 19 version
- Configured country-law preset(s) matching the jurisdiction(s) you operate in, tuned with your HR/legal team during scoping
- Deployment and installation on your Odoo instance (Community or Enterprise), with all dependencies wired and the module upgraded cleanly
- Configuration of your slabs, wage basis, resignation/termination rules and leave-encashment valuation, verified against sample leaver cases you provide
- QWeb settlement statement report branded to your company, plus the accounting journal mapping for the payable
- Written documentation — an admin configuration guide and an HR user guide covering the day-to-day settlement workflow
- A live training session for your HR and Finance users, recorded for future staff onboarding
- A defined post-go-live support window (two weeks) for fixes, questions and rule adjustments
这是给谁的
GCC HR Manager processing leavers
Runs offboarding for a UAE or KSA workforce and needs gratuity computed exactly to the local labor law — correct daily-wage basis, service slabs and resignation reductions — without rebuilding a spreadsheet for every departure.
Finance / Payroll Controller
Owns the numbers that hit the books. Wants each end-of-service payable calculated, documented and journaled automatically so the settlement is reconciled, auditable and posted to accounting with zero re-keying.
HR Operations lead at a multi-entity group
Manages several legal entities across different countries in one Odoo database and needs each company to apply its own gratuity rules and presets consistently, with settlements restricted to authorized HR and Finance staff.
Odoo administrator / IT owner
Maintains the Odoo instance and wants a clean, upgrade-safe custom addon with proper security records and source they can read and extend — not an opaque black box that breaks on the next version bump.
End-of-Service / Gratuity Settlement 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Matches your exact labor law (GCC, PK, IN) rather than a generic formula | 包含 | 包含 | 部分支持 | 不包括在内 |
| Configurable service-length slabs and resignation vs. termination reduction factors as editable data | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Full settlement (gratuity + leave encashment + dues - deductions) in one net figure | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Auto-recalculation via stored compute fields (@api.depends) when inputs change | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| QWeb settlement statement PDF and automatic accounting posting | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Row-level security via ir.model.access.csv + record rules restricting settlements to HR/Finance | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Delivered, installed, configured and validated by an Odoo team | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| Full source ownership plus documentation, training and a support window | 包含 | 部分支持 | 不包括在内 | 不包括在内 |
| Predictable cost and one working week timeline vs. open-ended in-house build | 包含 | 不包括在内 | 包含 | 包含 |
关于End-of-Service / Gratuity Settlement的常见问题
How long until the module is delivered and live?
This is a build-to-order engagement with a typical one working 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.
What support and updates do I get after go-live?
Your quote includes a defined post-go-live support window (two weeks) 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.
Does this work on Odoo Community or only Enterprise?
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.
Can it match my exact labor law, not just a generic formula?
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.
How is the final settlement figure calculated and can I trust it for audit?
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.
Can external systems create or read settlements automatically?
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.
What do you need from us to build it?
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.
相关模块
End-of-Service / Gratuity Settlement
Automate end-of-service gratuity and final settlements in Odoo with configurable equations per labor law. Built, installed and supported by ECOSIRE.
- Gratuity calculated from a fully configurable equation (daily-wage basis x service years x per-slab multiplier) editable as data, no code change needed
- Service-length slab engine — e.g. a lower rate for the first 5 years and a higher rate beyond, with unlimited configurable tiers
- Resignation vs. termination rule sets that automatically apply the correct reduction factor (e.g. 1/3, 2/3, full) based on completed years of service
- Country-law presets shipped as loadable Odoo data for GCC (UAE, KSA, Qatar, Oman, Bahrain, Kuwait), Pakistan and India, each editable after load