Payroll Reconciliation

A payroll period produces several representations of the same facts, and they are created by different processes at different moments. Reconciliation is the discipline of confirming they still agree.

• The payroll run: what was computed for each employee.
• The bank: what actually left the account and reached whom.
• The challans: what was deposited with each authority.
• The returns: what was reported to each authority, employee by employee.
• The general ledger: what was recorded as cost and as liability.

In a period where nothing went wrong, all five describe the same thing. When one diverges, the pair that breaks tells you where the error is, which is why running these as separate comparisons is more useful than a single check on the total.

The third row is the one with consequences outside the finance team. A challan and a return that do not agree means the money is with the authority and the credit is not with the employee. The employee discovers it when they file, months later, and the correction is a revised statement rather than an adjustment.

The fourth row is the same failure with a different cause and the same effect on the employee. It is also the most preventable, because identifiers can be validated when they are collected rather than when they fail.

Two further checks run across periods rather than within one.

The first is the year-to-date reconciliation. Every payslip carries cumulative figures, and those cumulative figures are what the annual tax certificate will be built from. If the year-to-date on the March payslip does not agree with the certificate, one of them was assembled from a different source, and the employee will be the one to notice.

The second is the quarterly one. Salary tax deducted through the quarter should agree with what was deposited and what was reported in the quarterly statement, and the employee's annual statement should show it. Checking this after each quarter rather than at year end is the difference between one correction and four.

Both of these are cheap when the figures are derived from the run and expensive when the return is prepared separately by someone working from a spreadsheet export. Preparing the same numbers twice from different sources is the single largest cause of breaks.

Reconciliation after the fact catches errors. A pre-release review prevents them, and it is a shorter list than most teams expect.

• Variance by employee against the previous period, with a threshold. Anything above it gets looked at individually.
• Headcount movement: joiners paid from the right date, leavers stopped, nobody paid twice.
• Negative or zero net pay, which is almost always a recovery exceeding what was earned.
• Statutory contributions as a proportion of their base, which surfaces a structure change applied to the wrong component.
• New bank details, since a changed account on an existing employee is worth a second look for reasons beyond accuracy.
• Total deductions against the statutory ceiling for the wage period.

A run that passes these six is rarely wrong in a way that reconciliation will later find.

The instinct is to correct the current period so the totals agree. That is often the wrong move, because it hides where the error occurred and creates a second discrepancy in the period it is corrected in.

The better sequence is to identify the period the break originated in, correct it there where the mechanism allows, and adjust forward only where it does not. For deposits and returns that means a correction statement against the original period rather than an adjustment in the current one, so the employee's credit lands in the year it belongs to.

Where an employee was underpaid, the correction is an arrear payable to them, and it carries its own tax treatment in the period paid. Where they were overpaid, it is a recovery subject to the deduction ceiling, which means it may take several periods and should be explained before the first deduction rather than after it.