Leave Carry Forward Policy: Year-End Guide for India

Every year, somewhere between October and March, the same email lands in the HR inbox: "How many leaves will I lose on 31st?" A clear leave carry forward policy is the only thing that stops that email from turning into a month of escalations, manual corrections and payroll disputes. If your rules on what rolls over, what lapses and what gets paid out are vague, the year-end close becomes a negotiation rather than a process.

This guide is written for Indian HR and payroll teams preparing for the 2026-27 year-end. It focuses on the operational side of the close: the decisions you need to take, the dates you need to fix, the way you tell employees, how you configure your HR system, and how you reconcile the numbers afterwards. We deliberately do not re-explain how to design a leave policy from scratch, and we do not go into the tax treatment of leave encashment. Those topics deserve their own treatment, and we link to them conceptually where they matter. Here, the question is narrower and more urgent: your leave balances are about to be frozen, so what do you do with them?

A note on scope before we start. Leave entitlements in India are shaped by a mix of the applicable state Shops and Establishments Act, the Factories Act for factory workers, the labour codes as they are brought into force and notified, your own appointment letters, and your company policy. These vary by state, by sector and by employee category. Everything below is general operating guidance, not legal advice. Please verify the specifics for your establishment with your legal counsel or labour consultant before you finalise a decision.

Why year-end leave management deserves its own project

Most HR teams treat leave as a daily transactional workflow: apply, approve, deduct. The year-end is different because it is the one moment when balances stop being a running number and become a decision. Every unused day is either carried, lapsed or paid. Each choice has a cost, a communication burden and an audit trail.

Here is what typically goes wrong when the year-end is left to chance:

• Surprise lapses. Employees discover on 1st January or 1st April that days they were counting on have vanished. Trust takes a hit even when the policy was technically followed.
• Last-minute leave rush. If the cut-off is not communicated early, a wave of applications arrives in the final fortnight, often in teams that cannot absorb it.
• Inconsistent treatment. One manager quietly allows a late application, another refuses. Inconsistency is the fastest route to a grievance.
• Payroll errors. Encashment amounts, carried balances and opening balances in the new year do not match, and nobody can explain why.
• Liability surprises. Finance learns about the accrued leave liability only after the books have closed.

A short, planned year-end project with a named owner, a calendar and a reconciliation step fixes almost all of this. The rest of this article is that project.

Calendar year versus financial year leave cycles

The first thing to settle is which cycle your leave year follows. In India, both are common, and some organisations run a mix without realising it.

The two common cycles

A calendar year cycle runs from 1st January to 31st December. It is popular with multinational subsidiaries, product companies and teams whose HR policies are inherited from a global parent. It aligns neatly with how employees think about their year.

A financial year cycle runs from 1st April to 31st March. It is popular with Indian companies, manufacturing units and organisations whose finance team drives the HR calendar. It aligns with the books, the budget, the appraisal cycle and payroll tax processing.

Some companies also use a joining-anniversary cycle, where each employee's leave year runs from their date of joining. This is fair but operationally heavy, because there is no single cut-off date and the close happens every month for a different group of people.

Comparing the cycles

What "2026-27 year-end" means for you

Because the target here is the 2026-27 year-end, it helps to pin down what that means in practice:

• If you run a financial year cycle, your close falls on 31st March 2027, and the new leave year starts on 1st April 2027.
• If you run a calendar year cycle, your close for the current year falls on 31st December 2026, and the new year starts 1st January 2027. Your 2026-27 planning window is therefore already open.
• If you run an anniversary cycle, you are effectively closing leave every month and the exercises below apply to each monthly batch.

Today is early October, so calendar-year employers are about eleven weeks from their cut-off. That is exactly the right time to begin. Financial-year employers have a longer runway, but the work is the same, and starting early costs nothing.

Should you switch cycles?

Occasionally an organisation asks whether to move from one cycle to another, for example from a calendar year to a financial year after being acquired by an Indian group. A switch is possible, but it needs care:

