Skip to content

Common Payroll Errors in India and How to Fix Them

Quick answer: Most payroll errors in India come from five sources: inputs (missed joiners, leavers, attendance or revisions), calculations (PF wages and ceiling, ESI coverage, professional tax slabs, TDS regime, minimum wages), payments (wrong bank details, duplicates, late salary), statutory filings (late or wrong PF, ESI, PT and TDS) and accounting. Fix each error in the next payroll or an off-cycle run, correct any filing it affected, log it, and change the process so it does not happen again.

A payroll error is any difference between what an employee or a government authority should have been paid and what was actually paid, or between payroll and the records that report it. Small errors are common, but they cost more than their amount: employee trust, interest and damages on late statutory dues, and time spent on corrections. This guide lists the payroll errors seen most often in Indian payroll, with what causes each, the consequence, how to fix it and how to prevent it, and ends with a simple error log and correction process. It is part of our guide to the payroll process in India.

Common payroll errors in India: input, calculation, payment, statutory and accounting errors, with how to fix and prevent each

What causes payroll errors?

  • Late or missing inputs: HR, managers and payroll working to different cut-offs.
  • Manual steps: figures typed into spreadsheets, formulas overwritten, copy-paste from last month.
  • Rule changes not applied: PF ceiling, ESI limit, minimum wage, professional tax slab or tax regime changes.
  • No independent review: the person who prepares payroll is also the one who approves and pays it.
  • Poor master data: wrong bank accounts, missing UAN or ESI numbers, wrong State or location.

Input errors

1. Leaver still paid

What happens: An employee who left in the month is paid a full salary because the exit was not passed to payroll.

  • Consequence: Overpayment that is hard to recover once the person has left; PF and ESI filed for someone no longer employed.
  • Fix: Contact the former employee to recover the excess, or adjust it against the full and final settlement if it is still pending.
  • Prevent: Exit information to payroll by the cut-off date; headcount check with HR every month.

2. Joiner missed

What happens: A new employee is not set up in time and gets no salary, or only a partial one.

  • Consequence: Late payment of wages, an unhappy new hire, and PF and ESI not filed for the month.
  • Fix: Pay through an off-cycle run or the next payroll, with PF, ESI and TDS on the arrears.
  • Prevent: Joining checklist with documents, bank details and UAN collected before the first payroll; see our payroll cut-off guide.

3. Wrong attendance or loss of pay

What happens: Leave not approved in time is treated as loss of pay, or loss-of-pay days are missed; the wrong divisor (26, 30 or calendar days) is used.

  • Consequence: Under- or overpayment and employee disputes.
  • Fix: Recalculate for the correct days with the monthly salary calculator and pay or recover the difference next month.
  • Prevent: Close attendance before processing; apply one written policy for the divisor, as explained in salary on 26 or 30 days.

4. Revision or arrears not applied

What happens: An approved increment or promotion is not entered, or is entered from the wrong date.

  • Consequence: Underpayment and arrears to calculate later, with PF, ESI and TDS on them.
  • Fix: Pay arrears in the next payroll; check them with the salary arrears calculator.
  • Prevent: Revision letters with effective dates sent to payroll by the cut-off; revisions listed in the monthly changes report.

Calculation errors

5. PF on the wrong wages or ceiling

What happens: PF calculated only on basic when wages under the Labour Codes include other allowances, or the ₹25,000 ceiling from 17 September 2026 not applied consistently.

  • Consequence: Short or excess PF; demands for arrears with interest and damages, or excess deductions from employees.
  • Fix: Recalculate PF for the affected months and pay the difference through a revised or arrears return, as the EPFO portal currently allows, with interest and any damages.
  • Prevent: Wage definition applied in one tested formula; see our PF wage ceiling guide and salary structure guide.

6. ESI applied to the wrong employees

What happens: An employee who crossed the ₹21,000 limit is dropped mid-contribution period, or a covered employee is missed.

  • Consequence: Short contributions, interest and damages, and an employee without ESI benefits when they need them.
  • Fix: Pay the missed contributions with interest. If the contribution period has closed on the portal (42 days after it ends), approach the ESIC branch office to correct the record.
  • Prevent: Keep an ESI-covered flag that follows the contribution-period rules, not this month's pay; see our ESI guide.

