ESI Compliance in India: A Complete 2026 Guide

ESI Compliance in India: A Complete 2026 Guide for Employers

If your company employs people in India and pays wages below a certain threshold, you almost certainly have obligations under the Employees' State Insurance (ESI) Act — whether you've thought about it or not. ESI is one of the oldest and most widely applicable pieces of social security legislation in the country, yet it remains one of the most misunderstood. HR and payroll teams often lump it together with EPF in their heads, assume "our HRMS handles it," and move on — until a labour inspector, an audit, or an employee's medical claim surfaces a compliance gap nobody noticed.

This guide walks through what ESI actually is, who it covers, how contributions work, what employers are responsible for month to month and year to year, and where companies most commonly slip up. It's written for HR managers, founders, and payroll teams running operations in India — whether you're a five-person startup crossing the applicability threshold for the first time or an established company trying to tighten up a compliance program that's grown organically over the years.

A note before we start: contribution rates, wage ceilings, and procedural rules under ESI are set by the central government and revised periodically. This article explains the mechanics and the "how it works" in general terms. Always verify current rates, thresholds, and forms on the official ESIC portal (esic.gov.in) or with your compliance advisor before making payroll decisions.

What Is the ESI Scheme, and Why Does It Exist?

The Employees' State Insurance Scheme is a self-financing social security and health insurance program for Indian workers, administered by the Employees' State Insurance Corporation (ESIC), an autonomous body under the Ministry of Labour and Employment. It was designed to provide employees — particularly those in the lower and middle income brackets — with medical care, cash benefits during sickness or maternity, and compensation in the event of employment-related injury or death, without the employee having to bear the full cost out of pocket.

Unlike EPF, which is primarily a retirement savings mechanism, ESI is fundamentally an insurance scheme. Both employer and employee contribute a percentage of wages every month, and that pooled fund is used to run a network of ESI hospitals, dispensaries, and empanelled private hospitals where covered employees and their dependents can access free or subsidized treatment. It also pays out cash benefits directly to employees for specific covered events.

For employers, ESI is not optional once your establishment and your employees meet the applicability criteria. It is a statutory obligation enforced through registration, monthly contribution filing, and periodic inspection — with real financial and legal consequences for non-compliance.

Who Does ESI Apply To?

Two separate questions determine ESI applicability, and it's important not to conflate them:

1. Does the establishment fall under ESI?

The ESI Act applies to specific classes of establishments — factories and a wide range of other establishments (shops, hotels, restaurants, cinemas, road transport undertakings, educational institutions, and more, depending on state notifications) that employ a minimum number of persons, commonly a threshold of 10 or more employees (the exact count and which categories of establishments are covered can vary by state, since many states have issued their own notifications extending ESI coverage). Once an establishment is covered, it generally stays covered even if the headcount later drops below the threshold, unless a formal exemption process is completed.

2. Which employees within that establishment are covered?

Even in a covered establishment, only employees whose wages fall at or below a specified monthly wage ceiling are covered under ESI. Employees earning above that ceiling are excluded from the scheme (though some employers choose to offer equivalent private health coverage to non-covered employees as a benefit). The wage ceiling is revised periodically by the government, so payroll teams need a process to re-check applicability whenever an employee's compensation changes, and whenever the government issues a revision.

A practical implication: an employee who starts the year below the ceiling and crosses it mid-year (through an increment, for example) typically continues to be covered for the remainder of that contribution period under the scheme's continuity rules, rather than dropping out immediately. HR and payroll teams should understand these continuity provisions rather than mechanically removing anyone who crosses the ceiling on their next payslip — get this wrong and you risk either an unlawful deduction stoppage or an unnecessary one.

How ESI Contributions Work

ESI contributions are calculated as a percentage of "wages" as defined under the Act (which is broader than basic salary and includes most regular cash components paid to the employee, subject to specific inclusions and exclusions defined in the rules). Both employer and employee contribute:

• The employer's contribution is a percentage of the employee's gross wages, paid entirely by the employer on top of the employee's salary — it is a cost to the company, not a deduction from the employee.
• The employee's contribution is a smaller percentage, deducted directly from the employee's wages each pay cycle.

Both contributions are deposited together by the employer with ESIC through the online portal, along with a monthly contribution statement. Employees earning below a very low daily wage threshold are typically exempted from paying their share of the contribution, even though the employer's share still applies — this is a protective provision meant to avoid burdening the lowest-paid workers, and payroll teams should build this exemption into their salary structure logic rather than applying the employee contribution uniformly to everyone under the wage ceiling.