1. Decide the transition period. Often this is a short "stub" year. A company moving from a calendar year to a financial year may run a nine-month stub from January to March, with entitlements prorated.
2. Prorate entitlements honestly. If employees normally get 18 days of earned leave per year, a nine-month stub gives 13.5 days. Rounding rules should be written down.
3. Protect existing balances. Do not use the transition to quietly reduce balances. If the carry-forward limit changes, say so explicitly.
4. Put it in writing. A policy amendment, communicated in advance and acknowledged by employees, is far safer than an informal announcement.
5. Check statutory requirements. Some state laws define leave in terms of a calendar year or in terms of days worked in a year. Verify before you change.

If you do not have a strong reason to switch, do not switch in the same year you are trying to tidy up the close. One change at a time.

Mixed cycles are a hidden problem

We often see organisations where the policy says "financial year" but the HR system was configured on a calendar year, or where one entity of a group follows one cycle and another follows a different one. Employees on transfer between entities then carry two sets of rules. Before you do anything else, confirm that your written policy, your system configuration and your payroll calendar all describe the same cycle for each entity. If they do not, fixing that comes first.

The three fates of an unused leave balance

At the close, every unused day of every leave type ends up in one of three places. Understanding them as separate decisions, not one blurry "year-end treatment", helps you configure each leave type deliberately.

Carry forward

The balance rolls into the new year and sits alongside the fresh entitlement. Carry forward can be unlimited, capped at a number of days, capped as a percentage of entitlement, or subject to a total ceiling on accumulated balance.

Lapse

The balance expires at the cut-off and is removed. Nothing is paid and nothing rolls over. Lapse is the normal treatment for casual leave, many sick leave schemes, and "use it or lose it" benefits such as a limited number of wellness days.

Encash

The balance, or part of it, is converted into a payout, typically through payroll. Encashment can be mandatory at year-end (any balance above a cap is paid out), optional (the employee chooses), or reserved for exit only.

A good leave carry forward policy specifies, for each leave type, which of these three applies, in what proportion, and under what conditions. If you find yourself writing "at the discretion of management" in more than one place, that is a sign the policy needs another pass before the year-end, not during it.

Choosing the right treatment for each leave type

Different leave types serve different purposes, and the year-end treatment should reflect that purpose. The table below shows common patterns seen in Indian workplaces. It is illustrative; your own policy, contract terms and applicable state law decide what is right for you.

Two points are worth flagging. First, compensatory offs often follow their own clock. If your policy says a comp-off must be taken within 60 days, a comp-off earned on 20th December expires on its own date, regardless of 31st December. Make sure your system applies that expiry and not a blanket year-end rule. Second, event-based leaves rarely have a "balance" to manage at all, so leave them out of your year-end project unless your system shows them as a balance.

The earned leave question

Earned leave, also called privilege leave in many policies, is where most of the year-end decisions concentrate. The entitlement is usually larger, it accumulates over time, and it has the most direct cost implication. Several questions arise:

• Is there a cap on accumulation? Many policies set an overall ceiling, for example a total balance of 45 or 60 days. Anything above that is lapsed or encashed.
• Is there a minimum utilisation expected? Some employers require a minimum number of days to be availed each year for rest and well-being, treating it as a condition for carry forward.
• Does the statute you fall under set a floor? Certain state laws and the factory regime include provisions about accumulation and encashment for covered employees. If you employ workers in covered categories, verify what protections apply and make sure your policy does not fall below them.
• How does it interact with notice period and exit? Balances at exit are handled differently from year-end balances; keep the two treatments consistent but separate.

Year-end decision framework: carry, lapse or pay?

When leadership asks "what should we do with the unused leave?", you want a short framework instead of an opinion contest. Here is one that works across most organisations.

Step 1: Know your liability

Pull a year-to-date report of all unused balances, by leave type, department and salary band. Convert earned leave balances into a rupee liability using the basis your policy specifies (for example basic salary only, or basic plus dearness allowance), divided by the number of days your policy uses for the daily rate.

