ESI Compliance for Employers: A Practical 2026 Guide

ESI compliance is where many growing Indian companies first collide with social security law. Provident Fund gets the attention, but the Employees' State Insurance scheme — run by the Employees' State Insurance Corporation (ESIC) — arrives earlier for many businesses, covers a wider slice of benefits, and produces some of the most avoidable notices in Indian payroll. Miss the registration window when you cross the employee threshold, or deduct contributions and deposit them late, and you are dealing with interest, damages, and inspections over amounts that were never large to begin with.

This guide walks employers through ESI from first principles: who is covered, how contributions work, the registration and monthly filing process, what benefits employees actually receive, how contribution periods and the wage ceiling interact, and the operational mistakes that generate most ESI trouble. It is written for HR managers, founders, and payroll teams in India who want a working command of ESI compliance — with the standing caveat that rates, ceilings, and thresholds change by notification, so verify current figures on the ESIC portal before acting.

What Is ESI?

The Employees' State Insurance scheme is a contributory social security programme established under the Employees' State Insurance Act, 1948. In exchange for a small percentage of wages contributed by employer and employee, covered employees ("insured persons") and their dependants receive a package of benefits: free medical care through ESIC hospitals and dispensaries, cash compensation during sickness and maternity, disablement benefits, dependants' pensions after employment injury, and more.

Three design features shape how ESI behaves in payroll:

• It is wage-ceiling based. Only employees earning up to a notified monthly wage ceiling (₹21,000 in the general case for many years, with a higher ceiling for persons with disability — verify current figures) are covered. Employees above the ceiling are outside the scheme entirely.
• It is establishment-triggered. Coverage attaches to factories and notified establishments once they employ the threshold number of persons — generally 10 or more in most states (20 in a few, for certain establishment categories) — in areas where the scheme has been implemented.
• It runs on fixed contribution periods. Coverage decisions lock in for six-month blocks, which produces the counterintuitive rule that an employee who gets a raise above the ceiling mid-period continues contributing until the period ends.

The scheme applies to non-seasonal factories and to establishments notified by state governments — shops, hotels, restaurants, cinemas, road transport, newspapers, educational and medical institutions, and more, with the list varying by state notification. ESIC has extended implementation to most districts across India, so geographic non-coverage is far rarer than it used to be.

Who Must Register: Applicability in Practice

Work through applicability as three questions:

1. Is your establishment covered?

• Factories using power with the threshold number of workers are covered under the Act directly.
• Other establishments (shops, offices, service businesses) are covered by state notification once they cross the threshold headcount — commonly 10 employees, though a few states retain 20 for some categories.
• Location matters: the scheme applies in "implemented areas". With near-national implementation, assume covered unless you verify otherwise for a specific location.

The headcount test counts employees broadly — including those above the wage ceiling, contract workers on premises, and in many circumstances casual and temporary staff. A common and costly error is counting only coverable (below-ceiling) employees when testing the threshold.

2. Which employees are covered?

Every employee whose monthly wages are at or below the ceiling must be enrolled — permanent, temporary, casual, or engaged through a contractor working on your premises. There is no waiting period and no probation carve-out: coverage begins from day one of employment.

Apprentices engaged under the Apprentices Act are generally excluded; trainees under company-designed "training schemes", by contrast, have frequently been held to be employees — the label does not decide the question, the substance of the engagement does.

3. What counts as wages?

ESI wages are defined broadly: basic pay, dearness allowance, house rent allowance, city compensatory allowance, overtime (for contribution purposes, though overtime does not count when testing the ceiling), incentives paid at intervals not exceeding two months, and most other cash payments under the contract of employment. Items generally excluded include employer PF contributions, gratuity, encashment of leave at exit, and annual bonus. Two operational notes:

• Overtime asymmetry: overtime attracts contributions but is ignored when deciding whether the employee is within the ceiling — an employee at ₹20,500 base who earns overtime stays covered, and contributions are payable on the overtime too.
• Washing allowance and genuine reimbursements paid to defray special expenses are typically outside wages; relabelling salary as "reimbursement" to dodge ESI is a classic inspection finding.

Contribution Rates and the Money Flow

