There is one ESI rule that produces more shortfall notices than every other error combined, and it has nothing to do with arithmetic. It is a rule about timing.
The rule
ESI runs on two contribution periods each year:
- April to September
- October to March
Eligibility is tested at the start of a period. Not monthly. Not on the day something changes.
That single sentence is the whole problem, because it runs against the intuition of everyone who has ever configured a payroll system. A wage limit feels like a threshold you check each month — earning below it this month means covered, above it means not. ESI does not work that way.
What actually happens
An employee is covered in April. In July they receive an increment that takes their wages above the coverage limit.
The intuitive response is to stop deducting ESI from July. It is also wrong.
That employee remains covered until the end of September — the end of the contribution period that was running when their wages crossed the limit. Contributions continue on their actual wages, above the limit, until the period closes. Coverage ends at the boundary, not on the increment date.
An employer who stopped in July has under-contributed for three months, for that employee and for every other employee who received an increment in the same cycle. Which, in most companies, means the entire increment batch.
Why the recovery hurts
The shortfall is recoverable with interest, and it is usually found during inspection rather than by the employer. By then it has been sitting there for a year or two, quietly compounding, across a whole cohort of people.
What makes it expensive is that the error is systematic. A one-off mistake affects one person and one month. A wrongly configured eligibility test affects everyone who crossed the limit, in every cycle since the configuration was written.
The rule protects the employee too
It is worth understanding the intent rather than treating it as a trap.
Each contribution period has a corresponding benefit period. An employee who crosses the wage limit in July does not lose medical cover overnight — neither do their dependants. Cover runs on through the benefit period.
Without the boundary rule, a small mid-year raise could cost a family their medical cover in the middle of a treatment. The rule exists so that does not happen.
What to do about it
Configure the eligibility test at the period boundary, not monthly. If your payroll system tests the wage limit on every run, it will be wrong twice a year, every year.
Check what happened at your last increment cycle. If increments went out mid-period and ESI deductions stopped on the effective date, you have a shortfall. Correcting it proactively costs the contribution plus interest; being assessed for it costs the same plus the inspection.
Tell the employee. Someone whose deduction continues after a raise will ask why. "The rules test eligibility twice a year, and your cover continues until September" is a straightforward answer — and it is a benefit, not a deduction they are losing.
The wider pattern
Most payroll errors are not arithmetic. Arithmetic is easy to check and easy to fix.
The expensive errors are rules applied at the wrong moment: ESI stopped on the increment date, professional tax computed on the head-office slab rather than the workplace state, PF switched from the ceiling to full wages halfway through a financial year. Each is defensible-looking, each is wrong, and each compounds silently until somebody asks.