Step 2: Understand why balances are high

A large balance is a symptom. Common causes:

• Heavy workloads that make leave hard to take.
• Managers who discourage or delay approvals.
• Employees who are saving for encashment.
• A policy that accrues more than anyone can reasonably use.
• Seasonal businesses where leave is simply impractical for part of the year.

The cause changes the right response. If employees cannot take leave because of workload, a harsher lapse rule punishes them for a management problem.

Step 3: Choose the treatment per leave type

Use the table above as your starting point, then adjust. If you want employees to rest, prefer a modest carry forward cap and a clear lapse. If you want to reward retention and reduce liability, consider a defined encashment window. If cash is tight, prefer lapse and carry forward and defer encashment to exit.

Step 4: Test the cost

Run the numbers before announcing anything. The worked example below shows how.

Step 5: Decide, document, announce

Write the decision down, get the sign-off of the right approver (typically HR head plus finance), and announce it within a defined timeline. The announcement is covered in its own section later.

Worked example 1: carry forward with a cap

Let us take a fictional company, Brightline Components, which runs a financial year cycle and has these rules for earned leave:

• Annual entitlement: 18 days, credited at 1.5 days per month.
• Carry forward cap: 30 days into the next year.
• Any balance above 30 days lapses unless the employee is in an approved critical project (discussed separately).

Consider three employees at the close on 31st March 2027. The numbers are invented for illustration.

Meera's balance sits comfortably under the cap and rolls forward in full. Sanjay loses 4 days. Farid loses 16 days, which is nearly a full month of leave. That outcome is technically correct under the policy, but it is exactly the kind of situation that produces anger, and potentially attrition of a valued employee.

Here is how an HR team might respond without abandoning the cap:

1. Early warning. Send Farid and Sanjay an individual notice in January showing their projected lapse, with enough time to plan leave.
2. Manager nudge. Give managers a list of team members projected to lose more than 5 days and ask them to schedule leave.
3. Cap review. If many employees are in Farid's position, the issue is systemic. Consider whether the cap or the workload needs to change next year.

The cap is not the problem. Silence is.

Worked example 2: year-end encashment of the excess

Now take the same company and change one rule. Instead of lapsing the excess, the policy allows the excess above 30 days to be encashed at the year-end, at the rate of one day equal to basic salary divided by 26.

Assume Farid's monthly basic is Rs 52,000. The daily rate under this policy is 52,000 divided by 26, which is Rs 2,000.

• Excess days: 16
• Encashment amount: 16 times 2,000, which is Rs 32,000 (gross, before any applicable deductions)

For Sanjay, with a basic of Rs 40,000, the daily rate is about Rs 1,538 and the 4 excess days come to roughly Rs 6,154.

Now suppose 40 employees in the company have an average excess of 8 days at an average daily rate of Rs 1,700. The year-end cash outflow would be 40 times 8 times 1,700, which is Rs 5,44,000. It is a manageable amount for most organisations, but it lands in a single payroll month, so finance must be told early.

Three practical observations:

• State the daily rate formula in the policy. Whether you divide by 26, 30 or the actual working days of the month changes the payout. Pick one, write it down, and apply it consistently.
• Decide whether encashment is optional or automatic. An automatic payout of the excess is simple to run. An optional one needs an opt-in window and a default for those who do not respond.
• Tax is a separate topic. How the payout is taxed in the employee's hands, and the treatment at the employer's end, is covered in our separate guidance on leave encashment tax. For year-end planning, the only thing you need to do is flag the payout to your payroll and tax team so the right deductions are applied in the month of payment.

Cut-off dates: the heart of the year-end

Most year-end disputes are really disputes about dates. A well-defined set of cut-offs prevents nearly all of them.

The key dates to fix

Fix each of these dates in writing, and publish them as a calendar.

Decide how to treat the grey areas

Even with good dates, edge cases appear. Decide in advance how to handle each:

