Overtime Rules and Calculation in India: Payroll Guide

Ask ten Indian HR managers how they handle extra hours and you will get ten different answers. Some pay a flat per-hour rate that was fixed years ago and never revisited. Some hand out compensatory off and hope nobody asks questions. Some genuinely do not know whether their supervisors are entitled to anything at all. And a surprising number discover, usually during an inspection or a due-diligence exercise, that their approach to overtime calculation in India has quietly diverged from what their own appointment letters promise.

Overtime is one of those payroll areas that looks trivial until you model it properly. The arithmetic is simple — hours multiplied by a rate multiplied by a premium — but almost every input to that arithmetic is contested. Which hours count? Which salary components form the base? Which employees are covered? What happens when a shift crosses midnight, or when someone works on their weekly off, or when the attendance device records a punch at 6:58 pm instead of 7:00 pm?

This guide walks through the whole chain: the legal principles that shape overtime rules India-wide, the mechanics of the overtime pay calculation formula, four fully worked examples with illustrative numbers, the policy and approval design that keeps costs sane, and the system configuration that turns attendance into a defensible payroll output. It is written for people who actually have to run the month-end, not for people who only have to talk about it.

A quick note before we start: this article explains principles and mechanics. It is not legal advice, and it deliberately avoids quoting specific statutory figures, thresholds or dates, because those vary by state, establishment type and employee category and they change. Confirm the exact rules that apply to your establishment with the relevant official notification or a qualified advisor.

Why Overtime Became a Live Payroll Issue

For years, overtime in many Indian organisations was managed by convention rather than by calculation. Factories had registers. Offices had an informal understanding that extra hours came with the job. Nobody reconciled the two.

Three things changed that.

The consolidation of labour law into four codes

India spent decades with dozens of separate central labour statutes, each with its own definitions, its own registers and its own coverage rules. The consolidation of that body of law into four codes — covering wages, industrial relations, social security, and occupational safety, health and working conditions — did more than reduce the number of documents.

It created, for the first time, a common definition of "wages" that flows across statutory payments. That single change has a direct and material effect on overtime, because overtime is calculated on a wage base, and if the definition of the base moves, every OT amount in your payroll moves with it.

It also standardised language around working hours, rest, weekly off and the treatment of extra hours across establishment types that previously sat under entirely different statutes. State-level rules and notifications still carry a great deal of the operational detail, so the picture is not uniform — but the underlying architecture is far more consistent than it used to be.

The emphasis on a defined working week and daily limits

The regulatory direction of travel is clear: a defined ordinary working week, a cap on daily hours, a limit on how long the working day can be spread across the clock, mandatory rest intervals, and a weekly day of rest. The commonly referenced benchmark in Indian practice is a forty-eight hour working week, with daily limits and spread-over limits layered on top.

What matters for payroll is not just the number but the structure. A forty-eight hour week can be arranged as six eight-hour days, five days of nine-and-a-bit hours, or four longer days — and the arrangement you choose determines when overtime starts accruing for each employee. Get the standard-hours configuration wrong in your system and every downstream OT figure is wrong too.

The shift to system-generated attendance records

This is the practical driver. Twenty years ago, an inspector looking at a muster roll saw handwriting. Today they see biometric logs, geo-tagged mobile punches, access-control data, shift rosters and an exportable audit trail.

That cuts both ways. Digital records make compliance far easier to demonstrate — but they also make non-compliance far easier to detect. If your access-control system shows an employee in the building for eleven hours a day for three weeks and your payroll shows zero overtime, that gap is now visible, timestamped and queryable.

The organisations that handle this well are the ones that treat attendance and payroll as one connected process rather than two systems that exchange a spreadsheet once a month.

The Building Blocks: What Counts as Working Time

Before you can calculate overtime you need agreement on what you are counting. Most OT disputes are not disputes about the multiplier — they are disputes about the hours.

Ordinary working hours

Ordinary working hours are the contracted standard for a given employee group: the daily hours and the weekly hours beyond which time becomes overtime. These need to be defined per employee group, not globally, because a factory shift, a retail store roster and a corporate office rarely share the same standard.

Two thresholds usually matter, and they interact:

• Daily threshold — hours worked beyond the standard day become OT for that day.
• Weekly threshold — hours worked beyond the standard week become OT for that week, even if no individual day crossed the daily limit.

Your policy must state which threshold governs, or how both are applied without double-counting the same hour. A common approach is to compute daily OT first, then check whether remaining regular hours exceed the weekly standard, and top up if so.

Spread-over

Spread-over is the total elapsed time from the start of work to the end of work on a given day, including intervals. It is a separate constraint from hours worked.

An employee could work eight hours with a three-hour unpaid break in the middle and still breach a spread-over limit, because the working day stretched too far across the clock. Split shifts in hospitality, retail and field service are the usual culprits. Spread-over is a scheduling compliance issue rather than a pay calculation, but your roster tool should flag it.

Rest intervals

Rest intervals — the meal break after a defined stretch of continuous work — are generally excluded from hours worked when they are genuine breaks during which the employee is free from duty.

The complication is the break that is not really a break. A security guard eating lunch at their post, a support agent staying logged in during the break, a driver waiting with the vehicle — these are not free from duty in any meaningful sense, and treating them as unpaid break time invites a dispute.

Rule of thumb: if the employee cannot leave the workstation and cannot decline to respond, it is working time.

Weekly off

The weekly day of rest is both a compliance requirement and a pay-rate trigger. Work performed on a weekly off is almost always treated differently from work performed on an ordinary working day — either through a premium rate, through a substituted rest day, or through both.

Your system needs to know, for each employee on each date, whether that date was a working day, a weekly off, a substituted off, a festival or national holiday, or a leave day. Those five categories often carry five different pay treatments.

"Hours worked" versus "hours present"

This distinction causes more payroll noise than any other single factor. Hours present is what the device records: first punch to last punch. Hours worked is what the employee was actually engaged in duty.

The gap between them includes:

• Unpaid meal and rest intervals
• Time on premises before the shift starts (early arrivals waiting for transport)
• Time after the shift ends that was not authorised work
• Personal time out of the building during the shift
• Idle time caused by a machine breakdown or a power cut, where treatment depends on your policy and the employment terms

A well-configured HRMS derives hours worked from hours present by applying documented break rules, grace periods and approval status. A badly configured one just subtracts the first punch from the last and pays OT on the difference, which is how a smoking break and a canteen queue end up on the payslip at premium rates.

