CozyHR
Menu
Products
Docs
Resources
Compliance
Company
Support
Blog
ESIStatutory CompliancePayrollEmployee Benefits

ESI Compliance in India: Contributions, Returns & Benefits

A practical ESI guide for Indian employers: coverage, wage ceiling, contribution periods, registration, monthly payment, benefits and an audit checklist.

CozyHR editorial team 16 October 2026 20 min read
CozyHR Blog
ESI Compliance in India: Contributions, Returns & Benefits

Employees' State Insurance (ESI) is one of the statutory deductions that looks simple on a payslip and turns complicated the moment real life intervenes: an employee's salary crosses the wage ceiling mid-year, a new hire joins on the 20th, someone goes on long medical leave, or a branch opens in a new state. This ESI compliance guide for India explains contributions, eligibility, registration, monthly payment, returns, benefits, and the common mistakes that trigger notices, so that HR managers, founders, and payroll teams can run ESI confidently and calmly.

As with all statutory topics, rates, wage ceilings, and procedures are revised by the government and the ESI Corporation from time to time, and the labour codes are reshaping definitions. Treat the numbers in this article as illustrations of how the mechanics work and always verify current rates and thresholds on the official ESIC portal before you configure payroll.

What ESI is and what it gives employees

ESI is a self-financing social security and health insurance scheme for employees earning up to a prescribed monthly wage limit. Both the employer and the employee contribute a percentage of wages, and in return the employee and their dependants become entitled to medical care and a set of cash benefits.

From the employer's side, ESI is a monthly compliance obligation with a fixed due date, a registration obligation, and a records obligation. From the employee's side, it is a valuable benefit that many do not fully understand. Part of your job is to make sure employees know what they are getting, because that increases acceptance of the deduction and reduces payroll queries.

Key benefits under the scheme

  • Medical benefit: Insured persons and their families can receive medical care through ESI dispensaries and hospitals. Benefits include outpatient care, specialist treatment, hospitalisation, and in some cases super-specialty care.
  • Sickness benefit: Cash compensation for a limited number of days in a year when the insured person is certified sick, subject to contribution conditions.
  • Maternity benefit: Paid leave support for insured women for the maternity period, subject to contribution conditions.
  • Disablement benefit: Temporary and permanent disablement benefits for employment injuries and occupational diseases.
  • Dependants' benefit: Periodic payments to dependants if the insured person dies due to an employment injury.
  • Funeral expenses: A lump sum contribution towards funeral costs.
  • Unemployment allowance: Support in specified circumstances such as involuntary job loss due to closure or permanent invalidity, under notified schemes.

The list of benefits and the number of days or amounts are updated periodically, so link to the official site in your employee communication rather than hard-coding amounts in your handbook.

Coverage: which establishments and employees fall under ESI

Establishment coverage

ESI applies to specified categories of establishments such as factories, shops, hotels, restaurants, cinemas, road transport undertakings, newspaper establishments, educational institutions, and private medical institutions, once they cross the prescribed headcount in the notified areas. The headcount threshold has been lowered in many states over time, and the scheme has been extended to more areas.

Two practical points:

  1. Coverage is area-based. An establishment in a notified area is covered; the same business in a non-notified area may not be. When you open a new branch, check the status of that location.
  2. Once covered, you generally stay covered. A temporary dip in headcount below the threshold does not automatically release you.

Employee coverage and the wage ceiling

An employee is covered if their monthly wages are within the prescribed wage ceiling. For many years this ceiling has been set at a fixed monthly amount, with a higher limit for persons with disabilities. The wage definition includes basic, dearness allowance, HRA, conveyance, special allowances, and other regular payments, but excludes items such as employer contributions to PF, retrenchment compensation, gratuity, and certain others.

This is a key difference from PF: for ESI, the ceiling test is generally applied to gross wages that are regularly paid, not just basic salary. Many first-time employers get this wrong and compute eligibility on basic alone.

What about overtime?

Overtime wages are generally included in wages for ESI contribution purposes, but they are not counted for the purpose of determining whether the employee crosses the ceiling in some interpretations. Because this has been a source of confusion, record how your advisor or the ESIC office has confirmed the treatment, and apply it consistently.

