The three designs
What happens to unused leave at the end of a leave year comes down to three choices, and most policies use different ones for different categories.
| Design | What happens to the unused balance | Where the cost lands |
|---|---|---|
| Lapse | It disappears at year end | On the employee, and on the fourth quarter when everyone takes leave at once |
| Carry forward, capped | Up to a stated limit moves to the next year, the rest lapses | An accumulating liability up to the cap |
| Encash the excess | The unused portion above the cap is paid out | A predictable payroll cost each year end |
Casual and sick leave commonly lapse, on the reasoning that they exist for events within a year rather than as a store of value. Earned or annual leave commonly carries forward, because it is the category the statute treats as accruing.
None of the three makes the cost disappear. Lapse pushes it into a year-end scheduling problem, carry forward defers it and lets it grow, and encashment converts it into cash on a known date. Choosing deliberately is the point.
Where the statute constrains the choice
For earned leave the employer is not free to design whatever it likes. The applicable state shops and establishments enactment, or the Occupational Safety, Health and Working Conditions Code, 2020 for establishments within its scope, prescribes the accumulation position for statutory leave, and policy operates within it.
Two consequences follow. A policy that makes statutory earned leave lapse entirely at year end is unlikely to be effective, whatever the handbook says. And a cap set below the statutory accumulation limit is a reduction of an entitlement rather than an administrative preference.
The specific limits vary by state and by establishment type. They are set out in statutory-leave, and are not restated here because a paraphrase in a second place is a paraphrase that will eventually disagree with the first.
Leave granted above the statutory minimum is a different matter. That part is contractual, and the employer can attach whatever carry-forward and lapse rules it chooses, provided it says so clearly and applies them consistently.
The liability nobody budgets for
An accumulated leave balance is a liability, and it has an unusual property: it grows even when nobody adds to it.
Leave is almost always valued at the salary in force when it is encashed or settled, not the salary at which it was earned. A balance built up over several years by an employee whose pay has doubled costs twice what it appeared to cost when it accrued. Across a workforce with long tenure and uncapped accumulation, this compounds quietly.
This is the practical argument for a cap, and it is a stronger argument than the administrative one. A cap does not just tidy the balances, it fixes the maximum exposure per employee and stops the number tracking salary inflation indefinitely.
It is also the argument for knowing what the balance is worth at current salary rather than at accrued salary. Organisations that report leave liability at historic rates understate it, and they discover the difference during a year with several senior exits.
The year-end scramble, and how to avoid it
A strict lapse rule produces a predictable pathology. Employees who have not taken leave through the year attempt to take it in the last few weeks, all at once, and the organisation either refuses it, which converts the entitlement into a grievance, or approves it, which leaves the fourth quarter uncovered.
The fix is not usually a change to the carry-forward rule. It is making leave obtainable earlier.
- Report balances to managers through the year rather than in December, so the problem is visible while it can still be solved.
- Ask teams to plan long absences at the start of the year, which spreads them and makes cover arrangeable.
- Look at which teams routinely reach year end with high balances. It is nearly always a small number of them, and the cause is usually a manager who does not approve leave or a team carrying a vacancy.
- Where a cap exists, warn before the balance reaches it rather than after it has lapsed.
A team that consistently cannot consume its leave is reporting something about its workload or its management, and the carry-forward rule is not the thing to adjust in response.
Exit, where the design finally matters
Most of the argument about carry forward happens at exit, because that is when the balance turns into money.
Three things should be settled in the policy well before then. What the balance is at the exit date, given the accrual method. What rate it is valued at, since basic, gross and a defined component produce materially different figures. And whether leave taken but not yet accrued is recovered, and from what.
The valuation basis is the line most often disputed, because employees generally assume gross and employers generally apply basic. Neither assumption is unreasonable, which is exactly why the policy needs to say which one applies rather than leaving it to be discovered.
Where the leave being settled is statutory earned leave, the encashment position is governed by the applicable enactment rather than by policy alone, so the policy should not state a basis that conflicts with it.
Frequently asked questions
What is leave carry forward?
The movement of unused leave from one leave year into the next, usually up to a cap, with the excess either lapsing or being encashed. Casual and sick leave commonly lapse; earned or annual leave commonly carries forward.
Can an employer make all leave lapse at year end?
Not for statutory earned leave, whose accumulation position is prescribed by the applicable state enactment or the Occupational Safety, Health and Working Conditions Code. Leave granted above the statutory minimum is contractual and can carry whatever lapse rule the employer states clearly.
Why does an accumulated leave balance cost more over time?
Because it is normally valued at the salary in force when it is paid rather than when it was earned. A balance built up over several years by someone whose pay has risen costs considerably more than it appeared to when it accrued.
What is a sensible carry-forward cap?
One at or above the statutory accumulation limit, since a cap below it reduces an entitlement rather than simplifying administration. Above that floor, the cap's real function is to fix the maximum exposure per employee so the liability stops tracking salary inflation.
How is carried-forward leave valued at exit?
On whatever basis the policy states, which is why it needs to state one. Employees generally assume gross salary and employers generally apply basic, and the gap between those two assumptions is the most-argued line in final settlements.
How do we avoid a year-end rush for leave?
Make leave obtainable earlier rather than changing the lapse rule. Report balances to managers through the year, plan long absences at the start of it, and look at the small number of teams that routinely reach December with high balances, since the cause is usually workload or an approval bottleneck.
How Engage handles carry forward
Engage applies carry-forward caps, lapse dates and encashment rules per leave category and policy group, and values balances at current salary rather than at the rate they accrued, so the reported liability is the real one. Balances are visible to managers through the year, which is what prevents the fourth-quarter scramble a lapse rule otherwise guarantees.
See leave management in Engage