Who Is Eligible for Overtime and Who Usually Is Not

This is the single area where the temptation to generalise is strongest and the cost of getting it wrong is highest. The honest answer is that eligibility depends on three things simultaneously: the establishment type, the state, and the individual employee's role and wage level.

The broad categories

Workers in factories and similar establishments. Employees engaged in manufacturing, operations and allied work in factory settings have historically had the clearest and strongest overtime entitlements, along with the most detailed record-keeping obligations.

Employees in shops and commercial establishments. These are governed primarily by state-level legislation, and this is where variation is widest. Working hours, overtime rates, permitted extra hours and record requirements can differ meaningfully between states. A retail chain operating in eight states may genuinely have eight configurations.

Supervisory, managerial and administrative roles. Employees genuinely employed in a managerial or supervisory capacity are commonly excluded from overtime entitlements. The key word is "genuinely." Exclusion depends on the actual nature of duties and authority — whether the person hires, assigns work, directs others, exercises independent judgement — and not on the job title printed on the appointment letter.

Wage-ceiling based exclusions. Some frameworks exclude employees whose wages exceed a specified level from certain entitlements. Where such a ceiling applies, it is a specific notified figure that changes over time, so you must check the current applicable number rather than relying on the one your predecessor configured.

Contract and third-party staff. Where workers are engaged through a contractor, overtime obligations typically sit with the contractor as the immediate employer — but the principal employer often carries responsibility for ensuring compliance, and in practice carries the reputational and audit risk. Build contractor OT verification into your vendor governance rather than assuming it is someone else's problem.

Apprentices, trainees and interns. These categories sit under their own arrangements and should not be assumed to follow the general rule in either direction.

How to actually decide

Do not make eligibility a judgement call at the payroll desk each month. Make it an attribute of the employee master, set once through a documented process and reviewed periodically.

A workable process:

1. List every distinct role in the organisation, grouped by establishment and state.
2. For each role, document the actual duties, decision-making authority and reporting relationships — not the title.
3. Map each role to an overtime eligibility classification with a written rationale.
4. Have the classification reviewed by someone who knows the applicable state rules for that establishment.
5. Store the classification against the employee group in your HRMS so payroll never has to guess.
6. Re-review whenever a role changes materially, and at least annually.

The documented rationale matters as much as the conclusion. If you are ever asked why a particular category was treated as exempt, "we reviewed the duties and recorded this reasoning on this date" is a defensible answer. "That's how it's always been" is not.

Verify before you configure. The specific eligibility rules, wage ceilings and exclusions applicable to your establishment type and state must be confirmed against the current official notification or with a qualified advisor. Treat the categories above as a map of the terrain, not as the rule itself.

The Overtime Rate Principle and the Wage Base

Here is where most of the money is, and where most of the errors are.

The premium rate principle

Indian practice is built on a premium rate: hours worked beyond the ordinary limits are paid at a rate higher than the ordinary rate of wages. The most commonly applied premium in Indian statutory frameworks is double the rate of wages — that is, twice the ordinary hourly rate for each overtime hour.

Some contexts, states or establishment categories may prescribe different treatment, and some employers voluntarily pay above the statutory minimum. Work on weekly offs and holidays frequently attracts its own treatment. Confirm the applicable rate for your establishment; then configure it once, centrally, rather than letting each location invent its own multiplier.

The part that actually costs you money: the base

The multiplier is the headline. The base is where the real variance lives.

"Ordinary rate of wages" is not a synonym for "basic salary." It is a defined concept, and in Indian frameworks it has generally been understood to be broader than basic pay alone — typically encompassing basic wages together with allowances that form part of ordinary remuneration, while excluding certain specified items.

The redefined concept of "wages" introduced through the labour codes sharpens this considerably. In broad architectural terms:

• There is a core of wages — basic pay, dearness allowance and retaining allowance style components.
• There is a list of specified exclusions — items such as certain allowances, contributions to social security funds, conveyance, house rent allowance, overtime itself, commission, and various other named components.
• Critically, there is a capping mechanism: if the total of the excluded components exceeds a specified proportion of total remuneration, the excess is pulled back into wages.

That last mechanism is the one that breaks legacy payroll configurations. A salary structure engineered years ago to minimise statutory cost by keeping basic low and allowances high will, under a capped definition, see a chunk of those allowances re-characterised as wages. The wage base rises. Every calculation built on the wage base — including overtime — rises with it.

What this means practically

Three actions follow.

One: audit your salary structures against the wage definition. For each grade and each entity, compute total remuneration, identify which components fall inside the wage core, which fall in the exclusion list, and whether the excluded total breaches the specified proportion. Where it does, calculate the pull-back.

Two: define your OT base explicitly in policy and in the system. Write down, component by component, which earnings elements enter the overtime base. Not "basic + DA" as shorthand — an actual list mapped to your payroll component codes. Ambiguity here compounds every month.

Three: model the cost before you switch. If your OT base is widening, the incremental cost on a high-OT population is not marginal. Run last quarter's actual OT hours against both the old and new base and put the delta in front of finance before it appears in a variance report.

The specific exclusion list and the applicable proportion for the capping mechanism are prescribed figures. Verify the current position for your establishment rather than relying on any number you see in an article, including this one.

Step-by-Step Overtime Calculation

The general overtime pay calculation formula has four steps.

Step 1 — Establish the OT wage base for the period. Sum the earnings components you have defined as forming the ordinary rate of wages, for the month or the day in question.

Step 2 — Derive the ordinary hourly rate. Divide the wage base by the standard hours for the same period. For a monthly-rated employee this is monthly wage base ÷ standard monthly hours. For a daily-rated worker it is daily wage ÷ standard daily hours.

Step 3 — Determine eligible OT hours. Take hours worked (not hours present), subtract standard hours, apply approval status and any caps, and separate the hours by rate category — ordinary working day OT, weekly-off work, holiday work.

Step 4 — Apply the multiplier and sum. Multiply eligible hours in each category by the ordinary hourly rate and the applicable multiplier, then add the categories together.

Choosing a denominator for standard monthly hours

This is a genuine design decision with real financial consequences, and organisations handle it differently. The common approaches:

Pick one per employee group, document why, and never change it mid-year without recalculating and communicating. A silent change to the denominator is one of the fastest routes to a grievance, because employees notice when the same overtime hour pays differently in March than it did in February.

