Overtime Rules in India: Calculation & Policy Guide

Overtime rules in India have quietly become one of the most audited, most disputed and least well-documented areas of payroll compliance. Most Indian employers can tell you their leave policy from memory. Far fewer can explain, on the spot, how their overtime calculation actually works: which wage components sit in the base, what happens when someone is on stand-by at 11 pm, whether a compensatory off can lawfully replace an overtime payment, and where the register that proves all of it is stored.

That gap is getting expensive. As the four labour codes and the associated central and state rules move into force, working hours, spread-over, rest intervals and overtime wages are being re-stated in a single consolidated framework rather than scattered across a dozen older statutes. Inspectors, auditors, acquirers doing diligence and employees themselves are asking sharper questions. And hybrid work, always-on support teams, field sales and 24x7 operations have made "when exactly does the working day end?" a genuinely hard question to answer.

This guide is a practical walkthrough of overtime rules in India for HR managers, founders and payroll teams: the statutory framework, how to build a defensible overtime calculation, how to treat on-call and comp-off, how to capture hours accurately in an attendance system, and a rollout playbook you can run in a quarter.

A note before we start. Working hours and overtime are governed by a mix of central legislation and state-specific Shops and Establishments rules, factory rules and notifications, and the position changes as codes and state rules are notified. Everything below is general guidance to help you design a sound process. Always verify the current central and state provisions applicable to your specific establishments — and the specific rates and limits in force — with qualified counsel before you finalise policy or run payroll.

Why overtime rules in India are getting fresh attention

Three things changed at roughly the same time, and they compound.

Consolidation of the statutory framework. The four labour codes bring wages, industrial relations, social security, and occupational safety and health under a smaller set of instruments. Working hours, daily and weekly limits, spread-over, weekly rest and overtime wages sit largely within the occupational safety and health framework, while the definition of "wages" — which drives your overtime wage base — sits within the wage framework. That linkage between the definition of wages and the overtime rate is the single most important structural change for payroll teams to understand.

State rules are being notified separately. The codes set the frame; states fill in the detail. Daily hour limits, permitted overtime in a quarter, spread-over caps, the exact overtime multiple, and record-keeping formats can all vary by state and by establishment type. A company with an office in Bengaluru, a warehouse in Bhiwandi and a support centre in Noida may be operating under three different sets of operational rules simultaneously.

Work patterns have outrun policies. Support rotas, night shifts, extended month-end closes, festival-season warehouse surges, on-call engineering rotations and field staff who log in from the road all generate hours that the policy written in 2019 never contemplated. When a dispute arises, the employer's attendance data is usually the only evidence available — and it is often incomplete.

The employers who handle this well are not the ones with the most complex policies. They are the ones who can produce, within a day, a clean record showing hours worked, who approved the extra hours, what wage base was used and what was paid.

The statutory framework: working hours, rest and overtime

Which law applies to your workforce

Start by mapping your establishments, because the applicable rules follow the nature of the establishment and its location, not your org chart.

• Manufacturing units and factories are typically governed by factory-type provisions on hours, rest intervals, weekly holidays, spread-over and overtime, now largely restated in the occupational safety and health framework and its rules.
• Shops, commercial establishments, offices, IT/ITES units, restaurants and retail are typically governed by the Shops and Establishments legislation of the relevant state, plus the applicable central framework. This is where variation is widest.
• Construction sites, mines, plantations, transport, beedi and cigar, and other specified sectors attract additional sector-specific provisions.
• Contract workers and staffing-agency personnel deployed at your premises bring principal-employer obligations. Their hours, overtime and records matter to you even though they are not on your payroll.

If you operate across states, you need a matrix — establishment by establishment — rather than a single national policy. More on how to build that later.

Daily and weekly working hour limits

The broad architecture across Indian working-hours law is consistent even where the numbers vary:

• A daily cap on ordinary working hours, commonly expressed as eight or nine hours in a day depending on the statute and state.
• A weekly cap on ordinary working hours, commonly expressed around forty-eight hours in a week.
• A maximum spread-over — the total elapsed time from start to finish of the working day, including rest intervals — commonly expressed as ten-and-a-half or twelve hours depending on the applicable rules.
• A mandatory rest interval after a defined stretch of continuous work, commonly after five or six hours, of at least half an hour.
• A weekly off — at least one day of rest in a week, with rules about substituting the day and about the maximum number of consecutive days worked without a rest day.
• Ceilings on overtime hours in a week, a quarter or a year, above which additional hours are not permitted at all — no matter how willing the employee is or how much you are prepared to pay.

