Leave Management in India: Policies, Compliance and Getting the Balances Right

Leave management is the process everyone assumes is trivial until year-end, when it turns out half the company's balances are wrong, someone was allowed to carry forward more than policy permits, and a resigned employee's encashment cannot be calculated because nobody is sure how much earned leave they actually accrued. The mechanics are simple in isolation; it is the accumulation of rules over a year, across leave types and locations, that quietly breaks.

It is also, more than most HR functions realise, a compliance obligation. In India, leave is not purely a matter of company policy — earned leave, its accrual, the limits on carry-forward and the right to encashment are governed by the Shops and Establishments Act of each state and, for factories, by the Factories Act. A leave policy that ignores these is not just generous or stingy; it can be non-compliant.

The leave types you actually have to manage

Most Indian organisations run some combination of a few standard leave types, and the rules differ meaningfully between them. Treating them all the same is the first mistake.

• Earned Leave (EL) / Privilege Leave (PL): accrues with service, usually carries forward, and is typically encashable — the type most tied to statutory rules.
• Casual Leave (CL): for short, unplanned absences; usually cannot be carried forward and lapses at year-end.
• Sick Leave (SL): for illness, sometimes requiring a medical certificate beyond a threshold of days.
• Statutory and special leave: maternity leave under the Maternity Benefit Act, plus paternity, bereavement or marriage leave where the company offers them.

Each type needs its own accrual rule, its own carry-forward behaviour and its own approval expectations. Casual leave that lapses and earned leave that accumulates cannot share a single rule, and the moment a company tries to run them from one spreadsheet column, the year-end reconciliation becomes guesswork.

Accrual and carry-forward: the rules that break spreadsheets

Accrual is where leave quietly goes wrong. Earned leave typically accrues monthly or per days-worked, which means a mid-year joiner, someone on long unpaid leave, and a full-year employee all accrue different amounts — and computing that by hand for a few hundred people, every month, is exactly the kind of task that gets approximated. Approximations compound into wrong balances.

Carry-forward adds a second layer. Most policies cap how much earned leave can roll into the next year, and anything above the cap either lapses or must be encashed. If that cap is not enforced automatically at year-end, some employees carry forward more than policy allows and the company has quietly created a liability it did not intend. Encoding accrual rate, maximum balance and carry-forward cap once — and letting the system apply them — is the only reliable way to keep balances correct.

State rules and holiday calendars are not company-wide

A business operating in Maharashtra, Karnataka and Tamil Nadu is subject to three different Shops and Establishments Acts, which can differ on earned-leave accrual rates, carry-forward limits and encashment. The same policy cannot be assumed to be compliant in all three simply because it was approved at head office.

Holiday calendars are the more visible version of the same problem. National holidays are shared, but a large share of Indian public holidays are state-specific — and a few are location or festival specific. If everyone is mapped to one company-wide holiday list, employees in a state with a regional holiday are marked absent when they are not, and their leave balances are wrong. Holiday calendars have to be defined per state or location and mapped to employees by where they actually work.

Approval workflows that route themselves

A leave request needs to reach the right approver, respect the reporting line, and in many organisations pass through more than one level for longer durations. When this runs over email, requests get lost, managers approve leave they have no visibility of clashing with, and HR becomes a chaser. A proper workflow routes each request to the employee's actual reporting manager, escalates or adds a second approver where the policy requires it, and shows the approver the team's calendar so two people are not both off during a critical week.

• Requests route by the reporting line held in the employee master — no per-employee configuration.
• Multi-level approval kicks in automatically for longer durations where policy demands it.
• Approvers see team availability, so clashes are caught before approval, not after.
• The whole trail is logged, so 'I never got the request' stops being a valid excuse.

Leave is meaningless if it doesn't reach attendance and payroll

The single most common failure in leave management is that leave lives in its own island. An approved leave has to do two things automatically: mark the attendance record so the day is not counted as absent, and inform payroll so that paid leave is paid and loss-of-pay leave is deducted correctly. When leave, attendance and payroll are separate systems, someone re-keys the approved leave into the muster and again into the pay run — and every re-keying is where a paid day becomes an unpaid one, or the reverse.

Connected, it just works: an approved leave adjusts the attendance record and flows into the pay run as either paid or loss-of-pay according to the leave type, with nothing typed twice. Encashment at exit reads the accrued earned-leave balance directly, so full-and-final settlement is calculated rather than reconstructed.

Leave management rewards getting the rules right once and then getting out of the way. The organisations that struggle are the ones re-deciding the rules every month in a spreadsheet; the ones that don't have encoded accrual, caps, calendars and approvals into a system that applies them the same way every time — which is the only way balances stay correct across a full year and a multi-state workforce.