Leave is where HR software adoption is won or lost, and it happens faster than most buyers expect.
An employee opens the app, sees a casual leave balance that does not match what they believe they have, and tells four colleagues the new system is wrong. Whether it is actually wrong barely matters at that point. Within a week, half the team has gone back to messaging HR directly, and the leave module is a parallel record that nobody trusts.
The balance was probably right. The configuration behind it was probably incomplete. This post covers what a leave management system must model for an Indian company, and what to check before you commit to one.
The Three Jobs a Leave Management System Has
Strip away the interface, and only three remain.
- EntitleDecide how much of each leave type a given employee has, at any date, including people who joined in March and people leaving in November.
- ApproveRoute a request to the right person, enforce the rules, and record the decision.
- AccountProduce a balance that survives a year-end close, a full-and-final settlement, and an employee who disagrees.
Every system on your shortlist does the second job adequately. Approval workflows are not where products differ. The first and third are where they do, and both are decided entirely by how much policy detail the system can actually hold.
Where Indian Leave Policy Gets Complicated
Multiple leave types, each with different rules
A typical Indian SME runs at least four: earned (privilege) leave, casual leave, sick leave, and loss of pay. Many add comp-off, work-from-home as a tracked category, maternity and paternity leave, and bereavement.
These are not four instances of the same thing. Earned leave usually accrues monthly and carries forward. Casual leave is often granted annually and lapses. Sick leave may require documentation beyond a certain threshold. Loss of pay isn't a balance; it is what happens when a balance runs out, and it must flow to payroll as a deduction.
A leave management software that models one generic type with a number attached will force you to run at least one of these outside it.
Accrual timing and pro-rata
This is where most configuration errors originate. Does earned leave credit monthly, quarterly, or annually? On the first of the period or the last day? Does an employee who joins on the 20th get that month's credit, a proportion of it, or nothing?
Then the same question at the other end. Someone resigning in August has accrued eight months of entitlement against an annual grant they may have already partly consumed. Whether the system handles that automatically or leaves it to a manual calculation in the settlement sheet is worth asking directly, because it is the single most common source of exit disputes.
Carry-forward, lapse, and encashment
Three linked rules that most companies define loosely and most systems require precisely.
How much earned leave carries into the next year. What the ceiling is on accumulated balance. Whether the excess lapses or is encashed. Whether encashment is automatic at year-end or on request. Whether the encashment rate is basic or gross.
If your policy document does not answer all six, the system will force you to answer them during setup, which is not a bad outcome but is one to budget time for.
Sandwich rules and the interaction with holidays
Leave taken on a Friday and a Monday, with the weekend in between. Does that count as two days or four? Practice varies widely across Indian companies, and both answers are defensible.
The same question applies to a public holiday falling inside a leave block, and to a half-day adjacent to a weekly off. These rules are easy to state and hard to configure, and they are exactly the cases where a system either applies your policy automatically or produces a number your HR lead has to override manually every month.
Comp-off with an expiry
Comp-off is earned for work on a weekly off or holiday, and most policies expire it if unused within a defined window. That means it is not a static balance; it is a set of dated credits, each with its own lifespan, some part-consumed.
Systems that treat comp-off as a single number cannot express this. If comp-off matters in your operation, ask to see it demonstrated with a credit earned in one month and partly consumed two months later.
Different policies for different groups
Confirmed employees and probationers. Head office and the plant. Grade-based entitlements. Contractors on a different structure entirely.
One leave policy across the whole company is the exception, not the rule, past about eighty people. Check that the leave management system supports policies assigned by department, location, or employment type, and check what happens when someone transfers between them mid-year.
The Balance Test
Before you sign, ask the vendor to configure your actual leave policy in a trial and then produce three numbers: the current balance for an employee who joined in the middle of last year, the settlement figure for someone exiting next month, and a comp-off balance with one part-consumed credit. If all three match what your HR lead calculates by hand, the system can hold your policy. If the vendor needs to "check with the product team" on any of them, you have learned something more useful than a feature list would have told you.
The Statutory Floor
Company policy sits on top of a statutory minimum, and that minimum is not uniform.
Your state's Shops and Establishments Act, or the Factories Act if you are a registered factory, sets earned leave entitlement, eligibility conditions, and encashment rules, and they differ meaningfully between states. Maternity benefit is governed centrally under the Maternity Benefit Act, with entitlement varying by number of children and additional obligations attaching above certain headcount thresholds.
Two practical points for software selection. First, a leave management system should let you configure it to your state's rules rather than assuming a single national default, which matters immediately if you have employees in more than one state. Second, leave records are part of what you must maintain and produce on inspection, so retention and export for exited employees are not optional.
Verify the specific entitlements against your registration and state rules rather than using a general figure, and have the policy checked before it is configured rather than after.
What to Check Before You Buy
- Configuration depth versus configuration effortA system that can express every rule above but requires a consultant for each change is a different proposition from one your HR lead can adjust. Ask who makes a policy change six months in, and how long it takes.
- Mid-year policy changesYou will change something. Ask what happens to balances already accrued under the old rule when a new one is applied. A system that recalculates history retroactively and a system that applies changes forward produce very different numbers, and only one of them will match what you told employees.
- The payroll handoffLoss of pay days, encashment amounts, and leave-without-pay adjustments have to reach payroll in a usable format by a fixed date every month. Ask to see that export.
- Employee-side visibilityThe balance an employee sees has to be the balance the system uses, visible without asking HR. This largely determines whether people trust the system, and it is the cheapest problem to solve.
- The audit trailWho applied, who approved, when, and what the balance was before and after. Without it, any disagreement becomes one person's recollection against another's.
The Migration Nobody Plans For
Opening balances are the hardest part of a leave rollout and the part that gets two hours in a project plan.
You are importing a balance per employee per leave type, as of a specific cutover date, from a spreadsheet maintained by hand that almost certainly contains errors. Those errors become the new system's errors, and the software gets blamed.
Two things reduce the damage. Reconcile before importing rather than after, ideally by circulating each employee's balance for confirmation before go-live. And pick a cutover at the start of a leave year rather than mid-cycle, which removes most pro-rata complexity from the migration.
This is the same internal-time cost that shows up in every HR software rollout, and it belongs in your evaluation alongside what HR software should actually cost.
How Squad HR Handles Leave
Squad HR's leave management system lets you configure policies against your own rules — leave types, entitlements, approval chains, and holiday calendars — and assign different policies by department or location rather than forcing one structure across the company. Employees can view their balances and history without raising a request, and leave data exports to Excel, CSV, or PDF for payroll and compliance. Setup for most small teams runs inside 48 hours, and the Leave Management page has the details. If comp-off expiry or sandwich rules are central to your policy, run them through a trial before committing rather than taking the feature list on trust — that advice applies to us as much as to anyone else on your list.
Questions Worth Asking Every Vendor:
- Configure my actual policy in the trial. How long did that take, and who did it?
- How does earned leave accrue for a mid-month joiner, and what does a mid-year exit settlement produce?
- Can carry-forward, lapse, and encashment rules be set independently, and what are the ceilings?
- Is comp-off tracked as dated credits with expiry, or as a single balance?
- What happens to existing balances when a policy changes mid-year?
- What does the monthly loss-of-pay export to payroll look like?
A leave management system is not really a software purchase. It is a forced exercise in writing your leave policy down precisely, which most companies have never done. The system is what enforces it afterwards. Choosing one that can hold the policy you actually run, rather than the simplified version that fits the software, is most of the decision.