When payroll tax deposits drift away from what was withheld

A frequent failure is drift between the tax withheld in payroll, the tax deposited and the figures on filed returns. It starts with off-cycle adjustments that never reach the deposit or ledger. It shows up at reconciliation, and it is fixed by tracing every adjustment and amending what was filed.

How it starts

The regular payroll run is rarely the problem. It is calculated by the system, the tax liability is summarised, and the deposit goes out from that summary. Trouble begins outside the run.

A manager asks for a manual check for someone who was underpaid. A terminated employee's final pay is cut by hand. A bonus is voided and reissued with different withholding. A benefits correction changes taxable wages after the fact. Each of these produces a real change to tax owed, and each one is easy to process in the payroll system without anyone telling the person who schedules deposits.

The deposit is then made from the original run total. The payroll register now holds one number, the bank shows another, and the general ledger may carry a third if the adjustment was booked late or to a suspense account. Nobody notices, because each record looks complete on its own.

A quieter version comes from setup. An employee changes work location or a new jurisdiction applies, and the tax profile is not updated. Withholding continues for the old authority. The deposits match the register perfectly, yet both are wrong.

How it gets noticed

It is usually caught late. The most common moment is when the regulatory return is being prepared and the wages and tax reported by payroll will not tie to what was deposited. A notice from a tax authority about an underpayment or a missing deposit is the other common trigger, and by then penalties may already be attached.

The annual employee tax statements are a further checkpoint. If the totals across all statements do not agree with the sum of the periodic returns, something moved without being reported. Employees also find these errors, typically someone who sees withholding for a place they no longer work.

The earlier, better signal is a routine reconciliation of summary payroll payment information against financial records. When the tax liability account in the ledger does not clear to zero after each deposit, that residue is the drift showing itself. Teams that look at this account every cycle catch the problem while it is small and fresh.

Fixing it

Start by building the full list of adjustments for the affected period. Pull manual checks, voids, reissues and retroactive changes from the payroll system, and compare them with what was recorded as payroll payment adjustments in the ledger. Anything present in one and absent from the other is a candidate cause.

Next, recompute the liability per authority and per tax type. Compare it with confirmed deposits, not scheduled ones. The difference should be explainable item by item. If it is not, keep digging before filing anything, because a partial correction creates a second mismatch.

Then correct in the right order. Make any catch-up deposit first, so the shortfall stops accruing interest. File amended returns that reflect the corrected wages and tax. Where employee statements have already gone out, issue corrected statements and tell the affected people why. For jurisdiction errors, register where required, update the employee profile, and work with both authorities on refunds and amounts due.

Finally, book the ledger entries that bring the tax liability account back to a clean balance, with a note tying each entry to the adjustment that caused it. That trail matters if an auditor or agency asks later.

Questions to ask the people who run it

• When a manual or off-cycle check is cut, who tells the person scheduling tax deposits, and how?
• Is the deposit amount taken from the run summary, or from a report that includes adjustments made since?
• Who reviews the payroll tax liability account in the ledger, and what happens when it does not clear?
• How is a work location change captured, and who confirms the tax profile was updated?
• When an agency notice arrives, where does it go first, and who owns the answer?
• Are voids and reissues ever handled outside the payroll system, for example through accounts payable?
• What do people do when a reconciliation is off by a small amount? Do they investigate it or plug it?

The answers often reveal informal workarounds that no procedure describes. Those workarounds are usually where the drift lives.

Keeping it from coming back

Tie every off-cycle payment to the tax calculation in the same system, so adjustments cannot bypass the liability summary. Base deposits on a report that includes all activity since the last deposit. Make the ledger liability account part of the close, with a named owner. Treat any change to an employee's work location as a tax event that requires a second check before the next pay date. When the tax plan is reviewed, include the adjustment path, not just the regular run.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.