Payroll errors cost Indian companies more than just money. A single wrong EPF deduction, a missed TDS deposit, or an incorrect salary credit triggers employee complaints, compliance notices, and rework that drains HR bandwidth for days. Most of these mistakes stem from manual calculations, outdated Excel templates, and poor coordination between attendance, leave, and payroll data. For businesses operating across Delhi, Noida, and Gurugram with employees under different state rules, even a small oversight compounds into a serious compliance gap every month.
- 10 common errors: This post covers the most frequent payroll mistakes Indian companies make, from wrong PF calculations to missed filing deadlines.
- Real penalty figures: Each error includes the actual financial and compliance risk so you know what is at stake.
- Detection method: You will learn how to spot each error before it becomes a complaint or a notice.
- Fix and prevention: Every error includes a clear corrective action and a system level prevention step.
- Multi-state complexity: Specific attention to payroll errors that happen when companies manage employees across Delhi, Haryana, and Uttar Pradesh.
What Are Payroll Errors?
Payroll errors are mistakes in the calculation, processing, or reporting of employee compensation and statutory deductions. They range from simple data entry mistakes like entering wrong bank account numbers to complex compliance failures like calculating EPF on gross salary instead of basic wages. In India, payroll errors carry heavier consequences because every mistake potentially affects EPF, ESI, TDS, and Professional Tax filings submitted to government authorities.
These errors are not just accounting problems. They directly affect employee trust, statutory compliance, and the company’s financial exposure. When a payroll error reaches an employee’s bank account, the damage is already done. The correction cycle takes additional time, creates negative payroll adjustments, and sometimes requires revised government filings.
10 Common Payroll Errors in India and How to Fix Them
1. Calculating EPF on Gross Salary Instead of Basic Wages
What goes wrong: The EPF contribution should be 12% of basic wages plus dearness allowance. Many companies incorrectly calculate it on gross salary, which inflates the deduction and creates a mismatch with EPFO records.
Impact: Employees see higher deductions than expected. When they check their UAN passbook, the numbers do not match. EPFO may flag the discrepancy during an inspection, and correcting historical records requires filing supplementary returns.
How to detect: Compare the EPF deduction on any payslip against 12% of that employee’s basic salary. If the number is higher, the calculation base is wrong.
Fix: Set the EPF calculation base to basic wages plus DA only. Verify the configuration in your payroll software and run a test payroll before the next cycle. For past months, calculate the excess deduction and adjust through arrears.
2. Missing Professional Tax Deductions for Haryana and UP Employees
What goes wrong: Companies with offices in Delhi often apply Delhi’s zero Professional Tax rule to all employees, including those posted in Gurugram (Haryana) or Noida (Uttar Pradesh). Haryana mandates Rs 200 per month for salaries above Rs 15,000. UP has varying PT slabs.
Impact: The employer becomes liable for unpaid PT amounts plus interest. During a state labour department audit, missing PT deductions result in penalty notices and back payment demands.
How to detect: Filter your payroll register by work location. Check if employees in Haryana locations show Rs 200 PT deduction and UP employees show the applicable amount. If all show zero, PT is not configured by state.
Fix: Configure location-based PT rules in your payroll system. Each employee’s work location should determine which state’s PT slab applies. This is critical for Delhi NCR companies managing teams across multiple states from a single office.
3. Late TDS Deposit (After 7th of the Month)
What goes wrong: TDS deducted from employee salaries must be deposited with the government by the 7th of the following month. Late deposits attract interest at 1.5% per month under Section 201(1A) of the Income Tax Act.
Impact: Interest compounds monthly. A Rs 50,000 TDS deposit that is 3 months late costs Rs 2,250 in interest alone. Additionally, late filing of Form 24Q attracts a penalty of Rs 200 per day under Section 234E, capped at the TDS amount.
How to detect: Cross-check the deposit date on your TDS challan against the 7th deadline. If your payroll processing consistently closes after the 5th, TDS deposits are at risk.
Fix: Set a hard deadline to close payroll by the 3rd of every month. Configure automated reminders for TDS deposit by the 5th, giving a 2-day buffer before the 7th deadline.
4. Incorrect HRA Calculation (Metro vs Non-Metro)
What goes wrong: HRA exemption rules differ for metro and non-metro cities. Delhi, Mumbai, Kolkata, and Chennai qualify for 50% of basic salary as HRA. All other cities qualify for 40%. Companies frequently apply 50% to employees in Noida or Gurugram, which are not classified as metro cities for HRA purposes.
Impact: Incorrect HRA structuring leads to wrong tax calculations. During assessment, the Income Tax department can disallow the excess exemption and demand additional tax with interest.
How to detect: Check the salary slip of employees posted in Noida, Gurugram, Faridabad, or Ghaziabad. If HRA is 50% of basic, the rate is wrong for these locations.
Fix: Map each work location to its correct HRA category. Delhi employees get 50%, while Noida, Gurugram, Faridabad, and Ghaziabad employees should get 40% unless your company policy provides a flat rate regardless of exemption eligibility.
5. Not Updating ESI When Employee Crosses the Wage Ceiling
What goes wrong: ESI applies to employees earning up to Rs 21,000 gross salary per month. When an employee gets a salary revision that pushes them above this ceiling, many companies continue deducting ESI. The reverse also happens, where new hires below Rs 21,000 are missed.
Impact: Excess ESI deductions reduce the employee’s take-home pay unnecessarily. ESIC may reject claims if the employee was not eligible in the first place. Missing eligible employees exposes the company to penalties during ESIC inspections.
How to detect: Run a monthly report of all employees with gross salary near the Rs 21,000 threshold. After every salary revision cycle, recheck ESI eligibility for the entire team.
Fix: Configure your system to automatically check gross salary against the Rs 21,000 ceiling every month. When an employee’s salary crosses the threshold due to increment, bonus, or arrears, the system should flag it for review.
6. Salary Credit to Wrong Bank Account
What goes wrong: Employees update their bank details via email or verbal request. HR updates one system but forgets another. The bank transfer file goes out with the old account number. The salary bounces or credits to a closed account.
Impact: The employee does not receive salary on time. Recovery from the wrong account involves bank correspondence that can take 7 to 15 days. Employee trust drops immediately.
How to detect: After every payroll run, check the bank rejection report. If you do not have one, compare the bank file against the latest employee master data before submission.
Fix: Use an employee self-service portal where employees update bank details themselves. Route every bank change through an approval workflow that updates all connected systems in one action.
7. Ignoring LOP Days in Salary Calculation
What goes wrong: Loss of Pay days from unapproved leave or absence are not deducted from the salary. This happens when attendance data is not synced with payroll, or when the HR team manually tracks attendance in a separate sheet.
Impact: The company overpays the employee. Recovering the excess amount in the next month creates confusion and complaints. If LOP is not tracked properly, the attendance management system and payroll show conflicting records.
How to detect: Compare the number of paid days in the salary register against the actual attendance record for each employee. If paid days equal calendar days for employees who had unapproved absences, LOP is not being applied.
Fix: Integrate attendance and payroll on the same platform. When an employee’s leave is rejected or attendance is unmarked, the system should automatically flag it as LOP and reflect the deduction in payroll.
8. Wrong Gratuity Calculation at the Time of Exit
What goes wrong: Gratuity is payable to employees who complete 5 continuous years of service. The formula is (last drawn salary x 15 x years of service) / 26. Companies frequently use 30 instead of 26 as the divisor, or calculate on basic salary instead of last drawn salary (basic plus DA).
Impact: Underpayment leads to employee disputes and legal claims. Overpayment results in a direct financial loss to the company. Both scenarios create complications during the full and final settlement.
How to detect: Manually verify the gratuity amount for the last 3 exits against the correct formula. If the numbers differ, the calculation logic is wrong.
Fix: Lock the gratuity formula in your payroll system: (Last drawn salary x 15 x completed years) / 26. Ensure “last drawn salary” is defined as basic plus DA, not CTC or gross.
9. Not Filing EPF Returns by the 15th
What goes wrong: EPF challan and ECR must be filed by the 15th of the following month. Missing this deadline triggers damages under Section 14B of the EPF Act, calculated as a percentage of the arrears.
Impact: Damages range from 5% for delays up to 2 months, 10% for 2 to 4 months, 15% for 4 to 6 months, and 25% for delays beyond 6 months. In extreme cases, EPFO can initiate prosecution proceedings against the employer.
How to detect: Check the ECR filing date on the EPFO portal for the last 6 months. If any filing is after the 15th, you have a pattern of late compliance.
Fix: Close payroll by the 3rd, generate ECR by the 5th, and file by the 10th. This gives a 5-day buffer before the 15th deadline. Set automated alerts at each stage.
10. Processing Arrears Without Recalculating Tax
What goes wrong: When a salary revision is applied mid-year with retrospective effect, the arrears are paid in the current month. Many companies add the arrears amount to the current salary without recalculating the annual tax projection. This results in under-deduction of TDS for the arrears component.
Impact: The employee receives a higher net pay in the arrears month but faces a large TDS deduction in subsequent months to compensate. In some cases, the employer does not correct the projection at all, and the employee discovers a tax shortfall during annual filing.
How to detect: After processing arrears, check whether the TDS projection for the remaining months has been recalculated. If the TDS amount in the arrears month is the same as the previous month, the projection was not updated.
Fix: Every time arrears are processed, recalculate the annual taxable income and redistribute the remaining TDS across the remaining months of the financial year. Your payroll system should handle this automatically when arrears are added.
Payroll Error Impact Summary
| Error | Financial Risk | Compliance Risk | Detection Difficulty |
|---|---|---|---|
| EPF on gross instead of basic | Medium | High (EPFO mismatch) | Easy |
| Missing state-wise PT | Low per employee | High (state audit) | Easy |
| Late TDS deposit | High (1.5%/month interest) | High (Section 234E penalty) | Easy |
| Wrong HRA metro/non-metro | Medium | Medium (IT assessment) | Medium |
| ESI wage ceiling not updated | Low | High (ESIC inspection) | Medium |
| Salary to wrong bank account | High (recovery delay) | Low | Easy |
| LOP days not deducted | Medium (overpayment) | Low | Medium |
| Wrong gratuity formula | High (per exit) | Medium (legal dispute) | Easy |
| Late EPF filing | High (5% to 25% damages) | High (prosecution risk) | Easy |
| Arrears without tax recalculation | Medium | Medium (Form 24Q mismatch) | Hard |
Monthly Payroll Error Prevention Checklist
Use this checklist before every payroll cycle to catch errors before they reach employee bank accounts.
| Day | Check | What to Verify |
|---|---|---|
| 1st | Attendance sync | All attendance data pulled from biometric or app. No missing punches unresolved. |
| 1st | Leave reconciliation | Approved leave reflects in attendance. Rejected leave marked as LOP where applicable. |
| 2nd | New joiner data | All new employees have complete records: PAN, Aadhaar, UAN, bank details, tax regime. |
| 2nd | Exit processing | Resigned employees removed from active payroll. F&F calculated separately. |
| 3rd | Salary revision check | Any mid-month revisions or arrears correctly applied with tax recalculation. |
| 3rd | EPF base verification | EPF calculated on basic plus DA only, not gross. Spot check 5 random employees. |
| 4th | State-wise PT check | Delhi employees: zero PT. Haryana employees: Rs 200. UP employees: applicable slab. |
| 4th | ESI eligibility | Employees above Rs 21,000 gross excluded. New hires below Rs 21,000 included. |
| 5th | Bank file validation | Compare bank account numbers in transfer file against latest employee master. |
| 5th | TDS projection review | Annual tax projection updated for any income changes, arrears, or regime switches. |
| 7th | TDS deposit | TDS challan deposited with government. Confirmation receipt saved. |
| 10th | ECR generation | EPF challan generated from payroll data. Employee-wise breakup verified. |
| 15th | EPF and ESI filing | ECR uploaded to EPFO portal. ESI contribution deposited. Receipts archived. |
How to Reduce Payroll Errors Permanently
- Integrate attendance and payroll on one platform. When attendance data flows directly into payroll calculations, LOP errors, overtime miscalculations, and missing shift data disappear. Manual data transfer between systems is the single biggest source of payroll errors in Indian companies.
- Configure state-wise compliance rules from day one. If your company operates across Delhi NCR, set up separate PT, LWF, and minimum wage rules for Delhi, Haryana, and UP. Do not rely on one generic template for all locations.
- Run a parallel payroll for the first month after any system change. Compare the new system output against the previous month’s manual calculations. Verify EPF, ESI, TDS, and net pay for at least 10 employees across different salary bands.
- Set automated deadline alerts. TDS by 7th, EPF and ESI by 15th, Form 24Q quarterly. Alerts should trigger 5 days before each deadline, not on the deadline day.
- Use employee self-service for data updates. When employees update their own bank details, address, and tax declarations through a portal with approval workflows, the data stays current and the change history is tracked automatically.
Final Word
Payroll errors are preventable. Most of them happen because data is scattered across systems, compliance rules are not configured by location, and deadlines are tracked manually. The cost of fixing one payroll error, including employee communication, revised filings, and HR time, is always higher than the cost of preventing it.
For growing businesses in Delhi NCR with employees across multiple states, the right approach is choosing a payroll system that connects attendance, leave, compliance, and salary processing in one flow. That eliminates the manual handoffs where most errors are born.
Frequently Asked Questions
What are the most common payroll errors in India?
The most frequent payroll errors include calculating EPF on gross salary instead of basic wages, missing Professional Tax deductions for multi-state employees, late TDS deposits, incorrect HRA metro classification, and not updating ESI eligibility after salary revisions. These errors affect both employee compensation and statutory compliance.
What is the penalty for late EPF payment?
EPFO charges damages under Section 14B based on delay duration. Delays up to 2 months attract 5% damages, 2 to 4 months attract 10%, 4 to 6 months attract 15%, and delays beyond 6 months attract 25% damages on the outstanding amount. Prolonged defaults can lead to prosecution.
How do I check if my payroll calculations are correct?
Pick 5 employees from different salary bands. Manually verify their basic salary, EPF deduction (12% of basic plus DA), ESI (if applicable), TDS, and Professional Tax against the payslip. Also compare the net pay on the payslip with the actual bank credit. Any mismatch indicates a calculation or data transfer error.
Is Professional Tax the same across Delhi NCR?
No. Delhi has zero Professional Tax. Haryana charges Rs 200 per month for salaries above Rs 15,000. Uttar Pradesh has varying slabs. Companies with employees across these states must configure PT deductions based on each employee’s work location, not the company’s registered office.
What happens if TDS is deposited late?
Late TDS deposit attracts interest at 1.5% per month under Section 201(1A) of the Income Tax Act. Additionally, late filing of the TDS return (Form 24Q) attracts a penalty of Rs 200 per day under Section 234E, up to the total TDS amount. Both penalties are separate and cumulative.
How can payroll software prevent errors?
Payroll software prevents errors by automating calculations based on configured rules, syncing attendance data directly into salary processing, applying state-wise deductions automatically, and generating filing-ready documents before deadlines. The system removes manual data entry and formula dependency that cause most errors.
What should I do if I discover a payroll error after salary is paid?
Calculate the exact difference, communicate clearly with the affected employee, and process the correction in the next payroll cycle as an adjustment. For statutory errors like wrong EPF or TDS, file revised returns with the respective authority. Document every correction for audit records.
How often should companies audit their payroll?
Run a basic payroll verification every month using the prevention checklist before processing. Conduct a detailed payroll audit quarterly, covering EPF reconciliation, TDS projections, ESI eligibility, and bank detail accuracy. Annual audits should include full statutory reconciliation before Form 16 generation.
