Payroll Checklist Before Salary Processing

There is a hard line in the payroll month, and it is the moment the bank file goes out. Before it, an error is a correction that takes two minutes. After it, the same error is a conversation with an employee about money that is already in their account, or worse, money that is not.

Recovering an overpayment is legally awkward, practically unpleasant and terrible for trust. Underpaying is worse. So the checklist below is deliberately front-loaded: almost all of it runs before the calculation, and the rest runs before the file is released.

Why the checklist runs before the calculation, not after

Reviewing a finished payroll register is a poor way to find errors. The numbers look plausible because the system computed them correctly from whatever it was given, and a wrong input produces a right-looking output. Nobody spots that an employee who resigned on the 12th was paid for 30 days by reading a column of net pay figures.

Checking inputs is different, because inputs can be reconciled against something outside payroll: a signed offer letter, an approved attendance sheet, an exit intimation, a bank change request. That external reference is what makes the check meaningful.

Every item below should be verifiable against a document, not against someone's recollection. If the only evidence is that a manager said so on a call, that is the gap.

Master data: joiners, exits and revisions

Master data errors are the expensive ones, because they repeat every month until somebody notices.

• Every new joiner's salary structure matches the signed offer, component by component, not just on total CTC
• Joining date matches the actual first day worked, which decides the pro-rata calculation
• PAN, bank account and IFSC captured and verified, with the account name matching the employee
• PF UAN captured or a fresh one triggered, and the ESI insurance number where the employee is covered
• Previous employer income and TDS collected on Form 12B for anyone joining mid-year
• Every exit has a confirmed last working day, notice recovery or shortfall, leave encashment and asset clearance status
• Exits are marked inactive with the correct date so PF and ESI exit dates are right, not just excluded from the run
• Salary revisions carry an effective date and an approval reference, with anything retrospective treated as an arrear
• Location or state transfers are updated, because that changes professional tax and sometimes the leave rules

Bank account changes deserve their own rule. Verify any change request through a channel other than the one it arrived on, and never process a change that comes in as a reply to a payroll email thread. Payroll diversion fraud works precisely because a bank change looks like routine admin, and it lands in the same inbox as everything else.

Attendance and leave

This is where loss of pay disputes are born, and they are almost always process disputes rather than arithmetic ones.

• Attendance cycle closed for the period and approved by each manager, with a name against the approval
• Loss of pay days computed on the divisor your policy states, applied the same way for every employee
• Unapproved absence distinguished from sanctioned leave, and leave balances updated before the run
• Overtime approved in advance where policy requires it, and within the ceiling the applicable Act sets
• Holidays applied by location, not company-wide, for anyone in a different state
• Compensatory offs granted and consumed correctly, particularly where they expire
• Anyone on unpaid leave, maternity leave or a sabbatical flagged with the correct treatment for the whole period

Maternity leave is worth checking by name rather than by rule, because the payment continues at full wages for 26 weeks under the Maternity Benefit Act while attendance shows the employee as absent. Systems that derive pay from attendance sometimes get this wrong in exactly the month you least want to explain it.

Earnings, arrears and one-time payments

• Variable pay, incentive and commission files approved in writing by whoever owns that budget
• Reimbursement claims received inside the cut-off, within policy limits, and with bills where required
• Arrears tagged to the month they relate to, so the statutory and tax treatment follows the right period
• Joining or retention bonuses recorded with their recovery clause, so a later exit triggers it
• Any off-cycle or advance payment already made this month brought into the register rather than left outside it
• One-time payments checked against last month, so a bonus paid twice is caught before release

The off-cycle point is the one that quietly breaks things. A payment made outside the run does not appear in the TDS projection, does not hit the PF or ESI base, and does not reach the accounting entry. Six of those across a year and the annual reconciliation stops tying, usually discovered in March when there is no time to fix it.

Deductions and recoveries