That last point deserves emphasis because it is routinely missed. Overtime rules in India are not purely a pay question. There are limits beyond which extra hours are simply not lawful. Paying double for hours that exceed the statutory ceiling does not cure the breach; you have then created a payment record that documents the breach.

Spread-over and why it trips up shift operations

Spread-over is the total window from the first hour of work to the last, inclusive of breaks. A shift that starts at 9 am, breaks from 1 pm to 4 pm, and resumes until 9 pm may involve only nine hours of actual work but a twelve-hour spread-over. Split shifts in hospitality, retail, logistics and facilities management routinely breach spread-over caps while looking perfectly fine on an hours-worked report.

If you run split shifts, your attendance system needs to compute and flag spread-over as a distinct metric, not just total hours.

Weekly offs and the substitution question

Most frameworks permit a weekly off to be substituted for another day, subject to conditions — typically that the substituted day falls within a defined window before or after, and that the employee does not work more than a defined number of consecutive days without rest. Some rules require notice or display of the substituted day.

The compliance failure mode here is informal substitution: a manager asks someone to come in on Sunday and take Wednesday off, nobody records it, and the attendance system shows a worked weekly-off with no compensating rest day. That single unrecorded swap is what turns into a claim two years later.

The overtime wage rate concept

Across the Indian framework, where an employee works beyond the prescribed daily or weekly ordinary hours, overtime wages are payable at a premium multiple of the ordinary rate of wages — typically twice the ordinary rate, subject to the applicable law and state rules.

Two practical implications follow:

1. The multiple is not the hard part. Doubling a number is easy. The hard part is what you are doubling.
2. The base is the hard part. "Ordinary rate of wages" is a defined concept, and getting it wrong understates every overtime payment you have ever made — which is exactly the kind of systematic error that produces large arrears findings in an audit.

Some employers also apply a higher multiple, or a flat premium, for work on a weekly off or a national or festival holiday. That may come from the applicable rules, from a settlement or standing orders, or from company policy. Whichever it is, write it down and apply it consistently.

Getting the overtime wage base right

This is where most overtime calculation errors live, so it is worth going slowly.

The "ordinary rate of wages" idea

Conceptually, the ordinary rate of wages for overtime purposes is meant to reflect what the employee ordinarily earns for ordinary hours — not just the line item labelled "basic". Depending on the applicable statute and rules, it commonly includes basic wages, dearness allowance where applicable, and allowances that are part of ordinary remuneration, while typically excluding items such as bonus payments and, in many formulations, overtime itself.

What this means in practice: an employer who calculates overtime on basic salary alone, when the applicable framework contemplates a broader base, is systematically underpaying. Multiply that by a few hundred employees over a few years and the exposure is material.

The wage-definition linkage you cannot ignore

The wage framework introduced a structural concept that payroll teams need to internalise: a floor on what proportion of total remuneration must be treated as "wages". Broadly, the definition of wages includes basic pay, dearness allowance and retaining allowance while excluding a specified list of items (certain allowances, conveyance, house rent allowance, overtime, commission, and so on) — but with a critical proviso: where the excluded components exceed a specified share of total remuneration (commonly framed as one-half), the excess is deemed to be wages.

The practical effect on many Indian salary structures, which historically kept basic low and allowances high, is that the deemed-wages rule pushes the statutory wage base upward. Since overtime is calculated on a wage-based concept, that same upward pressure flows into your overtime rate.

Action for payroll teams: do not assume your overtime base equals your PF base equals your gratuity base equals "basic + DA" as configured in 2018. Re-derive each base from the current definitions applicable to you, document the derivation, and encode it in the payroll engine as a named formula rather than a hardcoded column.

What typically sits inside and outside the base

The table below is a working framework for the conversation with your advisers. Treat it as a checklist of components to classify, not as a legal determination — the correct classification depends on the applicable statute, rules and the facts of your structure.

Converting a monthly salary to an hourly overtime rate

Once you have the correct base, you need a divisor. Three conventions are common in Indian payroll, and the one you choose must be stated in policy and applied consistently:

• Days-in-month divisor: monthly wage base ÷ actual calendar days in the month ÷ standard daily hours.
• Fixed 26-day divisor: monthly wage base ÷ 26 ÷ standard daily hours. Widely used where a six-day week and paid weekly off are the norm.
• Standard-hours divisor: monthly wage base ÷ (standard weekly hours × 52 ÷ 12). Cleaner for five-day-week knowledge-work settings.