Contribution rates and how to calculate them

The scheme has a split contribution: a percentage of wages from the employer and a smaller percentage from the employee. The combined rate is a small slice of gross wages, and both parts are calculated on the same wage base.

The calculation method

  1. Determine ESI-eligible gross wages for the month, including all regular components and overtime, but excluding excluded items.
  2. Check that the employee's monthly wages are within the ceiling (as defined at the start of the contribution period).
  3. Apply the employee rate to compute the employee deduction.
  4. Apply the employer rate to compute the employer contribution.
  5. Round up to the next rupee as required.

A worked example

Assume an employee earns the following in a month (for illustration only):

ComponentAmount (₹)
Basic11,000
HRA4,400
Conveyance1,600
Special allowance2,000
Gross wages19,000

If the wage ceiling in force is above this figure, the employee is covered. Multiply 19,000 by the employee rate and the employer rate separately, round each up to the next rupee, and the total payable to ESIC is the sum of both. Present the calculation on the payslip so employees can see exactly how much is deducted.

Days worked and loss of pay

Contributions are calculated on wages actually payable for the month. If an employee is on loss of pay, the wages for contribution purposes reduce accordingly. For days of zero wages, you still report the employee with zero wages in the monthly contribution file where required, and the number of days worked must be accurate.

Daily wage workers

For employees whose daily average wage is very low, the employee share may be exempt, with the employer paying its share. The exemption threshold is set by the government; verify the latest value.

The contribution period and the "ceiling crossing" rule

ESI uses contribution periods and benefit periods rather than month-by-month eligibility:

  • April to September (contribution period) leads to the following January to June benefit period.
  • October to March (contribution period) leads to the following July to December benefit period.

The key rule for employee coverage: if an employee's wages exceed the ceiling during a contribution period, the employee continues to be covered until the end of that contribution period. You do not remove them from ESI the month they cross the ceiling. You remove them at the start of the next contribution period if wages still exceed the ceiling.

Practical example

An employee earning below the ceiling gets a hike effective in July, taking gross wages above the ceiling. Because July falls inside the April to September contribution period, contributions continue through September. From October, the employee is no longer covered, provided wages remain above the ceiling at that point. HR should record the exit-from-ESI reason correctly in the portal.

This rule trips up payroll teams who stop deductions the very month wages cross the ceiling, leading to short payment and notices.

Registration: getting your employer code and employee numbers

Employer registration

When an establishment becomes covered, the employer must register on the ESIC portal and obtain an employer code number. The process is online and requires documents such as the establishment's proof of existence (registration certificate, GST, or shop licence), PAN, address proof, and details of the owner or authorised signatory. The registration should be completed within the statutory time from the date the establishment became covered.

Employee registration and the IP number

Each insured person receives an insurance number (IP number), generated through the portal after the employer registers them with details such as name, date of birth, date of appointment, Aadhaar, mobile number, address, nominee, and family details. Registration should happen on or before the date of joining, so that the employee is covered from day one.

A few practical tips:

  • Capture family details at registration, because ESI benefits extend to dependants and an incomplete record delays claims.
  • Keep Aadhaar and mobile details accurate. Mismatches cause problems when the employee tries to log in or claim benefits.
  • Make registration a mandatory step in your onboarding checklist, not an afterthought at month end.

Branches and multiple locations

If you have branches in different states or sub-regional office areas, each may require a separate registration or sub-code depending on current rules. Track the code, the location, and the responsible person in a simple register.

Monthly payment: due dates and mechanics

The due date

Employer and employee contributions are payable on a monthly basis, with the due date being within a fixed number of days after the end of the wage month. Late payment attracts interest, and prolonged default attracts damages. Because the due date is a fixed calendar day, build it into your payroll calendar with a reminder a few days earlier.

Payment process

  1. Prepare the monthly contribution file in the format required by the portal, listing each insured person, days worked, wages, and contribution.
  2. Upload the file and verify the validation report.
  3. Generate the challan.
  4. Make the payment through the supported online banking modes.
  5. Save the challan and payment confirmation.