Rounding conventions

Rounding sounds trivial and generates a disproportionate share of disputes. Decide and publish:

• Rounding of OT minutes. Nearest 15 minutes, nearest 30 minutes, or exact to the minute. Whichever you choose, apply it symmetrically — rounding down against the employee while rounding up for attendance regularisation is indefensible.
• Minimum OT block. Many policies require a minimum continuous stretch (say 30 minutes) before OT is recognised at all, to avoid paying premium rates for someone who lingered to finish an email.
• Rate decimals. Carry the hourly rate to at least two decimals internally; rounding the rate to whole rupees before multiplying by a large hour count creates visible errors.
• Final amount rounding. Round the final OT amount, typically to the nearest rupee, and document the direction.

Now the worked examples. All figures below are illustrative and chosen for clarity of arithmetic. They are not statutory rates, benchmark salaries or recommendations.

Example 1 — Monthly-rated office employee

Illustrative scenario. Priya works in a corporate office on a five-day week, with a standard day of 9 hours including a 1-hour unpaid meal break — so 8 hours of working time per day, 40 hours per week. She is in an overtime-eligible category under her employer's classification. In a given month she works 14 approved overtime hours on ordinary working days.

Her illustrative monthly earnings:

Note what happened with the special allowance. The excluded components (HRA ₹12,000 + conveyance ₹2,400 = ₹14,400) sit below the threshold in this illustration, but the employer's structure review determined that part of the special allowance falls inside the wage core. The specific treatment depends on your actual structure and the applicable definition — this is exactly the kind of decision to document with your advisor.

Standard monthly hours. The employer uses a fixed convention: 40 hours per week × 52 weeks ÷ 12 months = 173.33 hours.

Ordinary hourly rate: ₹35,600 ÷ 173.33 = ₹205.39 per hour

Overtime at a double-rate premium: ₹205.39 × 2 = ₹410.78 per OT hour

OT payable: 14 hours × ₹410.78 = ₹5,750.92, rounded to ₹5,751

Now observe the difference the base makes. Had the employer paid OT on basic only:

• Hourly rate: ₹24,000 ÷ 173.33 = ₹138.46
• OT rate: ₹276.92
• OT payable: 14 × ₹276.92 = ₹3,876.88

That is a shortfall of roughly ₹1,874 for one employee in one month — about 33% under. Multiply by a hundred employees and twelve months and the exposure is no longer a rounding issue. This is the single most common and most expensive overtime error in Indian payroll.

Example 2 — Daily-wage factory worker

Illustrative scenario. Ramesh is a daily-rated machine operator in a manufacturing unit. Standard day: 8 hours. Six-day week. His illustrative daily wage (basic + DA as defined for his category) is ₹720.

In a fortnight he works:

Ordinary hourly rate: ₹720 ÷ 8 = ₹90.00 per hour

OT rate at double the ordinary rate: ₹90 × 2 = ₹180.00 per hour

Ordinary-day OT: 10.5 × ₹180 = ₹1,890

Weekly-off work. Treatment here depends on the applicable rules and the employer's policy. Two common approaches in this illustration:

• Approach A — premium on all hours worked: 8 hours × ₹180 = ₹1,440, with no substituted rest day.
• Approach B — substituted rest day plus ordinary pay: the worker receives a compensatory rest day within the permitted window and the 8 hours are paid at the ordinary rate, ₹720. Note that the permissibility and conditions of substitution are governed by the applicable rules; this cannot be assumed.

Under Approach A, total additional pay for the fortnight is ₹1,890 + ₹1,440 = ₹3,330 on top of regular wages.

Under Approach B, total additional pay is ₹1,890 + ₹720 = ₹2,610, plus a rest day owed.

The gap between those two treatments is why the weekly-off question has to be settled in policy, aligned to the applicable rules, and configured in the system — not decided by whoever is processing payroll on the 28th.

Example 3 — Shift worker crossing midnight

Illustrative scenario. Anil works night shift in a BPO. Rostered shift: 10:00 pm to 6:30 am, with a 30-minute unpaid break — 8 hours of working time. On one occasion the shift is extended to 9:15 am to cover an escalation.

His illustrative monthly OT wage base is ₹28,000. Standard monthly hours by the employer's convention: 8 hours × 6 days × 52 ÷ 12 = 208 hours.

Ordinary hourly rate: ₹28,000 ÷ 208 = ₹134.62 per hour

OT rate: ₹134.62 × 2 = ₹269.24 per hour

Hours calculation for the extended shift:

• In-punch: 21:52 (8 minutes early — inside the grace window, so shift start remains 22:00)
• Out-punch: 09:21 (6 minutes after the extended end at 09:15)
• Elapsed from shift start to out-punch: 11 hours 21 minutes
• Less unpaid break taken: 30 minutes → 10 hours 51 minutes worked
• Less standard 8 hours → 2 hours 51 minutes of overtime
• Employer's rounding convention: nearest 15 minutes → 2 hours 45 minutes (2.75 hours)

OT payable: 2.75 × ₹269.24 = ₹740.41, rounded to ₹740

The three configuration traps in this example:

Date attribution. The shift begins on one calendar date and ends on the next. Your system must attribute the whole shift — and its OT — to a single shift date, usually the start date. If it attributes hours to the calendar date on which they occurred, the 6:30 am portion lands on the following day, and if that day happens to be the employee's weekly off, your system will happily apply weekly-off rates to ordinary shift hours.

Month-end crossover. When a night shift starts on the last day of a month and ends on the first day of the next, the hours must follow the shift-date rule consistently, or you will double-count in one period and short-pay in the other. This is the classic March 31 / April 1 problem.

Night shift allowance versus overtime. Many employers pay a night shift allowance for working unsocial hours. That allowance is compensation for the timing of the shift, not for its length. It does not replace overtime for hours beyond the standard, and overtime does not replace it. Both may apply; configure them as separate components with separate triggers.

Example 4 — Field employee on a six-day week

Illustrative scenario. Kavita is a field service technician attached to a branch office, on a six-day week with a standard 8-hour day (48 hours per week). She uses a mobile app with geo-tagged punches at the first and last customer sites of the day.

Illustrative monthly OT wage base: ₹31,200. Standard monthly hours convention: 48 × 52 ÷ 12 = 208 hours.