ESI contributions are a percentage of gross ESI wages, split between employer and employee. The rates in force in recent years — employer 3.25% and employee 0.75% of wages, following the 2019 reduction — should be verified against current notifications before you configure payroll.

Mechanics worth knowing:

• Employees earning below a notified daily average wage are exempt from the employee share (the employer still contributes). The threshold is modest and mostly relevant for very low-wage or part-month cases.
• Rounding: contributions are calculated per employee and rounded up to the next rupee.
• The employer bears its share; deduction of the employer share from wages is illegal. Only the employee share may be deducted from salary.
• New implementation areas have historically enjoyed reduced rates for an initial period — relevant if you open facilities in newly notified districts.

The Contribution Period / Benefit Period System

ESI runs on two interlocking six-month cycles:

Two rules follow that regularly surprise payroll teams:

1. Mid-period ceiling crossings don't end coverage immediately. An employee earning ₹20,000 who is raised to ₹25,000 in June continues to be covered — and contributions continue on the full (now higher) wages — until 30 September. Coverage ends only from the next contribution period.
2. Benefits lag contributions. An employee's entitlement to cash benefits in a benefit period depends on contributions in the corresponding earlier contribution period, which is why continuous, timely deposit matters to employees and not just to compliance officers.

Registration: Getting Onto the System

Employer registration

Registration is online. Since the government unified several registrations through the Shram Suvidha portal, new companies frequently receive ESIC (and EPFO) registration numbers at incorporation itself through the incorporation form. If not, employers register on the ESIC portal within the statutory window — 15 days from becoming coverable is the timeline commonly cited under the regulations. On registration you receive a 17-digit employer code number, and separate sub-codes can be obtained for branches in other regions.

Keep ready: incorporation documents, PAN, address proof of the establishment, bank details, headcount and wage details, and details of directors/partners. There is no registration fee.

Important: liability runs from the date you became coverable, not the date you registered. Registering late does not erase the intervening contribution liability.

Employee registration (insured persons)

Each covered employee is registered on the portal — ideally on or before their first day, and within the short window the regulations allow — and receives a 10-digit Insurance Number and a Pehchan card (e-Pehchan) that gives the employee and dependants access to medical care. Capture at onboarding: Aadhaar (ESIC has been moving toward Aadhaar-seeded records), bank details, family/dependant particulars with dates of birth, and a nominee. An employee who already has an insurance number from previous employment keeps it for life — always ask before generating a new one, because duplicate insurance numbers fragment the contribution history that benefit entitlements depend on.

The Monthly Compliance Cycle

Once registered, the employer's rhythm looks like this:

Step 1 — Compute contributions each payroll run

Identify covered employees (at or below the ceiling as at the start of the contribution period, plus all new joiners at or below it), compute employer and employee shares on ESI wages, and deduct only the employee share from salary.

Step 2 — File the monthly contribution and pay

Contributions are due within 15 days of the end of the month (verify the current due date). Filing and payment are integrated online: upload or confirm the employee-wise contribution details and pay through the portal. The monthly contribution filing effectively doubles as the ongoing return.

Step 3 — Maintain registers and records

Keep an employee register with wages and contributions, an accident book, and inspection-ready records of challans and filings. Preserve records for the period the regulations require — multi-year retention is the safe operating assumption.

Step 4 — Handle events

• New joiners: register before or at joining; coverage runs from day one.
• Exits: mark date of leaving on the portal promptly; lingering "active" employees who have left generate mismatch notices.
• Zero-contribution months for any employee (unpaid leave, for example) should carry the appropriate reason code rather than being skipped.
• Accidents at work: report through the portal within the prescribed timelines; the accident report protects the employee's claim to disablement benefits and the employer's record.

Step 5 — Reconcile

Monthly: payroll register vs portal filing vs bank debit. Half-yearly: a fuller reconciliation aligned to the contribution period, including ceiling-crossers who exit coverage at the period boundary.

What Employees Get: The Benefits Package

Employers who can explain ESI benefits well convert a payslip deduction into something employees value. In outline (conditions and rates per current ESIC rules):

