On this page Jump to section
Check exceptional inputs
Include worker, pay period, requested pay date, event reason, supporting document, approval, and the source of any amount supplied. Distinguish an input from a payroll calculation. A complete packet can still be declined; payroll owns that decision.
Define the exceptional request
Record who requested the off-cycle review, which employee or group it concerns, the relevant pay period and the reason supplied. Keep the requested payment date separate from any date payroll has approved. A request for an additional run is not itself authorization to process one.
Use the payroll team's approved checklist and restricted document location. The assistant should collect source inputs and approvals, not calculate an outcome from incomplete instructions or change payroll settings to accommodate a request.
Assemble one traceable packet
Each input should point to its source and show whether it is proposed, confirmed or awaiting a decision. Use employee references that payroll recognizes while avoiding unnecessary personal information in the summary.
- Request scope
- Include Requester, employee reference, period and stated reason.
- Clarify Which items are included and which remain part of the normal payroll workflow?
- Source amount or hours
- Include The supplied record, its author, date and approval status.
- Clarify Is this an input provided for review or a calculation already approved by payroll?
- Related payroll activity
- Include Relevant run or correction references requested by the reviewer.
- Clarify Could the same item already be included in another pending or completed run?
- Authorization
- Include Decision owner, approved version and the limits of the instruction.
- Clarify Has payroll approved processing, requested changes or declined the request?
- Delivery and response
- Include Packet version, recipient, delivery time and feedback.
- Clarify What remains outstanding, and who owns the next action?
Check overlap before handoff
Compare the request with the related records payroll has authorized you to inspect. Flag a possible overlap with a normal run or earlier correction using both references. Do not remove an item from either workflow without an explicit instruction from the responsible owner.
If a manager changes the requested hours or amount, retain the previous version and the revised source. Explain the difference in the cover note. A reviewer should not have to discover that the attachments changed after approval.
Example: a late time correction
A manager supplies additional time after the regular input packet has been handed off. Record the late arrival, affected period and manager approval reference. Ask payroll whether the item belongs in a revised regular packet, an off-cycle review or another approved process.
The assistant should not promise the employee a payment date or decide the treatment. When payroll responds, record the instruction and update the packet status. If the request is declined or held for evidence, preserve that outcome rather than keeping an apparently approved task open indefinitely.
Deliver with a concise exception note
State what is complete, which inputs remain uncertain and which approval is still needed. Include the current packet version and source links. Keep requested dates visible, with any approved timing attributed to the person who confirmed it.
After handoff, track payroll's response and any replacement documents. Administrative completion means the requested records and decisions are traceable; it does not mean a payment has been processed. Record payment completion only from the authorized source and within your assigned role.
Payroll support can help maintain the input checklist, collect approvals and organize these exception packets without transferring payroll decision authority.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.