Ordinary hourly rate: ₹31,200 ÷ 208 = ₹150.00 per hour

OT rate: ₹150 × 2 = ₹300.00 per hour

A sample week from her attendance record:

Applying a 30-minute minimum OT block: Thursday's 5 minutes is dropped. Applying nearest-15-minute rounding to the remainder: 40m → 45m, 2h 50m → 2h 45m, 2h 15m → 2h 15m. Recognised daily OT = 5 hours 45 minutes.

Weekly threshold check. Hours worked in the week: 50h 35m. Recognised OT: 5h 45m. Remaining regular hours: 44h 50m — below the 48-hour weekly standard, so no additional weekly top-up is due. Had the daily OT been lower and the regular hours crossed 48, the excess would be added as weekly OT.

OT payable for the week: 5.75 × ₹300 = ₹1,725

The field-specific problems this example surfaces:

• Travel time. Is the journey from home to the first customer site working time? Is travel between sites during the day? Is the journey home from the last site? Policy must answer all three explicitly. A defensible common position: travel between assignments during the working day counts; the first commute out and the last commute home generally do not — but if the employee is required to collect equipment or report in first, the calculation changes.
• Break verification. Kavita's 45-minute break is a policy assumption, not a recorded fact. If the app does not capture break punches, you are deducting time you cannot evidence. Either capture the break or state clearly in policy that a fixed deduction applies.
• Waiting time. An hour waiting at a locked customer site is time the employee cannot use freely. Most reasonable policies treat it as working time.
• Connectivity gaps. When the app cannot punch, there must be a fallback with manager attestation, and those records must be flagged as manually adjusted in the audit trail.

Overtime Versus Compensatory Off

Comp-off is the most commonly misused tool in Indian HR. The comp-off vs overtime question is not a matter of preference — it depends on whether the extra hours attract a statutory premium.

The core distinction

Overtime pay compensates for extra hours with money, at a premium rate. Compensatory off compensates with equivalent time away from work, usually at parity (one hour worked, one hour off) or occasionally at a premium in time.

The critical point: where a premium wage rate is legally required for overtime hours, substituting comp-off does not discharge that obligation. Time off at parity is, by definition, worth less than pay at a premium multiplier. Offering comp-off in place of a legally required premium is a shortfall dressed up as a benefit.

Where each fits

Comp-off is generally appropriate for:

• Employees genuinely outside overtime eligibility — senior professionals, managers, roles where exclusion has been properly assessed
• Work on a weekly off where a substituted rest day is the permitted treatment under applicable rules
• Recognition beyond what is legally required, as an additional benefit rather than a replacement
• Occasional exceptional effort where the employee actively prefers time to money

Overtime pay is generally required for:

• Any employee in a covered category working beyond the applicable limits
• Any situation where the applicable rules prescribe a premium wage rate
• Any case where your own employment contract or settlement promises it, regardless of the statutory floor

Designing a hybrid policy

Most organisations need both. A clean structure:

1. Classify first. Every employee group is tagged OT-eligible or comp-off-eligible based on the documented assessment. This is not a per-instance choice.
2. Never allow substitution downward. An OT-eligible employee cannot be moved to comp-off for hours that attract a premium. Lock this in the system so it cannot be done by exception.
3. Allow upward flexibility. An OT-eligible employee may receive comp-off in addition to their premium pay if the organisation chooses. That is a benefit, not a substitution.
4. Set a validity window. Comp-off that must be used within 30, 60 or 90 days keeps the liability visible and short. Indefinite comp-off balances become an unquantified obligation on the balance sheet and a source of resentment when people are told the balance has lapsed.
5. Decide the lapse or encashment rule upfront. Either comp-off lapses after the window — communicated clearly in advance, with reminders — or it converts to payment. Silent lapse is a grievance generator.
6. Require the same approval rigour. Comp-off should be pre-approved and recorded exactly like overtime. It is a cost, just a deferred one.
7. Report the balance monthly. Comp-off outstanding, by department, with ageing. If the balance is growing, you have a capacity problem, not a leave problem.

The hidden cost of comp-off

Comp-off is not free. It is a staffing cost paid later, and it lands unpredictably. A warehouse that accumulates 300 comp-off days during a peak season will lose those days somewhere in the following quarter, usually clustered around holidays, and the operational disruption often exceeds what the overtime payment would have cost.

Model comp-off liability the same way you model leave liability, and report it to finance with the same seriousness.

Approval Workflow Design

Uncontrolled overtime does not announce itself. It arrives as a slow upward drift in a cost line nobody owns, and it is usually discovered during budget season rather than in the month it occurs.

Pre-approval as the default

The governing principle: overtime is authorised in advance, not discovered afterwards.

A workable model:

1. Forecast. Managers submit expected OT requirements for the coming period against known workload — a production run, a month-end close, a seasonal peak, a project deadline.
2. Allocate. OT budget is issued per cost centre in hours and rupees, approved at the appropriate finance level.
3. Request. An individual instance of overtime is raised — ideally by the employee or the manager, before the hours are worked — specifying the reason, expected hours and the cost centre.
4. Approve. The reporting manager approves against available budget. The system shows remaining budget at the point of approval.
5. Work and record. Attendance captures actual hours.
6. Validate. Actual hours are matched to approved hours. Variances beyond a tolerance are flagged.
7. Post-facto exception route. Genuine emergencies happen. Provide an exception path with a higher approval level, a mandatory reason code, and visibility in the exception report. Do not let it become the main road.

Caps and guardrails

Caps serve two purposes: compliance with permitted limits, and protection of employee wellbeing and work quality.

Typical cap structures:

• Per day — maximum OT hours in a single day, and a hard stop on total hours from shift start
• Per week — often the most operationally useful cap
• Per quarter — aligned to any applicable statutory limits on total overtime in a period
• Per cost centre — a rupee ceiling that forces prioritisation
• Consecutive days — no more than N consecutive days with overtime, protecting against sustained strain

Configure caps as warnings at a threshold and hard blocks at the limit. A warning at 80% of the quarterly cap lets a manager reallocate work; a block at 100% prevents a compliance breach. Make the cap override, if you allow one at all, require a senior approval and a written reason.

Exception reporting

The monthly OT exception report is the single most valuable control document in this whole process. It should surface:

Circulate it to line managers and finance, not just to HR. Overtime is a management issue with a payroll symptom.