• Leave applied before the cut-off but taken after. For example, an employee applies on 28th March for leave starting 2nd April. Does it draw on the old year's balance or the new year's? The common approach is to deduct leave from the balance of the year in which the leave days fall, not the year in which the application was made. Whatever you choose, state it.
• Leave spanning the year-end. A leave from 29th March to 3rd April crosses the boundary. Split it: the first days draw on the old year, the remainder on the new year.
• Pending approvals at the cut-off. If a manager has not approved a request by the deadline, what is the default? Auto-approve, auto-reject or escalate? Silent rejection by inaction is the most common source of grievances.
• Backdated leave entry. Employees or managers sometimes try to record leave after the year-end for days that were already past. Set a window, for example five working days, after which backdated entries need HR approval and a written reason.
• Leave without pay interactions. If an employee has insufficient balance and takes unpaid leave, make sure this is not reclassified later after the new year credit lands, unless your policy explicitly allows a regularisation.
• Employees on notice period or exiting near the close. Their balance may be settled in the final settlement instead of the year-end process. Keep them out of the bulk run and handle them separately.
• New joiners and recent hires. Prorated entitlements for those who joined in the last quarter should be calculated by the rule in your policy, and those balances typically carry forward without hitting a cap.
• Employees on long leave at the cut-off. Someone on extended medical or maternity leave at 31st March should not lose balance because they could not apply. Check whether your policy and applicable law protect them, and plan a specific treatment.

Communicating the year-end to employees

A rule nobody has read is a rule that will be disputed. Treat communication as a campaign with several touchpoints, not a single email.

A communication timeline

1. Announcement (60 to 75 days out). A short note covering the cycle, the cut-off dates, the carry forward cap, what lapses and whether encashment is available. Link to the full policy.
2. Personal balance statement (about 45 days out). A generic message is easy to ignore. A message that says "you have 34 days; 4 will lapse on 31 March unless used" is not. If your system can generate this per employee, use it.
3. Manager brief. Managers need their own message: who in their team is at risk of losing leave, what the deadlines are, and what they are expected to do. Ask them to plan leave in the team calendar, not wait for last-minute requests.
4. Reminders (30, 15 and 7 days out). Short, specific, with the exact date and a link to apply.
5. Final notice (3 days out). Last chance to apply and last chance to opt for encashment, if applicable.
6. Post-close confirmation. Opening balances in the new year, with a window for employees to raise queries.

What a good announcement contains

• The cycle and the exact cut-off date, written as a full date, not "year-end".
• A table of leave types with their treatment: carry, lapse, encash.
• Caps and limits in days, with one worked example employees can relate to.
• The last date to apply and the last date for approval.
• How the encashment rate is computed, if it applies.
• Who to contact with queries and how long the response will take.
• A line making clear that the policy document prevails if there is a discrepancy.

A sample announcement

Here is an illustrative message you can adapt. It is intentionally short.

Subject: Your leave balance and the 31 March 2027 cut-off Our leave year closes on 31 March 2027. Here is what happens to your unused leave: - Earned leave: up to 30 days carry forward. Anything above 30 lapses. - Casual leave and sick leave: unused days lapse. - Compensatory offs: valid for 60 days from the date earned, as per policy. Please apply for leave you want to use before 22 March 2027. Managers will approve by 26 March. Your personal balance statement is available in the HR portal, and it shows how many days are at risk. If something looks wrong, write to the HR helpdesk before 15 March so we can correct it before the close.

Tone and fairness

Avoid scare language. Employees should not feel that taking leave is a threat to their career, which is the effect of "use it or lose it" messaging combined with an unspoken expectation to stay available. Pair the reminder with an explicit message from leadership that planned time off is encouraged.

Also think about inclusion. Field staff, shift workers and employees without regular email access need another channel such as notice-board posters, supervisor briefings or messaging apps. Messages in the primary regional language of your workforce reduce confusion.

Keep a record

