Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
ESI coverage applies to employees at or below ₹21,000/month gross but runs on six-month contribution periods. A salary revision mid-period keeps the employee covered until the period boundary, creating a moving match target between payroll and the ESIC challan and systematic headcount mismatches every April and October.
Match each month's ESI challan to payroll and bank debit using the IP number as the key at employee level. Apply 4% combined contribution (3.25% employer + 0.75% employee) on gross wages, maintain coverage through the current contribution period even after salary revision, and run a dedicated reconciliation for the April and October transition months.
IP-number keyed matching, wage-ceiling transition rule honouring the six-month period, bi-annual transition reconciliation, and 15th-of-month deadline trigger with Section-level interest rule.
Clean monthly ESI reconciliation, zero late-payment interest, correct IP-level contributions at the period boundary, and a defensible ESIC portal and audit trail.
ESI contribution reconciliation in India involves matching the monthly ESIC challan to three sources: the ESIC portal return, the bank debit, and the ESI expense ledger in the books. For most companies, ESI reconciliation is more complex than PF reconciliation because the covered employee headcount changes at every contribution period boundary — and the 6-month lag between wages and coverage eligibility means the reconciliation target is not simply “who earned below ₹21,000 this month.”
This guide is for payroll, compliance, and finance teams responsible for monthly ESI closing.
What ESI Contribution Reconciliation Involves
ESI contribution reconciliation confirms three things each month:
- The number of covered employees (active IP numbers) in the ESIC portal matches the number of covered employees in the payroll register for the same wage month.
- The total contribution amount in the ESIC portal (employer 3.25% + employee 0.75% of gross) matches the ESI expense entry in the books and the amount in the ESIC challan.
- The bank debit for the ESI challan amount matches the challan on the ESIC portal, using the challan number as the match key.
When all three agree, the month is closed. When they do not, the cause is typically a headcount difference (coverage boundary) or a contribution calculation difference (gross salary definition or wage ceiling transition).
How ESI Contribution Reconciliation Works
Step 1 — Determine the Covered Headcount
At the start of each reconciliation, identify the covered headcount for the wage month. Coverage depends on wages in the preceding contribution period — not on current month wages. Employees who crossed the ₹21,000 ceiling in the previous period may still be covered in the current period if the current period started less than 6 months ago.
Step 2 — Calculate Contributions and File the Return
For each covered employee, calculate employer contribution (3.25% of gross salary) and employee contribution (0.75% of gross salary). File the monthly return on the ESIC portal, listing each covered employee by IP number with gross wages and contribution amount. The portal calculates the total challan amount.
Step 3 — Pay the Challan and Match to Bank
Pay the challan on the ESIC portal before the 15th of the following month. The bank debit narration follows the pattern: ESIC CHALLAN [NUMBER] ESI CONTRIBUTION [MONTH]. Match the challan number in the bank narration to the challan number in the ESIC portal. The amounts must agree.
Step 4 — Reconcile to Books
The ESI expense ledger should show employer contribution for the wage month. Employee contribution (deducted from salary) should appear in the ESI payable account. Together, they should equal the total challan amount.
ESI Contribution Rate and Coverage Reference
| Component | Rate | Basis | Applicability | Filing Deadline |
|---|---|---|---|---|
| Employer contribution | 3.25% | Gross salary | All covered employees | 15th of following month |
| Employee contribution | 0.75% | Gross salary | Employees earning above ₹137/day | 15th of following month |
| Total contribution | 4.00% | Gross salary | Combined employer + employee | 15th of following month |
| Wage ceiling (general) | ₹21,000/month gross | Gross monthly salary | All employees except persons with disability | Assessed each contribution period |
| Wage ceiling (disability) | ₹25,000/month gross | Gross monthly salary | Persons with disability only | Assessed each contribution period |
| Contribution period | 6 months | April–Sep / Oct–Mar | Coverage determined by preceding period wages | Return filed monthly; coverage reviewed semi-annually |
India-Specific Complexity: The 6-Month Coverage Lag
The most operationally complex aspect of ESI reconciliation is the contribution period structure. ESI does not determine coverage month by month — it determines coverage for a 6-month block (April–September or October–March) based on wages earned in the preceding 6-month block.
Practical consequence for salary revisions: An employee earning ₹19,500 per month during October–March is covered for the following April–September period. If this employee receives a salary revision to ₹23,000 effective April 1, they remain covered for the full April–September period. The ESIC portal will include this employee at the ₹23,000 gross, with contributions calculated at 4% of ₹23,000 = ₹920 per month. The payroll system must reflect this correctly — it is not a portal error.
Transition months. April and October are the highest-risk months for ESI reconciliation. New employees whose wages in the preceding period qualified them for coverage are added; employees who remained above the ceiling for the full preceding period are removed. The IP number count changes in both directions simultaneously, and the reconciliation headcount must be verified against the ESIC portal’s own active IP count for the period.
ESI vs PF reconciliation complexity. ESI reconciliation is generally more complex than PF reconciliation for three reasons: (1) the covered headcount changes at period boundaries rather than being stable month to month; (2) the gross salary definition for ESI differs from the EPF wage definition (which excludes HRA); (3) the ESIC portal’s IP-number-level data requires employee-level matching, not just aggregate amount matching.
For companies managing ESI reconciliation alongside PF and TDS, reconciliation software India that ingests ESIC portal exports and payroll system data reduces the monthly headcount verification from a manual exercise to an exception-based review. The ESIC — Employees’ State Insurance Corporation publishes the current contribution rates, wage ceiling thresholds, and IP number registration procedures for all covered employers.
For the bank statement matching component — matching challan number to bank debit narration — the approach is identical to the methodology in the bank reconciliation process guide. Where the ESIC challan amount does not match the bank debit, the investigation approach follows the same steps as TDS challan mismatch resolution. All ESI reconciliation evidence — covered headcount, wage calculations, challan confirmations — must be retained as described in the reconciliation audit trail India guide to meet statutory audit requirements. TDS reconciliation software that handles multi-register statutory matching can extend to ESI challan matching using the same challan-number-as-match-key approach.