The divisor materially changes the answer. On a monthly base of ₹26,000 with an eight-hour standard day:

• 26-day divisor → daily rate ₹1,000 → hourly ₹125.00
• 30-day divisor → daily rate ₹866.67 → hourly ₹108.33
• 48-hours-per-week standard-hours divisor → 208 hours per month → hourly ₹125.00

A 15% spread between conventions on the same salary is not a rounding issue. Pick your convention, justify it against the applicable rules and any settlement or contract, document it, and never let two entities in the same group quietly run different conventions.

Overtime calculation in India: a step-by-step method

Here is the sequence to encode in your process and your system.

Step 1 — Establish the standard. For each establishment and employee category, record the standard daily hours, standard weekly hours, the spread-over cap, the rest-interval rule, the weekly off day, and the applicable overtime multiple. This is your rules matrix.

Step 2 — Capture actual hours. Pull clock-in and clock-out from the attendance system, net of unpaid breaks. Apply rounding rules consistently — for example, to the nearest five or fifteen minutes — and state the rule in policy. Do not round only in the employer's favour; asymmetric rounding is an audit red flag.

Step 3 — Identify eligible overtime. Compare actual worked hours against the daily and weekly standard. Decide, in policy, whether overtime accrues on a daily basis, a weekly basis, or the greater of the two, and stick to it. Exclude hours that were not authorised under your approval workflow only if your policy genuinely provides for that — and be aware that a blanket "unapproved hours are unpaid" rule is a weak position if you knowingly let the work happen.

Step 4 — Derive the wage base. Compute the correct monthly wage base for that employee for that month, applying the deemed-wages proviso where relevant.

Step 5 — Derive the hourly rate. Apply your documented divisor.

Step 6 — Apply the multiple. Multiply eligible overtime hours by the hourly rate by the applicable multiple (typically twice the ordinary rate, subject to the applicable law and state rules). Apply any higher multiple for weekly offs or holidays if your rules or policy require it.

Step 7 — Check the ceilings. Before you pay, verify that overtime hours do not exceed the permitted weekly, quarterly or annual limits, and that spread-over and consecutive-days rules were respected. Breaches need escalation, not a silent payment.

Step 8 — Pay in the same wage period. Overtime should ordinarily be paid with the wage period in which it was earned, or per the timeline specified by the applicable rules. Chronic lagging of overtime into later months is both a compliance and a trust problem.

Step 9 — Record it. Update the overtime register and the muster roll / attendance record with the hours, the dates, the rate and the amount paid, in the format prescribed by the applicable rules.

Step 10 — Reconcile. Each month, reconcile total overtime hours in the attendance system against overtime hours paid in payroll, and investigate any variance above a small threshold.

Worked examples of overtime calculation

Numbers make this concrete. The figures below are illustrative and use a two-times multiple purely for demonstration; apply the multiple, divisor and base that your applicable rules and policy actually require.

Example 1: A six-day-week operations executive

Priya works at a commercial establishment on a six-day week, eight hours a day, with Sunday as her weekly off. Her monthly wage base for overtime purposes, after applying the correct definition, is ₹26,000. The establishment uses a 26-day divisor.

• Daily rate: ₹26,000 ÷ 26 = ₹1,000
• Hourly rate: ₹1,000 ÷ 8 = ₹125
• Overtime rate at two times: ₹250 per hour

In a month, Priya works two extra hours on each of six weekdays during a system migration: 12 overtime hours.

• Overtime wages: 12 × ₹250 = ₹3,000

Her gross for the month becomes her regular salary plus ₹3,000, shown as a distinct overtime line item on the payslip.

Example 2: A five-day-week support engineer with weekend work

Arun works a five-day week, nine hours a day, standard weekly hours of 45. His monthly wage base is ₹45,000. The establishment uses a standard-hours divisor: 45 × 52 ÷ 12 = 195 hours per month.

• Hourly rate: ₹45,000 ÷ 195 = ₹230.77
• Overtime rate at two times: ₹461.54 per hour

In a month he works:

• 4 hours of weekday overtime → 4 × ₹461.54 = ₹1,846.15
• 8 hours on a weekly off during a release weekend → 8 × ₹461.54 = ₹3,692.31

Total overtime: ₹5,538.46 for 12 hours.