Retain the announcements, the date they were sent and the recipient list. If a dispute arises later, evidence that the rule was communicated in advance protects both the employee and the employer. Some employers also take a simple acknowledgement through the HR portal.

Configuring your HR system for the close

Even the best policy fails if the system is set up differently. Whether you use a spreadsheet, an on-premise tool or a cloud HRMS, review the following configuration points well before the cut-off.

Core settings to check for each leave type

Run a test in a safe environment first

Before the real close, simulate it. If your system offers a sandbox, or lets you run the year-end process in a preview mode, do that with a copy of current data. At minimum:

1. Pick ten sample employees spanning different cases: below the cap, above the cap, joined recently, on long leave, with negative balance, with pending requests.
2. Calculate their expected carry forward and lapse by hand.
3. Run the process.
4. Compare. Investigate any difference before the real run.

This simple exercise catches most configuration errors.

Lock and unlock sensibly

A year-end freeze stops people from changing balances after the numbers are final. But employees and managers will still need to apply for leave in the new year, and HR will need to correct genuine errors. Configure the freeze so that:

• New-year leave applications are allowed from the first day, or even earlier, if the new year's credit has already been posted.
• Edits to closed-year data require HR admin rights and generate an audit entry.
• The freeze applies to approvals too, or you define an explicit grace window for approvals of requests submitted before the cut-off.

Integrate with payroll

If encashment is part of the year-end, the payout has to travel from the leave module to payroll without re-keying. Check:

• The encashment day count and amount flow into the correct payroll month.
• The earnings component used for the payout is mapped correctly for statutory purposes in your payroll configuration. Your payroll and tax advisers will tell you how the component should be treated.
• Loss-of-pay days that were derived from leave are not double-counted.
• The payslip shows the encashment as a separate, labelled line so employees can understand it.

Roles and approvals

Define who can do what during the close: who can run the year-end process, who can approve exceptions, who can override a cap for an individual, and who can reverse the process. Keep the permission list short. A close that any HR executive can trigger or reverse is a close that can be run twice.

Back up before you run

Take a full export of balances and leave transactions before you run the close, and keep it with the reconciliation file. If something goes wrong, you can restore or at least explain.

Handling exceptions with discipline

Every year-end produces a handful of requests that do not fit the rule. How you treat them says a lot about the culture.

Common exception requests:

• An employee who could not take leave because of a critical delivery and now faces a large lapse.
• A manager asking that the entire team be given an extension.
• An employee returning from long medical leave.
• A senior leader with a very large balance asking for special encashment.

A simple exception process keeps this fair:

1. One channel. Requests go to a single HR mailbox or ticket queue, not to individual HR people.
2. A form. Employee name, leave type, days involved, reason, manager's recommendation.
3. A decision panel. HR plus finance, or HR plus the department head. Not one person alone.
4. Written outcome. Approved, partially approved or declined, with the reason.
5. A log. Keep a register of exceptions granted. Review it at the end of the year to see whether the policy itself needs to change.

If you notice that 30 employees are asking for the same extension, you do not have 30 exceptions. You have a policy problem, and it is cheaper to fix it once and announce it to everyone than to grant it in 30 private emails.

The step-by-step year-end checklist

Use this checklist as a working document. Adjust the timings to your cut-off date.

Phase 1: Preparation (about 90 to 60 days before)

• [ ] Confirm the leave year definition for every legal entity and location.
• [ ] Review current policy for carry forward, lapse and encashment for each leave type.
• [ ] Check whether any applicable state Shops and Establishments Act, factory rules, labour code provisions or contracts impose minimums. Take legal advice where unsure.
• [ ] Run a balance report by leave type, department and salary band.
• [ ] Calculate the liability for earned leave and the projected cost of any encashment.
• [ ] Take decisions on cap changes, encashment options and exceptions. Record them with approvals.
• [ ] Tell finance and payroll about expected encashment amounts and the month of payout.

Phase 2: Communication (about 75 to 30 days before)

