Statutory Benefits in India: EPF, ESI, Gratuity + ID Mismatches

Statutory employee benefits in India are not only EPF, ESI, and gratuity formulas. The silent failure mode most payroll teams miss is mismatched employee identifiers across government portals - PAN, UAN, and ESIC numbers - even when the monthly contribution math is perfect.

This guide covers what each benefit does, how it shows up in payroll, and the operator checks that stop "fully automated" remittances from bouncing with penalties.

What "statutory" actually means for payroll operators

Statutory here means deductions and employer contributions required by law for covered employees: Provident Fund (EPF/EPS/EDLI), Employees' State Insurance (ESI) where applicable, professional tax in many states, TDS on salary, and gratuity eligibility rules over the employment lifecycle. Getting the % right is table stakes. Getting the person to match across EPFO, ESIC, income tax, and your HRMS is where filings die quietly.

The non-obvious failure: identifier mismatch across portals

Companies often assume that if contribution amounts calculate correctly, they are safe. Reality: a single-digit UAN error, a PAN typo, or a name spelling that does not match Aadhaar / bank KYC can cause silent ECR or return file rejections. The payslip looked clean. The remittance still failed. Penalties arrive weeks later, and the team blames "automation" instead of master-data hygiene.

• UAN vs name: EPFO rejects when the employee name string does not match the UAN record closely enough.
• PAN vs TDS: wrong PAN does not always block salary credit - it breaks Form 16 / AIS reconciliation later.
• ESIC IP number: ESI coverage math can be right while the IP number is wrong or inactive for that wage period.
• Bank IFSC / account: salary may still credit via another path while statutory portals stay inconsistent.

Operator rule: treat identifier validation as a payroll gate, same as attendance lock. Do not run ECR until UAN, PAN, and ESI identifiers are checked for joiners and for anyone whose KYC changed mid-month.

EPF in practice (not the textbook slide)

Employee PF is typically 12% on PF wages (subject to wage ceiling / voluntary higher contribution rules). Employer share splits across EPF and EPS as configured. The 2026 wage-ceiling change matters for who sits under the statutory band - see PF ceiling limit 2026.

Edge cases that break "perfect math":

• First and last month with join/exit mid-month
• LOP days that change PF wages
• Employees who opt for higher voluntary PF while EPS stays capped

ESI: coverage first, then calculation

ESI is not "always on." Confirm applicability (wage threshold, location, establishment coverage) before you deduct. Then keep the ESIC IP number aligned with the person in your HRMS. For who gets what once covered, see ESIC benefits to employees. A correct 0.75% / 3.25% style calculation on the wrong IP is still a failed remittance story.

Gratuity: lifecycle, not monthly deduction theatre

Gratuity is an eligibility and payout obligation over tenure (Payment of Gratuity Act rules for covered establishments), not a casual monthly line item you invent for aesthetics. Track DOJ, exits, and continuous service carefully. Wrong DOJ in the HRMS is another identifier-class error - dates are identifiers too. To estimate a payout, use the gratuity calculator.

Professional tax and TDS sit next to EPF/ESI

State professional tax slabs and TDS regime choices ride on the same employee record. If you want the employer-side PT walkthrough, use professional tax for employers (2026), or professional tax in Karnataka for a single-state view. For the monthly run order, follow payroll processing steps in India.

How Zeba approaches this

Zeba runs India payroll automation with attendance and leave in the same system, so statutory wages start from locked payable days - not a spreadsheet afterthought. Mid-month joiners and exits are handled on a pro rata basis against the actual month (not a lazy static 30-day divisor that skews PF and tax). Teams still own KYC discipline: UAN, PAN, and ESIC identifiers must be correct in the employee master before remittance.

On mobile, customers already use Zeba for daily attendance that feeds that payroll path - 5-star ratings across app stores and about 4.9 on Google Business Profile reflect that field and office teams actually use the product, not just finance.

What employees see at the end of this chain is covered in payslips and Form 16. If you are new to the idea of one system for all of this, start with what is HRMS.

Operator checklist before you file

1. New joiners: UAN / PAN / ESI IP / bank verified against documents
2. Name spelling matches KYC (including middle names and initials policy)
3. Attendance and leave locked for the wage month
4. Preview PF/ESI/PT/TDS exceptions
5. Only then generate remittance files

FAQs

Why did ECR fail when PF amounts looked correct?

Amount correctness does not guarantee portal acceptance. Mismatched UAN, name, or establishment mapping commonly rejects filings after payslips are already published.

Should mid-month joiners use a 30-day divisor?

Prefer actual calendar days (or your documented day-count policy) consistently. A static 30-day divisor for every month skews PF wages and tax in short months and long months. Zeba prorates against the real month length.

What should HR fix first - formulas or KYC?

Both. But if filings bounce, start with identifiers. Perfect math on the wrong UAN still fails.