Reconcile the challan amount with the payroll register before paying. A mismatch of even a few rupees across a large workforce can mean an employee has the wrong days or wages in the file.

Handling employees who left mid-month

If an employee leaves during the month, contributions are still payable on wages for the days up to exit. In the file, indicate the exit with the correct reason code and last working day. Declare the exit on the portal so the employee's coverage ends properly and they can be picked up by the next employer.

New joiners mid-month

New joiners are covered from their date of appointment, and contributions are due for the wages payable. Ensure the IP number is generated in time to include them in that month's file.

Returns, records, and inspections

Return of contributions

Under the current system, the monthly contribution filing effectively replaces the older paper-based half-yearly returns for many employers. Still, keep a clear record of the contribution periods, the filed data, and payments, because inspections and audits look for a consistent chain: payroll register, contribution file, challan, and bank statement.

Registers and records

Employers are expected to maintain records such as:

  • Register of employees and wages
  • Attendance records
  • Accident book
  • Inspection book
  • Records of contributions paid

Digital maintenance is generally accepted, but ensure records can be produced on request, and retain them for the period required by the rules. Align your record-keeping with the broader statutory registers you maintain for other laws so that you only need one source of truth.

Inspections and social security officers

The ESIC may inspect records and verify compliance. Common checks include whether all eligible employees are registered, whether wages in the ESI file match payroll, whether contributions are paid on time, and whether exits are declared. A tidy master record and reconciled challans make inspections uneventful.

ESI and other statutory compliance: how it fits together

ESI interacts with other payroll compliances in ways that matter:

  • PF: PF ceiling logic differs from ESI. An employee may be PF-covered but ESI-exempt (or the reverse). Maintain separate flags in your payroll system.
  • Minimum wages: If your wage structure is built on minimum wages, a small revision can push employees across the ESI ceiling. Model this before approving increments.
  • Bonus: Statutory bonus is part of wages in the month paid if it is paid with wages; check how it affects the ceiling test and monthly contribution.
  • Maternity benefit: Employees covered under ESI may receive maternity benefit through ESIC rather than from the employer. Coordinate with your maternity leave policy and the relevant act to avoid double payment or gaps.
  • Labour codes: The social security code consolidates multiple laws, including ESI, and may change definitions and thresholds. Track notified rules for your state.

Common ESI mistakes and how to avoid them

  1. Removing an employee from ESI the month wages cross the ceiling. Respect the contribution period rule.
  2. Computing eligibility on basic salary instead of gross wages.
  3. Missing registration for new joiners until month end. This creates a gap in coverage and potential penalties.
  4. Not declaring exits. The employee's coverage stays alive on the portal and may affect their next employer.
  5. Incorrect days worked. Zero-wage days and loss-of-pay days should be consistent with attendance records.
  6. Rounding errors. The rules require rounding up to the next rupee for each of the two contributions.
  7. Ignoring branches. New locations may need separate codes.
  8. Paying late and ignoring interest and damages. Small delays accumulate.
  9. Not communicating benefits to employees. Employees who do not know about benefits perceive the deduction as a pure cost.
  10. Weak records. Missing attendance or wage records make inspections painful.

Employee communication: turning a deduction into a benefit

Many employees dislike deductions. A short onboarding note can change that perception. Include:

  • A simple explanation of ESI in two or three lines.
  • How to activate the insurance number and access the portal or mobile app.
  • A list of what is covered, linked to official pages.
  • Guidance on how to claim sickness or maternity benefits.
  • Whom to contact in HR for ESI queries.

When an employee crosses the wage ceiling and leaves the scheme, explain what is happening and what changes. If you provide a private group health policy, explain how it complements ESI so that employees know what to use first and what to claim from the group policy.

ESI audit checklist for HR and payroll teams

Run this checklist every quarter, or at least before each contribution period begins:

  • Employer registration is active and sub-codes are mapped to locations.
  • Every eligible employee has an IP number and complete family details.
  • The wage ceiling configured in payroll matches the current notified value.
  • Employees who crossed the ceiling are tracked with the correct contribution period end date.
  • Exits and joiners were declared on time in the portal.
  • Monthly contribution files reconcile with payroll registers and bank statements.
  • Challans for the last 12 months are stored and retrievable.
  • Attendance, wage records, and accident register are up to date.
  • Daily wage worker exemptions are applied correctly.
  • Contribution rates in the payroll engine are verified against official notices.
  • Inspection book is updated.
  • Grievances and claims are logged with response times.

