Annual leave derived from the hire date under §38, other leave types configured by you, and a three-step approval chain.
The leave type decides where the balance comes from; the approval chain decides who gets the say.
Set whether it is paid, whether it is statutory, how it accrues, how it carries over and what a request must satisfy — such as minimum notice.
Annual leave comes from the §38 service bands; other types accrue by the method you configured, producing each person's balance.
The employee sees their balance in self-service and submits a request, and can cancel one that has not taken effect.
The department manager approves first, then HR confirms. A manager only sees their own department's queue.
The whole path from leave policy to year-end carry-over.
Paid or unpaid, statutory or not, how it accrues, how it carries over, and what a request must satisfy.
Entitlement derived from hire date and service length, per Article 38 of the Labor Standards Act.
Unused balances roll over at year end according to each type's rules.
Employee submits, department manager approves, HR confirms — three separate rights.
A manager sees their own department's leave spread and pending queue.
Entitled, used and remaining days per employee per leave type.
Article 38 ties entitlement to service: 3 days at six months, 7 at one year, rising to a 30-day cap after ten years. The system derives it from the hire date and increases it when someone crosses a threshold, so HR is not adjusting everybody's allowance by hand each year.
hr.leave.request is an employee submitting; hr.leave.approve is a manager deciding for their own team; hr.leave.manage is HR seeing the whole company and giving final confirmation. They are separate because they are three different acts.
Tell us how you run payroll today, which time clock you use and how many departments you have. We will tell you straight whether it fits.