Leave carry-forward, lapse, and encashment

Carry-forward, lapse, and in-service encashment are three cycle-end treatments for unused leave. An organisation may define them in policy and employment terms. They are not one nationwide formula, and they are not the same as paying unused leave when someone exits. Indian rules can depend on employer policy, establishment type, applicable state rules, applicable law, and the leave type. This article explains the concepts so you can write a rule you can operate. It is not legal advice. It is not a statutory quota table. SME review of this explainer is pending.

Credit method — annual allotment versus monthly accrual — decides how the balance grew. Cycle-end treatment decides what happens to what is left. Read the credit comparison in annual allotment versus monthly leave accrual first if your team still argues about why January’s number looks large. Type names (casual, sick, earned) live in their own primer; this page assumes you already named types.

Three different endings for unused days

Treatment	What it means in operations	Typical policy knobs
Carry-forward	Unused days move into the next cycle as opening stock, often on top of the new grant or first accruals	Which types, maximum days that may move, whether old stock expires first
Lapse	Unused days become zero (or a named remainder) at cycle end; they are not paid and not moved	Which types, whether any remainder is protected, notice to employees before the date
In-service encashment	While employed, unused days (usually a named type and a named slice) are paid in a cycle, not because the person is leaving	Eligibility, cap, payroll timing, whether encashed days leave the leave ledger

You can combine them. Example shape only — not a recommended national default: earned leave may carry forward up to a cap; anything above the cap may lapse or, if policy says so, be offered for in-service encashment; casual leave may lapse at year end with no carry-forward. Sick leave rules vary widely. Do not copy a neighbour company’s PDF without checking your own establishment and terms.

Do not write “every Indian employer must encash earned leave in December.” That sentence is false as a universal operating rule. If a particular law or standing order applies to you, take advice and put the outcome in your policy — not in a blog paragraph pretending to be a gazette.

Carry-forward, usually with a cap

Carry-forward is a ledger movement on a date: unused eligible days become next cycle’s opening balance, subject to a maximum. Without a cap, long-tenured employees can accumulate a liability that finance notices only when someone actually uses a six-week block. With a harsh cap and no communication, people dump leave in the last fortnight and operations suffer. The cap is a business choice as much as a leave choice.

Write four facts:

1. Which leave types carry forward. Many offices carry earned leave and lapse casual leave. That is a pattern, not a law on this page.
2. The maximum days (or months) that may sit as carried stock, or the maximum that may move in one transition.
3. Order of consumption next year: does new grant get used first, or old carried stock? This changes who hits the cap later.
4. The exact date and timezone of the job. 1 January 00:00 IST versus “sometime in the first week” will produce tickets.

If you allot 18 EL on 1 January and allow 30 carried, an employee with 25 unused on 31 December might open January at 30 carried plus 18 new, or at 30 total including new, depending on whether the cap applies to carried stock only or to the combined bucket. Those two designs feel similar in a meeting and produce different numbers. Draw them once on a whiteboard, then configure leave management to that drawing.

Joiners in December and employees on long leave across the boundary need a named rule: do they participate in the carry-forward job, and is unused joining-year pro-rata treated like everyone else’s unused stock?

Lapse is a dated zero, not a rumour

Lapse means the unused quantity disappears from available balance on the cycle-end date. It is not a payroll event unless you have somehow linked it to pay — normally you have not. Employees experience it as “my days vanished.” If you never announced the date, they experience it as theft. Publish the lapse date the same way you publish attendance close: on a calendar people already watch.

Lapse policies that work in small Indian teams usually:

• Name the types that lapse fully (often casual) versus types that only lapse above a carry-forward cap.
• Give a reminder window — not as fake “best practice days,” just a real date in your SOP, such as the second week of December if your cycle is calendar year.
• State whether applications already approved into the next cycle consume old stock or new stock.
• State what happens to pending applications that straddle the boundary.

Do not lapse in the tool but keep a paper register that still shows the old number. One book. If a manager promised “we will not lapse yours this year,” that is a granted exception with an owner, not a silent skip of the job. See granted versus policy leave if you use ad-hoc credits to undo a lapse; doing that without a reason code recreates the balance you just zeroed.

In-service encashment is not exit encashment

In-service encashment is a pay event for a sitting employee: a slice of unused leave is converted to money in a named payroll cycle, and those days leave (or reduce) the leave balance. Organisations may offer it yearly, never, or only above a cap. Eligibility often excludes probationers, or includes only confirmed staff, or only certain grades. None of that is implied by the word “encashment” alone.

Separate this clearly from exit. When someone leaves, unused leave may be part of settlement under policy and applicable rules. That path is the full and final settlement process — a later, different workflow with different documents. Do not use FNF as your quota table. Do not tell employees that the December in-service window is “the same as what you get when you resign.” The dates, caps, tax handling, and who initiates the request usually differ. This article does not specify exit payment formulae.

If you run in-service encashment, operations need:

• A request window or an automatic selection rule (for example, days above cap).
• A freeze: leave applications after the cut-off cannot raid the days being encashed.
• A payroll input: amount and employee list, after leave ledger reduction, not the other way around.
• A payslip line employees can recognise, so they do not think salary increased permanently.

Payroll calculation can carry the amount. Government filing and bank payment remain separate jobs. Do not invent a statutory rate in this explainer.

How the three collide in one year-end week

Picture a calendar-year earned leave type with a carry-forward cap and an optional in-service encashment of days above cap. Sequence matters:

1. Stop accepting applications that would change the year-end unused figure, or accept them with a written “counts in this cycle / next cycle” stamp.
2. Compute unused closing balance.
3. Move up to the cap into next year (carry-forward).
4. Offer or auto-process encashment of the remainder, if policy says so.
5. Lapse whatever is still left, if policy says so.
6. Post the new cycle’s allotment or continue monthly accrual on the new period.

If you post the new allotment before carry-forward, you will not know whether the cap applies to old stock, new stock, or both. If you encash before you freeze applications, someone will take leave you already paid. Run the sequence as a checklist, once, with one owner — the same discipline as monthly leave close, just yearly.

What not to bury in the same SOP paragraph

Keep cycle-end treatment away from sandwich-leave mechanics, half-day math, and holiday calendars. Those change whether a day was leave at all. Cycle-end assumes the ledger is already correct. Also keep it away from granted ad-hoc credits: a special grant in March should state whether it lapses in December or follows the type’s default. If you are writing the whole policy document, the leave policy template can hold section order; this page stays the three endings.

Compensatory off, if you use it, often has its own expiry (“use within n days of earning”) rather than a January carry-forward. Do not force comp-off through the EL year-end job unless you intentionally designed one bucket — most teams should not.

Manager and employee language that prevents tickets

Replace “your leave will be encashed” with “unused EL above 30 days may be carried, lapsed, or paid in the March payroll if you are eligible — see the policy section.” Replace “CL never carries” with “CL unused on 31 December lapses; it is not paid in service.” Replace “HR will see at FNF” with “exit settlement is a different process; do not wait for resignation to understand year-end.” Precision is kinder than optimism.

Show employees two numbers in November if you can: available now, and projected lapse or cap if they take no more leave. A projection is not a legal notice. It is how you avoid a rush on 30 December that wrecks shifts.

---

Carry-forward moves unused days, usually up to a cap. Lapse zeros them on a date. In-service encashment pays a named slice while the person is still employed. Organisations may define each; none is a nationwide must on this page. Keep exit settlement on its own track. Write the sequence before you run the year-end job.