Leave management

Leave Management Software: Policy, Balances and Approvals

Leave management software holds each employee's entitlement, applies your policy to a request, routes it through the right approvers and keeps the balance correct afterwards. It covers leave types, accrual schedules, carry-forward caps, holiday calendars and encashment rules. The point is arithmetic you can defend: a balance every employee, manager and auditor agrees with, without a spreadsheet.

Free 1-user plan · No credit card · Talk to a real recruiter

What does leave management software do?

It holds entitlement, applies your policy to a request, routes it for approval and keeps the balance correct afterwards. That last part is the whole job. Balances are the number employees argue about, auditors sample and finance provisions against, so a product that gets requests right but balances wrong has failed at the only thing it existed for. Underneath sit four things: the types you offer, the entitlement each grade or location receives, the accrual schedule that credits days, and the rules deciding what happens to anything unused. Approvals, calendars and notifications are the visible surface; the arithmetic is the product. Most teams arrive here from a spreadsheet that worked until the second location, the first mid-year joiner, or the first resignation with a disputed closing figure. The HRMS view shows how this connects to attendance, payroll and the employee record.

How should you define leave types and entitlement?

Keep the list short and make every definition explicit before anyone configures anything. Most Indian employers run some combination of earned or privilege leave, casual leave, sick leave, unpaid absence, maternity and paternity provisions, bereavement, and compensatory off earned against extra work. Each type needs its own answers: who is eligible, from what date, whether probation counts, the smallest unit that can be booked, whether documentation is required, and whether it may go below zero. Then decide what varies by grade, by location and by tenure, because that variation is precisely where spreadsheets stop coping. Write the rule for someone joining mid-year before you write anything else, since that single case drives half of your later questions. Minimum entitlements and their conditions differ across state legislation and establishment type and they do change, so have your finance team or a compliance advisor confirm the current position wherever you employ people.

Want this priced against your own hiring volume?

Free forever for 1 user · no credit card

How does accrual work, and when should balances be credited?

Accrual is the schedule that turns a policy into days somebody can actually book. The two common shapes are front-loaded, where the full annual quota appears at the start of the leave year, and earned, where days credit monthly or per completed period of service. Front-loading is simpler to explain and exposes you when someone resigns in month two having taken the year. Earned accrual is safer for the employer and generates more questions at the counter. Whichever you pick, settle four details: the credit date, rounding of part days, whether probation accrues, and how a mid-year joiner or leaver is prorated. Then handle migration honestly, because opening figures carried across from a spreadsheet are the most common source of disputes in the first quarter after go-live. Reconcile them against payroll records before switching anything on.

What happens to unused leave: carry-forward, lapse and encashment?

Three decisions, and they interact. Carry-forward sets how much unused balance survives into the next leave year, usually with a cap. Lapse sets the date anything above that cap disappears, and whether employees are warned before it does. Encashment is the option to convert balance into money instead of time, normally bounded by type, eligibility and a maximum. Finance cares about all three, because unused balance sitting on the books is a liability somebody has to provision for, and an uncapped figure grows quietly for years. Employees care because the rules decide whether a planned holiday or a payout is possible at all. Publish the cap, the date and the eligibility in the same screen where people apply. Tax treatment of encashment and any statutory floor on carry-forward vary, so check your current position with your finance team before promising anyone anything.

How should approval chains and holiday calendars work across locations?

Route by reporting line rather than by department name, and decide in advance what happens when the approver is themselves away on leave. Delegation, an automatic second approver, or an HR override are the three usual answers, and choosing none of them is how requests sit unanswered for a week. Add a second level of approval only where it genuinely changes a decision, such as long absences, sabbaticals or unpaid periods. Calendars need the same care: a company with offices in different states will not share one holiday list, and the mismatch surfaces as people applying for a day that is already a holiday where they sit. Support several calendars, assign each person to exactly one, and handle optional or restricted days where employees choose a limited number themselves. Push the calendar, the balance and pending requests into an employee self-service portal so HR stops relaying answers.

What should you test during a leave software demo?

Do not watch a clean request get approved. Bring the cases that break products. Ask the vendor to configure someone joining on the sixteenth of a month and take the prorated entitlement to a decimal. Ask what happens when a request spans a weekend and a public holiday, and whether those days are deducted. Apply for more than the balance and see whether it blocks, warns, or quietly goes negative. Cancel an approved request whose dates have already passed. Change the policy mid-year and watch whether it applies backwards. Then inspect the exports: a balance and accrual report your finance team can reconcile, and an unpaid-absence file that payroll software can read without manual editing. Finally ask who can override a balance directly, and whether that override leaves a visible record with a name against it.

Why does the leave year-end turn into a crisis?

Because three deadlines collide. Balances lapse, delivery commitments peak, and everyone who ignored their entitlement all year applies at once. Teams that handle it well do four things. They publish the lapse date early and remind people twice with their individual remaining figure attached, not a generic notice. They stagger approvals so an entire function cannot be away in the same fortnight, using a visible team calendar rather than a first-come rule. They close the encashment window before the rush instead of during it. And they reconcile balances against attendance records well ahead, so disputes surface in a quiet week rather than the last one. The failure mode is silence: nobody knows where they stand until it is too late to use anything, and HR spends the final month arbitrating. Automating that reminder is a small change with a disproportionate effect.

Leave policy decisions, and what each one costs you if it stays vague