• Medical benefit: full medical care for the insured person and dependants through ESIC facilities, from day one of insurable employment, with no ceiling on treatment expenditure. Retired insured persons meeting conditions can retain medical care for a nominal annual contribution.
• Sickness benefit: cash compensation at a substantial fraction of average daily wages (around 70% under long-standing rules) for up to 91 days a year, subject to a minimum contribution record in the relevant contribution period. Enhanced and extended sickness benefit exist for specified situations and long-term diseases.
• Maternity benefit: paid leave benefits for confinement, miscarriage, and related contingencies at rates near full average daily wages for the durations the rules provide, subject to contribution conditions — this operates alongside the Maternity Benefit Act framework for eligibility questions.
• Disablement benefit: for employment injury, temporary disablement benefit at a high fraction of wages for the duration of disablement, and permanent disablement pension proportionate to loss of earning capacity — with no minimum contribution condition for employment-injury cases.
• Dependants' benefit: monthly pension to dependants where an employment injury leads to death.
• Other benefits: funeral expenses, vocational and physical rehabilitation, and unemployment allowance under the Rajiv Gandhi Shramik Kalyan Yojana / Atal Beemit Vyakti Kalyan Yojana-type schemes for involuntary job loss, per conditions in force.

The package is why courts and inspectors treat ESI evasion severely: unpaid contributions translate directly into employees losing sickness cash, maternity cash, and injury pensions when they need them.

ESI and Contractors: The Principal Employer Problem

If contract workers deployed on your premises are not covered by their contractor, the liability lands on you as principal employer. The Act makes the principal employer responsible for contributions in respect of employees engaged through immediate employers (contractors), with a right to recover from the contractor afterwards.

A working control set:

1. Collect each contractor's ESI registration number before work begins.
2. Make monthly challan and filing proof a condition of invoice payment.
3. Verify that the workers actually deployed to you appear in the contractor's filings — headcount matching, not just challan totals.
4. Keep these records establishment-wise; inspections routinely start with the contractor file.
5. Where a contractor is unregistered, either require registration or cover the workers under your own code and recover the cost contractually.

Inspections, Interest, and Damages

ESI enforcement follows a familiar arc: data-driven notices (mismatches between filings, PF data, and income-tax data), inspections under the Act, assessment of contributions on omitted wages or omitted persons, and recovery. Consequences of default include:

• Simple interest on delayed contributions (12% per annum has been the long-standing rate — verify current).
• Damages on a graded scale rising with the length of default, up to the full amount of the contribution in the worst band.
• Prosecution in serious cases — deducting employee contributions and failing to deposit them is treated as a criminal breach, not a paperwork lapse.
• Benefit-denial exposure: if an employee suffers a contingency during a period the employer failed to insure them, the employer can be made to bear the cost.

The most common assessment themes are wage-component disputes (allowances excluded from ESI wages without basis), uncovered contract labour, trainees treated as non-employees, and threshold miscounting. All four are preventable with configuration and a contractor file.

Common Mistakes and How to Avoid Them

1. Registering late after crossing the threshold. Track headcount monthly against the threshold, counting all employees, and register within the window. Liability backdates regardless.
2. Testing the ceiling with the wrong wage figure. Use gross ESI wages excluding overtime for the ceiling test; do not use CTC or net pay.
3. Stopping contributions the month an employee crosses the ceiling. Coverage continues to the end of the contribution period — configure payroll to hold coverage until the boundary.
4. Deducting the employer share from employees. Illegal, and a reliable inspection finding. Only 0.75%-type employee share comes from wages.
5. Ignoring day-one coverage for casual and temporary staff. Short-tenure staff are covered; "he was only here for three weeks" is not a defence.
6. Duplicate insurance numbers. Always ask joiners for an existing IP number; portability preserves their benefit history.
7. Leaving exits unmarked on the portal. Causes mismatches and inflated compliance demands; make date-of-leaving updates part of the offboarding checklist.
8. Assuming a "stipend" or "consultant fee" avoids ESI. Substance governs; misclassified workers are assessed with interest and damages.

Setting Up ESI Correctly in Payroll: A Checklist

• Map which establishments and locations are covered and hold sub-codes where needed.
• Configure ESI wage components explicitly — what is in, what is out — and document the basis for exclusions.
• Automate the ceiling test at the start of each contribution period, plus day-one coverage for joiners.
• Hold coverage for mid-period ceiling-crossers until the period boundary.
• Apply the low-wage employee-share exemption where relevant.
• Generate the monthly contribution file from payroll rather than re-keying into the portal.
• Calendar the monthly due date with an owner and a backup owner.
• Maintain the contractor compliance file with monthly proof collection.
• Reconcile monthly and at each contribution-period boundary.
• Store challans, filings, registration certificates, and accident reports in an audit-ready archive.