The structural question nobody asks

If the same team generates significant overtime every single month, that is not overtime. That is a headcount gap being financed at a premium multiplier.

Run the arithmetic annually: total OT cost for a team divided by the fully loaded cost of an additional employee. When the ratio approaches or exceeds one, you are paying 2x for capacity you could buy at 1x — and you are paying it in employee fatigue as well as in rupees.

Capturing Overtime Accurately

Every overtime calculation is only as good as the hours feeding it. This is where the operational work lives.

Capture methods and what each gets wrong

Biometric devices. Accurate and hard to dispute, which is why they remain the standard for fixed-location work. Watch for: device downtime with no fallback, failed reads on worn fingerprints (common in manual work), queues at the device inflating elapsed time, and devices with drifting clocks. Sync device time to a single source and monitor for gaps.

Mobile and geo-tagged attendance. Necessary for field, sales and service teams. Watch for: GPS drift in dense urban areas, punches from outside the geofence, battery-dead scenarios, and offline punches that sync hours later with the original timestamp — make sure your system preserves the punch time, not the sync time.

Access control and door logs. Useful as a corroborating source, poor as a primary one. Door logs capture presence in the building, not engagement in work, and they miss tailgating entirely.

System and application logs. For knowledge and support work, login/logout or activity data can supplement punches. Be careful: monitoring granularity that feels like surveillance damages trust faster than it improves accuracy.

Supervisor-attested manual records. Still necessary for exceptions, breakdowns and remote sites. Must be flagged as manual in the audit trail, must carry a reason, and must be reviewed for volume — a location where 30% of records are manual has a device problem or a process problem.

Grace periods

Grace periods exist so that a two-minute late arrival is not a half-day deduction and a three-minute late departure is not an overtime claim. They need to be defined at both ends:

• Entry grace — lateness tolerated before a lateness marking applies
• Early-entry grace — early arrival that does not start the OT clock
• Exit grace — early departure tolerated
• Late-exit grace — the buffer after shift end before OT begins accruing

The last one is the important one for overtime. Without it, every employee who takes ten minutes to shut down and walk out generates a daily OT claim. With too generous a setting, genuine short overtime disappears. Something in the 10–20 minute range with a separate minimum OT block is a common balance.

Publish the grace settings. Employees who understand the rule stop disputing the output.

Break deduction rules

Three models, in decreasing order of defensibility:

1. Punched breaks. Employees punch out and in for breaks. Most accurate, highest friction, best for factory and shift environments.
2. Auto-deduct with exception. A fixed break is deducted automatically for shifts over a threshold length, with an exception route for employees who worked through the break with manager confirmation. Good balance for most environments.
3. Blanket auto-deduct. A fixed deduction with no exception route. Simple, and wrong every time someone works through lunch.

Whichever you use, the rule must be written in the attendance policy and visible to employees. Deducting unrecorded time silently is exactly the kind of thing that surfaces badly in a dispute.

Night shift and date-crossover handling

Covered in Example 3 above, but worth restating as a configuration checklist, because it is the most common source of silent errors:

• Each shift definition must declare whether it crosses midnight
• All hours of a crossing shift attribute to the shift start date
• Weekly-off and holiday determination uses the shift date, not the calendar date of each hour
• Month-end crossover follows the same shift-date rule
• Weekly hour totals accumulate by shift date
• Test the configuration explicitly on a month boundary and a weekly-off boundary before going live

Rounding rules that cause disputes

Revisit the rounding conventions from earlier, and then test them against real data. Take a month of actual punches, run them through your rounding rules, and look at the aggregate effect. If rounding systematically reduces recognised OT across the population, your rule is asymmetric and you should fix it before someone else points it out.

Configuring Overtime in an HRMS

Manual overtime processing does not scale past about thirty employees, and it does not survive an audit past about a hundred. The configuration work is front-loaded; done properly, month-end becomes a review rather than a reconstruction.

OT rules by employee group

Overtime rules attach to employee groups, not to individuals. A typical group definition combines establishment, location/state, employment category and shift pattern.

Each group carries its own rule set:

• Standard daily hours and standard weekly hours
• Standard monthly hours denominator and the convention used
• OT eligibility flag
• OT wage base component list
• Multipliers by day type
• Caps at each level
• Rounding and minimum block settings
• Grace period settings
• Break deduction model
• Approval workflow route

Get the group structure right at the outset. Retrofitting groups after a year of payroll history is painful and error-prone.

Multipliers by day type

At minimum, configure distinct multipliers for:

Make each multiplier a configurable parameter with an effective date, never a hard-coded value. When a rate changes, you change a parameter with a start date; history remains intact and retrospective recalculation becomes possible.

Auto-computation from attendance

The pipeline should run without manual intervention:

1. Raw punches ingest from all sources, timestamped and source-tagged
2. Punches map to rostered shifts, with crossover handling
3. Grace periods apply
4. Break deductions apply per the group's model
5. Hours worked is derived from hours present
6. Day type is determined for the shift date
7. Standard hours are subtracted; gross OT hours emerge by category
8. Approval status is matched; unapproved hours are flagged, not silently paid
9. Caps are applied, with breaches flagged
10. Rounding and minimum blocks apply
11. Net payable OT hours by category are written to the OT register

Every step should be inspectable. When an employee asks why they were paid 5.75 hours and not 6.25, you need to be able to show them which rule removed the difference and when.

Locking the OT register before payroll cut-off

Attendance data must stop moving before payroll starts, or your reconciliation will never tie out. A clean cut-off sequence:

• T-5 days: attendance period closes for input; employees see their draft OT
• T-4 days: employee regularisation and query window opens
• T-3 days: manager approvals and regularisation decisions due
• T-2 days: HR reviews the exception report and resolves open items
• T-1 day: OT register is locked; no further changes without a formal reopen
• T-day: payroll pulls the locked register

After the lock, changes go through the arrears process in the following cycle — not through a quiet edit to the current one. This single discipline eliminates most month-end chaos.

The audit trail

Every OT record should carry, immutably:

• The source of each punch and its original timestamp
• Any manual adjustment, with who, when, previous value, new value and reason
• The approval chain with identities and timestamps
• Which rule version applied, with its effective date
• The full calculation breakdown from hours present to rupees payable
• The lock event, and any reopen with its authorisation

This is what turns "we think we paid correctly" into "here is the record." It matters for inspections, for disputes, for due diligence, and for your own sanity when someone questions a figure from eight months ago.