Because both the wage ceiling and the contribution percentages are subject to government revision, the single most important control an Indian payroll team can build is a documented process for checking the ESIC portal or a reliable compliance bulletin at the start of each financial year (and whenever a mid-year notification is issued) rather than relying on rates hard-coded into a spreadsheet from years ago.

Contribution Periods and Benefit Periods

ESI runs on a distinctive twice-yearly cycle rather than a simple calendar-month cycle:

• There are two contribution periods each year, each spanning six months.
• Corresponding to each contribution period is a benefit period, which begins roughly six months after the contribution period starts and also runs for six months.

The logic is that an employee's eligibility for most cash benefits in a given benefit period is determined by whether contributions were paid on their behalf during the corresponding earlier contribution period. This lag is a common source of confusion for employees ("I'm covered under ESI, why wasn't my claim approved?") — HR teams should proactively explain this cycle when onboarding ESI-covered employees, since it prevents a lot of downstream grievance-handling.

Payroll and HR teams should maintain a simple internal calendar marking the start and end of each contribution period and benefit period, along with the associated filing and payment due dates, so nothing slips through the cracks during a busy month.

What Registration Involves

When an establishment first becomes covered under ESI, the employer must register the establishment with ESIC and obtain a 17-digit registration number. In most states this is now integrated with other registrations through unified portals (such as Shram Suvidha or state-specific single-window systems), but the ESIC-specific registration and code allotment remains a distinct step employers need to complete.

Once the establishment is registered, every eligible employee must be individually registered under the scheme and issued an Insurance Number, which today is generated along with an ESIC-issued Pehchan card (the physical/e-card that lets the employee and dependents access ESI medical facilities). This registration should happen as part of the new-hire onboarding workflow — not as an afterthought weeks later — because an employee cannot access ESI medical benefits or file a claim without an active Insurance Number.

A well-run HR onboarding checklist for any ESI-eligible new joiner should include:

1. Collecting the documents needed for ESI registration (identity proof, bank details, family/dependent details for the Pehchan card).
2. Submitting the registration through the ESIC portal within the prescribed timeline.
3. Confirming the Insurance Number is generated and sharing the Pehchan card details with the employee.
4. Briefing the employee on which hospitals/dispensaries they're mapped to and how to use the scheme.
5. Recording the ESI status in the HRMS so it flows correctly into monthly payroll processing.

Monthly Compliance: What Employers Must Do Every Cycle

ESI compliance isn't a one-time registration exercise — it's a recurring monthly obligation with a fairly unforgiving due-date structure. A typical monthly cycle looks like this:

Step 1: Compute contributions during payroll run. For every ESI-covered employee, calculate the employer and employee contribution based on that month's gross wages (subject to the ESI wage definition), applying any relevant exemptions for very low earners.

Step 2: Deduct the employee's share. The employee contribution is withheld from the salary in that month's payslip, clearly itemized as a statutory deduction.

Step 3: File the monthly contribution and remit payment. The combined employer and employee contribution must be deposited with ESIC, along with the required contribution details, by the statutory due date each month — historically this has been a fixed number of days after the end of the wage month, and missing it triggers interest and penalty exposure even if the amount is eventually paid.

Step 4: Reconcile new joiners and exits. Any employee who joined or left during the month needs to be reflected accurately — new joiners registered promptly, and exits marked so contributions stop being filed for someone no longer on the payroll (while ensuring any final-month contribution due is still paid correctly).

Step 5: Retain records. Maintain wage registers, attendance records, and contribution challans in a form that would hold up to an ESIC inspection, for the retention period prescribed under the rules.

Because this is a monthly, recurring, deadline-driven process, most mid-sized and larger employers in India run it through payroll software or an HRMS with built-in statutory compliance modules (like CozyHR) rather than manually recalculating contributions and filing challans by hand every month. The risk of a manual process isn't usually the calculation itself — it's a missed deadline because someone was on leave, or a new joiner who fell through the cracks between the HR team and the payroll team.

Benefits Employees Can Access Under ESI

It's worth HR teams understanding — and being able to explain to employees — what ESI actually delivers, because a scheme employees don't understand is a scheme they undervalue and sometimes resent seeing deducted from their payslip.

Broadly, ESI-covered employees and their dependents can access:

