Leave is the most-touched part of HR and the easiest to get wrong. One mis-posted sick leave becomes a wrong loss-of-pay figure. That becomes a wrong net salary. That becomes a payroll correction next cycle. The error does not stay in the leave register. It lands in payroll.
Which leave types do you actually owe?
The Employees State Insurance Act dates from 1948 and the Provident Funds Act from 1952, but leave itself is state law. Statutory leave in India is set by the Shops and Establishments Act of each state, not by one central rule. A firm with branches in 3 states can owe 3 different earned-leave entitlements. Treating them as one policy is where most gaps start. The Ministry of Labour and Employment holds the central framework these sit inside.
- Earned or privilege leave. Accrues against days worked. Carries forward, up to a cap.
- Casual leave. Short notice. Usually does not carry forward.
- Sick leave. Often needs a certificate past a threshold you set.
- Maternity leave. 26 weeks for the first two children under the Maternity Benefit (Amendment) Act, 2017.
- Paternity leave. No statutory right in the private sector. Whatever you give is policy, so write it down.
- Compensatory off. Against work on a national or festival holiday.
- Loss of pay. The fallback when the balance runs out, and the one that moves salary.
How does ESI change your sick leave policy?
ESI covers employees earning up to 21,000 per month, so in most firms it applies to part of the workforce and not all of it. For covered staff, sick leave is not only your policy. It is a cash benefit. The Employees State Insurance Corporation says "ESIC provides 70% of average daily wages in cash during medical leave, upto 91 days in two consecutive benefit periods."
That matters for two reasons. Your own sick-leave rule sits on top of a statutory benefit, so the two have to be read together. And the certificate rules that trigger the benefit are not the same as the ones in your handbook. Decide which applies first, and say so in the policy.
ESIC also says "ESIC provides 100% of average daily wages in cash up to 26 weeks in confinement and 6 week in case of miscarriage, during maternity leave and 12 weeks for commissioning mother and adopting mother." Where an employee is covered, check the route before you compute the payment.
What is the accrual rule, exactly?
Most leave disputes are accrual disputes. Decide and write down 4 things. Whether leave accrues monthly or yearly. Whether it starts on joining or after probation. How a mid-month joiner is pro-rated. What happens to the balance at year end.
Write the answers as rules a system can apply the same way every month. If two people in HR would compute a joiner's opening balance differently, the policy is not finished.
What should the carry-forward and encashment caps be?
The PF statutory wage ceiling of 15,000 per month and the 2017 maternity amendment are both fixed points you design around. Your leave caps are not. An uncapped balance is a growing liability on your books. Cap what carries forward. State what lapses. State what is encashable and when.
Encashment also has a tax consequence payroll must handle. Leave encashed during service is taxable as salary, and sits alongside the 12% employee PF deduction already coming off the same payslip. Encashment at retirement or resignation is treated differently. If your leave system cannot tell payroll which is which, someone works it out by hand, and that is a defect waiting to happen.
Which records settle a dispute?
A balance tells you how much leave is left. It does not tell you who approved what, when, and on what grounds. The trail is what you need when someone disputes a loss-of-pay cut, or when an inspector asks.
Hold 8 fields per request: employee, leave type, applied date, from and to dates, half-day flag, approver, approval timestamp, and the reason or certificate reference. Those 8 settle almost every dispute without rebuilding a conversation from memory.
Why connect leave to attendance and payroll?
Because they are the same data seen 3 ways. In separate files the reconciliation is manual, monthly, and fails quietly. An approved leave that never reached payroll shows as absence, and the employee loses a day of pay.
One record removes the step rather than speeding it up. 247HRM leave management shares the employee record with attendance and payroll, so an approved leave reaches the run without anyone exporting anything.
Which errors actually happen?
| Error | How it shows up | What prevents it |
|---|---|---|
| Approved leave never reaches payroll | Marked absent, loses a day of pay | One shared record, not an export |
| Balance goes negative unnoticed | Leave granted that was never available | Hard validation at approval |
| Mid-month joiner gets a full-year balance | Over-granted leave, found at year end | Pro-rata rule on joining date |
| Holiday list differs by location | Comp-off wrongly granted or refused | Location-specific holiday calendars |
None are complex. All 4 are common, and all 4 surface as payroll corrections rather than leave problems, which is why they get fixed in the wrong place.
What should you audit each quarter?
Pull 3 reports. Negative balances. Balances above the carry-forward cap. Staff with no leave taken all year.
ESI contributions run at 3.25% from the employer and 0.75% from the employee, so a staff member wrongly shown as absent distorts both the wage base and the filing. Each points somewhere different. Negative balances mean approval validation is not enforcing. Balances above the cap mean the year-end rule did not run. Zero leave taken is a burnout and liability signal, and often means someone worked through leave they will later ask to encash. PF records for the same staff sit with the Employees Provident Fund Organisation, and the two should agree on who was on the rolls.
Who should see what?
In a firm of 1,200 staff across 3 states, that is 1,200 balances moving every month against 3 different rule sets. Employees see their own balance and history. Managers see team balances and pending approvals, not medical details. HR sees everything and holds the certificates. Finance needs the encashment liability, not the reasons.
Role-based access rather than shared spreadsheets is what keeps sick-leave reasons from circulating. That is a privacy matter and a trust one.