• [ ] Publish the year-end calendar and the policy summary.
• [ ] Send each employee a personal balance projection.
• [ ] Brief managers and give them a team-level report of at-risk balances.
• [ ] Open the encashment election window, if applicable.
• [ ] Set up an HR helpdesk channel for queries.

Phase 3: Clean-up (about 30 to 10 days before)

• [ ] Clear pending leave approvals older than a defined period.
• [ ] Check attendance regularisation and make sure absences are correctly mapped to leave or loss of pay.
• [ ] Resolve negative balances and decide on recovery or carry treatment.
• [ ] Confirm comp-off expiries and close out stale ones.
• [ ] Validate joiners' proration and leavers' settlement treatment.
• [ ] Run the close in a test environment with sample employees and fix configuration gaps.

Phase 4: Cut-off (last 10 days)

• [ ] Send the final reminder and the final notice.
• [ ] Close the leave application window on the announced date.
• [ ] Chase managers for remaining approvals.
• [ ] Close the encashment election window and apply the default to non-responders.
• [ ] Take a full backup of balances and transactions.

Phase 5: Close and open

• [ ] Run the year-end process: carry forward, lapse, encashment.
• [ ] Post the new year's entitlement and opening balances.
• [ ] Freeze the closed year with audit controls.
• [ ] Send each employee a confirmation of their opening balance.
• [ ] Process encashment through payroll in the planned month.

Phase 6: Reconcile and learn

• [ ] Complete the reconciliation described below and sign it off.
• [ ] Resolve employee queries within the stated window.
• [ ] Record exceptions granted and the lessons learnt.
• [ ] Update the policy and the calendar for next year.

Reconciliation: proving the numbers add up

Reconciliation is the step that turns "we ran the close" into "we can prove the close was right". It is also the step most often skipped.

The basic equation

For every employee and every leave type, the following should hold:

Opening balance + credits + adjustments - leave availed - lapsed - encashed = Closing balance carried forward

At the company level, add up each term across all employees and check that the totals balance. Then check that the new year's opening balance equals the old year's carried forward balance.

A worked reconciliation

Suppose the earned leave summary for a team of ten, in days, looks like this after the close. These are invented numbers.

The expected closing is 210 plus 180 plus 4, less 96, 22 and 10, which gives 266. The system shows 262, so four days are unexplained. Investigating the four-day difference might reveal that the manual adjustment of 4 days was posted in the system after the close ran, or that a joiner's proration was applied twice. This is the point of reconciling: find the answer before the employee does.

Checks to run

• Roll-forward check. Closing balance of last year equals opening balance of this year, per employee.
• Cap check. No employee's opening balance exceeds the cap, unless an approved exception exists.
• Lapse check. Total lapsed days match the sum of balances above caps, plus lapsing leave types.
• Encashment check. Days in the leave module match days paid in payroll, and the amounts match the formula.
• Negative balance check. No negative opening balances unless approved.
• Population check. The number of employees processed equals the active headcount, excluding those who left before the close.
• Sample check. Pick 20 to 30 random employees and recompute by hand.
• Liability check. Compare the earned leave liability after close with the figure finance has provided for in the books.

Document and sign off

Keep a short reconciliation pack: the pre-close backup, the post-close report, the check results, the list of exceptions and the signed approval by HR and finance. This pack is what an auditor, an inspector or a curious employee will want to see.

Handling errors found later

Errors will occasionally slip through. When you find one:

1. Quantify it: who, how many days, which leave type.
2. Correct it in the system with an adjustment entry and a reason, never by overwriting history.
3. Tell the employees affected, quickly and plainly.
4. Fix the root cause so it does not repeat.

Common pitfalls and how to avoid them