Two things to notice. First, the same 12 overtime hours cost the employer far more for Arun than for Priya, because the wage base differs — which is exactly why the base matters more than the multiple. Second, if the applicable rules or company policy set a higher premium for work on a weekly off, the second line would rise accordingly, and the system must be able to apply different multiples to different day types.

Example 3: The wage-base correction that changes everything

Ravi's cost to company is structured as: basic ₹12,000, HRA ₹6,000, conveyance ₹2,000, special allowance ₹10,000. Total monthly remuneration: ₹30,000.

The old (incorrect) approach — overtime on basic only, 26-day divisor, eight-hour day:

• Hourly: ₹12,000 ÷ 26 ÷ 8 = ₹57.69
• Overtime at two times: ₹115.38 per hour
• 20 overtime hours → ₹2,307.69

The corrected approach applying the deemed-wages proviso — excluded components (HRA ₹6,000 + conveyance ₹2,000 + special allowance ₹10,000) total ₹18,000, which is 60% of ₹30,000, exceeding the one-half threshold. The excess of ₹3,000 over the ₹15,000 half-mark is deemed to be wages, so the statutory wage base becomes ₹12,000 + ₹3,000 = ₹15,000.

• Hourly: ₹15,000 ÷ 26 ÷ 8 = ₹72.12
• Overtime at two times: ₹144.23 per hour
• 20 overtime hours → ₹2,884.62

That is a 25% increase on the same hours, from a change nobody sees on a payslip line. Across a workforce of 300 people over three years, an error of that shape is the sort of finding that turns a routine review into a provisioning exercise. This is a simplified illustration of the mechanic — confirm the precise computation applicable to your structure with your advisers.

A quick reference table

On-call, stand-by and the grey zones

Indian working-hours law was written primarily for physical workplaces where presence and work were the same thing. Modern operations break that assumption, and this is where most policy gaps sit.

The core question: is the employee working or merely available?

The distinction that matters is between time during which an employee is genuinely free to use as they wish, subject only to being reachable, and time during which their freedom is materially constrained by the employer's requirements. The more constrained the employee, the stronger the argument that the time counts as working time.

Useful factors to think through:

• Response-time requirement. A 15-minute response obligation constrains behaviour far more than a "respond within two hours" expectation.
• Location restriction. Being required to remain at or near the premises is a strong indicator of working time. Being free to be anywhere with connectivity is weaker.
• Frequency of actual call-outs. An on-call rotation that is activated three times a night is functionally a night shift.
• Ability to substitute or decline. If the employee can swap out of the rota, the constraint is softer.
• Equipment and readiness obligations. Requirements to remain sober, in uniform, or with equipment ready point toward working time.

A workable policy structure for on-call

Rather than trying to answer the metaphysical question in every case, most Indian employers land on a layered structure:

1. A stand-by allowance for being on the rota — a fixed amount per on-call shift or per week, paid regardless of whether the employee is called.
2. Actual engaged time treated as working time, captured from the ticketing, telephony or incident system, and fed into hours worked. If that time pushes the employee past daily or weekly standards, overtime rules apply.
3. A minimum engagement block — for example, any call-out is counted as at least one hour of engaged time — so that a four-minute 3 am call is not recorded as four minutes.
4. A rest-after-callout rule — if an employee is engaged for more than a defined period during the night, they get a delayed start or a rest day, protecting both compliance and safety.
5. A cap on consecutive on-call weeks to prevent the same two engineers absorbing the entire rota.

Document how the stand-by allowance interacts with the overtime wage base. If it is a fixed monthly allowance, it may affect the exclusion-cap computation described earlier; if it is a variable per-shift payment, the treatment may differ. Get this classified explicitly rather than by default.

Travel, training and "just checking email"

• Travel between home and the usual workplace is ordinarily not working time. Travel between work sites during the day, or travel that the employer requires outside ordinary hours as part of the job, is more likely to be.
• Mandatory training is generally working time. Voluntary, self-paced learning is generally not — but "voluntary" needs to be genuinely voluntary.
• After-hours messaging is the hardest. A message-response culture that keeps people effectively on duty until midnight creates both compliance risk and burnout. The realistic controls are norms (no-expectation-of-response windows), tooling (scheduled send, escalation paths rather than direct pings), and an escape valve for genuine incidents that is logged when used.

Comp-off versus overtime pay

Compensatory off is the most commonly misused instrument in Indian HR practice. It is popular because it is cash-neutral. That is precisely why it needs guardrails.

The central point

