| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Time Off (hr_holidays)
• Calendar (calendar) • Employees (hr) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3205 |
| Technical Name |
wt_hrms_leave |
| License | OPL-1 |
| Website | https://way4tech.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Time Off (hr_holidays)
• Calendar (calendar) • Employees (hr) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3205 |
| Technical Name |
wt_hrms_leave |
| License | OPL-1 |
| Website | https://way4tech.com |
WT HRMS Leave Management — Policies, Encashment & Comp-Off
Three additions to Odoo's hr_holidays: configurable Leave Policies (carry-forward, encashment, eligibility, attachments), Leave Encashment requests with monetary calculation, and Compensatory-Off requests for weekend/holiday work.
leave management · leave policy · leave carry forward · leave encashment · comp off · compensatory off · leave balance · leave probation rules · medical attachment leave · HR leaves Odoo · Odoo 19 · Odoo 18 · community edition · enterprise alternative · open hrms · HR software · HR automation · way4tech
Live Preview
A real screenshot from a working WT HRMS install on Odoo 19.
The Problem This Solves
Odoo's hr_holidays handles allocations and time-off requests but lacks the policy controls and side-features (encashment, comp-off) every real HR team needs.
No carry-forward / probation rules
Most companies cap how many unused days roll over and exclude probationers from sick/casual leave — vanilla Odoo has nowhere to record either rule.
Encashment is manual
Paying cash for unused leave at year-end or exit means a spreadsheet, an email approval, and no audit trail in Odoo.
Comp-off is invisible
When employees work a holiday or weekend, "I'll take Friday off in lieu" lives in chat and gets forgotten or disputed.
The Solution — Three Models, Plug Into Standard Leaves
All three models reuse the WT HRMS approval mixin so encashment and comp-off requests flow through the same configurable approval chain as the rest of your HRMS.
- ✓ Leave Policy model linked to any
hr.leave.type - ✓ Annual allocation default + max carry-forward cap (0 = no rollover)
- ✓ Encashment toggle with optional fixed rate per day (0 = use daily wage)
- ✓ Min service months — new joiners can't claim until they've been with the company long enough
- ✓ Max consecutive days — cap a single request (e.g. casual ⤠3 days)
- ✓ Attachment required with after-N-days threshold (e.g. medical certificate after 3 days sick)
- ✓ Probation eligibility flag — choose which leave types probationers can take
- ✓ Leave Encashment requests — monetary, currency-aware, auto-totalled (days à rate)
- ✓ Sequenced encashments —
ENC/YYYY/0001 - ✓ Compensatory Off requests with worked-date and comp-off-date fields
- ✓ Submit / Approve / Reject on encashments & comp-offs — HR Manager group gated
- ✓ Multi-step approval chain via
wt.hrms.approval.mixin - ✓ Native leave menus reorganised under WT HRMS → Leaves with Requests, Allocations, Encashments, Comp-Off
- ✓ mail.thread chatter on every encashment & comp-off
- ✓ Multi-company aware
Step-by-Step User Guide
Install the module
Install WT HRMS Leave Management from Apps. Odoo's hr_holidays and wt_hrms_core are pulled automatically.
Define leave policies
Open WT HRMS → Configuration → Leave Policies. Create one policy per leave type (Annual, Sick, Casual, Maternity, â¦): set annual days, max carry-forward, min service months, max consecutive days, attachment threshold and probation eligibility.
Use Odoo's native leave requests
Employees keep using WT HRMS → Leaves → Leave Requests (the standard hr_holidays action). Allocations are managed under Leaves → Allocations.
Raise an encashment request
Go to WT HRMS → Leaves → Encashments, click New. Pick employee, leave type, days to encash and a per-day rate — total amount auto-computes. Click Submit to send through the approval chain.
Log a comp-off
Open WT HRMS → Leaves → Comp-Off Requests. Record the date worked (holiday/weekend), the date the employee plans to take in lieu, and a reason. Submit → HR Manager Approve / Reject.
Audit through chatter
Every encashment and comp-off has full mail.thread chatter and a sequenced reference, so HR can reconstruct exactly who approved what and when.
Marquee Features
Leave Policies
One policy per leave type, with annual allocation, carry-forward cap, eligibility and attachment rules in a single screen.
Carry Forward Cap
Configurable max days that roll over to next year — set 0 to disable rollover entirely for that leave type.
Encashment Engine
Days à rate auto-totals on the encashment request. Currency tracked per record, with chatter audit + sequenced reference.
Service Eligibility
Min-service-months gate so brand-new joiners can't claim certain leave types.
Max Consecutive Days
Cap how many days a single leave request can span (e.g. casual ⤠3, sick ⤠7) on a per-policy basis.
Attachment Threshold
"Require medical certificate when leave exceeds N days" — one toggle plus one number.
Probation Rules
Tag each policy as probation-eligible (e.g. emergency leave) or not (e.g. annual). Crystal-clear for HR ops.
Comp-Off Tracking
Worked-date and planned comp-off-date, plus reason and approval — finally a real record of "I worked Saturday."
WT HRMS Approval Chain
Both encashment and comp-off use the same multi-level approval engine as Loans, Advances and Lifecycle.
Compatibility & Requirements
| Odoo Edition | Community & Enterprise |
| Odoo Version | 19.0 |
| Module Dependencies | hr_holidays (Odoo core) · wt_hrms_core |
| Python Packages | None |
| External Services | None |
| Security Groups Used | base.group_user (request own), hr.group_hr_user, hr.group_hr_manager (approve, configure) |
About Waqas Riasat & Way4Tech
We build Odoo modules that fix real business pain — not nice-to-have features. The WT HRMS suite is a Community-only HR + Payroll replacement that we use ourselves and ship with hand-tested upgrade paths.
way4tech.com · info@way4tech.com · WhatsApp +92 315 411 4748
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module