• Medical benefit: Treatment at ESI hospitals and dispensaries, and at private hospitals empanelled with ESIC, for the employee and eligible family members, generally without a direct cost at the point of care.
• Sickness benefit: A cash benefit paid to the employee during certified periods of sickness, subject to eligibility conditions tied to the contribution record.
• Maternity benefit: Cash benefit during a period of leave connected with pregnancy, confinement, or related conditions, for eligible insured women employees, paid in addition to (and coordinated with) any maternity leave entitlement under other applicable laws.
• Disablement benefit: Compensation for temporary or permanent disablement arising from an employment injury.
• Dependants' benefit: A periodic payment to the dependents of an employee who dies as a result of an employment injury.
• Other benefits: Depending on the scheme's current provisions, this can include funeral expenses, vocational rehabilitation support, and certain unemployment-linked benefits under specific government schemes layered on top of the core ESI framework.

Because the specific eligibility conditions, waiting periods, and benefit amounts are set out in the ESI rules and change periodically, HR teams should point employees to the official ESIC resources or their appointed compliance consultant for exact figures rather than promising specific amounts from memory.

Common Employer Mistakes on ESI Compliance

Across HR and payroll teams in India, a handful of mistakes come up again and again:

1. Misjudging the wage ceiling at the point of hiring or increment. An employee hired just below the ceiling gets a mid-year raise that pushes them over, and payroll simply stops the deduction without checking the continuity rule for the current contribution period — this can create a compliance gap that only surfaces at inspection time.

2. Treating "wages" for ESI the same as "basic salary." The ESI wage definition is broader than basic pay and includes most regular cash allowances; employers who calculate contributions only on basic salary risk under-contributing, which is a compliance exposure even if it feels like a cost-saving measure.

3. Delayed registration of new joiners. If an eligible employee isn't registered promptly, they may be unable to access medical benefits when they actually need them — which becomes an HR and employee-relations problem, not just a compliance one.

4. Missing the monthly due date. Even a few days' delay in remitting contributions can trigger interest, and repeated delays invite closer regulatory scrutiny.

5. Poor recordkeeping. Wage registers, attendance data, and challans that aren't organized and retrievable make an ESIC inspection far more stressful and time-consuming than it needs to be — and can expose the company to adverse findings simply because it can't produce evidence of what it already did correctly.

6. Assuming ESI doesn't apply because "we're a startup." Applicability is based on establishment type and headcount, not on how new or small a company perceives itself to be. Fast-growing startups frequently cross the ESI threshold without anyone flagging it, especially when hiring happens in bursts across multiple locations.

7. Not accounting for contract and outsourced staff. If your establishment engages contract labour through a contractor, there are specific compliance responsibilities around ensuring those workers are also covered where applicable — principal employers can be held accountable if a contractor fails to comply.

Building an ESI Compliance Checklist for Your Organization

Here's a practical, reusable checklist HR and payroll leaders can adapt:

At the establishment level

• [ ] Confirm whether your establishment(s) meet ESI applicability criteria in each state you operate in.
• [ ] Complete ESIC registration and obtain the establishment code, if not already done.
• [ ] Map out contribution periods and benefit periods for the current year on an internal compliance calendar.
• [ ] Document your internal process owner (HR, payroll, or an outsourced compliance partner) for each ESI-related task.

At the employee level

• [ ] Build ESI eligibility checks into new-hire onboarding (wage ceiling check, registration, Pehchan card issuance).
• [ ] Re-check eligibility whenever an employee's compensation changes materially.
• [ ] Ensure exits are reflected accurately and promptly in ESI filings.
• [ ] Maintain a clear internal record of each employee's ESI status, insurance number, and contribution history.

Every payroll cycle

• [ ] Calculate employer and employee contributions using the current wage definition and rates.
• [ ] Deduct and clearly itemize the employee's share on the payslip.
• [ ] File the monthly return and remit payment before the due date.
• [ ] Reconcile the filing against the payroll register to catch discrepancies before they compound.

Periodically

• [ ] Reconcile records ahead of any scheduled or surprise ESIC inspection.
• [ ] Refresh your understanding of current wage ceilings and contribution rates at least once a year, and whenever a government notification is announced.
• [ ] Audit contractor and outsourced-staff compliance if your establishment engages contract labour.
• [ ] Review employee awareness — run a short internal communication explaining ESI benefits and how to use them.