Where a statute requires overtime wages at a premium rate for hours worked beyond the prescribed limits, a compensatory off is generally not a substitute for that monetary entitlement. Comp-off is best understood as an additional rest benefit, or as the mechanism for handling substituted weekly offs where the applicable rules permit substitution, rather than as a currency you can pay overtime in.

Some frameworks do contemplate compensatory holidays in specific circumstances — for example, where a weekly holiday is lost due to permitted exemptions. Those are defined situations with defined conditions, not a general licence.

The safe operating rule for most employers: use comp-off for extra full days worked by employees for whom overtime wages are not statutorily triggered, and use overtime wages where the statute triggers them. Where you are unsure, take advice for that specific employee category and state.

Comparison at a glance

If you run comp-off, run it properly

• Set an expiry — typically 30 to 90 days — and enforce it in the system, with a reminder to the employee and manager before lapse.
• Track provenance. Every comp-off credit should point to the specific date worked that generated it. An untraceable balance is unusable evidence.
• Decide the exit treatment in advance and state it in policy: lapse, encash, or must-be-taken-during-notice.
• Watch the accrual pattern. If one team generates comp-off relentlessly, you have a staffing problem, not a leave-policy problem.
• Never let comp-off be granted verbally. If it is not in the system, it does not exist — and that cuts both ways.

Exempt versus non-exempt in the Indian context

Indian law does not use the American "exempt / non-exempt" vocabulary, and importing that mental model wholesale causes errors. But an analogous question does exist: which employees are covered by working-hours and overtime provisions at all?

The coverage question in India typically turns on:

• The statute applicable to the establishment, and whom it defines as a worker, employee or person employed.
• Category-based exclusions in the applicable statute or state rules — many frameworks exclude or partially exclude persons in positions of management, in a confidential capacity, or in supervisory roles above a wage threshold, and sometimes travelling staff or those whose hours are inherently unmeasurable.
• Wage thresholds, where applicable, above which certain provisions may not apply.
• The substance of the role, not the title. Designating someone "Assistant Manager" does not exclude them if their actual duties are non-supervisory and non-managerial. Title inflation is common in Indian startups and is a genuine liability when the underlying work is operational.

How to run the coverage assessment

1. List every role, not every person, in each establishment.
2. For each role, capture the substance: does the person supervise others, exercise independent judgement on material matters, hire/discipline, control their own hours, handle confidential business information as a core function?
3. Map against the applicable statute and state rules for that establishment.
4. Classify into three buckets: clearly covered by overtime provisions; clearly outside; genuinely uncertain.
5. Take advice on the uncertain bucket and record the reasoning. A short written rationale per role, dated and approved, is disproportionately valuable if challenged later.
6. Re-run annually and whenever a role's scope changes materially.

The pragmatic middle path

Many Indian employers adopt a deliberately generous position for borderline roles: they either pay overtime, or they provide a clearly documented alternative benefit (a shift allowance, a compensatory rest structure, a higher fixed component) that is transparently linked to the extended-hours expectation. The cost of being generous to a small borderline population is almost always lower than the cost of defending a misclassification across a large one.

What does not work: classifying broadly as "exempt" because the employees are salaried, or because they are in an office, or because "nobody in our industry pays overtime to that level". Industry practice is not a defence.

Capturing overtime accurately in your attendance system

Every overtime dispute is ultimately an evidence dispute. Your attendance system is the evidence.

What good capture looks like

• Event-level timestamps, not daily summaries. Store every punch, swipe, geo-check-in or session event with its source. Summaries can be recomputed; raw events cannot be reconstructed.
• A single source of truth. Biometric devices, mobile check-in, web check-in and access-control logs should flow into one attendance ledger with a recorded source per event. Three systems that disagree are worse than one imperfect system.
• Break handling that matches policy. If breaks are unpaid and deducted, capture them. If they are auto-deducted, state that clearly in policy and give employees a way to flag days when they worked through.
• Shift-aware computation. A night shift crossing midnight must be attributed to one work date, not split across two. Get this wrong and every overnight shift generates phantom overtime or lost hours.
• Spread-over as a first-class metric, especially for split shifts.
• Rounding rules applied symmetrically and disclosed.
• Exception flags, not silent corrections. Missing punches, over-long shifts, unapproved overtime, spread-over breaches and consecutive-days breaches should raise a visible exception with an owner and a resolution status.
• An immutable audit trail. Every manual adjustment must record who changed what, from what to what, when, and why. Edit rights should be narrow and reviewed.
• Retention aligned to the applicable rules — commonly several years — with the data actually retrievable, not archived into a format nobody can open.