Platforms like CozyHR are built around exactly this chain — attendance rules, OT computation and payroll posting in one system with the trail intact — which removes the export-reimport step where most reconciliation errors are born.

Payroll Processing of Overtime

Where overtime sits on the payslip

Show overtime as a distinct earnings line, never merged into another component. Where multiple rate categories apply, show them separately:

• Overtime — ordinary days (hours × rate)
• Overtime — weekly off (hours × rate)
• Overtime — holiday (hours × rate)

Each line should display hours, rate and amount. A payslip that says "Overtime: ₹5,751" with no hours or rate invites a query every month. One that says "Overtime — ordinary days: 14.00 hrs @ ₹410.78 = ₹5,751" answers the query before it is asked.

Where OT relates to a prior period, label it as arrears with the period identified.

Statutory treatment at a conceptual level

This section describes principles only. The specific treatment of overtime for each statutory contribution depends on current rules and the definitions applicable to your establishment — verify with your advisor.

Provident fund. PF contributions attach to a defined wage base. Overtime has conventionally been understood as falling outside the components on which PF contributions are computed, on the reasoning that it is a variable payment for extra hours rather than part of ordinary wages. The redefined wage concept and its capping mechanism make it worth re-confirming your treatment rather than assuming the legacy position carries forward unchanged.

ESI. Employee state insurance contributions have generally been computed on a broader base of wages paid, and overtime has typically been included in that base for contribution purposes. Separately, there is the question of whether overtime counts toward the wage ceiling that determines coverage — the conventional treatment is that it does not push an otherwise-covered employee out of coverage, but this is precisely the kind of rule to confirm rather than infer.

Income tax. Overtime is salary income and is taxable. For TDS purposes it forms part of the employee's estimated annual salary. The practical difficulty is that overtime is variable and unpredictable, so a projection made in April will be wrong by March for anyone with significant OT. Two approaches: project a conservative OT estimate and true up in the final quarter, or recompute the projection each month based on year-to-date actuals. The second is more accurate and is what a properly integrated payroll system should do automatically.

Bonus and gratuity bases. Whether overtime enters the calculation base for statutory bonus or gratuity depends on the definitions in the applicable frameworks. This has historically been a source of litigation; do not assume either way.

Arrears and retrospective overtime

Retrospective OT arises when hours are approved after cut-off, when a rate or base changes with retrospective effect, when a misclassification is corrected, or when a dispute is settled.

Handle it properly:

1. Compute the correct amount for the original period using the rules and rates that applied then, not today's
2. Compare to what was actually paid
3. Post the difference as a clearly labelled arrears line identifying the original period
4. Recompute the statutory impact for the original period, and handle any resulting contribution or tax adjustments through the correct mechanism
5. Document the reason in the audit trail
6. If the same root cause has affected other employees, fix the population, not just the person who complained

That last step is the one organisations skip, and it is the one that converts a single correction into a systemic liability when someone eventually notices the pattern.

Month-end reconciliation

The reconciliation between attendance and payroll is non-negotiable. Run it every month, before disbursement:

Keep the reconciliation as a signed-off artefact each month. It is the document an auditor will ask for, and it is the fastest way to demonstrate the process works.

Registers, Records and Display Requirements

Indian labour compliance is substantially a record-keeping regime. The obligations differ by establishment type and state, but the pattern is consistent.

What is typically required

• A register of workers or employees with identification and employment particulars
• An attendance or muster record showing daily presence and hours
• An overtime register recording overtime worked and paid, usually with dates, hours, rate and amount per employee
• A wage register showing components, deductions and net pay
• Wage slips issued to employees in the prescribed manner
• Notices of working hours, rest intervals and weekly off displayed at the workplace
• Notices of the applicable minimum wage rates where required
• Abstracts of applicable legislation displayed as prescribed
• Leave records, including compensatory off where applicable

The labour codes and associated rules have pushed toward consolidated register formats and electronic maintenance, which is a genuine simplification for multi-location employers. The specific formats, retention periods and whether electronic maintenance is accepted in a given state must be confirmed for your establishment.

What an inspector or auditor typically asks for

Based on how these reviews usually proceed, expect a sequence roughly like this:

1. Registers for the review period — attendance, overtime, wages, in the prescribed format
2. A reconciliation between them — do attendance hours, OT register entries and wage register amounts agree?
3. A sample trace — pick an employee and a month, and follow the calculation from raw punches to bank credit
4. Evidence of the rate applied — how was the ordinary rate of wages derived, and which components were included?
5. The eligibility classification — which employees are treated as exempt, and on what documented basis?
6. Evidence of limits observed — do the records show any employee exceeding permitted daily, weekly or periodic overtime?
7. Approval evidence — was the overtime authorised?
8. Proof of payment — bank statements or payment records matching the wage register
9. Display compliance — are the required notices up, current and legible?
10. Contractor records where contract labour is engaged

The organisations that get through this comfortably are not necessarily the ones with zero errors. They are the ones who can produce a coherent, internally consistent record quickly, explain their methodology, and show that anomalies were identified and corrected through a documented process. An organisation that finds and fixes its own errors reads very differently from one that cannot answer basic questions about its own data.

Retention

Keep records for at least the prescribed retention period for your establishment type, and in practice longer. Disputes surface years later. Electronic retention with a verifiable audit trail is generally easier to defend than a stack of physical registers in a store room, subject to confirming that electronic maintenance is accepted for your establishment and state.

Common Mistakes and What They Cost

Paying overtime on basic only

The most expensive and most widespread error. When the ordinary rate of wages is broader than basic pay, computing OT on basic alone under-pays every overtime hour — and the shortfall compounds silently, month after month, across the whole eligible population.

As Example 1 showed, the gap can easily be a third of the correct amount. Fix: audit your OT base against the applicable wage definition, correct it, and quantify the historical exposure.

Ignoring weekly-off and holiday premium rates

Applying the standard OT multiplier to weekly-off and holiday work, when a different treatment applies, is under-payment on exactly the hours employees resent most. Fix: configure distinct day types with distinct treatments.

Uncontrolled overtime becoming structural

When OT runs at a consistent level every month with no approval discipline, it stops being overtime and becomes a shadow headcount financed at a premium. Fix: budgets, caps, exception reporting, and an annual OT-versus-headcount analysis per team.