An HRMS with ESI logic built in — CozyHR among them — handles the ceiling tests, period-boundary rules, coverage holds, and challan-ready outputs automatically, which is exactly the machinery that spreadsheets get wrong at the edges.

How ESI Interacts with Other Statutory Frameworks

ESI and PF. The two schemes run on different wage ceilings, different wage definitions, and different portals, but inspectors increasingly cross-match their data. An employee visible in PF filings but absent from ESI (while below the ESI ceiling) is an automated red flag. Keep the two employee masters synchronised — same joining dates, same exits, consistent wage components.

ESI and the Maternity Benefit Act. Where a woman employee is entitled to maternity benefit under ESI, the Maternity Benefit Act generally cedes ground to the ESI framework, subject to the eligibility conditions of each. HR should determine which regime applies before processing maternity leave pay, because paying salary in full while ESI also pays benefit — or paying neither — are both errors seen in practice.

ESI and the Employees' Compensation Act. For establishments and employees covered by ESI, employment-injury compensation flows through ESI's disablement and dependants' benefits rather than the Employees' Compensation Act; for workers outside ESI (above the ceiling, or in non-implemented pockets), the Compensation Act remains the operative regime. Site-accident SOPs should branch on coverage status.

ESI and the new labour codes. The Code on Social Security consolidates ESI law and contemplates expansions — including pathways for gig and platform workers and establishments below thresholds opting in — with implementation proceeding by notification. Track notifications rather than assuming the 1948 framework's edges are permanent; the direction of travel is broader coverage.

ESI vs Group Health Insurance: A Comparison Employers Are Often Asked For

Employees — and sometimes founders — ask why the company "pays twice" for ESI and a group mediclaim policy. The honest answer is that they are different instruments doing different jobs:

The practical takeaway: for below-ceiling employees, ESI is the legal floor and group insurance is an experience upgrade; for above-ceiling employees, group insurance is often the only cover. Companies that explain this framing during onboarding field noticeably fewer "why is ESI cut from my salary" tickets.

Worked Examples

Example 1 — Crossing the establishment threshold. A Jaipur design studio grows from 8 to 11 employees in March, including two part-time assistants. The part-timers count. The studio becomes coverable, registers within the window, enrols the seven staff members whose gross wages are below the ceiling, and starts contributions from the coverage date. Had it waited until its CA noticed in July, liability would still run from March — with interest.

Example 2 — The mid-period raise. An insured employee earning ₹19,800 gross is promoted to ₹24,000 effective 1 July. July falls inside the April–September contribution period, so contributions continue on ₹24,000 — the full new wage — through September. From 1 October, the employee exits coverage. Payroll must both hold coverage for three months and compute on the higher wage; systems that key coverage off current salary alone fail this case in both directions.

Example 3 — Contractor housekeeping staff. A Gurugram office engages six housekeeping workers through a facilities vendor. The vendor's invoices are paid for a year without contribution proof; an inspection finds the workers were never enrolled. As principal employer, the company is assessed for contributions with interest and damages, and then has to pursue the vendor for recovery. A one-page monthly compliance annexure to the invoice would have prevented the entire episode.

Example 4 — The overtime month. An insured employee at ₹20,600 gross works overtime worth ₹2,400 in a festival month. The overtime does not push them out of coverage (it is ignored for the ceiling test) but contributions for that month are payable on ₹23,000. Payroll needs the asymmetry coded explicitly.

An Onboarding and Offboarding SOP for ESI

At offer stage: determine expected coverage from the offered gross; mention the deduction in the salary annexure so the first payslip is no surprise.

Before day one: collect Aadhaar, bank details, family particulars with dates of birth, nominee, and any existing insurance number from prior employment.

On day one: register the insured person (or map the existing IP number to your establishment), generate the e-Pehchan card, and hand the employee a one-pager on how to locate their dispensary and use medical benefits.

During employment: update dependant records on marriage or childbirth; report workplace accidents through the portal within timelines; keep wage revisions flowing into the ESI wage base automatically.