Field, remote and hybrid staff

For field and remote employees, presence-based capture does not work. Practical approaches:

• Geo-tagged mobile check-in and check-out, with the location recorded at the event and a clear privacy notice explaining that location is captured only at punch events, not continuously.
• Task or visit completion as a corroborating signal — check-ins to customer sites, tickets closed, deliveries confirmed.
• Self-declared hours with manager attestation for genuinely unmeasurable roles, with random sampling and periodic review.
• Written expectations about after-hours availability, so that the boundary is defined rather than assumed.

Whatever you choose, be explicit with employees about what is captured and why. Attendance monitoring that feels covert damages trust far more than it protects compliance.

Common capture failures worth auditing for

• Employees clocking out at the scheduled time and continuing to work.
• Managers instructing teams not to record extra hours to protect a budget line.
• Overtime approvals granted after the fact, in bulk, without review.
• Devices at a site that have been offline for weeks with nobody noticing.
• Contractor staff whose hours are tracked by the vendor in a spreadsheet you never see.

Approval workflows that hold up in an audit

An approval workflow has two jobs: control cost before it is incurred, and produce evidence afterwards.

The pre-approval path

1. Request — the employee or the manager raises an overtime request with the date, expected hours and business reason, ideally before the hours are worked.
2. Manager approval — first-level approval against a team budget or hours quota.
3. Threshold escalation — requests above a defined number of hours, or that would push the employee toward a statutory ceiling, route to a second approver (department head, HR or plant head).
4. Compliance check — the system validates against daily, weekly and quarterly caps, spread-over, and consecutive-days rules before the request can be approved.
5. Actualisation — approved hours are reconciled against actual clocked hours; variance beyond a tolerance goes back for confirmation.
6. Payroll lock — approved and actualised hours flow to payroll on a cut-off date, after which changes go to the next cycle as arrears with a reason code.

Handling emergencies and retrospective approval

Real operations produce unplanned overtime: an incident at 2 am, a shipment that must go out, a system that will not close. Build a defined exception path rather than pretending it will not happen — a retrospective approval route with a short window (say 48 hours), a mandatory reason, and monthly reporting of retrospective approvals as a percentage of total. If that percentage stays above 20–30%, your planning is the problem, not your workflow.

Governance signals to monitor monthly

• Overtime hours by team, by employee and by month, with trend.
• Employees approaching or breaching statutory ceilings.
• The top ten overtime earners, and whether the same names recur every month.
• Retrospective approvals as a share of total.
• Attendance exceptions open beyond a defined ageing threshold.
• Variance between attendance-system overtime hours and payroll-paid overtime hours.

Chronic overtime concentrated in a few individuals is nearly always a headcount, scheduling or skills-coverage issue. Overtime that is systematically approved but never questioned eventually becomes an implied contractual term, and withdrawing it later becomes its own dispute.

Payroll integration: from hours to payslip

The handoff between attendance and payroll is where clean data goes to die. A few principles.

One flow, one cut-off. Attendance closes, exceptions are resolved, approvals are final, and only then does payroll pull. Manual re-keying between systems is the leading cause of overtime payment errors in mid-sized Indian companies.

Overtime as a distinct earnings head. Show it on the payslip as its own line — ideally with hours and rate, not just an amount. Employees who can see the arithmetic raise fewer disputes, and a payslip that shows hours and rate is strong evidence.

Correct statutory treatment of the overtime component. Overtime wages are generally taxable as salary and subject to TDS. Their treatment for PF and ESI purposes follows the applicable definitions and thresholds, and is not something to assume — confirm it, configure it, and document the configuration. Note that overtime earnings can push an employee's gross across an ESI wage threshold in a given month, which needs a defined handling rule.

Arrears with reason codes. Late overtime should be paid as identifiable arrears, tagged to the month it relates to, so that the register and payroll can be reconciled after the fact.

Multi-state configuration. If you operate across states, the rules matrix must be encoded per establishment: standard hours, multiple, ceilings, register format. A single global overtime rule across a multi-state footprint is a compliance gamble.

Month-end reconciliation as a standing control. Three numbers should tie every month: overtime hours computed by the attendance system, overtime hours approved in the workflow, and overtime hours paid in payroll. Investigate and document every material variance.

Registers, records and returns

Documentation is not administrative overhead here; it is the entire defence.