Policy decision The question it settles How it is usually left vague What it costs later
Leave year start Which twelve months a quota belongs to Assumed to match the financial year, never written Prorating and carry-forward run on two different clocks
Accrual timing When days become available to book Described as annual, applied monthly by whoever runs it People book days they have not yet earned
Probation treatment Whether new joiners accrue or may apply Handled case by case by the hiring manager Inconsistent offers and a dispute at confirmation
Prorating rule What a mid-year joiner or leaver receives Rounded by hand inside a spreadsheet Final settlements that will not reconcile
Carry-forward cap How much unused balance survives the year Left uncapped because nobody ever set a number A growing liability finance has to provision against
Lapse date When balance above the cap disappears Announced in the final week of the year A rush of requests the business cannot absorb
Encashment eligibility Who may convert balance to money, and how much Decided per request by whoever asks loudest Precedents you cannot refuse the next person
Negative balance Whether anyone may go below zero Allowed silently because the spreadsheet permits it Recovery arguments during exit settlement

Before you move leave off a spreadsheet

  • Publish one document naming every leave type, its eligibility and its smallest bookable unit.
  • Fix the leave year start date in writing and check it matches how you already prorate.
  • Reconcile every opening balance against payroll records before migration, not after.
  • Set a carry-forward cap and a lapse date, then tell people both at the start of the year.
  • Build one holiday calendar per location and assign every employee to exactly one.
  • Name a delegate for each approver so requests never wait on somebody who is away.
  • Show employees their live balance on the same screen where they apply.
  • Send lapse reminders twice, each carrying the individual balance, well before the deadline.

Want to see your own leave policy configured instead of a generic one?

FAQ

Leave management — FAQs

What is a leave management system? +
It is software that stores each employee's entitlement, accepts and routes requests, and maintains the resulting balance. It holds the policy behind those numbers too: which types exist, how days are credited, what carries into the next year and what lapses. The value is not the request form, which any tool can produce, but a balance that employees, managers, finance and auditors all read the same way without anyone rebuilding it by hand.
What is the difference between leave management and PTO tracking? +
They describe the same function with different vocabulary. Paid time off is generally a single pooled allowance that covers holiday and sickness together, a pattern more common in North American companies. Indian employers usually run separate named types with their own eligibility and documentation rules. Any competent tool models both, but check during evaluation that it supports several types with different rules rather than only a single pooled bucket.
How does a leave management system calculate accrual? +
It applies your credit schedule to each employee's eligibility. Front-loaded policies grant the annual quota at the start of the leave year. Earned policies credit a fraction monthly or per completed period of service. On top of that sit prorating for joiners and leavers, whether probation accrues, and how part days round. Ask the vendor to run a mid-month joiner during evaluation and show the resulting figure to a decimal, since that single case exposes most differences.
Can employees see their own leave balance? +
They should, and on the same screen where they apply. Most balance questions reaching an HR inbox exist only because the number lives somewhere the employee cannot reach. Showing the current figure, what is pending approval, what will lapse and when removes a large share of that traffic. It also reduces disputes, because a balance visible all year is much harder to argue about than one revealed at settlement.
What is carry-forward and how should we cap it? +
Carry-forward is the unused balance that survives into the next leave year. Capping it matters because an uncapped balance accumulates for years and becomes a liability finance has to provision against, and a settlement nobody budgeted for when a long-serving employee leaves. Set a maximum, set the date anything above it lapses, and publish both at the start of the year. Any statutory floor on what must be allowed varies, so confirm your position with a compliance advisor.
How does leave connect to payroll? +
Through unpaid absences, encashment and settlement. Unpaid days reduce the payable amount for the month, encashment converts balance into a payment, and closing balances feed the final settlement when somebody leaves. If the two systems are separate, this handoff is a monthly manual step and a recurring source of error. Where they share one employee record it happens automatically. Combining it with HR automation is usually what removes the last spreadsheet from the cycle.
Can we run different leave policies for different locations? +
Yes, and most growing Indian companies need to. Entitlements, holiday lists and applicable conditions differ across states, so a single company-wide policy quietly becomes wrong the moment you open a second office. Look for the ability to assign policies and holiday calendars by location, and to report on them separately. What each location actually requires is a question for your compliance advisor, since the rules differ by state and change over time.
What happens to leave when someone resigns? +
The closing balance has to be calculated to the last working day, prorated against the accrual rule, adjusted for anything taken beyond entitlement, and then either encashed or lapsed according to your policy. This is where vague policies become expensive, because a leaver reads the rule literally and there is no goodwill left to fall back on. Fix the prorating and negative-balance rules in writing long before you need them for a specific person.
How long does it take to move leave off spreadsheets? +
Configuration is usually the quick part; the migration is not. Expect most of the effort to go into agreeing the policy precisely enough to encode, and reconciling opening balances against payroll records. Teams that go live cleanly finish that reconciliation before the switch and start the new system on a fresh leave year where possible. Starting mid-year is workable but means carrying opening figures somebody has to be able to defend later.
Do we need leave software for a team of thirty? +
The trigger is variety rather than headcount. Thirty people in one office, one policy and one holiday list can run on a shared file for a while. Thirty people across two states, three leave types and a mix of tenures cannot, because prorating and carry-forward stop being arithmetic anyone wants to do by hand. Most teams switch after a settlement dispute or a year-end where nobody could agree what a balance actually was.
Pitch N Hire ATS

The applicant tracking system for recruiters and hiring teams

Pitch N Hire is an applicant tracking system. Post roles, screen applicants, run structured interviews, and make offers from a single pipeline — free for 1 user.

  • One pipeline for every role, applicant, and interview stage
  • Structured scorecards so the panel compares candidates on the same criteria
  • Careers page, job posting, and candidate communication in one place

Free for 1 user · No credit card · Talk to a real hiring expert

Built for recruiters & hiring teams

Bring your leave policy and we will configure it live

Walk through accrual, carry-forward and approvals using your own rules, or start free for a single user and try it yourself.

Prefer to talk? Book a demo · Talk to sales · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo