← Return to all articles

HR and payroll · 23 September 2026 · Seereon Team · 4 min read

Payroll software in India: getting PF, ESI, PT and TDS right every month

Indian payroll is not hard because of salaries. It is hard because of statutory deductions. A plain guide to PF, ESI, PT and TDS — and how software keeps them consistent.

Computing a salary is simple. Computing it correctly for every employee, every month, under Indian statutory rules is where payroll goes wrong — and it is why payroll software in India has to do far more than add up numbers.

This is a plain overview for HR and finance teams — not legal advice. Rates and thresholds change; always check current notifications or ask your consultant.

The four statutory deductions

Provident Fund (PF)

Employer and employee contributions on PF wages, with rules on wage ceilings and which salary components count. The common errors are applying the wrong wage base and missing new joiners or exits in the monthly return. Agree in writing which components make up PF wages, and apply that definition consistently.

Employees' State Insurance (ESI)

Applies to employees below a wage threshold in covered establishments. Errors usually come from employees crossing the threshold mid-year, and from contribution periods. Check eligibility against current rules every month rather than once a year.

Professional Tax (PT)

A state tax with slabs that differ by state. For multi-location companies, the right slab depends on where the employee works — an easy thing to get wrong in a spreadsheet. Record each employee's work location as a field, not a note.

Tax Deducted at Source (TDS)

Income tax deducted monthly based on projected annual income, the chosen tax regime and the employee's declarations. Mistakes here show up at year-end as large corrections. Collect declarations early in the year and ask for proofs well before the final quarter.

A worked example: one month, three changes

For example, imagine a company with 80 employees in two states. In one month it has three new joiners, one exit and a salary revision for ten staff.

In a spreadsheet, each of those changes touches several places: PF wages, ESI eligibility, the PT slab for the right state, and the TDS projection for the rest of the year. Miss the revision in the TDS sheet and tax for those ten people is under-deducted for months — until a large correction lands in someone's March salary.

In payroll software, the joiner, the exit and the revision are each entered once, effective from a date, and every calculation picks them up. The payroll team's job is to review the result, not rebuild it.

Why spreadsheets fail

Spreadsheets do not fail on day one. They fail slowly: a formula copied wrongly, a new joiner added below the range, a threshold changed in one sheet and not another. Each month's payroll is built from last month's file, so errors carry forward.

What payroll software in India should do

  • Pulls attendance and leave automatically, so pay is based on approved data.
  • Applies statutory rules centrally. When a rate changes, it changes once, for everyone.
  • Keeps an audit trail of every change to pay.
  • Produces payslips, bank files and statutory reports from the same run.
  • Lets employees serve themselves — payslips, tax declarations and leave balances.

Common payroll mistakes

  • Arrears handled as manual additions. Revisions with back-dated effect should be calculated by the system so statutory deductions follow.
  • Full and final settlements computed outside payroll, which leaves the year's records incomplete.
  • Not reconciling challans with the payroll register every month.
  • Leaving tax declarations to the last quarter, which squeezes TDS into a few salaries.
  • One person holding all the payroll knowledge, with nothing written down.

A monthly payroll checklist

  1. Lock attendance and approve exceptions.
  2. Review joiners, exits and salary revisions.
  3. Run payroll and review variances against last month.
  4. Approve, publish payslips and generate bank and statutory files.
  5. File returns and challans on time.

Year-end is built every month

Annual TDS certificates, statutory returns and audit queries all depend on twelve months of consistent data. If each month is locked, reviewed and reconciled, year-end becomes a reporting exercise rather than an investigation. Keep a short note of every unusual decision — a one-off bonus, a back-dated revision, a disputed deduction — alongside the payroll record, so whoever answers an audit query a year later knows why it was done. If payroll sits within a wider HR system, see our checklist on HRMS for small business.

Frequently asked questions

Does payroll software replace our payroll consultant?

Not necessarily. Software makes the calculations consistent and the records complete. A consultant or chartered accountant still advises on salary structures, interpretation of the rules and anything unusual.

What happens when statutory rates change?

In good payroll software the rule is updated centrally and applies to everyone from the effective date. Ask any vendor who maintains those rules and how quickly changes are applied.

Should we run a parallel payroll before going live?

Yes. Run one or two months on both the old method and the new system, and compare net pay and every deduction employee by employee. Differences usually reveal data problems you would rather find before go-live.

Where SeerHR fits

SeerHR takes attendance from biometric devices or the mobile app, runs payroll with PF, ESI, PT and TDS calculations maintained by our team, and gives employees a self-service app. HR spends the end of the month checking exceptions, not computing salaries.

Book a free consultation to see a payroll run on sample data that looks like yours.

#Payroll#Statutory compliance#SeerHR