At exit: mark the date of leaving on the portal in the same cycle as the final payroll; include ESI in the full-and-final checklist; remind the departing employee that benefit-period entitlements may continue for a time and that their insurance number is portable to the next employer.

A 90-Day Remediation Plan for Messy ESI

Days 1–30 — Diagnose. Reconcile the last twelve months: payroll ESI register vs portal filings vs bank debits. List employees with missing insurance numbers, unmarked exits, or wage-base discrepancies. Pull the contractor file and identify vendors with no compliance proof.

Days 31–60 — Regularise. Deposit any shortfalls with interest before they are demanded. Fix wage-component configuration and the ceiling/period logic in payroll. Enrol missed employees and close out stale records. Put contractor proof-of-compliance clauses into vendor renewals.

Days 61–90 — Systematise. Move monthly filing generation into payroll software, assign owner and backup for the due date, add ESI steps to onboarding and offboarding checklists, and archive a clean quarter as your baseline. Schedule a half-yearly self-audit aligned to contribution-period boundaries — the natural moment to catch ceiling-crossers and coverage exits.

Frequently Asked Questions

1. When does ESI become applicable to a company? Generally when a factory or notified establishment in an implemented area employs the threshold number of persons — 10 in most states for most categories, 20 in some — counting all employees, including those above the wage ceiling. Registration is due within the short statutory window after crossing the threshold, and liability runs from the coverage date, not the registration date.

2. Which employees have ESI deducted from salary? Employees whose monthly ESI wages are at or below the notified ceiling (₹21,000 in the long-standing general case; higher for persons with disability — verify current figures). They contribute the employee share (0.75% under prevailing rates) and the employer adds its share (3.25%). Employees above the ceiling are outside the scheme.

3. What happens when an employee's salary crosses the ESI ceiling mid-year? Coverage continues until the end of the running six-month contribution period (April–September or October–March), with contributions payable on the full higher wages. The employee exits coverage only from the start of the next period. Stopping deductions in the raise month is a compliance error.

4. Is ESI applicable to interns, trainees, and casual workers? Apprentices under the Apprentices Act are generally excluded. Company-scheme trainees and casual or temporary workers are usually employees for ESI purposes and are covered from day one if within the ceiling. The engagement's substance, not its label, decides coverage.

5. Who is liable for ESI of contract workers — the contractor or the company? Both are in the frame: the contractor as immediate employer should comply, but the principal employer is statutorily responsible if the contractor defaults, with a right of recovery. Collect contractor registration details and monthly compliance proof, and tie them to invoice payment.

6. What are the penalties for late ESI payment? Interest on the delayed amount (12% per annum has long applied), graded damages that rise with the period of default, and potential prosecution — especially where employee contributions were deducted but not deposited. Persistent default can also mean bearing benefit costs for uninsured contingencies.

7. Can an employer opt out of ESI by providing private health insurance? No. ESI is statutory; private group medical cover, however generous, does not substitute for coverage of eligible employees. Exemptions from the scheme exist only through formal government processes where establishments provide comparable or superior benefits, and they are narrowly granted — assume ESI applies unless a specific exemption order says otherwise.

8. What should we do if we discover past non-compliance? Quantify the gap (persons, periods, wages), regularise registrations, deposit arrears with interest, and correct the payroll configuration that caused the miss. Doing this proactively — before an inspection forces it — materially reduces damages exposure and preserves employees' benefit records. Consider professional advice for large or multi-year gaps.

Conclusion: Treat ESI as an Employee Benefit You Administer, Not a Tax You Endure

ESI is one of the few payroll items where compliance failure directly injures your own people: a missed contribution period can cost an employee sickness cash or a maternity benefit at the worst possible time. Run it the way you would run any benefit you were proud of — clean enrolment on day one, correct wage bases, deposits on time, contractors verified, exits closed out.

The mechanics are exactly what modern payroll software exists to absorb. CozyHR computes ESI with the ceiling tests, contribution-period holds, and wage-component rules built in, generates challan-ready monthly files, tracks contractor compliance, and keeps your filings reconciled with payroll — alongside PF, professional tax, TDS, and LWF in a single run. If ESI edge cases keep surfacing in your audits, try CozyHR and close them at the source.