Leave in Kuzhu is policy-driven: earned leave accrues monthly, casual and sick leave follow your calendar, carry-forward and encashment run by the rules you set. Employees see their own balance and apply from the app; approvers see the team calendar before they say yes.
Why it exists
Leave management software has one job that matters: when an employee asks "how many leaves do I have?", the answer must be right, instantly, without HR opening a spreadsheet. Kuzhu keeps a running ledger per person per leave type — earned, casual, sick, comp-off, unpaid and anything you define — with every accrual, grant, application and encashment as an entry. The balance is never a guess; it is the sum of its own history.
Policy is where Indian leave gets interesting: accrual monthly or yearly, pro-rated for joiners, carry-forward with caps, encashment at exit, sandwich rules around week-offs and holidays, and different rules for permanent staff, contract workers and interns. All of that is configuration per employment type, not custom development — set it once and the ledger applies it every month.
The workflow is built for the people in it. Employees apply from the phone in two taps and see the balance impact before they submit. Managers approve with the team calendar in view, so granting the fifth overlapping leave in a week is at least a conscious act. HR sees who is out today, what is pending too long, and which balances are about to lapse — before the year-end rush, not during it.
The outcome
“Leave balances nobody disputes, because everybody can see them.”
Feature by feature
Start
01
Any leave type — EL, CL, SL, comp-off, maternity, LOP — with its own accrual rules
02
Carry-forward, lapse and encashment computed at year end, not argued about
03
Holiday calendars per state and branch
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Earned, casual, sick, comp-off, maternity, unpaid — each with accrual, carry-forward, encashment and applicability rules per employment type.
Balances are granted or begin accruing automatically, pro-rated for mid-year joiners. Opening balances import from your old system.
Employees pick dates, see the balance impact and conflicts with holidays instantly, and submit from the app or the web.
Managers see the team calendar beside the request. Approvals route by your chain — manager, then HR, or whatever the policy says.
Approved unpaid leave becomes LOP in the same month’s payroll automatically. Encashments at exit compute from the ledger, not from memory.
Worth a closer look
Buyer questions
2 answers
The answer
Most systems store leave balance as a number and mutate it, which is why balances drift and nobody trusts them. Kuzhu stores transactions — accrual, application, approval, cancellation, lapse, encashment — and derives the balance. Any employee’s number can be explained line by line for any date in the past, which ends the annual argument with interest.
The answer
Branch-wise holiday calendars mean Diwali in Udaipur and Pongal in Chennai both do the right thing. Sandwich rules — whether the Sunday between two leave days counts — are policy switches, applied consistently instead of re-litigated per request. Restricted holidays work as an entitlement with its own little ledger.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Terms used here
Leave balance
Leave balance is the number of days of each leave type an employee has available, after accruals, usage, carry-forward and lapses.
Earned leaveEL / Privilege leave
Earned leave, also called privilege leave, is paid leave that accrues with service, can be carried forward within limits, and is encashable at exit.
Casual leaveCL
Casual leave is short-notice paid leave for personal matters, usually 7 to 12 days a year, credited annually or monthly and not carried forward.
Sick leaveSL
Sick leave is paid leave for illness, usually 7 to 12 days a year, with a medical certificate required beyond two or three consecutive days.
Compensatory offComp-off
Compensatory off is paid leave granted in place of working on a holiday or week-off, usually to be used within a fixed window.
Maternity leave
Maternity leave in India is 26 weeks of paid leave for the first two children (12 weeks thereafter) under the Maternity Benefit Act, for women with 80 days of service in the past year.
Paternity leave
Paternity leave is leave for new fathers; there is no central law for private employers in India, so it is a company policy, commonly 5 to 15 days.
Holiday calendar
A holiday calendar is the list of paid public holidays for the year, which in India differs by state and often by branch, including national and optional (restricted) holidays.
Yes — policies attach to employment types. Permanent staff, contract workers, interns and consultants each accrue and carry forward by their own rules.
By policy: carry forward up to a cap, lapse the rest, or convert to encashment. It runs automatically at the year boundary you configure.
Yes — their own branch’s calendar, in the app, alongside the team’s approved leaves, so planning happens before applying.
The full-and-final settlement reads the ledger: eligible balance is encashed at the configured rate, and the calculation is shown, not asserted.
Works best beside
Other people modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us