Misclassifying employees as exempt

Applying a "manager" or "supervisor" label to a role that does not carry genuine managerial or supervisory authority, in order to avoid overtime, creates exposure that accumulates for as long as the misclassification persists — and it typically affects a group rather than an individual. Fix: classify on actual duties, document the reasoning, review annually.

Managing overtime in spreadsheets

Spreadsheets have no audit trail, no version control, no rule versioning and no protection against a broken formula propagating across a thousand rows. They also do not survive the departure of the person who built them. Fix: move OT rules into the system that holds the attendance data.

No reconciliation between attendance and payroll

Without a monthly tie-out, errors are discovered by employees, auditors or inspectors rather than by you. Fix: the reconciliation checklist above, signed off monthly.

Treating comp-off as a substitute for premium pay

Discussed above. Where a premium is legally required, comp-off does not discharge it. Fix: classify employees, lock the substitution rule in the system.

Inconsistent rounding

Rounding applied differently across locations, or asymmetrically against employees, produces both grievances and a bad look in an audit. Fix: one documented convention per employee group, published, tested against real data.

Silent night-shift errors

Date attribution bugs on crossover shifts are hard to spot because they produce plausible-looking numbers. Fix: test crossover configuration explicitly at month boundaries and weekly-off boundaries.

No employee visibility

When employees cannot see their own OT hours until the payslip arrives, every disagreement becomes a month-old forensic exercise. Fix: give employees real-time visibility of their recorded and approved OT.

Getting Your Overtime Process Right in 30 Days

A practical sequence for an organisation starting from a messy baseline.

Week 1 — Find out what is actually happening

• Pull the last twelve months of OT data by employee, department, location and month. If the data does not exist in usable form, that is your first finding.
• Document the current OT rules actually in use at each location — including the informal ones. Expect variation you did not know about.
• List every employee group and its current OT eligibility treatment, with whatever rationale exists.
• Identify the salary components currently forming the OT base at each location.
• Map every attendance capture method in use and its known failure modes.
• Check which statutory registers exist, whether they are current, and whether they reconcile to payroll.
• Identify the top ten employees and top three departments by OT volume.

Deliverable: a one-page baseline. Current annual OT cost, current rules, known gaps, biggest risks.

Week 2 — Decide what the rules should be

• Confirm, with a qualified advisor, the rules applicable to each establishment type and state you operate in: working hour limits, OT rates, eligibility, record requirements.
• Validate your employee classification against actual duties, not titles. Correct what needs correcting and document the reasoning.
• Define the OT wage base component by component, mapped to your payroll component codes, and check it against the applicable wage definition including any capping mechanism.
• Decide the standard monthly hours denominator per group and record the rationale.
• Set rounding conventions, minimum OT blocks and grace periods.
• Set caps: daily, weekly, quarterly, per cost centre.
• Decide the comp-off policy and where it applies.
• Quantify the financial impact of any base or rate correction and take it to finance before implementation, not after.

Deliverable: an approved rules document, signed off by HR, finance and your advisor.

Week 3 — Build it into the system

• Configure employee groups with their full rule sets.
• Configure day types and multipliers with effective dates.
• Configure the approval workflow, budgets and cap warnings and blocks.
• Fix shift definitions, especially midnight crossovers, and test at month and weekly-off boundaries.
• Configure break deduction and grace period rules per group.
• Map OT components to payslip lines and to the correct statutory treatment.
• Build the exception report and the reconciliation report.
• Run a parallel test: take one full past month of real attendance data, process it through the new configuration, and compare line by line against what was actually paid. Investigate every difference until you can explain it.

Deliverable: a configured, tested system with a documented parallel-run comparison.

Week 4 — Launch and embed

• Communicate to employees: what the rules are, how OT is calculated, how to request and approve it, how to see their own data, how to raise a query. Use examples with real numbers.
• Train managers on approval responsibilities, budgets, caps and the exception report. Managers approving overtime need to understand they are approving a cost.
• Publish the policy document and update appointment letter templates if the terms have changed.
• Run the first live cycle with extra scrutiny — daily monitoring of the exception report during the cycle, not just at the end.
• Complete the first full reconciliation and have it signed off.
• Update or create the statutory registers in the required format and check display notices at every site.
• Schedule the ongoing rhythm: monthly exception review, quarterly trend review, annual rules refresh and classification review.

Deliverable: one clean cycle completed end to end, with the reconciliation signed and the governance calendar set.

Overtime Policy Outline

A structure you can adapt. Each clause below is a heading with a one-line description of what it should contain.

1. Purpose and scope — why the policy exists, and which entities, locations and employee categories it covers.
2. Definitions — ordinary working hours, overtime, spread-over, weekly off, holiday, hours worked, hours present, comp-off, OT wage base.
3. Standard working hours by employee group — the daily and weekly standard for each group, and the shift patterns in use.
4. Rest intervals and spread-over — break entitlements, when they are unpaid, and the maximum spread of the working day.
5. Weekly off and holidays — how the weekly off is determined, rules for substitution, and the list of holidays.
6. Overtime eligibility — which employee groups are eligible, which are not, and the basis on which classification is determined and reviewed.
7. Overtime wage base — the exact list of salary components that form the ordinary rate of wages for OT purposes.
8. Calculation method — the per-hour derivation, the standard hours denominator, multipliers by day type, and the order of daily and weekly threshold application.
9. Rounding and minimum blocks — the rounding convention, the minimum OT duration recognised, and how rates are carried to decimals.
10. Caps and limits — maximum OT per day, week and quarter, consecutive-day limits, and what happens at each threshold.
11. Pre-approval process — who requests, who approves, within what timeframe, and against which budget.
12. Emergency and post-facto approval — the exception route, the higher approval level required, and mandatory documentation.
13. Attendance capture and evidence — accepted capture methods per group, fallback procedures, and how manual entries are handled.
14. Compensatory off — who is eligible, accrual basis, validity window, approval process, and lapse or encashment treatment.
15. Travel and field work — which travel time counts as working time, treatment of waiting time, and out-of-station rules.
16. Night shift — shift date attribution, allowance treatment, and the interaction between allowance and overtime.
17. Payment timing — which payroll cycle OT is paid in, the cut-off date, and how post-cut-off hours are handled.
18. Payslip presentation — how OT appears, with hours, rate and amount shown separately by category.
19. Statutory deductions — a plain-language note on how OT is treated for statutory contributions and tax.
20. Arrears and corrections — how retrospective OT is computed, approved and paid, and how errors affecting a group are remediated.
21. Records and registers — what is maintained, in what format, for how long, and who is responsible.
22. Dispute resolution — how an employee raises an OT query, the response timeline, and the escalation path.
23. Monitoring and reporting — the exception report, the reconciliation, and the review cadence with owners.
24. Non-compliance — consequences of working unapproved OT, approving beyond budget, or falsifying attendance.
25. Policy review — review frequency, owner, and the trigger events that force an off-cycle review.
26. Annexures — worked calculation examples, request and approval form templates, and group-wise rule summary tables.