Depending on the applicable statute and state rules, employers are typically expected to maintain:

• A register of workers / muster roll with attendance.
• An overtime register or record capturing dates, overtime hours, the rate, and amounts paid.
• A wage register and wage slips in the prescribed form.
• Records of rest intervals, weekly offs and substituted holidays.
• Notices of periods of work and shift schedules, displayed as required.
• Records for contract labour engaged at your premises.
• Any annual or periodic returns required in your state, and any registrations or renewals.

Increasingly, rules permit electronic maintenance of registers, which is a significant practical benefit — but only if your electronic records contain the prescribed fields, can be produced in the prescribed format on demand, and carry a credible audit trail. An HRMS report that is missing two mandated columns is not a compliant register.

Verify formats and retention periods for each state in which you operate, and re-verify when state rules are amended. Formats change; a register you set up three years ago may no longer match the notified form.

Common disputes and audit risks

Three additional situations deserve specific attention.

Diligence. Buyers and investors increasingly test overtime and working-hours compliance directly, because it is quantifiable. Expect requests for attendance data, overtime registers, the wage-base derivation and a sample recomputation. A clean answer here removes an escrow conversation.

Exit disputes. Overtime and comp-off claims cluster around resignations and terminations. Whatever your system says at the moment of exit is what you will be arguing from.

Collective escalation. Overtime grievances tend to move from individual to collective quickly, because the underlying calculation error is usually systematic. A single query about the wage base is worth investigating seriously the first time it is raised.

A rollout playbook for SMBs and startups

You do not need a six-month programme. You need ninety focused days.

Days 1–30: establish the facts

• Build the establishment matrix. Every registered location, its statute, its state, headcount, shift patterns and whether contract labour is engaged.
• Extract twelve months of attendance data and compute, for each establishment: hours beyond standard, spread-over breaches, weekly-off violations, consecutive-day runs. Do not fix anything yet — measure.
• Recompute the wage base for a representative sample of employees using the current definitions, and compare to what payroll currently uses. Quantify the gap.
• Inventory registers and records against the prescribed formats for each state. Note what is missing.
• Run the role-coverage assessment and produce the three-bucket classification.
• Take advice on the uncertain items: coverage bucket, wage base derivation, the applicable multiple and divisor per establishment, and register formats.

Output: a one-page risk summary with quantified exposure, and a decision list for leadership.

Days 31–60: decide and configure

• Write the working-hours and overtime policy. One document, plain language, covering standard hours, rest intervals, weekly offs and substitution, overtime eligibility and rate mechanics, approval workflow, on-call and stand-by, comp-off rules and expiry, and record retention.
• Configure the system to match the policy: shift definitions per establishment, overtime rules, spread-over and ceiling validations, approval routing and thresholds, exception flags, register outputs.
• Fix the payroll mapping: overtime as a distinct earnings head, correct base formula, correct divisor, correct statutory treatment, arrears reason codes.
• Decide the remediation position on any historical gap, with advice. Options range from prospective correction to voluntary back-payment; the choice depends on materiality and risk appetite, and should be a documented leadership decision rather than an implicit one.
• Train managers. They are the control point. They need to understand that suppressing hours creates liability, that approval is a real decision, and that chronic overtime is a resourcing signal to escalate.

Days 61–90: run, monitor and prove

• Go live on the new configuration from a clean wage period.
• Communicate to employees: what changes, how overtime is now calculated, how to raise a query, and what to do if hours are not recorded correctly.
• Run the monthly control pack: overtime by team, ceiling proximity, retrospective-approval rate, open exceptions, attendance-to-payroll reconciliation.
• Do a first-cycle deep review — sample twenty employees, recompute overtime by hand, and confirm the system matches.
• Schedule the standing cadence: monthly control pack, quarterly register and format check, annual policy and coverage review, and a review trigger whenever central or state rules change.

A note on sequencing for very small teams

If you are a twenty-person startup, compress this. Get three things right in the first month: know which statute applies to your establishment, capture hours honestly in one system, and pay overtime where it is triggered on a wage base you have had checked. The registers and workflow sophistication can follow. What you cannot do is defer the honest capture of hours — everything else can be rebuilt later from good data, and nothing can be rebuilt from bad data.

Frequently asked questions

Is overtime pay mandatory in India for all employees? No. Overtime entitlements depend on the statute applicable to the establishment, the state rules, and whether the individual falls within the covered category. Many operational, clerical and technical roles are covered; persons in genuinely managerial, supervisory or confidential roles may be treated differently under the applicable framework. The assessment must be based on the substance of the role, not the job title, and should be documented and reviewed with advice.

