Payroll Garnishment Workflow: From Order Receipt to Remittance Proof
Updated: 2 days ago
A garnishment can be configured correctly and still leave the employer with money deducted from an employee but not delivered to the right case. Receipt of the order, the payroll deduction, the outgoing payment and the recipient's application of that payment are separate events. A useful payroll workflow keeps their dates, amounts and owners connected.
Give each order one administrative owner through intake, setup, first withholding, remittance and eventual change or closure. Another team or provider may perform individual steps. The owner needs enough evidence to identify what happened and pursue the next action when a handoff fails.
The Garnishment Remittance Reconciliation below is useful when a deduction, transfer or recipient posting needs follow-up. Its amounts track money after the withholding decision for U.S. wage garnishments and support orders. Apply the order and governing law to the required action, with a separate review when competing orders need priority or allocation decisions.
Table of contents
Route the order before choosing a deduction rule
Start with the complete document, its delivery record and the employer and employee identities. Match the named person to the employment record through a restricted identity check. A similar name, an old payroll number or a business trading name is not enough to explain a mismatch. Record who will resolve uncertainty without circulating the order through ordinary team chat.
Classify the instruction before selecting a payroll deduction code. An ordinary creditor garnishment, child support IWO, IRS wage levy and federal administrative garnishment can require different bases, limits and procedures. The Department of Labor's CCPA guidance distinguishes these categories. Its ordinary garnishment limit does not supply a universal formula for tax levies or support orders, and the CCPA does not determine order priority.
For child support, current OCSE employer instructions call for checking whether the IWO is regular on its face. They also address obtaining the underlying support order when the sender is someone other than a court or child support agency. Assign that document review explicitly. Payroll should not improvise validity rules from an email subject line or treat every request for money as an enforceable order.
An IRS wage levy needs the levy instructions and the employee's Statement of Dependents and Filing Status. If the employee does not return the statement within three days, use the IRS default of married filing separately with no dependents; a later statement can change the exempt amount. IRS guidance explains the exempt amount and supplies Publication 1494 tables. A W-4 is not a substitute for that statement. Record the applicable table year and the reviewer's calculation rather than copying the ordinary creditor percentage into the levy setup.
Keep an inventory of other active orders for the employee. A newly received document may amend an existing instruction, duplicate it or introduce a competing obligation. Resolve that relationship before creating another deduction. When orders compete, obtain the supported priority and allocation decision, then bring the approved amounts back into this operating process.
Put the legal deadline on the payroll calendar
Record when the employer received or was served with the order, how it arrived and when payroll obtained it. Preserve both dates if a branch office forwarded the document later. An internal forwarding delay should be visible in the record, rather than replaced with a more convenient intake timestamp.
Read the document for required responses as well as withholding. A court answer, employment-status response, employee copy and first deduction can involve different actions and dates. Give each required action an owner, its governing instruction and a due date. A payroll cutoff is an internal processing boundary; it cannot establish a legal deadline.
For interstate child support, OCSE distinguishes issues governed by the issuing state from those governed by the employee's work state. Its current employer page identifies the work state as governing when withholding begins and payments are sent. Ask the responsible reviewer to resolve the actual jurisdiction and timing, then record the resulting first pay date. Avoid a universal rule that every new order waits until the next convenient cycle.
The same calendar needs a remittance date. OCSE states that child support payments must be sent no later than seven business days after wages are paid, and the work state may require a shorter period. Document the applicable deadline and the scheduled release date. Check how weekends, holidays, provider cutoffs and payment processing affect the schedule under the actual instructions.
The IWO form transition also deserves a current reference. OCSE's October 7, 2026 update, revised October 9, reports that OMB approved a new form expiring August 31, 2029 and extended the previous version to August 31, 2027. Child support agencies must generate the revised form by September 1, 2027. Do not reject a form solely because an older printed expiration date appears to have passed; review it against that published transition and the applicable instructions.
For a late discovery, record the missed action and obtain a timed resolution from the responsible agency, legal reviewer or service owner. Do not quietly backdate setup or recover a missed amount from the next paycheck without an authorized basis. Keep the original receipt record available so the response addresses the actual delay.
Receipt, first withholding and remittance need separate dated records. An internal payroll cutoff does not determine the legal deadline.
Configure an order another reviewer can reproduce
Separate the original instruction from the payroll application's configuration. Store the source document in a restricted repository. The configuration record should identify the order type, employer, employee, case identifier, pay frequency, approved start date, deduction basis, limit treatment and remittance destination. Include the effective version when an amendment changes an amount.
Write a short calculation note that explains the approved treatment in ordinary language. Identify which earnings and deductions feed the basis, how a periodic obligation is translated to the payroll frequency and how the configured limit operates. Link the legal or agency authority used by the reviewer. The note should let a second person reproduce the result without relying on a dropdown label.
Administrative fees need separate treatment. Record whether a fee is permitted under the applicable instruction, the authorized amount and how it interacts with the withholding limit. Do not enable a default fee simply because the application offers it. Distinguish a provider charge to the employer from any amount lawfully deducted from the employee.
Then compare the saved setup with the approved record. Check the employee assignment, effective dates, frequency, deduction priority, remittance identifier and destination. A correct deduction code on an employee with a similar name is still an incorrect setup. Retain the reviewer's identity, date and the specific preview or export examined.
Verify changed payment instructions through an established agency or court contact route. Use a previously validated channel or an independently obtained official contact when a new message requests a different destination. Preserve the original and replacement instructions and the verification result. A bank-detail change and a withholding-amount change are separate changes even when they arrive together.
For a small team, choose a reviewer who can see the instruction and the saved result. If no independent person is available before a required action, document that limitation and arrange an appropriate compensating review without treating the limitation as permission to miss the order's deadline.
Inspect the first withholding in actual pay
The first live deduction deserves an employee-level check against the approved calculation. Compare the actual paid earnings, legally required deductions, applicable basis, permitted limit and resulting withholding. A preview from the previous week may no longer represent the final payroll after a leave adjustment, bonus or corrected time entry.
Under the CCPA, disposable earnings generally means earnings remaining after legally required deductions. Voluntary deductions usually do not reduce that basis. For ordinary garnishments, the federal weekly ceiling is the lesser of 25% of disposable earnings or the excess over 30 times the federal minimum hourly wage. More protective applicable state limits must also be considered. Use the appropriate pay-period treatment and order-specific rules.
Keep the application calculation and the reviewer's expected result together. A matching total supports the amount for that run; it does not establish that every future variable-pay situation is configured correctly. Identify which future events require review, such as an off-cycle payment, changed pay frequency or additional order.
Explain zero withholding as carefully as a positive amount. The employee may have no earnings, insufficient available earnings or an approved allocation leaving nothing for this order. A missing employee assignment can produce the same zero in a report. Retain the reason and evidence so the next reviewer can distinguish a lawful result from a failed setup.
If the result differs, establish whether the issue affects this order, this employee's entire calculation or a wider population using the same configuration. Follow the payroll exception process for the affected payment and obtain the necessary decision before release. An operational worksheet cannot authorize an otherwise unlawful deduction or a delay in wages.
For employee questions, provide the information payroll can substantiate: the issuing body, case reference, effective deduction and contact route. Restrict access to the underlying documents. A dispute about the debt itself belongs with the proper issuing or legal channel; a payroll setup error still needs the employer's prompt investigation.
Follow withheld money beyond the payroll register
A deduction reduces the employee's payment and creates an amount to remit. An export marked ready does not show that the bank released money. A bank debit does not identify whether the recipient applied it to the right case. Track those stages separately so a team can locate the failure without sending the same funds twice.
For each remittance, retain the payroll run, pay date, order identifier, amount withheld, destination, payment reference and applicable deadline. Add the scheduled release, actual transmission and settlement evidence as they become available. Record the person or service responsible for obtaining recipient confirmation when application is disputed or remains unresolved.
A combined payment needs its detail file. OCSE permits a single child support check for multiple employees going to the same State Disbursement Unit when the required employee amounts, withholding dates and identifiers are itemized. A bank total alone cannot reconstruct those allocations. Preserve the detail actually transmitted, including the version used if a file was regenerated.
Where payroll hands the work to AP, require an explicit acceptance of the amount, destination, deadline and supporting detail. AP returns the payment reference and settlement evidence to the order record. If the provider remits, ask what event its status describes and which party monitors rejection or return. Avoid interpreting a generic processed status as all three events.
Reconcile the remittance to cash and the garnishment liability account. Keep processing charges outside the order principal unless the approved treatment specifically provides otherwise. If the bank debits one batch amount, preserve a bridge from that debit to each included employee and case. Investigate any difference rather than clearing it through a convenient expense account.
Choose a review cadence that can catch a failed transmission before the applicable deadline. A monthly review can find aging balances, but a short legal remittance window requires checks during the pay cycle. Assign a backup for absences and a way to escalate an overdue acknowledgment while the normal owner is unavailable.
Reconcile one order with the four-amount worksheet
Use the Garnishment Remittance Reconciliation for one order and pay cycle. Copy the fields below into a restricted working document. Keep the source amounts separately available and attach the supporting references. This is a financial reconciliation after the withholding decision; it does not calculate how much the law permits payroll to deduct.
Identify the line.
Order or case reference: ____;
employee reference: ____;
employer: ____;
payroll run and pay date: ____;
reviewer: ____.
Record the first-withholding requirement and this cycle's remittance deadline: ____.
Use a restricted employee reference rather than placing full personal identifiers in a general finance log.
Opening funds held: A = _____. Enter the previous reconciled amount withheld but not yet settled out of the employer's or remitter's account for this order. Carry the supporting transactions forward. Do not use the employee's total debt balance or the agency's arrears figure as this opening amount.
New withholding: B = _____. Enter the actual finalized payroll deduction for the current cycle. Identify any difference from the preview and retain the approved correction. Include the linked pay run rather than assuming that every run in the period used the same effective setup.
Settled remittances: C = _____. Enter remittance payments that have settled out for this order during the reconciliation window. Support them with the bank or remitter evidence and allocation detail. Use the remittance to the required recipient; do not count both provider funding and the provider's later payout as separate remittances. A scheduled payment or an unaccepted instruction stays pending. Identify returns, refunds and other authorized adjustments separately instead of forcing them into an unexplained balancing number.
Closing funds held: D = A + B - C = _____. Explain every amount remaining with the employer or remitter and assign the next action and date. Confirm whether it is scheduled within the applicable deadline, returned or overdue. A zero closing balance does not answer whether the recipient applied the money correctly.
Recipient application check.
Of the settled remittances, amount matched to the intended case: _____;
amount still awaiting application evidence: _____;
recipient contact or confirmation reference: _____.
Keep the second amount visible alongside the cash reconciliation. Do not add it back to funds held merely because the recipient's record is missing.
Review the exceptions. For each unresolved item, record its amount, current location or uncertainty, owner, next action and next review date. State what evidence would resolve it. Keep payment returns and employee refunds tied to their original transaction with the approved accounting and payroll treatment.
Consider a fictional order with $40 opening funds held, $120 newly withheld and $100 settled out. The closing funds held are $60. Suppose the recipient has applied only $80 of the settled $100. The file has two follow-ups: arrange or investigate the $60 still held, and trace the $20 already sent but not applied. Resending $80 would combine those different problems.
If the recipient later locates the $20, update the application check with its confirmation. That event does not change the $60 funds-held balance because no additional money left the account. If the remaining $60 is then properly remitted and applied, both checks can be reconciled. Preserve the intermediate records so another reviewer can understand why the follow-ups closed.
For a file containing returns or refunds, use explicit authorized adjustment lines and reconcile the expanded movement history. Do not declare the simple four-amount equation complete while excluding a cash movement. The worksheet's purpose is to expose missing explanations, not to make every balance appear clean.
The fictional file has $60 still held and $20 already sent but not applied. Resolving application of the $20 does not change cash already sent.
Match the response to the failed handoff
When payroll withheld nothing unexpectedly, begin with the saved order assignment and actual calculation. Check whether the effective date, employee match or available earnings explains the result. Determine the affected pay dates and obtain instructions for correction. A catch-up deduction needs its own support; the original missed amount does not create unlimited capacity on the next run.
When money was withheld but transmission failed, retain the rejected file or response and identify whether any payment nevertheless exists. Confirm the order amount, deadline and payment status before resubmitting. Tell the responsible service owner what must be resolved and by when. Preserve the failed attempt alongside the replacement instruction so the history shows a controlled retry.
When money settled but the agency reports no receipt, trace the payment reference and transmitted case detail. Check destination, identifiers, amount and pay date. Ask the recipient or remitter to locate or correct the application, using their established process. Record what is known about cash movement and what remains uncertain rather than treating a missing case posting as proof that no money moved.
When an employee reports excessive withholding, compare the final deduction with the order and applicable limits. Separate a calculation error from a disagreement with the underlying obligation. Have the responsible reviewer determine any refund, future offset or agency correction and its payroll treatment. Document the employee communication and action taken without promising a remedy before its authority is established.
When an employee was terminated or never employed, follow the order-specific status-response requirements. A zero payroll result is not itself a response to the sender. Keep evidence of the notification and review any later final-pay or other payment event under the applicable instruction.
Use the exception record to preserve specific decisions and deadlines. Avoid a status such as with provider unless it includes the named contact, reference, required response and next escalation. The employer's operational owner should be able to explain what is happening even when the provider performs the correction.
Change or close an order without erasing its history
A new amount, changed work location, reduced hours, leave, rehire or different pay frequency can affect an active order. Route the event to the owner before the next affected payment. Record whether it changes the calculation, timing, reporting or remittance destination, and which reviewer resolved that question.
Treat an amendment as a versioned instruction. Preserve the old document and effective configuration, identify what the new document replaces and check the first result under the revised version. Avoid overwriting the prior amount in the only retained record. Historical withholding needs to remain explainable after the current setup changes.
For child support, OCSE says withholding continues until the agency, court or other sender notifies the employer to change or stop it. An employee's statement that the obligation is paid is a reason to seek the appropriate confirmation, not a substitute for that notice. Other order types need their own termination or release rules.
Before closing the administrative case, distinguish stopping future deductions from finishing the remittance work. Confirm the authority and effective date for the stop. Then reconcile funds held, pending transfers, returns and unresolved application questions. A closed deduction code can coexist with an unpaid or misapplied remittance that still needs an owner.
Retain the source, setup versions, calculations, employee communications, remittance detail, exception decisions and closure evidence under the applicable retention schedule and any legal hold. Limit access according to role and remove routine access when responsibilities change. Retrieval should work by employer, employee reference, order and pay date without relying on one person's inbox.
Handle employment decisions separately from administrative inconvenience. The CCPA protects an employee from discharge because earnings are garnished for any one debt. Do not infer that having more than one order makes an adverse employment action permissible; obtain the applicable legal review.
Assign service ownership before automating remittance
Choose the operating model by the work the team can actually perform. An employer with occasional straightforward orders may maintain a restricted order file and a manual reconciliation if it can reliably meet deadlines and provide backup coverage. A higher-volume employer may benefit from automated intake and remittance, but should require accessible calculations, payment detail and exception reporting.
Ask a prospective provider to demonstrate one order arriving, its reviewed setup, a variable-pay calculation and a remittance exception. Request a sample export showing which amounts were withheld, transmitted, settled and returned. Ask whether recipient application is tracked, how disputes are handled and what evidence remains available after the contract ends.
Put the division of work in writing: receipt monitoring, document review, payroll configuration, employee communication, release approval, funding, remittance and exception follow-up. Identify who interprets the applicable requirements and who merely enters an approved instruction. Price implementation, per-order processing, corrections and historical-data retrieval using the actual proposed terms.
During a provider switch, reconcile every active order's last old-system deduction and first new-system deduction. Carry forward unsettled funds and unresolved recipient questions separately from the remaining employee obligation. Confirm which provider will remit each withheld amount so the employer neither loses a payment between systems nor authorizes both to send it.
Approve automation when the evidence supports the promised handoffs and the employer can perform the retained work. Begin with a controlled review of actual first-run outcomes, then set recurring checks around remittance deadlines and events that change the order. The recurring decision is whether each withheld amount reached its required destination, with an accountable next action for anything that has not.
Explore the Decision Guides library.
See the Payroll Operations & Controls hub.
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.
