When a pay change misses the payroll cutoff

A frequent pay failure starts when an approved change to someone's earnings reaches payroll after the period has closed. The employee is paid at the old rate, a manual check follows, and the correction ripples into deductions and tax records. Employees usually notice first. The lasting fix sits upstream.

How it starts

A manager agrees a raise, a promotion or a shift allowance. The paperwork moves through HR approvals at its own pace. Nobody owns the date by which it must land in the payroll system, so it arrives late, or it arrives on time with the wrong effective date.

The payroll team processes what is in front of them. Time worked is entered, earnings are calculated from the record as it stands, and payments go out. The change exists in an email or a form, yet the system has never seen it.

Sometimes the change does get keyed in, but with the date it was approved and not the date it was meant to apply. The system then treats the earlier periods as correct. No arrears are generated.

Why it compounds

An earnings error rarely stays an earnings error. Pension contributions are often calculated as a share of pay, so they are now short. Benefit deductions tied to salary bands may sit in the wrong band. Withholding is computed on the lower figure, so tax records for the year no longer match what the employee is owed.

When the fix arrives, it often lands as a lump sum. That lump can push the employee into a higher withholding bracket for that run, which prompts a second complaint. Each patch creates something else to reconcile at period end.

How it gets spotted

The employee is almost always the first to know. They open their payslip, see the old rate, and contact payroll or their manager. By the time the inquiry reaches someone who can act, the pay run has closed.

Other signals appear later and quieter. Manual checks start clustering around particular departments or managers. Period-end adjustments grow in volume and drift away from routine items like accrual true-ups toward one-off corrections. Reconciliations between the HR record and the payroll record throw up mismatches in rate or grade.

A useful test is to pull the recent manual checks and read the reasons. If most of them say some version of "change not processed", the problem is not in payroll's calculations.

Fixing the pay that went wrong

Correct the employee first. Decide whether the shortfall is paid by manual check now or added to the next scheduled run. A manual check gets money to the person quickly but adds handling, approval and reconciliation work. Folding it into the next run is cleaner if the employee can wait.

Recalculate the deductions for every affected period, not only the gross pay. Pension, benefits and any wage-based garnishments all need checking. Apply the withholding treatment the jurisdiction expects for back pay, which may differ from regular earnings.

Fix the effective date in the employee record so the history is right. Then tell the employee plainly what happened, what they will receive, and when. A clear message heads off repeat inquiries.

Fixing the cause

The durable fix lives at the handoff between whoever approves a change and whoever processes it. Publish a cutoff for each pay period and make it visible to managers and HR. Give one named person responsibility for confirming that approved changes have reached the payroll system before the run.

Require an effective date on every change request, separate from the approval date. Where the system allows it, have HR changes flow into payroll directly, with an exception report for anything approved but not yet applied.

Before each run, compare a list of approved changes against what the system shows. Anything outstanding is either processed or flagged to the employee in advance. Late changes will still happen. The goal is that they are known and handled on purpose.

Track manual checks by root cause over time. If the late-change category shrinks, the handoff is holding.

Questions to ask the people who run payroll

What the procedure says and what happens before a pay run are often different. These questions surface the gap:

• When a raise is approved, how does payroll actually find out about it?
• Who decides whether a late change goes in now or waits for the next run, and is that written down anywhere?
• Which effective date do you enter when the form shows more than one?
• What do you do when a manager emails a change directly and skips HR?
• When you issue a manual check, do you also recalculate pension and benefit deductions, or is that handled separately?
• Which departments or managers generate most of the corrections?
• How do you handle withholding on back pay, and who confirmed that approach?
• Is there a spreadsheet or inbox you rely on that the system does not know about?
• What happens to an employee inquiry after it arrives, and who closes it?
• If you could change one thing about how changes reach you, what would it be?

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.