Payroll looks simple: basic plus allowances, minus deductions, equals a bank transfer. The part that is not simple is the compliance layer — PF, ESI, professional tax, TDS and leave-without-pay — and it's exactly where small businesses meet their expensive surprises.
The monthly compliance checklist
Before any payslip goes out, these eight checks should pass. Miss one and the month has a paper problem in it:
- PF: 12% of (basic + DA) for both employer and employee, up to the wage ceiling — and e-payment before the 15th. New joiners enrolled in their joining month, not "next month".
- ESI: on gross up to ₹21,000 — 0.75% employer, 0.5% employee. The threshold is where most spreadsheets go wrong, because people change jobs mid-year.
- Professional tax: state slabs (Rajasthan has its own) — yes, it's tiny, no, you can't ignore it; arrears show up in audits.
- TDS under section 192: on salary above the exemption threshold, computed on the right regime assumptions — the old presumptions here create Form 16 rework in June.
- LWP proration: half-day/whole-day leave, and how it hits variable pay vs statutory deductions (LWP should not wrongly shrink PF wages).
- Payslips issued to every employee with the statutory split visible — this is also your employee's record.
- Bank file in the right format for your bank, with UPI handle mapping if you've moved to UPI salary credit.
- Registers updated (PF, ESI, TDS) — the filings are generated from these, and a stale register means a wrong challan.
The five most common payroll errors in small businesses
- Applying this year's rates to last year's slab data (or vice versa).
- Manual LWP math that compounds month over month.
- Employees who cross the ESI/PF thresholds mid-year and aren't re-checked.
- TDS computed on gross instead of taxable value — over-deduction that you must refund, plus a grievance.
- Leavers' final settlement computed without a proration of advances and leave encashment.
Every one of these is a formula error or a stale assumption — not a bad-faith mistake. Which is exactly why they all keep happening in spreadsheet-based payroll.
Why spreadsheets fail payroll
A payroll spreadsheet has four structural weaknesses: the rules live in formulas nobody documents, the file moves between people and versions, there's no audit trail of who changed what, and nobody owns the rule updates — when a slab changes in April, something has to change in the sheet, and nothing forces it.
Automated PF ESI TDS payroll calculation software removes the category of error, not just the symptom: the rules are versioned, every calculation is traceable to its inputs, compliance deadlines sit in a calendar that files the registers for you, and the bank file is a one-click export. If you're evaluating options, our payroll & HRMS system page walks through exactly what's included.
A 10-minute audit of your current setup
Don't need a new system? Run this audit quarterly:
- Pick last month's payroll and recompute one employee's PF, ESI and TDS by hand.
- Compare your challans against the registers for the last 6 months.
- Check every joiner and leaver from the last quarter against their first/last payslip.
- Verify your Form 16 samples (previous financial year) matched what employees were told.
Where you found a mismatch is where the money was leaking. And if you'd rather the audit ran itself every month — that's what a managed payroll service is for, and it's how most of our clients started: one messy month, then the whole thing on autopilot.
Key takeaways
- PF, ESI, PT and TDS are all slab-driven — the errors are almost always stale slabs or manual LWP math.
- Mid-year threshold crossings (ESI/PF) are the #1 silent compliance miss in small teams.
- LWP should never wrongly shrink statutory wage bases — check your formula.
- Do a 10-minute quarterly audit: recompute one employee, compare challans vs registers.
- Software removes the category of error; a spreadsheet just moves it.