What is the standard overtime rate in India? Overtime wages are commonly payable at a premium multiple of the ordinary rate of wages — typically twice the ordinary rate, subject to the applicable law and state rules. Some rules or agreements provide for a higher premium for work on weekly offs or specified holidays. Confirm the multiple applicable to each of your establishments; do not assume one national figure.

Which salary components go into the overtime calculation base? The base is built on the statutory concept of wages, which ordinarily includes basic pay and dearness allowance where applicable, while excluding items such as HRA, conveyance, statutory bonus, commission and overtime itself. Critically, where excluded components exceed a specified share of total remuneration, the excess is deemed to be wages — which pushes the base up for many Indian salary structures. Calculating overtime on basic alone is the most common and most expensive error.

Can we give compensatory off instead of paying overtime? Generally, where a statute requires overtime wages at a premium rate, a compensatory off does not substitute for that monetary entitlement. Comp-off works well as an additional rest benefit, and for handling substituted weekly offs where the rules permit substitution. Where you plan to rely on comp-off for a category of employees, get that specific position confirmed for your state and establishment type.

How should we treat on-call and stand-by time? Assess how materially the employee's freedom is constrained: response-time obligations, location restrictions, frequency of actual call-outs and ability to decline. A practical structure pays a stand-by allowance for being on the rota, treats actual engaged time as working time with a minimum engagement block, and adds rest-after-callout protection. Document the policy, capture engaged time from the incident or ticketing system, and classify the allowance explicitly for wage-base purposes.

Are there limits on how much overtime an employee can work? Yes. Beyond premium pay, most frameworks impose ceilings on overtime hours in a week, quarter or year, along with spread-over caps and rules on consecutive days worked without rest. Exceeding these is a breach regardless of how much you pay or how willing the employee is. Build these as hard validations in your approval workflow, not advisory warnings.

What records do we need to keep, and for how long? Typically a muster roll or attendance register, an overtime register showing dates, hours, rate and amount, wage registers and wage slips, records of rest intervals and weekly offs including substitutions, and applicable returns. Retention periods and formats are set by the applicable rules and vary by state. Electronic registers are increasingly permitted, provided they carry the prescribed fields and can be produced in the prescribed format with a credible audit trail.

We discovered we have been calculating overtime on the wrong base. What now? Quantify the gap first — by employee, by month, for the full look-back period. Then take advice on the remediation position, which may range from prospective correction to voluntary back-payment depending on materiality. Fix the configuration before the next payroll cycle so the error stops growing, document the leadership decision on historical treatment, and communicate clearly to affected employees. What you should not do is correct it silently and hope nobody reconciles backwards.

Bringing it together

Overtime rules in India reward employers who are boringly systematic. The framework is not conceptually hard — a standard number of hours, a premium rate above it, ceilings you cannot exceed, rest you must provide, and records that prove all of it. What makes it hard in practice is that the details vary by statute and state, the wage base is easy to get wrong, and the evidence lives in an attendance system that nobody audits until there is a problem.

If you do only five things after reading this:

1. Re-derive your overtime wage base against the current definitions and have it checked.
2. Pick and document one divisor convention per establishment.
3. Make your attendance system compute spread-over, ceilings and weekly-off breaches as visible exceptions.
4. Put a real approval workflow in front of overtime, with hard validations.
5. Reconcile attendance overtime hours against paid overtime hours every single month.

Those five controls prevent the large majority of overtime disputes and audit findings we see Indian employers walk into.

Getting this right is much easier when attendance, shift rules, approvals, comp-off tracking and payroll live in one system rather than four spreadsheets and a WhatsApp group. CozyHR is built for exactly this: multi-state shift and working-hours configuration, biometric and mobile attendance capture, spread-over and ceiling flags, overtime approval workflows, comp-off with expiry tracking, and a direct handoff into Indian payroll with statutory registers you can actually produce on demand.

If overtime calculation is currently a monthly spreadsheet exercise for your team, it does not have to be. Try CozyHR and see what a clean, audit-ready working-hours process looks like for your business.

This article is general information for HR and payroll professionals and is not legal advice. Working-hours and overtime obligations vary by statute, establishment type and state, and change as central and state rules are notified. Verify the current provisions applicable to your establishments with qualified professional advisers before finalising policy or processing payroll.