Dayzen HRMS + Project Management System — people ops and delivery in one product family.

See all modules
Dayzen

Attendance & Leave

Annual allotment versus monthly leave accrual

Published 9/22/2026 · Updated 9/22/2026 · Dayzen

Annual allotment credits a leave type with a full-year (or cycle) grant on a date. Monthly accrual adds a fraction each month as people serve. The choice changes joiner proration, mid-year exits, and whether someone can take leave before it is earned. This is a mechanics comparison, not a statutory minimums table.

Key takeaways

  • Allotment vs accrual is a credit method, not a leave type name.
  • Link carry-forward sibling; do not restate exit encashment.

Annual allotment and monthly accrual are two credit methods for the same leave type. Allotment grants a cycle’s quota on a named date. Accrual credits a fraction as each month (or completed period) closes. The method changes when a joiner can take leave, what happens on a mid-year exit, and whether balances may go negative. It is not a statutory-minimums table. Rules depend on policy, establishment type, applicable state rules, applicable law, and employment terms. This page is the operating comparison.

Write the method per type. Casual, sick, and earned leave can differ. Mixing an informal “full year in January” with a system that accrues monthly is how balances stop matching what managers say. For type names, use casual, sick, and earned leave. For extra credits outside the framework, use granted leave versus policy leave.

Two credit clocks, one balance

The balance is a number; the clock that feeds it is a policy choice. If HR says “you get 12 days a year” and the system adds 1 day on the 1st of each month, both are true only after twelve credits — in January the employee has 1, not 12. If the system posts 12 on 1 January (or on the anniversary), they have 12 on day one, including leave not yet “worked for” in calendar time.

Question Annual allotment Monthly accrual
When does the year’s quota appear? On the grant date (calendar year, financial year, or joining anniversary) In instalments, usually after each month or completed service period
What does a new joiner see in month one? Full cycle grant, a pro-rata grant, or nothing until the next grant date — you must choose A first fraction, or nothing until first completed month — you must choose
Can someone take leave before the year is “earned”? Yes, by design, unless you cap usage separately Only up to accrued stock, unless you allow advance or negative balance
Mid-year exit Often a clawback or settlement of unused / overused days against policy Usually stop accruing; unused accrued stock follows your lapse, carry-forward, or later settlement rules

Neither column is “more correct.” Allotment is simpler to explain and harder to police for overuse. Accrual is closer to “earned as you serve” and noisier for joiners who need a week off in month two. Leave management only helps if the configured method matches the paragraph managers quote.

Allotment: a lump on a date

On the grant date the system (or spreadsheet) posts the cycle quota. Typical Indian SME dates are 1 January, 1 April, or joining anniversary. Publish the date. If some teams still grant on anniversary while the tool grants on calendar year, you have two truths.

Operational example

Earned leave 18 days per calendar year, allotted on 1 January, to everyone on rolls that morning. Take 5 in February, 13 remain — still this year’s grant, not a monthly drip. Carry-forward, lapse, and in-service encashment act on what is left at cycle end; that is leave carry-forward, lapse, and encashment.

Allotment does not answer joiners by itself. You still write one of these:

  • Full grant on joining, even in November (generous, easy to overuse before probation ends).
  • Pro-rata grant: remaining months ÷ 12 × annual quota, often rounded in a named way (half day up, nearest day, or banker’s rounding — pick one and stop arguing in chat).
  • No grant until next 1 January, with a separate joining-year rule or a small starter grant.

Pro-rata is the usual compromise. Name the rounding. “Fair” without a rounding rule is three different numbers in three Excel files.

Accrual: a fraction each month

Accrual posts a slice of the annual quota as time passes. A common pattern is annual quota divided by 12, credited on the 1st of the next month or on the last working day, for employees who were active for that month. Some policies require a minimum days-in-month before the slice posts. Some skip the joining month. Some credit from date of joining with a first partial month. Again: write it.

Operational example

Policy: 12 days casual leave a year, accrued monthly. Eligible credit is 1.0 day per completed month. After March, a January joiner who completed three months has 3.0 if every month qualified. They cannot apply for 5 casual days in April unless you also allow advance leave or a negative balance. If they take 1 day in February, the March-end balance is 2.0, not “12 minus 1 with 11 sitting in a drawer.”