ESI vs EPF: A Quick Comparison

HR teams new to Indian statutory compliance often ask how ESI relates to EPF, since both are payroll deductions that appear on nearly every payslip for covered employees. The table below is a simplified comparison to keep the concepts straight — always confirm current thresholds and rates from official sources.

Many employees are covered under both schemes simultaneously, and payroll systems need to apply the correct wage definitions and ceilings independently for each — they are not interchangeable calculations, even though both deductions appear side by side on the payslip.

How HR Teams Should Communicate ESI to Employees

Compliance aside, ESI is a genuine benefit, and employees who understand it value it more — and are less likely to generate confused grievances that eat up HR's time. A few practical communication habits:

• Include a plain-language explainer of ESI (what it covers, how to use the Pehchan card, which hospitals are in-network) in your onboarding materials, not just a line item on the offer letter.
• Proactively tell employees when they've crossed the wage ceiling and what that means for their coverage going forward, rather than letting them notice a changed deduction on their payslip and ask HR.
• Keep a simple FAQ document accessible through your employee self-service portal, so employees can self-serve answers to common questions ("how do I claim sickness benefit," "how do I add a dependent") instead of routing every question through HR.
• Run a short refresher session annually, especially after any change in the wage ceiling or contribution rates, so managers and employees aren't caught off guard.

A Practical Walkthrough: How a Growing Startup Should Approach ESI

It helps to see the moving pieces in sequence rather than as a list of rules. Consider a hypothetical 40-person SaaS company operating out of two cities that has never formally registered under ESI because "we're a tech company, not a factory." Here's how a responsible HR lead would work through it:

Step 1 — Confirm applicability. The team checks whether their establishment type and headcount trigger ESI coverage in each state they operate in. Many states have extended ESI to a broad range of commercial establishments, not just factories, so "we're not a factory" is not a safe assumption on its own.

Step 2 — Segment the workforce by wage. Payroll pulls current gross wages for every employee and identifies who falls at or below the applicable ceiling. In a typical tech company, this is often concentrated in support functions, junior operations roles, and administrative staff — not necessarily engineers, but it's a mistake to assume no one qualifies without actually checking.

Step 3 — Register the establishment and eligible employees. HR completes establishment registration, then registers each eligible employee, prioritizing anyone who might need to file a claim soon (for example, someone approaching a medical procedure or maternity leave).

Step 4 — Update the payroll engine. Contribution rates are configured against the correct wage definition, with the low-wage employee exemption built in as a rule rather than applied manually.

Step 5 — Build the recurring calendar. The company sets calendar reminders tied to the actual statutory due date each month, with a named owner and a backup owner, so a single person's leave or attrition doesn't create a compliance gap.

Step 6 — Communicate to the workforce. HR sends a short note explaining what changed, why, and what it means for affected employees, along with FAQ content on the self-service portal.

Step 7 — Audit after the first two cycles. After the first two months of filings, HR and payroll do a joint review to catch any employees who were missed, any wage-definition errors, or any registration issues before they compound into a larger backlog.

This phased approach is deliberately conservative — it prioritizes getting coverage right for people who need it soonest, while building the underlying process so month three onward runs on autopilot rather than manual heroics.

What Triggers an ESIC Inspection, and How to Be Ready

Employers sometimes think of inspections as random, but in practice they're often triggered by identifiable events: a complaint from a current or former employee about a denied claim or missing registration, a routine sector-wide inspection drive, discrepancies flagged during cross-verification with other statutory filings (like PF or income tax returns), or simply the establishment's first few years after registration, when authorities often verify that the registration is being followed through with actual compliance.

Being inspection-ready isn't about being afraid of inspections — it's about having a compliance program clean enough that an inspection is a non-event rather than a fire drill. Practically, that means:

• Wage registers and attendance records that reconcile cleanly with what was actually filed and paid.
• A complete, chronological registration record for every eligible employee, including anyone who has since exited.
• Contribution challans and acknowledgment receipts filed and retrievable by month, not scattered across email inboxes.
• A documented internal process (even a simple one-page SOP) showing who is responsible for each step, so the company can demonstrate a functioning system rather than ad hoc effort.
• A clear record of any exemption applications, appeals, or correspondence with ESIC, if applicable.

Companies using an HRMS with built-in statutory compliance tracking generally find this far less stressful, because the records exist as a natural byproduct of running payroll each month rather than something that has to be reconstructed under time pressure.

