Payroll Exception Handling SOP: From First Report to Verified Resolution
Updated: Oct 25
An employee reports missing hours just as payroll is closing. The team finds the timesheet, enters an adjustment and tells the employee it is fixed. The following run imports the corrected timesheet again. What began as an underpayment has become a duplicate payment because the original case ended at entry rather than at a checked outcome.
A payroll exception handling SOP defines how an unexpected issue is received, assigned, investigated, corrected and confirmed. Its job is to keep the next required action visible through every handoff. A useful procedure follows the employee's payment, the payroll record and any reporting or accounting consequences until each applicable part has a documented result.
This procedure is for U.S. employers managing recurring payroll issues in an existing operation. Use the Payroll Exception Workboard below for missing pay, deduction errors, payment failures and discrepancies found by HR or finance. Federal sources were reviewed October 10, 2026. State and local wage rules, employment agreements and the facts of a particular payment can require specialist review. The operating examples are fictional and do not establish a universal correction deadline.
If repeat exceptions expose a payroll service limitation, discuss the missing correction controls with a SelectSoftware Reviews advisor. The consultation is free. Bring the specific correction, approval and confirmation steps you need a provider to demonstrate. Verify those capabilities and retained employer responsibilities with each candidate.
Table of contents
Receive the report without making paperwork a barrier
Choose a primary intake channel that employees, managers, HR and finance can find. Explain who monitors it, how to report an urgent pay issue and whom to contact if that person is unavailable. A shared mailbox or secure ticket queue can work. Its value comes from ownership and follow-through, rather than the choice of software.
Also accept reports that arrive elsewhere. An employee telling a supervisor that wages are missing has identified a possible problem, even if they used the wrong form. Have the receiving person bring it into the queue. Do not make the employee start again through another channel before someone assesses the payment risk.
Open a case with what is known: employee identifier, employing entity, relevant pay period or payment date, reported difference, discovery time and a person responsible for the next action. Mark the uncertain facts explicitly. A report saying "my deposit never arrived" needs payment-status investigation; it does not initially require the employee to calculate gross wages or identify an earnings code.
Logging should occur alongside urgent action. If funds may be misdirected or a wage deadline is approaching, contact the authorized payroll lead, provider or bank while recording the case. A rule that nobody may help before every field is complete can obstruct the very response the SOP is meant to organize.
Acknowledge the problem in useful terms
Tell the reporting person who owns the investigation and when the next update will arrive. Distinguish a confirmed error from a report still being checked. "We are reviewing the missing deposit and will update you by 2 p.m." communicates a real action. "Payroll is handling it" leaves the employee with no usable expectation.
Give the case one reference and connect related messages to it. If HR and the employee both report the same missed payment, retain both reports under that reference. When several employees share a source error, create a parent incident with individual affected-employee records. One shared cause does not mean every person has the same amount or payment status.
Keep sensitive evidence in restricted storage. The visible queue can use employee IDs and links to evidence without exposing bank numbers, Social Security numbers or whole workforce reports. FTC business guidance recommends collecting only needed information and restricting access to people with a legitimate need. Apply those principles to case attachments and exports as well as the main payroll system.
Set priority from the consequence and the next deadline
Record the next external obligation before assigning an internal service target. That may be a wage-payment requirement, final-pay deadline, agency response, remittance requirement or another applicable obligation. Then record the provider or banking cutoff needed to meet it. A convenient processing window does not determine whether waiting is lawful.
For covered nonexempt employees, federal overtime generally belongs on the regular payday for the pay period in which it was earned. DOL overtime guidance also explains the workweek basis of the calculation. State requirements can affect payment timing beyond that federal starting point. Have the responsible reviewer establish the rule for the affected worker and jurisdiction; employee hardship alone is an incomplete test for deferral.
Use three working priorities, with a reason attached to each:
Immediate response: a payment or applicable deadline is at risk, funds may be misdirected, or the potential error is spreading. Assign a lead and backup now, establish the permitted action and track the next time-sensitive decision.
Scheduled correction: the issue needs action, and the reviewer has established a lawful processing route with enough time to complete it. Name that run or action date, its dependencies and the next check.
Explanation or record review: no pay difference is currently established, but a question or discrepancy requires investigation. Keep reporting, accounting and legal deadlines visible even when net pay is unchanged.
These are workflow labels, not legal classifications. Do not decide urgency solely from the dollar amount, whether a person complained loudly or whether a manager called the change administrative. An incorrect cost allocation may leave net pay unchanged while obstructing a required close or grant report. A small wage shortfall can still need prompt correction.
Determine the obligation and available processing time before choosing the working priority.
Give waiting work a clock
"Waiting for manager" is a dependency, not a complete status. Record what fact the manager must supply, who is asking, the reply time and what happens if it does not arrive. If the deadline is too close for that plan, escalate to someone authorized to choose the next lawful action.
Reassess priority whenever facts change. A deposit question can become a payment failure; a wage question can reveal a group-wide rate error. Preserve the reason for the change and contact the new owner directly. Moving a ticket between queues does not establish that another person has accepted responsibility.
During each queue review, look first at upcoming obligations, missed update times and work waiting on outside parties. Age alone is insufficient: a new case with today's cutoff may require attention before an older explanatory question. Internal response targets should leave time for diagnosis, approval and delivery confirmation.
Reconstruct the amount and the payment already made
Preserve the original report, source record and processing output before changing them. Establish the employee, employer, earning period, workweek where relevant, payment date and exact version used in payroll. A corrected screen can show what should be true now while hiding what was actually processed earlier.
Compare expected and actual results at the right level. For a missing-hours issue, examine the underlying time and earnings calculation. For a deduction question, establish the authorization, effective date and collected amount. For a missing deposit, determine which payment instruction was released and its present status. Each investigation starts with a different kind of evidence.
DOL's hours-worked guidance includes work the employer suffers or permits, even when it was not requested. Investigate the hours and applicable pay obligations separately from a manager's failure to approve a timesheet on time. The approval failure may need a prevention action, but it should not become an automatic reason to omit compensable work.
State the supported correction as an expected result, then compare that result with all relevant entries already processed. Include regular runs, off-cycle runs, manual payments, reversals and pending instructions. Two operators should be able to see whether a proposed adjustment adds new wages, replaces a payment method or corrects a record without paying again.
Worked wage calculation: five missing hours
Assume a covered nonexempt employee has a $20 regular rate, works one 43-hour workweek and has no other compensation affecting that rate. The initial payroll records 38 hours and pays $760 gross. The approved time evidence later establishes five additional hours in that same workweek.
The supported gross result is 40 hours multiplied by $20, plus three overtime hours multiplied by $30: $800 plus $90 equals $890. Compared with the $760 already processed, the gross shortfall is $130. Simply multiplying the five missing hours by $20 would produce $100 and leave $30 unresolved.
This is a gross-wage example. Determine tax, deduction and net-payment treatment separately using the actual employee facts and current rules. Other remuneration, daily overtime rules or a different work arrangement can change the calculation. Keep the workweek, original $760 result and approved $890 target together so another reviewer can reproduce the $130 difference.
If a separate run already paid that $130 before the case owner prepares another instruction, the outstanding gross difference is zero on this same scope. Confirm the earlier entry and payment rather than importing the whole correction twice. An employee's continuing question may concern delivery or the payslip, not another entitlement to $130.
Test the affected population
When a wrong rate, code or integration mapping may affect more than one person, define the population to check. For example, identify employees using the same changed code during the affected runs. Preserve the selection criteria and results, including any people found unaffected. Do not assume the first reported employee is the only one affected.
Keep a suspected cause separate from a confirmed cause. "The time feed may have omitted late edits" is a useful hypothesis. "Version B excluded approved edits after export" becomes a cause statement only when the timestamps and files support it. Premature certainty can send the prevention work to the wrong team.
Authorize a correction that every operator can identify
The case owner assembles the proposed action. The appropriate approver reviews the amount, employee or population, timing, processing method and expected output. The operator executes the approved version. In a small team, one person may perform several tasks, with another person reviewing consequential changes and the resulting output.
Record approval for the specific instruction. A general permission to "fix payroll" does not show whether the reviewer approved $130 gross, a net payment replacement or a reversal. If diagnosis changes the amount or method, obtain the required approval for the changed instruction and mark the earlier version superseded.
Choose on-cycle or off-cycle processing after confirming the applicable timing requirements and current payment state. Waiting for a regular run can be appropriate only when that route meets the obligations and the approved correction can be tracked into it. Document the reason, the designated run and the check that will establish execution.
An off-cycle run needs its own funding, calculation, approval and reconciliation arrangements. Name who will release it and who will prevent the same source item from being paid in the next regular run. The additional run is a processing choice; it does not itself establish that the employee was paid correctly or on time.
Before release, compare the expected result with a preview or other available processing evidence. Review the affected wage bases, deductions, cash amount and employee statement as applicable. Confirm that an upload accepted by the system contains the approved employee, period and amount. File acceptance establishes transport, while the preview helps establish meaning.
Treat reissues and recoveries as separate decisions
When an employee reports a missing deposit, confirm the original payment status with the authorized provider or bank before choosing a replacement. Record whether it is pending, rejected, returned, cancelled or confirmed delivered, using that party's actual evidence. An attempted stop or reversal should remain an attempt until its outcome is known.
If waiting for that confirmation threatens the applicable pay obligation, escalate promptly for an authorized payment plan. The decision maker must consider both timely payment and duplicate-payment exposure. Do not silently postpone wages while a provider ticket waits, or treat uncertainty as proof that the first transfer failed.
A bank-detail change also needs identity verification through the employer's established process. FBI payroll-diversion guidance calls for heightened scrutiny of direct-deposit changes. Contact the employee through a previously established channel when checking a suspicious request; a phone number included in the change request does not independently verify the request itself.
For an overpayment, document the amount and preserve the payment evidence. Route any proposed employee recovery through the applicable wage-law, authorization and tax review. A negative payroll entry, future deduction or requested bank reversal is not automatically a permitted collection method. New York's rules, for example, allow overpayment deductions only under Part 195's conditions. The SOP should identify who makes that decision and keep it separate from correcting a mistaken source record.
Use the Payroll Exception Workboard to control handoffs
Copy the following three blocks into a restricted ticket or working document. Keep the summary visible to the people coordinating the case, and link to sensitive evidence with appropriate access. Each block answers a different operational question: what needs attention, what is authorized and what remains unconfirmed.
Dispatch: what happens next?
Case reference and linked incident: Assign one reference. Connect employee-level records to any shared cause without merging their individual payment outcomes.
Employee, employer and affected scope: Record an employee ID, employing entity, earning period or workweek, payment date and relevant run. Identify additional employees still being checked.
Reported difference and discovery: Describe the report in plain language, who received it and when. Distinguish known facts from open questions.
Priority and reason: Choose immediate response, scheduled correction or explanation/record review. State the consequence that justifies the label.
Obligation and processing cutoff: Record the applicable deadline, its reviewed basis and the provider or banking cutoff needed to meet it. Name the reviewer for unresolved timing.
Case owner, backup and dependency: Name the next-action owner and backup. Specify any fact or confirmation required from another person.
Next action and next update time: State the action, responsible person and check time. Record when the employee will next receive an update, even if investigation remains open.
Authorized instruction: what may be executed?
Source evidence and original result: Link the source version and original payroll or payment output. Record the expected outcome and how it was established.
Calculation and prior corrections: Show the supported target, comparable amounts already processed and outstanding difference. Identify pending runs, manual payments and reversals.
Selected route and intended output: Specify source repair, payroll adjustment, payment replacement, reporting correction or explanation, including any combination required.
Approver and approved version: Record who approved which amount, method, population and timing. Keep earlier versions visible as superseded.
Execution owner and unique reference: Name the operator and run or transaction reference. Explain how another operator can recognize the same correction before processing it again.
Next-feed treatment: State whether the corrected source will appear in a later import and how its previously processed component will be recognized and reviewed.
Confirmation: what is still open?
Payroll and employee-payment result: Attach the processed calculation and the available payment-status evidence. State any unresolved delivery question without calling it complete.
Source and dependent records: Record which time, HR, benefits or other source was repaired, by whom and with what confirmation.
Tax, reporting and accounting tasks: List each applicable task, owner, deadline and result. Give the reason when a workstream is not affected.
Employee communication and final reviewer: Record the update sent, questions remaining and who checked the completed outcome.
Cause and prevention reference: State the confirmed cause or remaining investigation. Link any separate prevention task to its owner and review date.
Use these six checks before recording case closure:
☐ The supported calculation and all prior corrections reconcile to the approved result.
☐ The employee payment or explanation has an evidenced outcome, with unresolved delivery issues still open.
☐ Necessary source repairs and dependent record changes are confirmed.
☐ Required tax, reporting and accounting tasks are complete, or a separately controlled task has an accepted owner and deadline.
☐ The employee received a clear update, and the final reviewer can locate the supporting evidence.
☐ A later feed cannot quietly repeat this correction; any prevention work has its own owner and check date.
Keep the case open if a required outcome is still unknown. If an employee payment is confirmed but a later reporting task remains, label the work explicitly, such as "payment corrected; reporting task open." Transfer only a genuinely separate task with an accepted owner and a link back to this case. A status label should tell the next reader which result is established and which still needs work.
If your current provider cannot return usable correction evidence, SelectSoftware Reviews offers a free advisor consultation to help you identify alternatives. Use a sample exception to ask candidates about approvals, payment status and the next regular import. Confirm the actual service scope before changing providers.
Confirm each affected workstream before closing the case
The payroll result, employee payment, source repair and downstream reporting can complete at different times. Give each affected part a check appropriate to its purpose. A correct register does not show that a returned deposit reached the employee. An employee's confirmation of receipt does not show that the next import or accounting export is correct.
For the missing-hours example, verify the $130 gross adjustment in the processed run, the corresponding approved net result and payment evidence, and the corrected time record. At the following import, confirm that those same hours do not trigger another $130 adjustment. The recurring feed check addresses the cause of the opening scenario.
For a payment replacement, connect the original instruction, any stop or return result, the replacement transaction and the employee-level outcome. Reconcile the cash consequences with finance. If both payments ultimately arrive, open or continue the overpayment decision rather than describing the extra payment as a harmless banking timing difference.
Different workstreams can finish at different times. Record the evidence and open task for each affected part.
Example: correct pay with the wrong allocation
Suppose employees received correct pay, but a payroll export assigned $2,400 to the wrong cost center. Finance discovers the issue before its reporting cutoff. Diagnose the mapping and obtain the accounting approval needed for the correction. No extra employee payment is indicated by this fact pattern.
Confirm the corrected posting and the export or mapping repair separately. If finance uses a manual journal for the current close, record how the next export will avoid repeating or double-correcting it. A revised mapping screenshot alone does not prove the $2,400 was moved in the ledger.
Assign the next decision based on finance's actual deadline and dependencies. The case may need immediate coordination even though net pay is unchanged. Its employee communication can be marked not applicable with a reason; its accounting and source checks remain applicable.
Reporting corrections need their own route
When a payroll discrepancy affects an already filed employment-tax return or wage statement, identify the employer, period, filed version and information needing correction. The IRS Form 941-X instructions set conditions for correcting employment-tax returns, including limits on prior-year federal income-tax withholding corrections. A current payroll adjustment does not automatically amend that return.
Assign wage-statement, federal-return and state or local reporting work separately where required. Use the instructions applicable to the error and reporting period, with a qualified reviewer for uncertain treatment. Preserve submission evidence and the required outcome for each task instead of closing everything when a provider says its internal ticket is resolved.
Store the case evidence under the organization's approved record-retention schedule. Preserve original and corrected versions with their relationship visible. The working queue can become quieter after closure, while the restricted evidence remains available for a later employee question, audit or provider exit.
Review unresolved work and recurring causes together
Set a queue-review cadence that matches the pay calendar and risk. During payroll preparation and release, review time-sensitive cases whenever new information or a cutoff changes the decision. Between runs, use a regular review to catch missed updates, outside-party dependencies and cases that have lost an owner.
Have the reviewer ask concrete questions: Which obligation is next? Which action has no accepted owner? Which case says processed but lacks its required confirmation? Which employee has not received the promised update? These questions reveal unfinished work without relying on a reassuring total of closed tickets.
Keep prevention separate from immediate correction. Paying the missing $130 can resolve the employee's wage difference, while the export defect still needs a configuration change and a check on a later run. Link those tasks so the prevention owner can see the consequence. Do not leave the employee case artificially open until every broader improvement is finished.
Review recurring causes using consistent definitions. Count affected employees, correction runs and distinct incidents separately. One faulty import affecting twelve employees is one shared incident and twelve employee outcomes. Treating it as either one trivial ticket or twelve unrelated causes distorts the operating picture.
Track response promises kept, outstanding deadline decisions, repeated source errors and corrections reopened for missing confirmation. Compare counts with payroll activity and the affected population where useful. A month with fewer employee reports may reflect a smaller run or a reporting barrier, rather than better accuracy.
If the same provider limitation repeatedly prevents usable approvals, status evidence or correction exports, bring those specific failures into a requirements review. First establish what the purchased service includes and which work the employer retains. A system change deserves evidence about the recurring gap, including what a replacement must demonstrate.
Introduce this SOP with one recent, resolved exception. Reconstruct the original report, the approved instruction, the payment and record checks, and the next-feed treatment. Use any missing evidence to refine the intake and handoffs. Then put the Workboard into the live queue and review the first cases with the people who will actually execute them.
Continue with related resources:
For a service review, a free SelectSoftware Reviews advisor call can help you find payroll providers to evaluate. Bring recurring exceptions and the proof each candidate must return after a correction. A provider choice should fit those responsibilities and your actual payroll operation.
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