Accrual systems fail in offices that still talk in annual totals. Managers approve “you have 12 CL” because the policy PDF says 12, while the ledger has 2. Train managers on the available number, not the headline annual figure. Show both on the application screen if you can: annual entitlement versus current available.

Joiners

A 15 June joiner is the test case. Under calendar-year allotment with pro-rata, they get a fraction of the remaining year and can often use it immediately, subject to probation. Under monthly accrual they may have zero until July, then one slice at a time. If culture says “leave after confirmation” at six months, neither method creates stock by itself — wait, grant a starter pack, or allow unpaid leave. Do not hide that inside the credit method.

Probation often blocks types independent of credit speed. Accrual plus “no EL in probation” plus “CL after 90 days” is three rules. Encode all three. If only the credit method is in the tool, the joiner applies EL in week three and someone rejects it late. Contractors and interns on the same module need “no entitlement” or another assignment, or accrual jobs will create balances you never meant to honour.

Mid-year exits (credit, not Full & Final math)

When someone leaves on 10 September, ask what has been credited, what has been used, and what policy does with the difference — not “what is the annual quota?” Under accrual, do not post credits after the last eligible month. Unused accrued stock may sit until you lapse it or handle it later in settlement. Under allotment they may have received 18 in January and used 14 — or 20 if negatives were allowed. Recovery of excess and unused stock are policy plus employment terms, not a universal formula.

Full and final is a later event. This article does not specify payment or recovery there. For that path, use the full and final settlement process guide. Do not run accrual on exited employees, and do not leave allotment sitting as if they will still be here on 1 January. Last working day must drive eligibility the same way it drives attendance close.

Taking leave before it is earned

Allotment already allows this: the year is granted up front. You may still cap how much can be taken in a quarter, or block EL until confirmation. Those are usage rules on top of credit.

Accrual does not allow it unless you add one of:

  • Advance leave: a named permission to take unaccrued days, with a documented maximum, often manager-plus-HR.
  • Negative balance: the ledger goes below zero and future accruals (or a recovery) bring it back.
  • Leave without pay: no balance movement on that type; unpaid time instead.

If you allow negatives without a cap, a leaver in month two can be several days “in debt.” If you forbid negatives but managers override in email, you have unofficial negatives. Pick a system behaviour and a named override path.

Negative balances: when they are a feature

A negative balance means used days exceed credited days on that type. It is not automatically a payroll deduction. It becomes one only if policy says excess is unpaid, recovered from salary, or settled later. Until then it is a ledger warning. It shows up when allotment was front-loaded before an exit, when accrual is monthly but an emergency was approved against future credits, when a cancellation never returned days, or when HR adjusted the wrong type without reversing the first debit.

Decide whether apply blocks at zero, warns, or routes to a higher approver. Block for accrual-heavy types. Warn if allotment treats the year as already given. Silent negatives are how year-end conversations turn hostile.

Do not mix methods on the same type without saying so

Allotting casual leave annually and accruing earned leave monthly is fine if each type’s screen matches its paragraph. What fails is accruing EL in the tool while HR still “opens 18 days” in a April register — two books. Equally bad: switching method in July without a conversion note (opening balance, unused allotment, whether July’s accrual double-counts). Publish date of switch, opening source, first new credit date, and who to ask — a named calendar event, not a quiet config edit.

What to put in the policy paragraph

For each leave type, five sentences are enough if they are specific:

  1. Credit method: allotment on [date] or accrual of [fraction] per [period].
  2. Joiner rule: full, pro-rata with named rounding, or wait until first grant/accrual.
  3. Eligibility: which statuses accrue or receive grants (confirmed, probation, notice period).
  4. Advance and negative: allowed or not, cap, who approves.
  5. Cycle-end: pointer to carry-forward, lapse, or in-service encashment — not a reprint of exit settlement.

If the paragraph cannot be configured in the leave product, the paragraph is fiction. Configure first, then print. Dayzen leave management supports configurable policies and quotas; it does not choose allotment versus accrual for you. You still write the method.


Allotment posts the cycle early. Accrual posts it in slices. Joiners, mid-year exits, unearned leave, and negative balances are where the methods disagree. Name the method per type, encode it, and keep FNF as a later event — not as a substitute for a credit rule.

See Dayzen in a walkthrough

Book a demo to evaluate Dayzen HRMS with your own processes.