Special Situations HR Teams Should Know About

A few edge cases come up often enough to be worth flagging explicitly:

Employees working across multiple states. If your company has employees who transfer between locations, or a distributed workforce with people working from different states, confirm how ESI applicability and the employee's mapped dispensary/hospital network should be updated to reflect their actual work location.

Seasonal and short-term hires. Even employees hired for a short, defined period can trigger ESI obligations if they meet the wage and establishment criteria — don't assume short tenure exempts them.

Employees on leave without pay. Understand how contribution periods and continuity of coverage are affected when an employee is on an extended unpaid leave, so you don't inadvertently create a coverage gap they're unaware of.

Mergers, acquisitions, and entity restructuring. When employees move between legal entities as part of a corporate restructuring, their ESI registration and contribution history needs to be handled deliberately — this is often missed in the rush of an M&A integration, leaving a compliance gap that surfaces only much later.

Remote-first and hybrid companies. Even fully remote companies with a registered office and payroll run out of India are not automatically exempt — applicability depends on the establishment's registration and the employees' wages, not on whether staff work from a physical office.

FAQs

Q1: Does ESI apply to every company in India? No. ESI applies to establishments of specified categories that meet the minimum employee-count threshold (commonly 10 or more, though this can vary by state notification), and within a covered establishment, only to employees earning at or below the prescribed wage ceiling. Check current applicability rules for your state and establishment type before assuming you're exempt.

Q2: What happens if an employee's salary crosses the ESI wage ceiling mid-year? Under the scheme's continuity provisions, coverage typically continues for the remainder of the ongoing contribution period rather than stopping immediately. Payroll teams should understand this rule precisely rather than abruptly halting deductions the moment a raise is processed.

Q3: Is the employee contribution mandatory for everyone below the wage ceiling? Employees earning below a very low daily wage threshold are generally exempted from paying their own contribution, though the employer's contribution still applies. This is a specific carve-out, not a general rule, so don't assume it applies to all covered employees.

Q4: What counts as "wages" for calculating ESI contributions? The ESI Act's definition of wages is broader than basic salary and generally includes most regular cash components paid to the employee, with specific statutory inclusions and exclusions. Employers should not calculate ESI contributions on basic pay alone without checking the actual wage definition.

Q5: What are the consequences of missing an ESI filing deadline? Late payment of contributions typically attracts interest, and persistent non-compliance can invite penalties and closer regulatory scrutiny, including inspections. Beyond the financial cost, delayed registration can also mean employees are unable to access medical benefits when they need them.

Q6: Do contract workers and outsourced staff need to be covered under ESI? If they meet the applicability criteria, yes — and the principal employer can carry responsibility for ensuring contractors comply, even though the contractor is the immediate employer. This is a frequently overlooked area in ESI compliance programs.

Q7: How is ESI different from private group health insurance that some companies offer? ESI is a statutory scheme with its own network of hospitals and a defined benefit structure, funded through mandatory payroll contributions. Private group health insurance is a discretionary employee benefit employers may offer on top of, or in addition to, statutory ESI coverage — it doesn't replace the legal obligation to register and contribute for eligible employees.

Q8: How often should we review our ESI compliance process? At minimum, once a year at the start of the financial year, and immediately whenever the government issues a notification changing the wage ceiling, contribution rates, or procedural requirements. Growing companies should also review applicability whenever headcount crosses a new threshold or they open operations in a new state.

Conclusion

ESI compliance is one of those areas of Indian payroll where the rules are stable enough to build a repeatable process around, but detailed enough that "we'll figure it out manually" tends to break down as a company scales past a handful of employees or locations. The employers who handle it well share a few habits: they check applicability deliberately rather than assuming, they build ESI checks into onboarding and compensation-change workflows rather than treating it as a once-a-year task, they keep clean, inspection-ready records, and they communicate the scheme to employees so it's understood as a benefit rather than just a mystery deduction.

If your team is still tracking ESI contributions, due dates, and employee eligibility across spreadsheets and manual reminders, it's worth asking how much of that could be automated. A payroll and HRMS platform like CozyHR is built to handle statutory calculations, filing reminders, and employee records in one place, so your HR and payroll teams can spend less time chasing deadlines and more time on the work that actually needs human judgment. If you'd like to see how CozyHR handles ESI and other statutory compliance workflows for Indian employers, we're happy to walk you through it.