Payroll data review before the close: what it checks and when you must run it

Payroll is usually the largest recurring cost on the ledger, and it is also the area where small posting faults hide longest. A payroll data review is a structured pass over wage, tax and liability figures before you treat them as final. This article covers what the review actually verifies, how it fits the close, and when you can defer it.

What the payroll data review checks

The review compares what the payroll system recorded against what the ledger and the liability accounts say. In practice it looks at three things.

First, gross-to-net arithmetic: wages, withholdings and employer taxes for each run, and for year-to-date totals. Second, liability balances: whether each payroll liability account agrees with the sum of unpaid withholdings and accrued employer taxes. Third, reconciliation: whether payments recorded against liability accounts match the amounts accrued, so the balances clear to what is genuinely outstanding.

How it protects the close

Payroll errors distort the close in predictable ways. An unreconciled liability account leaves a residual balance that nobody can explain at month end. A missed employer tax accrual understates expense and overstates the liability's offset. A duplicated payment leaves a credit sitting in a withholding account, which then quietly nets against the next quarter's filing.

Running the review before you close means you catch these while the correction is a journal entry in the current period. After the close, the same fault becomes a prior-period adjustment, with all the evidence and explanation that entails.

Is the review mandatory?

That depends on the service arrangement, not on the accounting. Where payroll is processed on your own ledger and you file the returns yourself, the review is a best-practice step: strongly advisable, but you choose when to run it. Where payroll is submitted to a service that handles the filings, a data review is typically a required gate before submission, because the service relies on your figures being complete and correct.

The accounting logic is the same either way. The only difference is who enforces it.

What to preserve before correcting anything

Before you fix anything the review flags, take a snapshot of the current state. Export the payroll register and the liability account detail as they stand. Note the period, the run dates and the flagged amounts. If a correction later proves wrong, you want to reconstruct what was there before you touched it.

Keep the review's findings with the working papers for the period. If a figure is later queried, the review output is your evidence that the data was checked and the correction was deliberate.

Telling a data fault from a posting mistake

Most flags from a payroll review are ordinary posting errors: a payment coded to the wrong account, a manual journal that bypassed the payroll module, a date outside the period. These are yours to fix, and the fix is a normal part of the close.

A different category exists where the underlying payroll data itself is damaged: year-to-date figures that disagree with filed returns across many employees, or liabilities that cannot be tied to any run. That is not a posting mistake, and no amount of journal entries will resolve it cleanly. At that point the work stops being bookkeeping. Preserve your backups and current-state exports, and hand the file to a data repair specialist before anything else is posted to it.

Where it sits in your sequence

Run the review after all payroll runs for the period are posted, but before you reconcile the bank and the liability accounts. That way the reconciliation confirms clean figures rather than papering over faults. If the review flags something material, correct it, re-run, and only then move to the reconciliation and the close.