The Payroll Checklist: What to Verify Before You Release Salaries

<p>A payroll checklist before salary release should cover five error sources: joiners and exits, attendance and leave, mid-cycle pay changes, statutory deductions and bank details. Verify each item against a source document, lock attendance before you run the calculation, and reconcile this month's gross against last month's, employee by employee, explaining every difference.</p> <h2>Why group a payroll checklist by error source</h2> <p>Most payroll corrections are not arithmetic mistakes. The calculation engine does what it is told. The errors come from the inputs: a resignation that HR recorded on the 28th for a last working day of the 12th, a shift allowance that was approved on WhatsApp and never entered, a bank account closed three months ago.</p> <p>So a useful payroll audit checklist is organised by where the data originates, not by the order of the salary register. If you check in that order, each section has a clear owner and a clear source document to check against. That is the difference between pre-payroll checks that catch things and a final review that only confirms what the system already decided.</p> <p>Fix the sequence first. Attendance closes, then inputs freeze, then calculation, then payroll verification, then release. If inputs are still moving while you are verifying, you are verifying a moving target.</p> <h2>Section 1: Joiners and exits</h2> <p>This is the single largest source of over and underpayment, because both events involve part-month pay and both involve statutory registrations.</p> <h3>For every joiner this cycle</h3> <ul> <li>Date of joining in the system matches the appointment letter, not the offer letter. Candidates who join a few days late are a recurring cause of overpayment.</li> <li>Payable days are calculated on your stated basis (calendar days or working days). Pick one basis and apply it to every employee. Mixed bases across a payroll run are impossible to explain to an auditor.</li> <li>Salary structure matches the approved CTC breakup, including any joining bonus and whether it is payable this month.</li> <li>PAN is on record. Without a valid PAN, tax deduction at source under Section 192 of the Income Tax Act is affected and the employee's Form 16 will not reconcile.</li> <li>UAN captured, or a fresh UAN generated, and Form 11 collected. If the employee was already an EPF member, their existing UAN must be used.</li> <li>ESI registration done where the employee's wages fall within the coverage limit set by ESIC, and the establishment is covered. Verify the current wage limit on the ESIC site before you apply it.</li> <li>Tax regime declaration recorded, and investment declarations captured if the employee has opted for the regime where they matter.</li> <li>Bank account and IFSC collected and in the employee's own name.</li> </ul> <h3>For every exit this cycle</h3> <ul> <li>Last working day confirmed in writing, and the employee's status changed on that date rather than on the date HR got around to it.</li> <li>Notice period shortfall recovery calculated, and the recovery base (basic or gross) matches what the appointment letter says.</li> <li>Leave encashment computed on the balance as at the last working day, after the final month's accruals and deductions are posted.</li> <li>Gratuity assessed where the employee meets the continuous service condition under the Payment of Gratuity Act, 1972. The exemption limit on gratuity has been revised over the years, so confirm the limit applicable to the payment date.</li> <li>Advances, loan balances, asset recoveries and any excess reimbursement netted off.</li> <li>Tax recomputed for the part year. Exit month tax is almost never the same as the monthly running figure.</li> <li>Employee excluded from the next cycle. A terminated employee who stays active in the master is how duplicate salary payments happen.</li> </ul> <h2>Section 2: Attendance, leave and loss of pay</h2> <p>Attendance is the input with the most records and the least scrutiny. Three checks catch most of it.</p> <ul> <li><strong>The period is locked.</strong> After the attendance cut-off, no manager should be able to edit a punch or approve a backdated regularisation into the closed period. Late corrections go into next month as an arrear, with a reason.</li> <li><strong>Zero pending approvals.</strong> An unapproved leave request sitting in a manager's queue usually becomes loss of pay by default. Run the pending list and clear it before calculation, not after an employee complains.</li> <li><strong>Exception review, not record review.</strong> Do not read 400 attendance records. Pull only the exceptions: zero-day employees, employees with loss of pay above a threshold you set, employees with no punches at all, employees with more paid days than the month has.</li> </ul> <p>Also confirm that holidays, weekly offs and comp-off credits are applied against the right calendar. Companies with multiple states or multiple shifts often run several holiday calendars, and an employee mapped to the wrong one produces a quiet loss of pay. If your <a href="/product/attendance">attendance and leave tracking system</a> feeds payroll directly, check that the sync ran after the lock and not before it.</p> <p>Overtime deserves its own line. Confirm the hours are approved, the rate basis matches your policy and the applicable state shops and establishments rules, and that overtime is not being paid twice (once as hours and once as a fixed allowance).</p> <h2>Section 3: Changes to pay</h2> <p>Every change to a pay element should trace to an approval with a date. The checks are about authorisation and effective dating.</p> <ul> <li>Increments: revised structure loaded, effective date correct, and arrears computed from the effective date if the revision was approved late.</li> <li>Promotions and transfers: new location mapped, because location drives professional tax, minimum wages and sometimes the holiday calendar.</li> <li>Variable pay, incentives and commissions: the payout file is signed off by the function that owns the target, and the amounts match that file to the rupee.</li> <li>New or stopped allowances: confirm which month the change starts, and whether the component is taxable.</li> <li>Reimbursements: claims approved, within policy limits, with bills where the exemption depends on proof.</li> <li>Minimum wages: where state notifications have revised rates or variable dearness allowance, check that affected employees are still at or above the notified rate. These revisions are issued by state labour departments and the timing differs by state.</li> <li>One-time payments: flagged as non-recurring so they do not repeat next month.</li> </ul> <h2>Section 4: Statutory deductions</h2> <p>Do not verify statutory amounts by eye. Verify the rules the system is applying, then test two or three employees at the boundaries.</p> <h3>Provident fund</h3> <ul> <li>Contribution is computed on the correct wage definition, and the treatment of the statutory wage ceiling matches the policy you have adopted for the establishment. Confirm the current ceiling and rates on the EPFO portal rather than from memory.</li> <li>Employees who have opted out validly (and are eligible to do so) are excluded consistently, with Form 11 on file.</li> <li>Employer contribution split between the pension and provident fund accounts, and administrative charges, follow the current EPFO rates.</li> <li>Voluntary provident fund deductions match the employee's written instruction.</li> </ul> <h3>ESI</h3> <ul> <li>Coverage is tested against the ESIC wage limit, and an employee who crosses the limit mid-contribution-period continues to contribute until the end of that period. This is the rule most systems get wrong when configured manually.</li> <li>Employee and employer rates match the rates currently notified by ESIC.</li> </ul> <h3>Professional tax and labour welfare fund</h3> <ul> <li>Professional tax is levied by state governments. The slabs, the deduction frequency and whether the state levies it at all differ. Deduct based on the employee's work state, and check the current slab with that state's tax authority.</li> <li>Labour welfare fund applies only in some states, often half-yearly or annually rather than monthly. Confirm whether this is a deduction month for each applicable state.</li> </ul> <h3>Income tax</h3> <ul> <li>Each employee's chosen tax regime is applied, and any mid-year change is handled per the rules for the assessment year.</li> <li>Proof-pending declarations are treated the way your policy states, especially in the last quarter when proofs are called in.</li> <li>Perquisites, previous employer income (Form 12B) and any employee request for higher deduction are included.</li> <li>Employees with sharp tax jumps this month have an explanation you can give in one sentence.</li> </ul> <h2>Section 5: Bank details and the payment file</h2> <p>This is the last gate, and failures here are visible to every employee at once.</p> <ul> <li>Any bank account changed this month is verified against a cancelled cheque or bank statement, and by a second person. Bank-change fraud works precisely because the request looks routine.</li> <li>No duplicate account numbers across employees, unless you have a documented reason.</li> <li>IFSC codes are current. Bank mergers have invalidated large blocks of IFSC codes in recent years.</li> <li>Net pay total in the bank file equals net pay total in the salary register. Compare the control total and the record count, not a sample.</li> <li>No zero or negative net pay rows in the file. Investigate each one before release.</li> <li>Funds are available in the disbursement account, and the file format matches what the bank expects for that account.</li> </ul> <h2>The final reconciliation before release</h2> <p>Run one comparison against the previous month and account for every movement. For each employee, the difference in gross should be explained by one of: joining, exit, revision, loss of pay, variable payout, arrear or reimbursement. Anything you cannot explain is an error until proven otherwise.</p> <p>Then check headcount movement against the HR master, confirm the sum of components equals gross, confirm gross minus deductions equals net, and confirm the statutory liability totals you will later use to file returns. Keep the signed-off register, the input freeze report and the bank file as the audit trail for the month. Running payroll inside a single system, as teams do with <a href="/product/payroll">HRZyra's payroll software</a>, removes the spreadsheet handoffs where most of these mismatches are introduced, but the checklist still needs an owner and a signature.</p> <p>One practical rule: whoever enters the inputs should not be the person who approves the release. Separation of those two roles catches more errors than any single review step.</p>