Using software to automate ESI

Because ESI depends on wage thresholds, contribution periods, rounding, and monthly file formats, it is a natural fit for automation. A good payroll or HRMS tool should:

  • Flag employees as ESI-covered or not at the start of each contribution period based on wages.
  • Keep covered employees in the scheme until the end of the contribution period even when wages cross the ceiling.
  • Calculate employer and employee shares with the correct rounding.
  • Generate the monthly contribution file in the required format.
  • Reconcile payroll and challan values.
  • Maintain history of IP numbers, family details, joining, and exit declarations.
  • Provide dashboards for upcoming due dates and pending registrations.

Without automation, build a monthly checklist and a locked spreadsheet that reproduces the logic. Review the checklist whenever a statutory notice changes rates or ceilings.

Scenario playbook: ESI situations HR teams meet every year

Theory is easy; real payroll cycles throw up awkward cases. The scenarios below show how to reason through them using the principles already covered. Treat each as a pattern, and confirm edge cases with your advisor or the local ESIC office.

Scenario 1: A hike pushes an employee over the ceiling in the middle of a contribution period

An associate earning just under the wage ceiling receives a promotion in August. Gross wages now exceed the ceiling. The correct response is to continue deductions and employer contributions until the end of the contribution period (September in this case), and only then mark the employee as no longer covered from October. Document the date of the hike, the contribution period, and the planned exit-from-coverage date in the employee file. Tell the employee in writing what will change from October, including the fact that their ESI dispensary access and claim eligibility will follow the benefit period rules. If you run a private group health plan, remind them of how it will respond.

Scenario 2: A new hire joins on the 28th

The employee is covered from the date of appointment. Wages for a short first month are low, but the days and wages must still be reported correctly in that month's contribution file. A common failure here is waiting until the following month to register the person, which creates a gap in coverage and a mismatch between payroll and portal. Build a rule into onboarding: no payroll record is activated until the IP number request has been raised.

Scenario 3: An insured employee is on extended unpaid leave

During unpaid leave, wages for the period may be nil. The employee should continue to be shown in the monthly file with zero wages and the right days, unless they have exited. If the leave is related to a medical condition or maternity, the benefits available through ESIC may be more valuable than any support the employer can offer, so guide the employee to claim in good time and keep a copy of the certificate on file.

Scenario 4: Variable pay or incentives spike wages in a single month

Employees with commission or incentives can see their gross wages swing sharply. Your ceiling test is generally made at the start of the contribution period based on regular wages, and a one-off spike does not by itself remove the employee from coverage. However, the incentive is part of wages for the month it is paid and contributions on it are payable. Ensure your payroll engine includes incentives in the ESI wage base for the month and that the monthly file reflects the correct amount.

Scenario 5: Employee resigns and a new employer needs the IP number

When an employee moves jobs, the IP number stays with them. Ask new joiners for their existing IP number, and ask leavers to share it with the next employer. Do not create duplicate numbers. If an employee had earlier coverage that was never exited by the previous employer, you may need to coordinate with that employer or the ESIC office to update the record before you can add the person. Keep a short escalation note in your onboarding SOP.

Scenario 6: A contract or outsourced workforce works at your premises

If you engage contract labour through a vendor, the contractor is generally responsible for registering and paying ESI for their workers, but the principal employer can be held responsible if the contractor defaults. Ask for proof of registration and monthly challans from vendors and keep them in a compliance folder. A quarterly vendor compliance review prevents unpleasant surprises.

Scenario 7: You open a branch in a new state

First, find out whether the location is a notified area and whether your headcount there crosses the threshold. Then register the branch (or add a sub-code, as applicable), map employees to the correct code, and confirm the dispensary or hospital tie-up for the area. Update your payroll master so contributions are reported against the right code. A single shared spreadsheet for branch codes, responsible persons, and due dates is enough to start.

