Multiple Wage Garnishments: Allocate Competing Orders Within the Limits
Two orders can each request an amount that looks affordable on its own and still produce an unlawful combined deduction. The mistake is giving every order a fresh allowance, or letting payroll's deduction sequence decide who receives the available money.
For a U.S. employer, the workable approach is to identify the order types, establish the applicable earnings limit, and apply the governing priority and allocation rules to the same pay-period record. A second order changes the allocation review even when the employee's pay has not changed.
This guide addresses the point where active orders compete. Use the broader garnishment operating model for intake, setup, remittance and ongoing order administration. Here, the output is a supported amount for each order, including an explained zero when no capacity is available. The Competing-Order Allocation Sheet below gives payroll and its reviewer a reusable way to make that decision.
When active orders compete, a provider comparison needs more than a promise to support garnishments. A free SelectSoftware Reviews advisor consultation can help you discuss the calculation detail and service responsibilities to ask providers to demonstrate.
Table of contents
Read the orders as a group before assigning money
Keep the complete active-order set together for the employee. Record each issuing court or agency, case identifier, order type, service information, requested withholding, effective timing and any amendment or termination. An amendment may replace an existing instruction rather than create another debt. Compare identifiers and the document's stated action before adding another deduction line.
Classify ordinary creditor garnishments, support withholding, federal administrative nontax garnishments, and tax levies separately. A bankruptcy court order also requires its own review. Labels in a provider's dropdown are useful only when they represent the correct legal category.
There is no universal priority ladder supplied by the Consumer Credit Protection Act, or CCPA. The Department of Labor explains that priority comes from state or other federal law. A service date can matter under the governing rule, but a date alone does not establish priority across every order type.
Write the source of the allocation rule beside the classification. If the order and the applicable authority appear inconsistent, obtain a timely answer from the issuing court or agency and, where needed, qualified counsel. Give the question an owner and deadline. Do not replace a disputed legal instruction with the deduction ordering that happens to be configured in software.
For interstate child-support withholding requested directly by an out-of-state child-support agency, federal regulations point to the employee's principal place of employment for specified matters, including limits, priorities and allocation among multiple support obligees. The address printed on the issuing order is therefore not a sufficient jurisdiction decision. Document the relevant work location and verify the rule that applies to this withholding situation.
Calculate capacity on the correct earnings basis
Disposable earnings under the CCPA are earnings remaining after deductions required by law. They are not necessarily the net-pay figure shown on the payroll preview. The legal definition prevents ordinary voluntary deductions from silently reducing the base used to calculate garnishment capacity.
For example, income taxes and the employee's Social Security and Medicare deductions belong in the required-deduction calculation. Voluntary insurance, ordinary voluntary retirement contributions and payroll advances usually do not. Keep a deduction-by-deduction explanation for anything whose treatment is uncertain. A provider code called after-tax does not resolve whether the deduction is legally required.
For ordinary creditor garnishments, the federal weekly ceiling is the smaller of 25% of disposable earnings and the amount above 30 times the federal minimum hourly wage. At the current $7.25 federal minimum, that protected weekly amount is $217.50. Apply zero rather than a negative result when earnings do not exceed the protected amount. An applicable state rule may allow less withholding; verify it before using the federal ceiling as the executable amount.
This is an aggregate limit for ordinary garnishment, not a separate allowance for each creditor. Also compare the calculated capacity with the amount actually requested under the orders. A ceiling permits no extra collection beyond the supported instructions.
Two ordinary orders, one available amount
Assume a fictional employee has $600 of weekly disposable earnings, two ordinary creditor orders requesting $100 each, and no support, tax levy, bankruptcy order or other higher-priority withholding. Assume the applicable state rule does not reduce the federal ceiling.
The percentage test is $600 × 25% = $150. The protected-earnings test is $600 − $217.50 = $382.50. Available ordinary capacity is $150, while the requests total $200. Deducting $100 for both orders would exceed the ceiling by $50.
The calculation does not answer how to divide the $150. If the confirmed governing rule authorizes paying the first order before the second and both may receive funds in this period, the result could be $100 and $50. A rule that permits only one active creditor withholding, or requires another allocation, produces a different result. Record the actual rule and response obligations; the example's conditional split is not a nationwide instruction.
Now suppose the same employee has a low-earnings week with $250 of disposable earnings. The percentage test is $62.50, but the amount above $217.50 is only $32.50. The ordinary capacity falls to $32.50. Keeping last week's fixed deductions would be wrong even though neither order changed.
Use the correct pay-period threshold. The Department of Labor lists protected amounts of $435 for biweekly pay, $471.25 for semimonthly pay and $942.50 for monthly pay at the current federal minimum. Semimonthly is not biweekly. These are ordinary federal thresholds, not amounts to apply indiscriminately to support or tax levies.
One employee-period calculation establishes ordinary capacity. The applicable allocation rule determines how orders use that capacity.
Allocate competing support obligations in the right sequence
Support withholding has different federal ceilings. Depending on whether the worker supports another spouse or dependent child, the CCPA generally permits up to 50% or 60% of disposable earnings for support. The additional five percentage points apply to support for a period more than 12 weeks in arrears. Verify the relevant facts, order instructions and applicable state or tribal limits rather than selecting 65% whenever an order contains any arrears.
Distinguish current support, ordered payments toward arrears and any medical-support component. The allocation rule may give different components different treatment. A larger outstanding debt does not automatically give that case a larger share of current-period withholding.
Indiana's employer guidance, for example, requires prorating current support among cases when available withholding cannot cover all current obligations. When current support can be paid in full but recurring arrears payments cannot, its guidance prorates the arrears after paying current support. Use this as a jurisdiction-specific example; confirm the employee's governing procedure before applying it elsewhere.
A support-only allocation with an explicit local rule
Assume a fictional Indiana employee has $800 of weekly disposable earnings and a verified 50% support ceiling for this scenario. Two orders request current support of $300 and $200, plus arrears payments of $40 and $20. There is no medical-support component, other order or employer fee in this example.
Available withholding is $400. Current support totals $500. Under the described Indiana procedure, Order A receives $400 × ($300 ÷ $500) = $240. Order B receives $400 × ($200 ÷ $500) = $160. No capacity remains for the ordered arrears payments. The $60 of requested arrears payments does not enter the current-support ratio.
Save the requested and allocated amounts separately. An unmet obligation is not erased because payroll cannot withhold it this period. Use the required reporting and remittance instructions for the shortfall. Keep the allocation attached to the case identifiers so the recipient can apply each payment correctly.
Rounding needs a defined final step. Calculate shares at sufficient precision, round the payment amounts according to the applicable instructions, and verify their sum equals the amount authorized for allocation. If rounding creates a cent difference, use the permitted method and record it. Do not increase the aggregate deduction to make two independently rounded shares fit.
Route mixed orders through their own rules
An ordinary creditor order does not receive an additional 25% allowance on top of higher-priority support withholding. The Department of Labor illustrates a case where support already exceeds the ordinary percentage ceiling, leaving no additional ordinary creditor garnishment. The support ceiling and the ordinary ceiling are not amounts that payroll may simply add together.
For an Indiana example with $500 of weekly disposable earnings and $100 of support withholding, the state's guidance allows the remaining $25 under the 25% ordinary limit to be applied to a business garnishment. That does not make $25 automatically correct in every state or case. Confirm the order, applicable protections and priority before releasing an ordinary deduction.
Federal administrative wage garnishment for nontax debt follows the governing federal authority. Under Treasury's 31 CFR 285.11, disposable pay subtracts health insurance premiums as well as amounts required by law to be withheld. Court-ordered withholding is not a deduction from that base. Keep this calculation separate from CCPA disposable earnings. The ordinary administrative amount is limited to the smaller of the ordered amount up to 15% of disposable pay and the amount above the protected minimum-wage threshold. Family support has priority over an order issued under that regulation. Other priority and competing-order provisions in the regulation must also be applied.
For a fictional weekly Treasury example, assume $800 of Treasury disposable pay after the applicable deductions, an order seeking 15%, and $160 already withheld under a qualifying order with priority. The administrative test gives $120, while 25% of $800 minus $160 leaves $40. Under the regulation's competing-order calculation, the smaller amount is $40. This assumes the stated order type, priority and facts; it is not a formula for an IRS levy or every student-loan program.
An IRS wage levy uses its own exempt-amount calculation. Do not process it through an ordinary 25% creditor code. The IRS supplies Publication 1494 with the levy to explain the exempt amount. Prior court-ordered child support can affect that calculation, and the IRS describes a route for addressing support that was not included. Preserve the support order date and levy receipt information and obtain the required direction rather than manufacturing a universal support-versus-tax ranking.
State tax levies and bankruptcy instructions also need their applicable authority. Keep them outside a generic ordinary-creditor worksheet until the responsible reviewer has established the correct treatment. More restrictive state creditor protections do not automatically override federal administrative nontax collection rules.
Classify the combination before using arithmetic. A correct calculation applied to the wrong order type remains an incorrect withholding.
Complete the Competing-Order Allocation Sheet
Copy these fields into a restricted worksheet or case record. Complete one cover record per employee and pay period, then repeat the order block for every active instruction. Keep identifiers and source documents in approved payroll storage. The sheet supports a review decision; it does not replace an order or determine jurisdiction by itself.
Period record
Field 1. Employee and payment: Record the employee identifier, payroll run, pay date, pay frequency and earnings period. Connect any separate payment in the same period to this record for review.
Field 2. Governing location: Identify the relevant work jurisdiction, the basis for choosing it and any uncertainty. Note whether an interstate or tribal rule requires further direction.
Field 3. Earnings included: List the amounts treated as earnings for this calculation, with the payroll lines supporting them. Describe any excluded payment and its authority.
Field 4. Applicable deductions: Itemize the legally required deductions for CCPA disposable earnings; keep usual voluntary deductions separate. For a Treasury order under 31 CFR 285.11, also subtract health insurance premiums when calculating its disposable pay. Keep court-ordered withholding outside that base subtraction.
Field 5. Disposable amount: Show the arithmetic from included earnings to each applicable base. Label CCPA disposable earnings and Treasury disposable pay separately when both are relevant. Record the deductions supporting each calculation instead of forcing one amount into all methods.
Field 6. Limits and protection: Record the applicable percentage, protected-dollar test, pay-period conversion, state or tribal restriction and source version. State which order types each limit governs.
Repeat for each order
Field 7. Instruction identity: Record the order type, issuer, case ID and document version. Identify an original, amendment, one-time instruction or termination without counting the same instruction twice.
Field 8. Timing evidence: Preserve service or receipt information, start requirement, response deadline and any expiration or stop instruction that matters to this order.
Field 9. Requested amount: Enter the current-period request and its components. Keep current support, arrears payments, percentage requests and fixed amounts distinguishable. Show any authorized conversion to this pay frequency.
Field 10. Priority and method: Name the authority supporting this order's position or share. Record whether the confirmed method is sequential payment, proration or another prescribed procedure.
Field 11. Expected allocation: Show the amount assigned, the calculation and the unused or unavailable capacity. Explain a partial amount or zero. Identify a legal question that remains unresolved.
Field 12. Recipient instructions: Preserve the authorized destination, required reference and due date. Each order's allocated amount must remain identifiable through payment preparation.
Review and execution record
Field 13. Aggregate check: Add the expected allocations and compare them with every applicable shared ceiling. Confirm that no order was given a duplicate allowance and that no amount exceeds its supported request.
Field 14. Fees and other deductions: Identify any proposed employer processing fee, its authority and its effect on withholding or remittance. Do not assume a fee may sit outside the relevant limit.
Field 15. Preview difference: Compare each expected allocation and the aggregate with the actual payroll preview. Record deduction codes, overrides and the first unexplained difference, including a zero that should be positive.
Field 16. Authorized decision: Name the reviewer, decision time and exact run version. Record the supported amounts to release, any unresolved instruction, required contact and the next decision deadline.
Field 17. Processed outcome: Capture each actual withheld amount and the aggregate after payroll runs. Compare them with the authorized version, not an earlier draft of the worksheet.
Field 18. Distribution and next review: Match each payment to its case reference and retained proof. State the event that requires recalculation, such as changed earnings, a new order, an amendment or a stop instruction.
Use five checks before authorizing the allocations:
Every active instruction appears once, with the relevant version and timing evidence.
Each calculation uses an explained earnings basis, period and limit.
Priority and allocation have authority specific to the order combination.
The preview matches the authorized per-order amounts and aggregate, including fee treatment.
Unresolved questions and required responses have named owners and deadlines; execution evidence can be matched back to this decision.
A failed check identifies work that remains. It is not permission to postpone a statutory deadline. The responsible reviewer must determine a timely compliant action and document the direction used.
Bring the completed allocation sheet to a provider discussion, including a partial amount and an explained zero. SelectSoftware Reviews can connect you with a free payroll-software advisor to explore providers for that evaluation.
Make an unresolved conflict a timed decision
When an answer is needed before cutoff, ask a narrow question. Provide the order types, applicable jurisdiction, relevant dates, requested amounts, current disposable-pay calculation and the specific rule that appears to conflict. Use approved secure channels for employee and case information. A general message asking which order wins often forces another round of questions.
Separate a legal uncertainty from a software defect. If the applicable rule is known and the preview allocates incorrectly, the question is how to implement the authorized result and verify it. If the rule is unknown, a successful manual override does not settle the legal question. Route those two problems to the people who can resolve them.
Set a callback or escalation time before the external deadline. Preserve agency directions in the case record, including who gave them, when and what facts were supplied. When an oral answer affects withholding, seek a written record or confirmation through the accepted channel and have the designated reviewer assess it.
Document why an order receives zero. Low disposable earnings, a higher-priority instruction, an order not yet effective and a missing setup are different explanations. The first three still require their applicable handling; the fourth may be an employer processing failure. A zero-deduction report should let a reviewer distinguish them without reopening every source document.
Keep employee communication factual and private. Explain the actual payroll amount and route questions about the underlying obligation to the proper issuer. Do not promise that an unpaid portion is forgiven, that payroll can cancel the order on request, or that next period will necessarily have the same deduction.
Require payroll to demonstrate the combined result
For an employee with several orders, confirm which calculations the provider performs and which decisions the employer must supply. Ask for a demonstration using the combination you actually encounter. A list of supported garnishment types does not establish correct priority, proration or limit handling in a particular configuration.
Use a small demonstration set: two ordinary orders whose combined requests exceed capacity; two support cases with current support and arrears; and a low-earnings period after a higher-earnings period. If relevant to the employer, add a supported federal administrative scenario. Require visible per-order calculations, aggregate limits and an explanation of zero or partial withholding.
Test the sequence after a new order is added, an amendment replaces an old amount and an existing instruction ends. Verify whether an import or manual override can bypass the shared limit. Review what the operator sees when an order requires information or a method the system cannot supply. These are requests for evidence from the proposed service, not claims that a named platform has passed them.
Before committing, document responsibility for updates to legal rules, employee facts, order entry and remittance. Specify access to the calculation detail and case references, including exports if the employer changes providers. An opaque deduction total is hard to challenge even when the provider offers useful administrative support.
Recalculate when the facts or payment change
Carry the authority record forward, but calculate against the current payment. Reduced hours, unpaid leave, a bonus, a commission or a separate check can change the available amount or require a different review. A standing order does not establish a standing deduction in every payroll period.
Do not treat an off-cycle run as a fresh ordinary garnishment allowance merely because it has a different run ID. Establish how the payment relates to the compensated period and governing order rules. The CCPA definition includes compensation for personal services such as wages, bonuses and commissions; lump-sum and support instructions may also require separate agency handling. Resolve that treatment before releasing the payment.
After processing, reconcile each order's actual withholding to its expected allocation. Then reconcile the withheld amounts to the payments and case references. A correct aggregate with money sent to the wrong case is still a failed outcome. Keep unresolved distribution work visible until its required action and result are confirmed.
When correcting an overwithholding, identify where the money is now. An amount still held by the employer and an amount already remitted call for different recovery coordination. Obtain the appropriate direction, correct the payroll and distribution records, and record any employee reimbursement or related action. Do not silently deduct less from another order next period to offset an unrelated error.
When an instruction ends, preserve the authorized stop document and rerun the remaining allocation. A released order may make capacity available to another active instruction, but the remaining order's rules and requested amount still control. Retain the previous allocation version so the change in the employee's deduction can be explained.
Start with the employees whose requests exceed available capacity or whose active orders use different legal regimes. Complete their allocation sheets with a second reviewer, resolve the governing method, and compare the result with the payroll preview. Then preserve that method with an event-based recalculation routine. This gives the team a specific reason for each amount instead of relying on the order in which deductions happen to run.
Questions that arise when the requests exceed pay
Should we divide the available amount equally?
Only when the applicable allocation procedure requires or permits that result. A support proration can depend on each case's current obligation, while an ordinary creditor sequence may depend on a different rule. Equal amounts are easy to enter but can be wrong even when the combined deduction stays below the ceiling.
Does an employee's voluntary repayment instruction change priority?
Do not use a voluntary instruction to displace an enforceable withholding obligation. Check its legal treatment separately. Treasury's administrative regulation specifically addresses employee assignments that interfere with its orders and provides a distinct written-consent rule for greater withholding. That is not general permission to enlarge every garnishment or rearrange all creditors.
Can we use a deduction to recover our own payroll overpayment first?
An employer recovery is a separate decision with its own state-law and tax considerations. It is not automatically a required deduction that reduces CCPA disposable earnings or an order that outranks other claims. Establish the permitted recovery route and its interaction with active withholding before adding it to the run.
Does having more than one order remove employee protections?
Do not translate the count of deduction lines into a termination decision. The CCPA protects against discharge for garnishment for one debt, even if that debt involves multiple proceedings. Other state or federal protections may apply, including Treasury's protection for its administrative orders. Refer employment decisions to the responsible HR or legal reviewer.
If your current service cannot show how combined deductions are calculated, a free SelectSoftware Reviews advisor conversation can help you frame a provider comparison. Use the same documented cases to assess the options.
Explore the full Decision Guides library.
Continue with the payroll operations collection.
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.
