Provident Fund (PF) and Employees' State Insurance (ESI) are two statutory deductions that apply to most security guard payrolls in India, and they're calculated differently from each other โ PF against basic pay, ESI against gross wages with an eligibility ceiling. Getting both right, for every guard, every month, is one of the more error-prone parts of running agency payroll manually.
PF: calculated on basic pay, not gross
A common mistake agencies make is calculating PF on a guard's full gross salary โ including HRA, allowances, and overtime. The standard employee contribution is 12% of basic pay specifically, not the full gross. This distinction matters: a guard with a large night-allowance or overtime component in a given month shouldn't see their PF deduction inflated by it, because PF is meant to track basic pay only.
Raksha Kavach's payroll engine applies this correctly by design โ PF is computed strictly against the base amount for the period, never against HRA, allowances, or overtime, so the deduction stays accurate regardless of how much of a guard's pay came from variable components that month.
ESI: a gross-wage ceiling, not a flat rule
ESI works differently โ it's a percentage of gross wages (commonly 0.75% on the employee side), but only applies at all when the guard's gross monthly wage is at or below the statutory ceiling, commonly โน21,000. A guard earning gross wages above that ceiling in a given month is typically not covered under ESI for that period.
Because gross wages can shift month to month with overtime and allowances, a guard might be under the ESI ceiling one month and over it the next โ which is exactly the kind of moving target that's easy to get wrong by hand but trivial for software to evaluate correctly every single payroll run.
The employer side โ a cost agencies often forget to track
What frequently gets missed is that PF and ESI aren't just employee deductions โ the employer (the security agency) also owes a matching contribution on top, which is a real cost to the business, not something withheld from the guard's pay. Employer-side PF is typically another 12% of basic, and employer-side ESI is a separate percentage (around 3.25% under the post-2019 ESIC revision) of gross wages under the same ceiling rule.
Raksha Kavach's compliance module computes and tracks this employer-side liability separately from the employee deduction, so an agency owner can see at a glance what they actually owe in statutory contributions for a given month or period โ not just what was deducted from guards' pay.
Why this needs to be automated, not manually tracked
Multiply this calculation across a roster of guards, each with different basic pay, different months of variable overtime and allowances, and different eligibility for ESI depending on that month's gross โ and manual PF/ESI calculation on a spreadsheet becomes a genuine liability, not just a time cost. A single formula error, applied across dozens of guards for months, compounds into a real compliance and financial problem.
This is exactly the kind of calculation Raksha Kavach's payroll and compliance modules are built to get right automatically, every period, with the employer-side contribution tracked alongside โ plus due-date reminders so filings don't slip.
PF is a percentage of basic. ESI is a percentage of gross, but only under the wage ceiling. Both have an employer side most spreadsheets forget to track.
Conclusion
PF and ESI aren't complicated in principle, but they're easy to get subtly wrong at scale โ wrong wage base, missed ceiling checks, forgotten employer-side contributions. Raksha Kavach's payroll engine and compliance dashboard compute both correctly from real attendance and salary data, track the employer's own liability, and remind agencies of upcoming due dates, removing the guesswork from statutory compliance.