Frequently asked questions

What should be checked before running monthly payroll in India?

Before running monthly payroll in India, verify joiner and exit records against appointment and resignation letters, lock attendance and clear pending leave approvals, confirm every pay revision has a dated approval, check that PF, ESI, professional tax and TDS rules are correctly configured, and validate bank accounts and IFSC codes. Then reconcile gross pay against the previous month.

When should attendance be locked for payroll?

Attendance should be locked at the attendance cut-off date, before payroll calculation starts. After the lock, managers should not be able to edit punches or approve backdated regularisations into the closed period. Late corrections are processed as arrears in the following month with a documented reason, which preserves the audit trail for the closed cycle.

Why does payroll differ for employees who exit mid-month?

Exit-month payroll involves part-month pay plus several one-time items: notice period shortfall recovery, leave encashment on the balance as at the last working day, gratuity where the employee meets the continuous service condition under the Payment of Gratuity Act, 1972, recovery of advances and assets, and tax recomputed for the part financial year.

Is professional tax the same across all Indian states?

No. Professional tax is levied by state governments, so the slabs, deduction frequency and whether the tax applies at all vary by state. Some states do not levy it. Deduct professional tax based on the employee's work state and confirm the current slab with that state's tax authority, since slabs are revised from time to time.

How do you catch payroll errors before paying salaries?

Compare each employee's gross pay this month against last month and require an explanation for every difference: joining, exit, revision, loss of pay, variable payout, arrear or reimbursement. Also check that the bank file control total and record count match the salary register, and investigate every zero or negative net pay row.

Who should approve the payroll release?

The person who enters payroll inputs should not be the person who approves release. Separating data entry from release approval catches errors that a single reviewer misses, and it is a basic control for bank detail changes in particular, where a fraudulent account change request looks identical to a routine one.