• Changing the rules at the last minute. If you must change a cap or a date, announce it with as much notice as possible, and consider honouring the old rule for the current year.
• Ignoring part-time, contract and consultant categories. Their leave entitlement may differ. Confirm who is covered by which policy.
• Treating the lapse as a cost-saving device. Employees quickly see through it, and it damages trust. Use lapse for its purpose, which is to encourage use of leave in the year it is earned.
• Forgetting multi-location differences. A policy that works in one state may need adjustment in another because of local law. Keep a location matrix.
• Letting managers decide informally. Informal extensions create inequity. Route everything through the exception process.
• Running the close on the last day itself. Run it after the cut-off has passed and approvals are complete, but within a day or two, so that data is fresh and corrections are cheap.
• Not reading the new year's first payroll. After the close, check that the first payroll of the new year reflects the correct loss-of-pay and leave deductions based on the new opening balances.

Frequently asked questions

1. Can we change our leave carry forward policy just before the year-end?

You can, but it is risky. A change that reduces employee benefits, such as lowering a cap, announced days before the cut-off, will almost certainly be seen as unfair and may conflict with the terms of employment or applicable law. If you need to change the policy, announce it well in advance, apply it prospectively where possible, and consider honouring the old rule for the current year. Take legal advice before reducing any existing entitlement.

2. Is it legal to lapse unused earned leave?

It depends on the establishment, the category of employee and the state or central law that applies. Some laws and rules set conditions on accumulation, carry forward and encashment for covered employees, and contracts may add to those. Lapsing of casual leave is common practice, while earned leave is more sensitive. Verify the position for your establishment and each state you operate in, because we are not giving a legal opinion here.

3. Should the leave year match the financial year?

There is no single correct answer. A financial year cycle is convenient when finance, appraisals and payroll tax processing all run on the same calendar. A calendar year cycle can suit global teams. What matters more than the choice is consistency: the policy, the system configuration and the payroll calendar should all describe the same cycle. Avoid switching cycles in the same year you are cleaning up other processes.

4. What happens to leave applied before the cut-off but taken after it?

Define it in the policy. The most common approach is to charge each day of leave to the leave year in which that day falls, so a leave that spans the boundary is split between the old and new year. A leave applied for in March for days in April would draw from the new year's balance. Whichever rule you choose, apply it to everyone and configure the system to match.

5. How do we treat employees who are on long leave or have resigned near the year-end?

Employees on extended leave should not lose their balance simply because they could not apply, so check whether your policy and any applicable law offer protection and decide a specific treatment. For employees who have resigned or are serving notice, balances are usually settled in the final settlement under the exit policy rather than the bulk year-end process. Keep these cases outside the bulk run and handle them with a clear rule.

6. Should we make year-end encashment optional or automatic?

Automatic encashment of the excess above a cap is simple to administer and gives a predictable cost, but it removes choice. Optional encashment respects preference but requires an election window, a default for those who do not respond, and a firm payroll deadline. Many employers choose automatic encashment for balances above the cap and keep optional encashment out of the process altogether. Whichever you choose, inform finance early, because the payout lands in a single month.

7. How early should we start preparing for the year-end?

About 90 days before the cut-off is a good target. That gives you time to review the policy, calculate the liability, take approvals, announce the rules and run a test close without rushing. For a calendar-year cycle that ends on 31 December 2026, that means starting now. For a financial year ending 31 March 2027, a start around the new year is comfortable, but earlier is better.

Conclusion

A year-end leave close does not have to be a scramble. The organisations that handle it well do a handful of simple things consistently: they fix one leave year for every entity, they write down what happens to each leave type, they publish cut-off dates early, they send employees personal balance statements, they test the close before running it, and they reconcile the numbers afterwards. A transparent leave carry forward policy, backed by a clear calendar and a documented exception process, turns a stressful period into a routine one.

Start with the checklist above, pick the one or two items that are weakest in your organisation today, and fix those first. If your leave data lives in spreadsheets, or your system makes the close a manual exercise, that is the right moment to consider a better tool. CozyHR is built to help Indian teams configure leave types, carry forward caps and encashment rules, send employees their balance projections, and reconcile the close without the spreadsheet gymnastics. If you would like to see how that works for your own leave cycle, we would be happy to have you try CozyHR and run a test close on sample data before the 2026-27 year-end arrives.