How leave accrual works, as a ledger and the maths behind it
By Validure team · · 18 min read
Entitlement versus accrual, a worked year with a mid-month joiner and an unpaid-leave month, carry-forward and encashment sums, the checks that catch negative and double-debited balances, and what Indian law actually requires.

Say a 30-person company gives every employee 18 days of earned leave on 1 January. A new joiner, Asha, starts on 1 January and takes 10 days over the next three months. On 31 March she resigns. HR opens the sheet and sees a balance of 8, which looks fine. Then someone asks how many days she had actually earned by March. The answer is 4.5, so she's 5.5 days overdrawn, and nobody can say whether to recover it, forgive it or argue about it.
Nothing there was a maths error. The policy never said when leave is earned, and the balance was a number somebody typed rather than something you can replay.
This post treats leave like accounting: a ledger of dated entries and a few formulas. It works through a full year of numbers, gives the checks that catch the usual mistakes, separates what Indian law requires from what's just policy, and ends with a decision table you can copy.
Entitlement and accrual are different things
Entitlement is the size of the yearly allowance: 18 days of earned leave, say. Accrual is the rule for when those days become yours. Two companies can both have "18 days" and behave completely differently.
| Credited upfront | Accrued monthly | |
|---|---|---|
| When Asha can use 18 days | From 1 January | Only as earned, 1.5 a month |
| Balance on 31 March | 18 minus 10 used = 8 | 4.5 earned minus 10 used = minus 5.5 |
| What happens when she leaves | A policy question, usually settled by argument | Visible on the ledger the day the leave was approved |
At a daily rate of 1,333.33 (we'll see where that comes from below), 5.5 days is 7,333.33. Small for one person. Across a year of leavers it adds up, and it's the reason most companies end up on monthly accrual. Upfront credit isn't wrong. It's friendlier, and it works when you're happy to absorb the occasional overdraw. Just decide it on purpose.
The rest of this post assumes monthly accrual, because it's the harder case and the one that needs a ledger.
The monthly accrual formula
For each employee, leave type and month:
accrual = monthly_rate x paid_days_in_month / calendar_days_in_month
where monthly_rate is the yearly entitlement divided by 12, and paid_days_in_month is the days from joining (or the 1st) to exit (or month end), minus days of unpaid leave. A full month gives the full rate. A mid-month joiner gets a share. A month with unpaid leave gets a reduced share.
Some companies prefer simpler rules, like "joined on or before the 15th gets the full month, after gets half" or "no accrual if unpaid leave exceeds 15 days". Those are fine. They're just easier to explain than to calculate, and every one of them is a rule your system must apply the same way each time.
A worked year
This is an example, with made-up numbers. The policy: earned leave of 18 days a year, so 1.5 a month, accrued on the last day of each month, rounded to two decimals per entry. The calendar year is January to December 2026.
The employee joins on Monday 16 March 2026. In August she takes 6 days of unpaid leave. She takes 3 days of earned leave in June, 4 in October, and a half day in November.
March is a part month: 16 to 31 March is 16 days out of 31, so 1.5 x 16 / 31 = 0.77. August has 31 days and 6 are unpaid, so 1.5 x 25 / 31 = 1.21.
| Month | Accrual | Taken | Balance at month end |
|---|---|---|---|
| March | 0.77 | 0.77 | |
| April | 1.50 | 2.27 | |
| May | 1.50 | 3.77 | |
| June | 1.50 | 3.0 | 2.27 |
| July | 1.50 | 3.77 | |
| August | 1.21 | 4.98 | |
| September | 1.50 | 6.48 | |
| October | 1.50 | 4.0 | 3.98 |
| November | 1.50 | 0.5 | 4.98 |
| December | 1.50 | 6.48 |
Total accrued: 0.77 + 1.21 + 8 x 1.50 = 13.98. Total taken: 7.5. Closing balance: 13.98 minus 7.5 = 6.48. The six unpaid days in August don't touch the earned-leave balance at all. They reduce what she earned that month and they reduce her pay, and they appear in two different places for two different reasons.
Rounding each entry to two decimals means the ledger total is exactly the sum of what's printed. Rounding only the final balance would make a printed table disagree with the balance, which is how people stop trusting a report.
Carry-forward and lapse
At year end, each balance is either carried into the next year, lapsed, or paid out. Three employees, same policy, a carry-forward cap of 10 days and lapse above it:
| Employee | Closing balance | Carried | Lapses |
|---|---|---|---|
| A (the worked year above) | 6.48 | 6.48 | 0 |
| B | 22.5 | 10 | 12.5 |
| C | 3 | 3 | 0 |
The ledger records this as one entry, not two. The carry is just the absence of a lapse: you post a lapse of minus 12.5 on 31 December for B and nothing for A or C. Balances roll over because they're a running sum, not because you copied a number into a new year's column.
A cap that lapses days is a legitimate policy, but check it against the law before you use it (see the section on what the law says, below). Under the national labour code provisions as summarised by several law-firm and HR sources, the carry-forward cap is 30 days, and anything above it has to be paid out rather than lost. If that applies to your establishment, "lapse everything above 10" may not be available to you for the leave the code covers.
Encashment: the formula and the divisor problem
Encashment is paying out unused days. The formula is:
encashment = (basic + DA) / divisor x days_encashed
The salary base is a policy choice that the market mostly settles on basic plus dearness allowance, rather than gross. Several payroll vendor sources describe that as common practice, and some employers choose gross as a perk. Which figure the law uses for leave pay is a separate question; the labour code's wage definition is a point to confirm with an adviser, since it changes what "wages" includes.
The divisor is where companies differ. Say basic is 36,000 and DA is 4,000, so the base is 40,000, and you're encashing 12.5 days.
| Divisor | Daily rate | 12.5 days |
|---|---|---|
| 30 | 1,333.33 | 16,666.67 |
| 31 (the month's calendar days) | 1,290.32 | 16,129.03 |
| 26 (working days, six-day week) | 1,538.46 | 19,230.77 |
Between 30 and 26 that's 2,564.10 on one person's encashment. Every source I found treated 30 as the most common choice among private employers, with 26 used by some, and none of them cited a statute fixing the divisor. I could not verify a statutory divisor, so treat it as policy: pick one, write it into the policy, and store the divisor and the rate on the encashment entry so it can be recomputed later.
Don't use the calendar days of whichever month you happen to run it in. It means the same leave pays differently in February and March, which no employee finds reasonable.
On tax: encashment during employment is generally taxed as salary. On retirement or resignation there's an exemption under section 10(10AA) for private employees, limited to the lowest of several figures including an overall cap that was raised to 25 lakh in 2023. Sources disagreed on whether that cap is lifetime or per event, so check the Income Tax department's guidance or ask your tax adviser before quoting it to an employee.
The ledger design
Store leave as append-only entries. One signed column: credits positive, debits negative.
| Column | What it holds |
|---|---|
| Employee, leave type | Whose balance, and which kind of leave |
| Entry date | The day the entry takes effect |
| Period | The month, such as 2026-08, for accruals |
| Kind | Accrual, debit, reversal, lapse, encash or adjustment |
| Days | Signed: credits positive, debits negative |
| Reference | The request or payroll run that caused the entry |
| Reason, created by, created at | Why, who and when |
You never edit or delete a row. A cancelled leave posts a reversal with the opposite sign. A mistake is fixed by an adjustment with a reason and an author. That's what makes a balance replayable, and a replayable balance is the thing that ends arguments.
Add one rule: there is only ever one accrual per person, leave type and month. If the monthly job runs twice, the second run should be refused instead of crediting everyone double. In a sheet, that's a check for duplicate rows on those three columns, and a developer can enforce it in the database so a rerun is safe.
The balance as of any date is the sum of the days column for that person and leave type, for every entry up to that date. A pivot table or a SUMIFS formula does it.
Checks that catch the usual mistakes
Run these before every payroll and every year-end.
| Check | What to look for | What a hit means |
|---|---|---|
| Negative balance | Sort the ledger by person, leave type and date, and add a running total of the days column. Look for any running total below zero for a leave type that doesn't allow negatives. It works for any date | Leave was taken before it was earned, or a debit was posted twice |
| Double or missing debit | For each approved request, compare the days approved with the days the ledger actually debited. For each cancelled request, the debits and reversals should net to zero | Approved with no debit, debited twice, or cancelled and never reversed |
| Same day taken twice | Add up the approved fractions per person per date (1 for a full day, 0.5 for a half). Look for a total above 1 | Two requests cover the same day, which is how people take the same Friday twice |
The second check is the one worth automating. If you have a developer, this is the query. I tested the logic on sample data; adapt the names to your schema:
SELECT r.id, r.employee_id, r.status, r.days AS requested,
COALESCE(-SUM(l.days), 0) AS debited
FROM leave_requests r
LEFT JOIN leave_ledger l
ON l.ref_type = 'request' AND l.ref_id = r.id
AND l.entry_kind IN ('debit', 'reversal')
WHERE r.status IN ('approved', 'cancelled')
GROUP BY r.id
HAVING COALESCE(-SUM(l.days), 0) <>
CASE WHEN r.status = 'approved' THEN r.days ELSE 0 END;
An approved 2-day request debited 4 days shows up as requested = 2, debited = 4. An approved request with no debit shows debited = 0. A cancelled request that was debited and never reversed shows a positive debited.
The same-day check only works if you keep one row per leave day with a fraction of 1 or 0.5. That is also what makes the next section tractable.
If you want a system to do this, Validure HR has leave requests, approvals and balances that accrue monthly, and the monthly accrual and approval steps are the ones above. Whatever you use, ours included, test it against the edge cases that follow before you trust it with real balances.

Edge cases that decide whether the policy survives
Probation. Decide whether leave accrues during probation but can't be used until confirmation, or doesn't accrue at all. Accruing but locking is the better choice: the ledger is continuous, and confirmation just opens the balance. Keep "accrued" and "available" as two numbers. The labour code summaries mention a 180-day-worked threshold before annual leave becomes a statutory entitlement, so a lock of about six months lines up with the law without needing a separate rule.
Holidays and weekly offs inside a leave. If someone is on leave from Thursday to Tuesday and the company is closed on Saturday and Sunday, is that 3 days or 5? Several sources say weekly holidays falling inside a leave aren't deducted, but those were commentary rather than the statute's text, so confirm for your establishment. Whichever you choose, apply it from the calendar: generate one row per working day and debit only those. The "sandwich rule", which counts the holidays between two leave days, is a policy that some companies adopt. If you adopt it, say so in writing.
Half days. A half day is a 0.5 row in the leave-day list. The only trap is two half days on the same date, one morning and one afternoon. The same-day check above catches a total over 1. Decide whether a half day of leave plus a half day worked counts as a present day for the attendance and payroll side.
Leave across a month end or a payroll cycle. A request from 29 October to 3 November should be debited day by day, with each day belonging to its own month. That matters most for unpaid leave, because the pay deduction has to land in the right payroll run. If you run a cycle that isn't the calendar month, say the 26th to the 25th for night-shift staff, the cycle is a property of the employee, and unpaid days fall into whichever cycle contains them.
Accrual date. Posting accrual on the last day of the month means leave taken early in June draws on May's balance. Posting it on the first means June's 1.5 is available during June. Neither is better. Pick one, and be aware that the first choice produces more temporary negatives in the check above.
Leavers. Run the accrual for the last month using the same formula, then compute the encashment or recovery in full and final settlement from the ledger balance as of the last working day. Don't recompute from a spreadsheet.
What the law requires and what's policy
I searched for this, and most of what's published online is from HR and payroll vendors and law-firm summaries. Treat what follows as the shape of the position and check the official text.
The four labour codes were brought into effect by a notification dated 21 November 2025. Annual leave with wages sits in the Occupational Safety, Health and Working Conditions Code, section 32. As the sources summarise it, a worker becomes entitled to leave after working 180 days in a calendar year (the earlier Factories Act threshold was 240), at one day for every 20 days worked, with carry-forward capped at 30 days. Leave a worker applied for and was refused can reportedly be carried forward without that cap. Several sources say any balance above 30 must be paid out, and that on separation the accumulated balance is paid out with no prescribed ceiling, though they disagree on exactly when the excess must be encashed. Days of layoff, maternity leave and annual leave taken are said to count towards the 180.
Put that against the worked year. One day per 20 days worked means 200 days of attendance earns 10 days. A company giving 1.5 a month is above that floor for most employees, so for the statutory part the policy is more generous than the law, and the cap and encashment rules are where you could be non-compliant.
Three cautions that matter more than any figure here:
- The codes are still being operationalised through rules. Draft central rules were published in December 2025 and the Ministry of Labour issued FAQs in March 2026. Sources differ on which rules are final, and existing laws continue in the meantime for matters not yet covered.
- State rules differ. Casual leave, sick leave and, in many cases, earned leave are set by state shops and establishments laws, and the number depends on where the establishment is, not where the head office is. I found Karnataka commonly quoted at 18 days of earned leave, but even vendor sources contradicted each other on Maharashtra, so I've left state figures out.
- Which establishments and which workers the code covers matters. A policy for a 25-person office may fall under a state shops act and not the code's leave section at all.
Everything else is yours to choose: accrual frequency, how joiners are prorated, how unpaid leave affects accrual, the divisor, the salary base, whether holidays inside leave count, and whether half days exist. It's the second list, not the first, that makes up most of your policy and most of the disputes.
A policy template as a decision table
Copy this, fill the right-hand column, and attach it to the leave policy.
| Decision | Common options | Our recommendation |
|---|---|---|
| Accrual | Upfront, or monthly | Monthly, posted on the last day |
| Rate | Yearly entitlement / 12 | 18 days / 12 = 1.5 |
| Joiner in month | Full month, half, or by days | By days: rate x days / calendar days |
| Unpaid leave | No effect, threshold, or by days | By days, same formula |
| Probation | None, or accrue and lock | Accrue, lock until confirmation |
| Carry-forward cap | 10, 30, none | Whatever the law allows for your establishment, no lower for covered leave |
| Above the cap | Lapse, or encash | Encash where the law says so; otherwise write it down |
| Encashment base | Basic + DA, or gross | Basic + DA |
| Divisor | 26, 30 | 30, fixed for every month |
| Half days | Allowed, or not | Allowed, as 0.5 rows |
| Holidays inside leave | Count, or don't | Don't count; document if you adopt a sandwich rule |
| Negative balance | Blocked, or allowed to a limit | Blocked; exceptions as logged adjustments |
| Exit | Encash, or recover | Compute from the ledger on the last working day |
Where a row says "whatever the law allows", that's not a dodge. It really does depend on the establishment, the state and whether the leave type is statutory. Get it checked by someone who knows your sector once, then write the answer down.
Do you need a system for this?
With a handful of employees, one site and one leave type, a sheet with a ledger tab and the checks above, turned into formulas, is enough. The case for a system grows with headcount, with the number of leave types, and with unpaid leave that has to feed payroll correctly. Validure HR keeps requests, approvals and accruing balances in one place so leave reaches payroll without retyping, but the policy table above is the part that matters whatever tool you use.
Sources and checks
Rates, thresholds and rules change, so verify against the official sources before relying on any figure: the Ministry of Labour and Employment for the labour codes, their rules and FAQs, India Code for the text of the Occupational Safety, Health and Working Conditions Code, 2020, and the Income Tax Department for the leave encashment exemption. For state leave entitlements, use your state labour department's site. The worked examples use round, made-up numbers and are illustrations, not advice.
Frequently asked questions
What is the difference between entitlement and accrual?
Entitlement is how many days you get in a year. Accrual is when you earn them. Eighteen days credited on 1 January and eighteen days earned at 1.5 a month are the same entitlement with different rules about when you can use them.
How do I accrue leave for someone who joins mid-month?
Multiply the monthly rate by the days from the joining date to month end, divided by the days in the month. At 1.5 a month, joining on the 16th of a 31-day month gives 1.5 x 16 / 31 = 0.77. Apply the same rule to leavers.
Can I lapse unused leave at year end?
It depends on the leave type and the establishment. Sources describing the new labour code say carry-forward is capped at 30 days with the excess paid out, so lapsing above a lower cap may not be allowed for covered leave. Check with an adviser who knows your state and sector.
Which divisor should I use for leave encashment?
Most private employers in the sources I found use 30, and some use 26. I couldn't find a statutory divisor. Choose one, write it in the policy and use it every month, because the choice moves the amount by about 15 per cent.
Does unpaid leave reduce earned-leave accrual?
That's a policy choice. The cleanest rule is to reduce that month's accrual in proportion to the unpaid days, as in the August example above. Some companies use a threshold instead. Either way, write it down.
Do I need a ledger, or is a balance column enough?
A balance column is fine for a few people. Once you have more than a few leave types or any disputes, a ledger is worth it, because every balance can be replayed and every correction has a name and a reason.