• Loan and advance instalments on schedule, with the closing balance checked against the sanction
• Notice period recovery calculated on the basis your appointment letter states, not on gross by default
• Excess or negative leave recovery agreed with the employee before it appears on a payslip
• Insurance premium or benefit recoveries applied for the right coverage period
• Total deductions within 50 per cent of wages, or 75 per cent where cooperative society deductions apply, under the Payment of Wages Act
• No employee with zero or negative net pay, which almost always means recoveries have been stacked into one month

When a recovery is too large to fit inside the ceiling, stage it across months and tell the employee the schedule. Forcing it through because the software permitted it creates both a compliance exposure and a grievance, and the grievance arrives first.

Statutory checks: PF, ESI, professional tax and TDS

These are the checks that produce notices rather than complaints, which is why they run every month even when nothing appears to have changed.

For provident fund: eligibility decided at joining against the ₹15,000 basic and dearness allowance ceiling, with the decision recorded rather than inferred. UAN captured and Aadhaar seeded, since the ECR will not accept the record otherwise. International workers flagged, because they are covered on full salary without the ceiling unless a social security agreement applies. Existing members who got a raise still contributing, because crossing the ceiling later does not end membership.

For ESI: gross wages of ₹21,000 or less, tested excluding overtime but with overtime included when the contribution is computed. Anyone whose raise crossed the ceiling mid-period still contributing until the contribution period closes on 30 September or 31 March. The employee share waived where average daily wages are ₹176 or less, with the employer share still paid.

For professional tax: the slab of the state the employee works in, which is not always the state on the company letterhead. Exemptions applied where the state provides them, including Maharashtra's higher threshold for women. Labour welfare fund deducted in the month the state actually collects it rather than every month.

For TDS: the tax regime election on record for the year, since the new regime applies by default unless the employee opts out. Investment declarations loaded, and proofs verified before the year-end months. Landlord PAN on file where annual rent exceeds ₹1,00,000 for an HRA claim. Previous employer income included for mid-year joiners. Perquisites valued and added. And the projection refreshed after every revision, bonus or exit, because that is what stops the March correction from being brutal.

Output checks before you release the bank file

Six checks, in this order, and none of them takes long once the report exists.

• Headcount reconciliation: opening plus joiners minus exits equals closing, with a name against every difference
• Variance report against last month, with a stated reason for every change above your threshold
• Net pay total on the register equals the bank file total, to the rupee
• Statutory totals equal the amounts you are about to pay in each challan
• No duplicate bank accounts, no duplicate employee IDs, and no employee missing from the bank file who is present on the register
• A sample of payslips read end to end, including one joiner, one exit and one employee with an arrear

The variance report is the highest-yield check on this page. Anything that changed should map to something you already know about. A change nobody can explain is an error that has not been identified yet, and it is far cheaper to explain it now than to reverse it later.

Who signs off what

A checklist without owners becomes a document that everybody has read and nobody has done. Name a role against each block and require the evidence, not the assurance.

The five checks that catch the most

If you only have twenty minutes before a run, these five find the majority of what would otherwise reach a bank account.

• Headcount reconciliation, which catches unprocessed exits and missing joiners
• The variance report against last month, which catches everything else that changed unexpectedly
• Negative and zero net pay, which catches stacked recoveries and structure errors
• Bank account changes made this month, verified independently
• Register total against bank file total, which catches the difference between what you approved and what will actually be paid

When something arrives after the cut-off

The instinct is to squeeze it in. Resist it for anything other than a genuine underpayment.

A late input pays in the next cycle as an arrear, with the effective month recorded so the tax and statutory treatment stays correct. Reopening a run that has been reconciled and approved means the reconciliation no longer applies, and it usually means two versions of the register exist with nobody sure which one matches the bank file. The exception worth making is where an employee would otherwise be paid materially less than they are owed, which is handled as an off-cycle payment brought into the register, not as a quiet transfer outside it.

Frequently asked questions

Print this once, assign the owners, and run it in the same order every month. The value is not in the individual checks, most of which are obvious in isolation. It is in doing them before the calculation rather than reading a finished register and hoping something looks wrong.