Month-end ESI routine you can copy

A consistent monthly routine prevents most ESI problems. Here is a simple routine that fits into a normal payroll cycle:

  1. Day 1 to 3 after attendance lock: Pull the list of joiners, leavers, and employees on loss of pay. Confirm that every joiner has an IP number and every leaver has an exit declaration pending or completed.
  2. During payroll processing: Run the ESI eligibility check. Flag employees whose gross wages crossed the ceiling and verify whether they are still within the contribution period.
  3. After payroll freeze: Generate the contribution file. Compare the total of employee and employer shares with the payroll register. Investigate any difference before uploading.
  4. Before the due date: Upload, validate, generate the challan, and pay. Save the acknowledgement.
  5. After payment: File the challan, the contribution file, and the reconciliation sheet in a dated folder. Record any exceptions and the action taken.
  6. At quarter end: Review open items such as pending IP numbers, exits not declared, and employees nearing the end of a contribution period. Update the compliance calendar for the next quarter.

Metrics worth tracking

You do not need a complicated dashboard to manage ESI well. A few simple indicators are enough:

  • On-time payment rate: Number of months paid on or before the due date out of the last twelve.
  • Registration lag: Average number of days between joining and IP number generation.
  • Exit declaration lag: Average days between last working day and exit declaration.
  • Reconciliation variance: Difference between payroll register and challan amount each month. The target is zero.
  • Open employee queries: Count of unresolved ESI-related questions or claims.

Review these in your monthly HR operations meeting. A trend line that improves quarter over quarter is a strong indicator that your process is healthy.

Policy and documentation tips

Document your ESI approach in a one-page internal SOP covering coverage criteria, the wage definition you use, the contribution period rule, owners for each step, and escalation contacts. Pair it with an employee-facing FAQ. When rates or ceilings change, update both documents on the same day and record the effective date. Keeping a short change log is useful for audits and for training new team members.

Frequently asked questions

1. What salary components are included for ESI?

Generally, all regular remuneration such as basic, DA, HRA, conveyance, special allowances, and overtime is included, while items such as employer PF contribution, gratuity, and retrenchment compensation are excluded. Check the current definition before configuring payroll.

2. Does ESI apply to employees who earn above the wage ceiling?

No, employees whose wages exceed the ceiling are not covered, except that an employee already covered continues to be covered until the end of the contribution period in which wages crossed the limit.

3. When should ESI registration be done for a new employee?

On or before the date of joining, so that the employee is covered from day one. Make it part of your onboarding checklist.

4. What happens if we pay ESI late?

Late payment generally attracts interest for the delay period, and persistent defaults can lead to damages and other action. Keep reminders ahead of the due date and reconcile early.

5. Can an employee be both in ESI and a private health insurance plan?

Yes. ESI is a statutory scheme and a private group health policy is a supplementary benefit. Explain to employees how they work together to avoid confusion at the time of a claim.

6. How are maternity benefits handled for ESI-covered employees?

Insured women who meet the contribution conditions receive maternity benefit through ESIC. Your leave policy should reflect this to avoid duplicate payment, while ensuring the employee gets the leave entitlements under the maternity law.

7. Do we need to report employees on loss of pay?

Yes. Include them in the monthly file with the correct days worked and wages, even if wages are zero for the month, unless the rules permit otherwise.

8. How long should we keep ESI records?

Retain records for the period specified in the rules and your general statutory records policy. Many employers keep them for several years to be safe; confirm the requirement with your compliance advisor.

Conclusion: make ESI routine, not reactive

ESI compliance is mostly about discipline: register people on time, apply the wage ceiling and contribution period logic correctly, pay on time, reconcile each month, and keep records ready. Employers who struggle with ESI usually have no calendar, no owner, and no reconciliation habit; those who run it well treat it as a monthly routine with a quarterly review.

If you want to reduce manual effort, CozyHR can help you track ESI eligibility, generate contribution data aligned to your payroll, and maintain the employee records that inspections ask for, all in one place. Try CozyHR when you are ready to move ESI and other statutory tasks off spreadsheets, and always confirm current rates, ceilings, and procedures with the official ESIC portal or your compliance advisor.