7. Professional tax slab or State wrong

What happens: An old slab is used after a State revises it, or PT is deducted for the head-office State instead of the State where the employee works.

  • Consequence: Short or excess PT and penalties from the State.
  • Fix: Correct deductions from the next month and file a revised return where the State allows.
  • Prevent: Check State slabs after every budget; map each employee to a work location. Our professional tax guide links to each State.

8. TDS under the wrong regime or old declarations

What happens: TDS calculated under the old regime when the employee did not opt out of the new one, or declarations not updated after proofs.

  • Consequence: Short deduction leading to a large deduction later in the year, or excess TDS that the employee recovers only through a refund.
  • Fix: Recalculate the annual projection and spread the difference over the remaining months.
  • Prevent: Collect regime choice at joining and each year; recalculate TDS whenever salary or declarations change.

9. Pay below the minimum wage

What happens: A State or central minimum wage revision (often with effect from 1 April or 1 October) is missed.

  • Consequence: Underpayment of wages, claims for the difference and penalties under the Code on Wages.
  • Fix: Pay arrears from the effective date.
  • Prevent: Check the minimum wages tracker each April and October.

10. Overtime and rounding errors

What happens: Overtime paid at single rate, or rounding applied differently in different places.

  • Consequence: Underpayment of overtime (it must be at least twice the ordinary rate) and small mismatches with challans.
  • Fix: Recalculate and pay the difference.
  • Prevent: One rounding rule in the settings; overtime checked with the overtime calculator.

Payment errors

11. Wrong bank details or duplicate payment

What happens: Salary sent to an old or wrong account, or an employee paid twice through a manual and a bulk payment.

  • Consequence: Funds lost or delayed; possible fraud if bank details were changed without verification.
  • Fix: Ask the bank to recall or reverse the transfer; recover duplicates promptly.
  • Prevent: Verify bank-detail changes directly with the employee; match the bank file to the approved register line by line.

12. Late salary

What happens: Salary paid after the 7th of the next month for a monthly wage period.

  • Consequence: Breach of the Code on Wages payment time limits and employee complaints.
  • Fix: Pay immediately and record the reason.
  • Prevent: Fix the payroll calendar so approval and funding happen before the due date; see salary payment rules.

Statutory filing errors

13. Late PF, ESI, PT or TDS deposits

What happens: Challans paid after the due date because of funding, approval or portal delays.

  • Consequence: Interest and damages on PF and ESI, interest on late TDS, and the employer loses the income-tax deduction for employees' PF and ESI contributions not deposited by the return due date.
  • Fix: Deposit with interest as soon as possible.
  • Prevent: Statutory payments scheduled in the compliance calendar; see payroll penalties.

14. Wrong UAN, ESI number or PAN

What happens: Contributions or TDS reported against the wrong employee identifier.

  • Consequence: Credits missing from employees' PF accounts or tax records, and mismatch notices.
  • Fix: Correct the member details on the portal and, for TDS, file a correction statement for Form 138 (Form 24Q for quarters up to March 2026).
  • Prevent: Verify UAN, ESI number and PAN at joining against official records.

Accounting errors

15. Payroll posted wrongly in the books

What happens: Only net pay posted as salary, employer contributions missed, or payments posted to expense instead of the payable.

  • Consequence: Wrong profit, payables that never clear and audit questions.
  • Fix: Pass correcting journal entries.
  • Prevent: Post from the register totals and reconcile each payable monthly; see our salary journal entry and reconciliation guides.

How to correct a payroll error

  1. Confirm the error: recalculate and agree the correct figure and the months affected.
  2. Tell the employee: explain what went wrong and how it will be corrected.
  3. Correct the pay: pay a shortfall in the next payroll or an off-cycle run; recover an overpayment in agreed instalments, keeping total deductions within the Code on Wages limits.
  4. Correct statutory items: PF, ESI and TDS on the corrected amount; correction statements or supplementary filings where needed.
  5. Correct the books with a journal entry referenced to the error.
  6. Log it and fix the cause: record the error, its root cause and the process change.

