Paid annual leave is more than a line on a payslip. It gives workers time away from work while preserving wages, and it gives employers a practical way to plan staffing without treating rest as an exception. In India, the current national starting point for many covered workplaces is section 32 of the Occupational Safety, Health and Working Conditions Code, 2020 (OSH Code). The Code came into force on 21 November 2025. This guide explains the section’s main rules in plain language, how to keep a useful leave record, and which questions to check before relying on a number. It is general information, not legal advice about a specific employer or claim.
Start with the right law and the right person
Before calculating leave, confirm that the OSH Code applies to the establishment and that the person falls within the Code’s definition of “worker” for this provision. The Code covers specified kinds of establishments, including factories, mines, docks, plantations, construction work and other covered workplaces, subject to its definitions, thresholds and exceptions. It is not safe to assume that every person called an employee, consultant, manager or contractor has identical coverage. The statutory definition and the facts of the role matter. A title alone may not settle whether someone is a worker; actual duties, supervisory powers, wage limits where relevant, and the applicable part of the Code may need review.
The Ministry of Labour and Employment’s published material describes the Code as consolidating 13 Central labour laws. That does not mean every local rule, order, contract term or more favourable benefit has vanished from practical consideration. The Ministry’s own FAQs say the Code prevails where a State-law provision is inconsistent, while also recognising a worker’s entitlement to a more favourable State-law benefit. The application can depend on the establishment, the appropriate government, current rules, transition provisions and the particular right in question. Check the current official text and government guidance for the relevant workplace rather than copying a formula from an unrelated state or industry.
The basic 180-day threshold
Section 32(1) says a worker is entitled to annual leave with wages in a calendar year if the worker has worked 180 days or more in that calendar year. The calendar-year framing matters: this is not automatically a rolling twelve-month test, nor should an employer silently substitute a financial year. The Code also explains how certain periods count toward the threshold. Periods of lay-off, maternity leave and annual leave already availed are included when calculating whether the worker has reached 180 days, but the section says leave is not earned for those counted periods.
For a worker who starts service after 1 January, the section contains a separate rule: the worker is entitled to leave at the stated rate if they have worked for one-fourth of the total number of days in the remainder of that calendar year. This prevents the threshold from being applied as though a late-year joiner had been available for the whole year. The precise number of days and any counting questions should be worked from the actual commencement date and the governing rules. If a payroll system automatically applies a full-year threshold to everyone, check that it handles this mid-year commencement clause correctly.
How leave accrues
Once the conditions are met, the general rate in section 32(1)(ii) is one day of leave for every 20 days of work in the calendar year. The section provides a different rate for an adolescent worker—one day for every 15 days of work—and for a worker employed below ground in a mine, also one day for every 15 days of work. These are statutory rates, not a promise that every workplace’s software calculates fractions in the same way. Where a result depends on rounding, qualifying categories or a more favourable term, check the applicable rule, settlement, award or service condition rather than guessing.
It is useful to separate the eligibility count from the accrual count. The section explicitly allows lay-off, maternity leave and annual leave availed to count toward the 180-day eligibility test, while stating that a worker does not earn leave for those periods so counted. The two calculations therefore are not necessarily identical. Keep a record that distinguishes days actually worked from periods included only for eligibility. That makes it easier to explain a balance, identify an input error and answer a worker’s question without treating every day in a paid or protected absence as a day of leave earned.
Holidays around a leave period
Section 32 says holidays that fall between annual leave days, including a prefixed or suffixed holiday, are excluded from the period of leave availed. In everyday terms, a weekly or other holiday that falls inside a continuous leave spell is not automatically deducted as one of the annual-leave days under this clause. The same clause mentions holidays immediately before or after the leave period. This can change the number of leave days debited, so a leave record should show the actual dates of absence and the holidays in between rather than only a total typed into a payroll field.
Do not confuse this annual-leave rule with every question about weekly rest, public holidays or a company shutdown. Those may be addressed by other provisions, the applicable rules, an award, agreement or service term. A clear calendar helps: mark the first and last leave date, the holidays within the spell, and any holiday immediately before or after. If the employer’s system deducts all calendar dates without distinguishing holidays, ask how it implements section 32 and the relevant rule. If the system excludes a day, retain the leave request and the calendar view so both sides can see the calculation used.
Carry-forward: the ordinary limit and the refused-leave exception
Unused annual leave is generally added to the leave allowed in the succeeding calendar year, but the ordinary carry-forward balance must not exceed 30 days. Section 32 then creates an important exception: a worker who applied for leave with wages and was not granted that leave in accordance with the section and applicable rules may carry forward the refused leave without a limit. The text therefore distinguishes ordinary unused leave from leave the worker sought but was refused. These are not interchangeable categories, and records should preserve which days fall into which bucket.
For a refused application, keep the date of the request, requested dates, the response, any reason given, and the eventual balance. A leave portal status alone may not reveal whether the request was refused, withdrawn, changed or left pending. If a manager asked the worker to move dates, retain the revised request and outcome too. Accurate documentation helps establish whether the statutory exception is relevant. It also protects the employer from treating a refused request as an ordinary unused balance without investigating what happened. This is practical recordkeeping, not a requirement to disclose private medical or family details to a general audience.
Encashment at year-end and balances above 30 days
Section 32(1)(viii) states that, without prejudice to the separation rule, a worker is entitled on demand to encash leave at the end of the calendar year. Section 32(1)(ix) also says that where total leave exceeds 30 days under the ordinary carry-forward rule, the worker is entitled to encash the excess. These clauses give workers a way to avoid losing value merely because the balance has grown beyond the ordinary accumulation limit. The Ministry’s FAQs explain that there is no prescribed maximum limit for leave encashment under the OSH Code and that leave exceeding 30 days, if applied for but not granted, can be encashed at year end.
“On demand” matters: keep a worker’s written request and the employer’s calculation rather than assuming that every balance is automatically paid in every payroll cycle. At the same time, do not treat an internal policy as permission to deny a statutory entitlement. The precise wage basis and any applicable procedure should be checked in the current Code, rules and relevant official guidance. The available sources make the entitlement clear but employers should not invent a calculation divisor or rate from another law if the governing rule or employment terms supply the applicable method. Explain the amount and basis on the payslip or accompanying record.
When employment ends during the year
Section 32(1)(vi) addresses a worker who is discharged, dismissed, quits employment, is superannuated or dies during the calendar year. The worker, or their heir or nominee where relevant, is entitled to wages in lieu of the leave quantum to which the worker was entitled immediately before that event, calculated under the preceding clauses. The section says this payment is due even if the worker has not worked the otherwise required period to become eligible to avail the leave. For discharge, dismissal or quitting, payment must be made before expiry of the second working day from the date of the event; for superannuation or death in service, before expiry of two months.
That rule is a reason to reconcile balances promptly at exit, not wait for an annual leave cycle. Confirm the last working date, service start, work and eligibility record, leave taken, carry-forward categories, refused leave, and any already-paid encashment. Keep the calculation and payment evidence with the final settlement record. Where there is a dispute about the worker’s status, balance or wage basis, preserve the records and obtain advice from a qualified professional or the competent authority. A simple exit checklist can prevent a payroll delay, but it must not narrow the statutory entitlement or override a more favourable binding term.
Applying for leave and planning cover
The statutory entitlement works best when both sides can see a predictable process. A worker can submit the requested dates through the normal channel, keep a copy or acknowledgment, and identify any urgent correction if the system records the wrong dates. An employer can publish the process, identify who decides requests, explain how conflicts are handled, and provide a response within a reasonable time. Any required notice period or scheduling procedure should come from the applicable rule or valid workplace policy; do not assume that a generic notice period from another employer is a legal requirement.
Operational planning can help leave requests be handled fairly. Teams may map minimum staffing for particular shifts, skills or safety-sensitive work, then use transparent criteria when several requests overlap. A process should not depend on who happens to know a manager personally. If a request cannot be granted on the requested dates, a clear explanation and proposed alternative can help the worker plan. The law’s unlimited carry-forward treatment for leave that was applied for but not granted makes it especially important to record the outcome accurately and not simply erase the request from the system.
Build a leave ledger people can understand
A useful leave ledger shows opening balance, current-year days worked, periods counted toward the 180-day test, leave accrued, leave requested, leave approved, days actually taken, holidays excluded from the spell, ordinary carry-forward and any refused leave carried without the ordinary cap. It should also show year-end encashment requests and payments, plus the final balance at separation. Each line should have a date or period and a source record. This is more reliable than a single “available days” number that cannot be explained when a worker changes shifts, joins mid-year or has an application refused.
Reconciliation is easier if the employer compares the ledger with attendance records and leave requests at regular intervals, not just once at year end. Ask whether an apparent discrepancy comes from a missing attendance entry, a duplicated leave day, a holiday treated as leave, an incorrect date range or a carry-forward cap applied to refused days. Correct the underlying source and record why the balance changed. Keep access limited to people who need the data to administer leave, and avoid circulating personal details in a shared spreadsheet or group chat. A worker should be able to request an explanation of their own balance through a practical channel.
Examples: apply the rules without overstating them
Suppose a covered adult worker has worked 200 days in a calendar year and has no relevant special category. The 180-day threshold is met. The general accrual rate is one day for every 20 days of work; 200 days at that rate corresponds to 10 days before considering how the governing rules treat the exact record and any applicable more favourable benefit. This example is only arithmetic to illustrate the rate. It does not decide whether every calendar day in a particular attendance record qualifies as a day of work, or how another law or binding term affects the final balance.
Suppose a worker has 35 days of leave and asks to carry it forward. Under the ordinary carry-forward rule, the next-year carry is capped at 30 days, and the worker is entitled to encash leave above that limit. If the worker had applied for leave with wages and the employer did not grant it, the refused leave may be carried forward without limit under the separate exception. The facts and records determine which rule applies. Do not simply label all 35 days “unused” or all 35 days “refused”; split the balance if it contains both categories and document the basis.
Suppose a worker’s employment ends before they have reached 180 days in the calendar year. Section 32’s separation clause says the worker is entitled to wages for the leave quantum to which they were entitled immediately before separation, even if they have not worked the otherwise required period to become eligible to avail leave. The amount still needs to be calculated from the relevant service and leave record and the preceding clauses. This means the 180-day threshold should not be used as an automatic reason to pay nothing at exit. The deadline for payment depends on the exit circumstance described in the section.
Worker questions worth asking
If a balance looks wrong, start with a focused written request. Ask which dates the employer counted as days worked, which periods it counted only for the 180-day threshold, and what rate it used for accrual. Ask for the leave ledger and the holidays included in a disputed leave spell. If the issue concerns a refused application, identify the request date and ask how the days were classified for carry-forward. If employment has ended, ask how the final leave amount was calculated and when it was paid. Clear questions about dates and arithmetic are easier to answer than an accusation that the entire system is wrong.
Keep copies of requests and responses. If the employer’s explanation does not resolve the issue, compare it with the official text and the applicable Central or State rules. A union representative, worker representative, labour department or qualified labour-law professional may help identify the appropriate route. Do not post another person’s private employment records publicly. If the concern involves retaliation, wage withholding or another serious issue, get advice on a safe and suitable channel. The right forum can depend on the establishment, the applicable government, the worker’s legal status and the nature of the dispute.
Employer questions worth resolving before payroll closes
Employers should confirm which establishments fall under the Code, which government is appropriate, which workers are covered, and whether any more favourable or transitional rule applies. Then test payroll with cases that expose common errors: a worker who joined partway through the year; a worker with a maternity leave or lay-off period; an adult worker and a worker in a special statutory category; a holiday inside a leave spell; ordinary leave above 30 days; an application refused; and an exit before 180 days. Keep test results and rule versions with the payroll configuration so that changes can be reviewed later.
Managers need practical training too. They should know where requests are recorded, how to respond, what to do when dates overlap, and when to involve HR or payroll. They should not promise a legal conclusion they are not authorised to give, nor leave a request in limbo because the calendar is inconvenient. HR should periodically compare written policy, portal behaviour and actual pay records against current official material. Where a system vendor’s default does not match the governing rule, fix the configuration rather than relying on workers to catch each error individually.
What not to infer from the 180-day figure
The 180-day eligibility threshold is not a rule that a worker must remain employed for 180 days before receiving any leave-related payment in all circumstances. The separation clause expressly addresses payment where employment ends earlier. It also is not a universal statement that everyone in every workplace receives exactly the same number of days. Coverage, the worker definition, the commencement date, special statutory categories, a more favourable law or term, and the applicable rules can all matter. Keep the headline figure connected to the rest of section 32 rather than quoting it as a complete answer.
Likewise, a 30-day carry-forward limit does not mean a worker forfeits every day above 30. The section provides for encashment of the excess above the ordinary limit and unlimited carry-forward of leave applied for but refused. A policy that describes only the cap leaves out important protections. Conversely, “unlimited” in this context is tied to the refused-leave clause; it should not be used to describe every unused leave balance. A sound explanation identifies the category of days, the record supporting it and the outcome required by the applicable rule.
Transition, updates and local variation
The Code’s commencement date is 21 November 2025, but an employer should still check the latest official rules, notifications and government FAQs when dealing with a current claim. The Ministry’s Labour Codes page lists the Occupational Safety, Health and Working Conditions (Central) Rules, 2026, and official FAQs discuss annual leave and carry-forward. State rules apply where the State Government is the appropriate government; Central Rules apply where the Central Government is the appropriate government. The relevant government may also issue orders or notifications that affect a covered establishment. Verify the exact jurisdiction and current text instead of treating a national summary as a complete compliance file.
Earlier discussions may refer to the Factories Act or a 240-day threshold. Historical records can matter for periods before the Code came into force, and transition questions should not be resolved by deleting prior balances or assuming every old calculation is invalid. For a present-day entitlement, read the law currently in force and ask how pre-commencement accrual is treated under applicable transitional provisions, rules and decisions. The Ministry has described the newer 180-day threshold as a change from the earlier 240-day eligibility rule. That comparison helps explain the reform but does not itself settle every historical or state-specific question.
A practical close-out checklist
For each calendar year, a worker can keep the appointment or service-start date, attendance or work record, leave requests and acknowledgments, approvals or refusals, holiday dates around leave periods, payslips and any balance statement. At year end, check whether the 180-day test has been applied, whether the accrual rate is correct, whether the carry-forward balance distinguishes ordinary unused days from refused days, and whether an encashment request or excess balance has been dealt with. At exit, ask for the final calculation and note the statutory payment deadline that matches the reason employment ended.
For each establishment, an employer can retain the legal applicability assessment, relevant orders and rules, the policy version, system configuration, payroll test cases, worker communications and reconciliation records. Give workers an accessible way to see or query their own balance. Correct mistakes promptly and preserve an audit trail of the correction. Where the legal position is genuinely uncertain, pause the assumption, consult current official sources and obtain professional advice rather than turning a software setting into a legal rule. Leave administration is strongest when both the entitlement and the arithmetic are visible.
Official reading
For the statutory text, consult section 32 of the Occupational Safety, Health and Working Conditions Code, 2020, through India Code and the Ministry of Labour and Employment’s published Code materials. The Ministry’s official FAQs on the OSH Code discuss the 180-day threshold, carry-forward, refused leave and encashment. The Ministry’s employer compliance handbook summarises the Code and related duties. Read the current applicable Central or State rules and any establishment-specific order alongside those sources; a short article cannot replace them.
India Code: Occupational Safety, Health and Working Conditions Code, 2020
Ministry of Labour and Employment: Labour Codes and rules
Ministry FAQ: Occupational Safety, Health and Working Conditions Code
Ministry FAQ: Labour Codes, leave carry-forward and encashment
This content is a collection of ancient history,books and various articles and collection of library and news and other post ; all details may not be the same. Readers are requested to verify the information themselves. Readers are not allowed to take any disciplinary action; content is only for educational purposes. If readers do not agree about the contents, they may send a personal comment to my personal email ID: achary.purna@gmail.com
