Why the same payroll errors keep coming back
Most payroll errors are input errors, not calculation errors. The HRA formula rarely goes wrong; what goes wrong is the attendance it was applied to, an increment that was never entered, or an employee who left and was still paid. Each error below has a cause you can control and a check you can add to your month-end.
This article is for accountants, HR executives and owners who run salaries every month and want fewer corrections, complaints and reversal entries. It covers seven errors that come up again and again in Indian offices, schools, hospitals and factories, the control that prevents each, and a pre-payroll checklist you can print. If you are still deciding whether to use software at all, start with our overview of payroll automation for SMEs.
Attendance and leave errors that change payable days
Payable days drive almost every earnings figure, so a mistake here spreads into basic pay, allowances, statutory deductions and net pay at once.
Cut-off date that nobody enforces
Many organisations close attendance a few days before month-end so salaries can be processed on time, for example on the 25th. Problems start when that cut-off is informal. A late punch regularised on the 28th, or leave applied for after the cut-off, may be counted in one month by HR, in the next month by the accountant, or not at all.
Control: put the cut-off date in writing and configure it in the system. Treat anything after the cut-off as an adjustment in the next month's run, shown separately so the employee can see it, and freeze attendance once it is approved. The full month-close routine is in our attendance-to-payroll export guide.
Loss-of-pay and leave balance mistakes
Loss of pay (LOP) goes wrong in three common ways: unpaid leave is deducted although the employee still had a balance; leave is marked as paid although the balance was used up; or the per-day rate is worked out differently from your written policy. In a school, for instance, a teacher's casual leave during exam week may be noted on paper and never reach the payroll sheet, so the deduction surfaces months later as a dispute.
Control: keep leave applications, approvals and balances in the same system as attendance, so LOP is marked only when the balance is genuinely zero. Write down the per-day rate rule and apply it to everyone. Each month, check a sample of LOP cases against the leave records.
Overtime paid without approval
Overtime errors run in both directions. Either the device records extra hours that were never authorised, such as an employee who stayed back waiting for transport, and payroll pays them; or genuinely authorised overtime on a busy dispatch day is missed because nobody passed it on.
Control: separate recorded hours from approved overtime. Overtime should become payable only after the department head or manager approves it, and the rules (minimum extra time before overtime counts, the rate, any daily or monthly cap) belong in your attendance settings rather than being decided case by case. Our guide to shift and attendance rules explains how grace time, half-days and overtime are usually configured. Before processing salary, check the overtime report against approvals.
For some categories of workers, such as factory workers, overtime rates and limits are governed by law. Confirm what applies to your staff with your adviser.
Arrears missed after increments and revisions
An increment approved in June but effective from April creates arrears for April and May. If the new figure is simply entered from June, the employee loses two months' difference. If the arrears are worked out by hand, the statutory deductions due on them are often forgotten.
Control: record every revision with its effective date, not just the new amount. When the effective date is in the past, calculate arrears month by month as a separate component so the deductions on it are computed too, and show it on the payslip with the months it covers. Keep the revision letter with the payroll records. Arrears also arise from late attendance corrections and backdated allowance changes, so put those through the same route.
Statutory deductions calculated on the wrong base
When PF, ESI or professional tax comes out wrong, the cause is usually the salary figure it was applied to, not the rate. Typical examples: a new allowance is added to the structure without being tagged correctly for PF or ESI; an employee's pay crosses a ceiling after an increment and the coverage change is mishandled; arrears or overtime are left out of the base when they should be included, or included when they should not; or a branch employee's professional tax is deducted using another state's slab.
Control: for every salary component, record whether it counts towards each statutory wage, as agreed with your CA, and review that mapping whenever you add a component or the rules change. The labour codes have introduced a common definition of wages, so a mapping that was correct a few years ago may need a fresh look. Reconcile statutory totals with the salary register every month before filing. The concepts behind these deductions are explained in how PF, ESI and professional tax work in payroll, and current rules are published on the EPFO and ESIC websites.
Joiners and leavers in the middle of the month
People who join or leave partway through a month are where manual payroll is weakest. A joiner on the 18th is paid for the full month because their row was copied from a colleague's; a leaver is paid for the full month because nobody told accounts; or a final settlement goes out without the outstanding advance being recovered.
- Joiners: enter the employee in the master with the actual joining date before payroll is processed, so salary is prorated automatically, and collect bank details and any existing UAN or ESI number on the first day.
- Leavers: record the last working day and mark the person inactive after the final run, so they drop out of future salary and statutory returns.
- Final settlement: before releasing it, check the loan and advance ledger, any leave encashment due under your policy, notice period recovery if applicable, and company assets to be returned.
- Information from managers: make it a rule that department heads tell HR about resignations and absconding cases before the attendance cut-off.
Bank transfer mistakes: wrong accounts and duplicate payments
Errors at the payment stage are the most expensive because the money has already gone. The usual ones are an employee's new bank account not updated, account numbers mistyped in the bank upload, a person paid twice because a corrected file was uploaded without cancelling the first, and salary sent to a former employee.
Control: allow bank details to change only through a documented request, with HR updating the employee master and a second person verifying the change. Generate the bank transfer sheet from the locked salary run instead of retyping it, and check that the bank file total equals net pay in the salary register. If a file has to be corrected, record clearly which version was uploaded.
A pre-payroll checklist to run every month
Run these checks in the same order every month, and give each one to a named person so nothing slips in a busy month.
| Check | What to look at | Owner |
|---|---|---|
| Attendance frozen | All regularisations up to the cut-off approved; late entries carried to next month | HR |
| Leave reconciled | LOP marked only where the leave balance is exhausted | HR |
| Overtime approved | Overtime report matches manager approvals | Department heads |
| Joiners and leavers | Joining and last working dates entered; leavers flagged for final settlement | HR |
| Revisions and arrears | Increments entered with effective dates; arrears calculated as a separate component | HR and accounts |
| Loans and advances | New advances entered; this month's instalments appear in deductions | Accounts |
| Statutory mapping | No new component added without statutory tagging; totals reconcile with the salary register | Accounts and CA |
| Bank details | Changes since last month verified; bank file total equals net pay total | Accounts |
| Variance review | Every employee whose net pay moved sharply from last month explained | Accounts |
| Approval and lock | Owner or finance head approves, then the payroll is locked before payment | Owner |
The variance review is often the quickest way to catch what slipped past the other checks. Sort employees by the change in net pay from last month and ask why for every large movement.
How payroll software prevents these errors, and what it cannot catch
Software does not remove the need for these checks, but it removes the places where most of them fail: retyping, copied rows, overwritten formulas and changes nobody recorded.
MATROP's payroll software keeps attendance and leave rules (shift timings, late marks, half-days, weekly offs, holidays, leave types, approval flow and balances) together with salary processing, so payable days and loss of pay come from approved records. Attendance can be imported from biometric devices or mobile attendance through an optional integration, with working days and overtime calculated automatically; our attendance and biometric software page explains the device options. Increments, arrears and loan or advance EMIs are handled as salary components and ledgers, the bank transfer sheet comes from the processed salary data, and a payroll can be locked after approval, with reprocessing under audit and approval available as an option. Role-based logins let department heads review attendance and, optionally, approve it, while audit logs record changes. Implementation includes setting up cut-off rules, overtime and leave types, with support during the first payroll run.
What software cannot catch is a wrong instruction: an increment agreed verbally and never passed on, a resignation nobody reported, or a statutory rule configured on wrong advice. Those depend on your process and your adviser. If your team is small and payroll errors are rare, a written checklist and a second person reviewing the spreadsheet may be all you need for now.
Questions people ask
Should a payroll mistake be corrected in the same month or the next?
If salary has not been paid yet, correct it and reprocess before payment. If it has been paid, most organisations adjust it in the next month's run as a separate, clearly labelled line, so the paid month's records stay intact.
How should we recover an overpayment from an employee?
Explain the error to the employee in writing, agree how it will be recovered, and deduct it as a labelled recovery rather than by reducing a salary component. Deductions from wages are regulated, so check with your adviser before recovering a large amount.
Who should approve payroll before the bank upload?
Someone other than the person who prepared it, usually the owner, finance head or principal. They should see the salary register, the variance against last month and the bank file total before approving.
What if we find a PF or ESI error from a previous month?
Do not quietly adjust it inside the current month's figures. The correction process depends on the scheme and the type of error, so check the current procedure on the EPFO or ESIC portal and take your CA's advice.