Payroll error log template

ColumnExample
Date found / reported by5 Nov 2026 / employee query
Employee and pay periodE07, October 2026
Error typeInput: loss of pay
Description and amount2 days' approved leave treated as LOP; underpaid ₹1,613 (₹25,000 ÷ 31 days × 2)
Root causeLeave approved after cut-off
Correction and datePaid in November payroll with PF
Process changeLeave approvals closed 2 days before cut-off

Reviewing the log every quarter shows patterns, such as repeated input delays from one department, that a single correction will not reveal. A simple payroll accuracy measure is: payslips paid correctly without later correction in a month divided by total payslips; track it and aim to raise it.

How employees should report payroll issues

Give employees one clear channel for pay queries, such as a payroll e-mail address or HR helpdesk, and ask them to include the pay month, the payslip line in question and what they expected. Acknowledge each query, resolve it within a set time, and if it reveals an error, record it in the error log. A clear process keeps small issues from becoming grievances.

Who is responsible for payroll errors?

The employer is legally responsible for paying correct wages on time and for depositing PF, ESI, professional tax and TDS, even when payroll is outsourced to a vendor. Within the business, responsibility is shared: HR for complete and timely inputs, payroll for correct calculations, finance for payments and deposits, and an approver for reviewing the whole. Writing these roles down, with the cut-off dates, prevents most errors. A deeper, periodic review of payroll controls is a payroll audit; our monthly payroll checklist covers the routine checks.

Reduce errors with tested formulas. The Complete Indian Payroll Excel Workbook calculates salary, PF, ESI, PT and TDS consistently each month. To understand the rules behind each step, see the Practical Payroll Management e-Book.

Frequently asked questions

What are the most common payroll errors?

The most common payroll errors in India are missed joiners or leavers, wrong loss-of-pay days, salary revisions not applied, PF calculated on the wrong wages or ceiling, ESI applied to the wrong employees, an out-of-date professional tax slab, TDS calculated under the wrong regime, pay below the minimum wage, wrong bank details, and late PF, ESI or TDS deposits.

Who is responsible for payroll errors?

Legally, the employer is responsible for paying correct wages and depositing PF, ESI, professional tax and TDS on time, even if payroll is outsourced. Inside the business, HR is usually responsible for the accuracy of inputs, the payroll team for calculations, and finance for payments and deposits, with an approver checking the whole payroll.

Does HR deal with payroll issues?

Usually yes. In most Indian companies HR handles employee queries about pay and supplies payroll inputs such as joiners, leavers, attendance and revisions, while payroll or finance processes the salary and statutory payments. Many payroll errors start with an HR input that was late or wrong, so HR and payroll must work to the same cut-off.

How do you correct a payroll error?

Find the cause and the amount, then correct it in the next payroll or an off-cycle run: pay any shortfall with PF, ESI and TDS on it, or recover an overpayment with the employee informed and within the legal deduction limits. Correct any statutory filing affected, record the correction in an error log and fix the process so it does not happen again.

What is payroll accuracy?

Payroll accuracy is the share of payslips paid correctly and on time without later correction. A simple measure is: payslips paid correctly without later correction in a month divided by total payslips. Tracking it monthly shows whether controls are working.

Position as of 15 November 2026. Correction procedures on the EPFO, ESIC and income-tax portals change from time to time; follow the current portal instructions. General information, not legal or tax advice. Official sites: EPFO, ESIC.

By
About the author
Vishvas YadavFounder, HR Calcy

Vishvas Yadav is the founder of HR Calcy and an HR and payroll consultant with 16+ years’ experience in India. He advises organisations on payroll and statutory compliance, wage structuring under the new Labour Codes, and labour law covering PF, ESI, CLRA, gratuity and bonus. Post Graduate Certification in HRM, XLRI Jamshedpur and SHRM. ISO 9001:2015 Lead Auditor (BSI). Based in Bengaluru.

View full profile

Post a Comment

Please do not enter any spam link in comment box. Thank you!

Previous Post Next Post