Frequently Asked Questions

1. Can we pay a fixed monthly overtime allowance instead of calculating actual hours?

Many employers do this for convenience, and it carries real risk. A fixed allowance is an estimate; overtime entitlement is a calculation based on actual hours at a prescribed rate.

If the fixed allowance is lower than what the hours-based calculation would yield, you have a shortfall for that period — and the fact that the employee received something does not cure it. If it is higher, you are over-paying and creating an expectation that is hard to withdraw.

If you do use a fixed allowance, treat it as an advance against calculated OT: compute actual entitlement each month, compare it to the allowance paid, and top up the difference where the calculation exceeds the allowance. You still need the underlying calculation, so the administrative saving is smaller than it appears.

2. Do employees working from home get overtime?

Eligibility is determined by the employee's category, not by their physical location. An OT-eligible employee working remotely remains OT-eligible.

The difficulty is evidential, not legal. Without a reliable capture mechanism, you cannot establish hours worked, and neither can the employee. Practical approach: require remote OT-eligible employees to use the same time-capture tool as on-site staff, apply the same pre-approval requirement, and set a clear expectation that unapproved extra hours will not be recognised. Also address the reverse problem — the always-on culture where nobody formally works overtime but everyone answers messages at 10 pm.

3. What happens if an employee works overtime without approval?

Legally, hours actually worked with the employer's knowledge or acquiescence are generally hours the employer is responsible for. "We did not approve it" is weak as a defence if the work was visible, benefited the employer, and was not stopped.

Practical approach: pay for hours genuinely worked, and treat the approval breach as a management and discipline issue rather than a payment issue. Investigate why it happened — an employee routinely working unapproved overtime usually signals a workload problem, an unrealistic deadline, or a manager who is not monitoring. If unapproved overtime is systemic in one team, the problem is the team's capacity, not the individual's compliance.

4. How should overtime be handled for employees on probation?

Probation affects the security of employment, not the statutory entitlements attaching to hours worked. A probationer in an OT-eligible category is normally entitled to the same overtime treatment as a confirmed employee in that category.

Denying overtime to probationers as a matter of policy is a common and indefensible practice. Apply the same rules; if your salary structure differs during probation, the OT base will differ accordingly, but the method does not change.

5. Can employees refuse to work overtime?

This depends on the employment contract, any applicable settlement or agreement, the nature of the work and the applicable rules. Some frameworks contemplate overtime being required in defined circumstances; others treat it as voluntary. Statutory caps on total overtime hours apply regardless of willingness — an employee cannot consent their way past a legal limit.

Practically, build your policy around voluntary overtime with genuine business exceptions clearly defined. Coerced overtime produces poor work, safety incidents and attrition, and the hours you gain are rarely worth the hours you lose. Where refusal is not an option for genuine operational reasons, say so in the contract rather than discovering the disagreement at 8 pm on a Friday.

6. Does overtime affect an employee's leave encashment, gratuity or full-and-final settlement?

It depends on the definition used for each calculation. Some calculations are based on a defined wage base that may or may not include variable payments such as overtime; others are based on last drawn salary as defined in the relevant framework or in the employment contract.

This has historically been contested territory. Define the treatment explicitly in your policy, confirm it against the applicable definitions with your advisor, apply it consistently, and make sure your full-and-final template reflects it. Inconsistency between what the policy says and what the settlement sheet does is what turns an exit into a dispute.

7. How do we handle overtime for employees who work across multiple states?

Employees who move between locations in different states create a genuine complexity, because working hour rules, overtime rates and record requirements vary at state level.

Common approaches:

• Anchor to the state of the employee's primary place of work for rule determination, provided that reflects reality and not just an administrative convenience
• Apply the rules of the state where the work is actually performed for each period, which is more accurate but heavier to administer
• Apply the most generous applicable treatment across the states involved, which is simple, safe and costs more

Whichever you choose, document the approach, apply it consistently, and confirm it with an advisor. For genuinely mobile employees — regional sales, service engineers, project teams — the third approach often costs less in administration and risk than it costs in incremental wages.

Bringing It Together

Overtime is not a difficult calculation. It is a difficult process, because it depends on accurate hours, correct classification, a defensible wage base, disciplined approvals and a reconciliation that ties the whole chain together. Any weak link produces numbers that look fine on a payslip and fall apart under scrutiny.

The practical priorities, in order:

1. Fix the wage base first. It is the highest-value correction, it affects every OT hour, and it is the error most likely to be found by someone else.
2. Fix classification second. Misclassification creates group-level exposure that grows with time.
3. Fix capture third. Accurate hours make everything downstream easier; inaccurate hours make everything downstream pointless.
4. Add controls fourth. Approvals, budgets and caps turn overtime from a discovered cost into a managed one.
5. Reconcile every month. It is an hour of work that prevents the kind of problem that takes weeks.

And treat overtime data as management information, not just a payroll input. Consistently high overtime in a team is telling you something about capacity, process, scheduling or leadership. The organisations that read that signal early avoid the ones that read it during a resignation interview.

A closing note, repeated because it matters: this article sets out principles and mechanics, deliberately without quoting specific statutory rates, thresholds, ceilings or dates — those vary by state, establishment type and employee category, and they change. Confirm what applies to your organisation against the current official notifications, or with a qualified labour law advisor, before you configure anything.

If your overtime process currently runs on exported attendance files and a spreadsheet that only one person understands, the integration is usually the easiest part to fix. CozyHR handles attendance capture, configurable OT rules by employee group, automated computation, approval workflows and payroll posting as a single chain with the audit trail preserved — so month-end becomes a review rather than a reconstruction. Worth a look if you would rather spend the last week of the month analysing your overtime than recalculating it.