TL;DR
- Core decision: Who in your organisation carries the duty when a court order, a statutory demand or a third-party instruction arrives, and the rest of payroll continues to move around it.
- When doing nothing is right: When the answer is already owned, written down, and has been tested against an actual order in the last twelve months rather than described in a procedure.
- What has to be true: A single role accepts the legal receipt of orders, a written priority order exists for shortfalls, and confidentiality is treated as a duty owed to the employee rather than a courtesy.
- How the options split: Between a model where payroll owns it end to end, a model where HR or legal owns the receipt and payroll owns the mechanics, and a model where a shared service centre handles intake under a published standard.
- Decision rule: Pick the model whose owner is named, trained, and reachable during a dispute, not the model that looks tidy on an org chart.
- Outcome to expect: Fewer contested deductions, faster resolution when something goes wrong, and a payroll function that can prove, on paper, that it acted on a valid instruction in the correct order, on time.
When the Order Arrives on a Tuesday Morning
A payroll lead in a mid-sized employer opens a letter from a county court. It names an employee, sets a weekly figure, and gives a date by which the first deduction must reach the court. The letter is correct, signed, and not the first the team has handled. What slows the lead down isn't the order itself. It's the realisation, halfway through reading, that the procedure on the shared drive doesn't say who is allowed to open the envelope, who decides whether the amount fits the earnings cap, and who speaks to the employee if the deduction will leave them short of rent. HR handles some garnishments. Payroll handles others. A colleague in finance once processed one without telling HR. Nobody has written down who, in the end, owns the consequence if any of it goes wrong.
That gap is the subject. Most content on garnishments treats the topic as a technical classification: what kind of order, what kind of priority, what kind of letter template. Useful, but secondary. The actual problem sits one layer up. It's the question of who accepts the obligation on behalf of the employer, who can be shown to have accepted it, and what happens to the employee, the third party, and the company when that acceptance is unclear.
But the technical layer is what gets taught, and the ownership layer is what gets discovered the first time an order is contested. This article is about the discovery.
Best tools for Payroll & Compensation
You Might Not Need to Read the Rest of This
Not every payroll team has a problem here. Some have already built the muscle. Reading the rest of this and acting on it without a real need is its own kind of waste, and the four stages below are designed to let you put the article down honestly when nothing applies.
Stage one, your current setup is genuinely fine. A payroll lead at a 400-person professional services firm has a single named owner for garnishments, an intake checklist that has been used against real orders in the past year, and a tested priority order for shortfalls. When the team processes an order, the checklist sits next to them, and the line manager never sees the reason for the deduction because nobody needs to ask. This setup isn't aspirational. It exists, and if it describes yours, you can stop reading. Revisit when the firm crosses a size threshold, enters a new jurisdiction, or loses the named owner.
Stage two, friction but no failure. A payroll lead at a 1,200-person retailer handles garnishments correctly, but the procedure lives in three documents, two of which disagree on priority order. Each order is processed correctly because the lead personally reconciles the documents. The day the lead is on leave and a colleague picks up an order, the documents will be read as written and the wrong priority may be applied. Nothing has gone wrong yet, which is exactly why the friction is hard to prioritise. The fix is a single source of truth. Until then, the team's correctness depends on one person.
Stage three, real risk. A payroll lead at a multi-site employer has processed orders for years without a written procedure at all. The team has built up habits that match what they remember from a training course. One order a year ago was held back from payroll by a week because nobody knew who had authority to confirm the deduction amount. The employee noticed. Nothing escalated, but the gap was real. This is the stage where the next unusual order, a contested amount, a complaint from a former employee, or a new jurisdiction will turn habit into liability. The procedure can't be written after the incident. It has to exist before.
Stage four, the edge case. A payroll lead at a group with operations in several states or countries has local procedures that work in each location but contradict each other across the group. An employee who transfers internally may carry an order across borders. The priority rules differ. The notification rules differ. The duty to tell the employee, and the duty not to tell the line manager, differ. The team has not encountered this yet because transfers have been rare. When one happens, the local habit will be applied to a foreign obligation, and one of the two procedures will be wrong. This is the stage where ownership of the cross-border piece needs to sit above the local teams and be written down before the first transfer happens.
Five Questions This Reader Asks at 11pm
Who actually owns garnishments in my organisation? You, in practice, because the letters arrive at payroll. But ownership in the sense the law cares about is whoever the employer has designated, by role or by procedure, to receive instructions on its behalf and act on them. If the procedure is silent, you own the consequence by default. That's not a safe place to be, and the only fix is a document.
What happens when earnings won't cover everything? A priority order applies, and the order in which deductions come off the pay run decides who gets paid and who waits. The priority order isn't a matter of preference. It's set by the interaction of statutes, court orders, and the terms of voluntary arrangements. Get it wrong and one party is underpaid while another is overpaid, and the employer has chosen, accidentally, who bears the loss.
Should the line manager be told? In most contexts, no. The manager's knowledge of the order isn't required for it to be processed, and disclosing the reason for a deduction to a third party inside the organisation can itself be a breach. Treat the reason as confidential between payroll, HR if HR has a defined role, and the parties named in the order.
What if an order looks wrong? You're entitled to ask the issuing party to confirm or correct it, and you should. Acting on a defective order is worse than pausing to clarify, provided the pause is short and documented. The instinct to process first and query later is the instinct that creates the contested-deduction file.
How long does this last? It lasts as long as the order says it lasts, plus any tail obligations for final payments when the employee leaves. The end isn't always announced, and the team that processes the final pay after a resignation is the team that decides whether a residual balance reaches the third party or stays in payroll. That decision is itself a deduction decision and it needs an owner.
The Three Honest Categories
Payroll owns it end to end. Payroll receives the order, interprets it, applies it, communicates with the employee, and answers queries from the third party. This is right when the volume is low, the orders are routine, and the payroll lead has the authority and the temperament to communicate directly with employees about sensitive matters. It fails when the volume rises past what one person can hold in their head, when orders become contested, or when payroll is asked to interpret something that's closer to a legal question than a payroll one. The single point of failure is the person.
HR or legal owns receipt, payroll owns mechanics. HR or legal receives the order, confirms it, writes the internal instruction, and passes it to payroll for execution. Payroll applies it on the next run and reports back. This is right when orders arrive with legal nuance, when the employee may need pastoral support, and when the volume justifies a clear division of labour. It fails when the handoff is informal, when instructions arrive late, or when the legal interpretation has to be revisited mid-run because something has changed. The single point of failure is the handoff itself.
A shared service centre owns intake under a published standard. A central team processes all garnishments for the group against a single procedure, with local teams feeding into it. This is right for multi-site or multi-jurisdiction employers where consistency matters more than speed. It fails when the centre is distant from the employee, when local law requires local handling, or when the standard isn't updated when the law changes. The single point of failure is the standard.
Five Diagnostic Questions You Can Answer Against Your Own Desk
Who signs the acknowledgement of receipt back to the issuing party? Open your last three orders and check whether the same role signed each acknowledgement. If different people signed, you don't have a single owner. The fix is to pick one and put it in the procedure.
Where is your priority order written down, and when was it last tested against a real shortfall? Find the document. If the document doesn't exist, you've a verbal priority order, which is the same as no order at the moment a shortfall happens. The test is simple: in the next quarter, run a hypothetical against a real pay run where two obligations compete, and write down what would happen.
What does your team do when an order arrives during a pay run that has already started? If the answer involves a phone call, you've a single point of failure on the phone. The fix is a standing instruction: late orders wait for the next run unless they're time-critical, and time-critical is defined in writing.
How does your team tell an employee about a deduction without telling the line manager? If the answer involves email, walk the path of the email and check who is cc'd, who is in the distribution list, and whether the manager's mailbox would see a reference to the order. If it would, the procedure is leaking.
When the employee leaves, who makes sure the final payment is processed against any outstanding order? If the answer is whoever happens to be running the leaver payroll that week, you don't have an owner for tail obligations. The fix is a leaver checklist that names the role and the steps.
Six Deduction Types, and What Each One Demands
Court-Ordered Garnishments
A court-ordered garnishment is an instruction from a court or a body acting with similar authority, telling the employer to withhold part of an employee's earnings and pay it to a third party named in the order. It earns a place on the list because it's the only deduction type where the employer is acting as a collection agent under someone else's authority, and the employer can be penalised for getting it wrong in ways that other deduction types don't expose.
The weakness is the gap between receipt and execution. The order arrives, the employer has a window to act, and within that window a series of small decisions are made about validity, amount, priority, communication, and timing. Each decision is defensible on its own. The cumulative record is what the court or the third party will look at if anything is contested, and that record is often patchy.
Statutory Deductions
A statutory deduction is one the employer is required by primary or secondary legislation to make, whether or not the employee agrees. It earns a place because it sits at the top of almost every priority order, which means it's the deduction that consumes earnings first when money is short and everything else has to give.
The weakness is that statutory deduction rules change more often than the procedure that handles them, and a procedure that was correct two years ago can quietly become wrong. The employer doesn't get a warning that the rule has moved, and the next short-pay period is the first time the gap shows.
Benefit and Pension Contributions
Benefit and pension contributions are deductions the employer has agreed, by contract or by enrolment, to withhold on behalf of a scheme and pay across. They earn a place because they look voluntary from the employee's side and statutory from the scheme's side, which puts the employer in the middle of two contracts at once.
The weakness is the silence between scheme rules and payroll rules. A scheme may allow an employee to opt out at any time. The payroll system may not reflect that opt-out for two cycles. In between, a deduction has been made that the employee no longer owes, and the refund process is where the procedure most often breaks.
Salary Sacrifice or Exchange Arrangements
A salary sacrifice or exchange arrangement is one where the employee agrees, in advance and in writing, to a lower cash salary in return for a non-cash benefit the employer provides. The deduction is the difference between the old salary and the new. It earns a place because it changes the basis on which almost every other deduction is calculated, including garnishments, which often apply to a defined portion of earnings.
The weakness is that most practitioners treat the sacrifice as a payroll quirk rather than as a deduction that interacts with every other deduction on the list. When an order arrives, the question of what counts as earnings, and whether the sacrificed portion is included, is the question that decides whether the right person gets paid.
Employer Loans and Advances
An employer loan or advance is money the employer has paid to the employee ahead of the normal pay date, with an agreement to recover it from later pay runs. It earns a place because it's the deduction type the employer has the most control over and the least external pressure to handle, which makes it the easiest to handle badly.
The weakness is recovery after the employee has left. If the loan was being recovered over twelve months and the employee resigns in month four, the remaining balance becomes a debt the employer may or may not be able to recover from the final payment, and the answer depends on what the original agreement said and what the local law allows.
Voluntary Deductions the Employee Can Stop
A voluntary deduction is one the employee has agreed to and can withdraw, such as a charitable giving arrangement or a union subscription. It earns a place because it sits at the bottom of the priority order and is the first to stop when earnings fall short, and the way it stops is often where the relationship with the employee is damaged.
The weakness is the assumption that voluntary means unimportant. A payroll team that quietly drops a voluntary deduction when money is short, without telling the employee, has made a decision on the employee's behalf and may have to unwind it later with interest.
The Decision Table
| Situation | Scale | Setup | Primary Pain | Recommended Starting Point |
|---|---|---|---|---|
| Single jurisdiction, low volume, one experienced payroll lead | Under 500 employees, one or two orders a year | Payroll owns it end to end, informally | The owner has not been named in writing | Write the procedure, name the owner, keep the model |
| Single jurisdiction, rising volume, several competing demands | 500 to 2,500 employees, growing order count | Payroll owns it, but other duties compete | Volume is exceeding one person's capacity to hold the detail | Move to HR-receipt, payroll-mechanics, with a written handoff |
| Multi-site, single jurisdiction, consistent order profile | 2,500+ employees, multiple sites | Local teams handle their own orders | Procedures drift apart across sites | Move to a shared service centre under a single published standard |
| Multi-jurisdiction, low cross-border movement | Any size, two or more jurisdictions | Each location handles its own | Cross-border transfer has not been planned for | Add a cross-border section to each local procedure before the first transfer |
| Multi-jurisdiction, frequent cross-border movement | Any size, regular internal transfers | Local teams handle their own | Different priority rules collide on transfer | Centre owns the cross-border piece, local teams own the local mechanics |
| Contested orders arriving regularly | Any size | Current owner handles each on its merits | The interpretation work is consuming the payroll function | Bring legal into intake, with payroll executing on legal's instruction |
| Statutory rules changing faster than procedure updates | Any size, regulated sector | Procedure reviewed annually | Reviews are missing mid-year rule changes | Add a quarterly review trigger tied to the regulator's publication schedule |
| Leaver process with outstanding orders | Any size, moderate turnover | Leaver payroll handled by whoever is on shift | Tail obligations are processed inconsistently | Add a named leaver checklist that includes a residual-order step |
Building the Order of Operations
When earnings won't cover every deduction on the run, a priority order decides who waits. The order isn't optional. It's determined by the interaction of statutes, court orders, the terms of any voluntary arrangement, and the contractual position between employer and employee. Payroll teams don't get to choose the priority. They get to apply it, in writing, every time.
The first practical question is which obligation has the strongest external authority. A statutory deduction usually sits above a contractual one. A court order, where it conflicts with a voluntary arrangement, usually sits above the arrangement, but the detail depends on jurisdiction and on what the order says about its own priority. The second question is whether the obligation has a stated cap, and whether the cap is on the deduction or on the resulting pay. Where a protected-earnings floor exists, the protected portion comes off the calculation before any priority is applied, and the rest is divided in the order set by the rules. The third question is what the employer has agreed in the employee's contract, because contractual deductions can sit above voluntary ones but below statutory ones, and the order between contractual and voluntary is set by the contract and the consent.
A priority order should be written down even when the team is confident they know it. The reason isn't that the team is wrong. The reason is that the next contested shortfall will be argued by reference to what the team did, and the argument is much harder to lose when the team can show the rule they applied and the moment they applied it.
| Step | Action | Who decides | What to record |
|---|---|---|---|
| 1 | Identify every deduction competing for the same earnings | Payroll | A line per deduction in the run, with the source |
| 2 | Apply any protected-earnings floor | Payroll, against the written rule | The floor figure and the source rule |
| 3 | Apply the priority order | Payroll, against the written rule | The order applied and the date of the rule |
| 4 | Calculate the short-pay, if any | Payroll | The amount and the party affected |
| 5 | Communicate the short-pay to the affected parties | HR or the named owner | The communication, the time, and the channel |
| 6 | Carry the residual to the next run, in the same priority | Payroll | The carried amount and the originating obligation |
The temptation, when a shortfall happens for the first time, is to ask the employee to choose who gets paid. Don't do this. The employer holds the obligation, not the employee. The decision is the employer's, made against the written rule, and recorded.
Handling It With the Employee
The first conversation about a garnishment is often the most difficult conversation the payroll team will have with that employee, because the deduction isn't something the employee agreed to and may not have wanted disclosed. The payroll team's job in that conversation is narrow. Confirm the deduction. Confirm the amount. Confirm the source. Don't interpret the underlying order. Don't offer a view on whether the order is fair. Don't suggest a course of action. Those conversations belong to a different role, and the payroll team's job is to make the handoff visible to the employee without making it their problem.
The line manager is the most common accidental disclosure. A payslip that references the order, a salary discussion in which the manager notices the deduction and asks why, a manager who is copied on a query by mistake. Each of these is a breach of confidentiality in the sense the law cares about, even when the breach is small. The fix is a written rule: the line manager isn't informed, the payslip shows the deduction in neutral terms, and any internal communication about the order is restricted by role. The rule is only useful if it's followed, and it's only followed if it's short enough to be remembered.
| Communication | Who sends it | What it says | What it does not say |
|---|---|---|---|
| First notification to the employee | Payroll, or HR if HR is the named owner | That a deduction will start, on what date, in what amount, and against what authority | Anything about the underlying claim, the third party, or the employee's options |
| Payslip description | Payroll system | A neutral label consistent across runs | The name of the third party or the type of order |
| Query response | The named owner | The amount, the date, the source, and a contact for the third party | An opinion on the order |
| Leaver notification | Payroll | What will happen to any residual deduction from the final pay | Anything about the employee's next role or the next employer |
| Internal reference | Restricted by role | That a deduction is being processed for an employee | The amount, the source, or the reason |
What to Put in Writing
The artefacts below are the difference between a defensible decision and a contested one. None of them are difficult to produce. All of them are skipped in a surprising number of organisations, and the gap shows up the first time anything is challenged.
| Artefact | Who owns it | When it is written | What it prevents |
|---|---|---|---|
| Named owner for garnishments and deductions | Head of payroll or HR director | At procedure adoption and on every role change | The "we thought payroll handled it" gap |
| Priority order for shortfalls | Head of payroll, reviewed by legal | At procedure adoption and on every rule change | The "we paid the wrong party first" challenge |
| Intake checklist for new orders | The named owner | At procedure adoption, used on every order | The missed step on a complex order |
| Confidentiality rule, written and short | Head of payroll or HR director | At procedure adoption | The accidental disclosure to a line manager |
| Leaver checklist, including residual orders | The named owner | At procedure adoption, used on every leaver | The unpaid residual at final pay |
| Acknowledgement template for receipt of orders | The named owner | At procedure adoption | The unsigned instruction |
| Communication template for first notification to the employee | The named owner, with HR input | At procedure adoption | The inconsistent first conversation |
| Annual review record of the procedure | Head of payroll | Once a year, dated and signed | The "we have always done it this way" defence |
| Record of training given to the named owner and any deputies | Head of payroll | On appointment and on every procedure change | The "nobody told me" defence |
| Log of contested orders and how they were resolved | The named owner | On every contested order | The pattern that a regulator or auditor will otherwise build themselves |
The list is longer than most teams expect, and the cost of producing it's lower than most teams expect. The cost of not producing it's paid later, in the form of a defence that has to be built after the fact.
Questions to Ask Before You Commit
Ownership. Ask the team or the provider who is named, in writing, as the owner of garnishments processing on the day an order arrives. A bad answer sounds like "we all look after it" or "it depends". A good answer names a role, names a deputy, and points to the document.
Priority. Ask for the priority order in writing, and ask when it was last tested against an actual shortfall or a realistic scenario. A bad answer describes the order in conversation but can't produce the document. A good answer produces the document and the test record.
Confidentiality. Ask how the procedure prevents an accidental disclosure to the line manager. A bad answer relies on people being careful. A good answer restricts the channel, restricts the distribution list, and labels the payslip in neutral terms.
Leavers. Ask what happens to a residual order when the employee resigns. A bad answer says the final pay is processed normally. A good answer names the step, names the role, and produces the checklist.
Contested orders. Ask what the procedure is when an order arrives that looks wrong. A bad answer is "we process it and query later". A good answer sets a short window for clarification, names the role who can pause the run, and records the decision.
Training. Ask when the named owner and any deputies were last trained on the procedure. A bad answer is a date that's more than a year old or no date at all. A good answer is a recent date, a training record, and a refresher scheduled.
Cross-border. Ask, if you operate in more than one jurisdiction, who owns the cross-border piece and where it's written down. A bad answer is that local teams handle it. A good answer names a role above the local teams and produces the cross-border section of the procedure.
Audit trail. Ask for the last three orders and the complete record for each, from receipt to final payment. A bad answer produces the orders and a gap in the middle. A good answer produces a complete file for each, dated and signed.
Rule changes. Ask how the procedure is updated when a statutory rule changes. A bad answer is "we review annually". A good answer ties the review to the regulator's publication cycle, names the role responsible, and produces the last update record.
Records retention. Ask how long the records are kept, where they're kept, and who can access them. A bad answer is "as long as payroll needs them". A good answer names a retention period, a storage location, and an access control.
The Cost of Getting This Wrong
The first cost is the employee. A deduction processed in the wrong amount, against the wrong priority, or without the right communication leaves a person short of money they were counting on, and the person least able to absorb the consequence is the one the deduction was applied to. That cost doesn't appear on an invoice. It appears in a complaint, a resignation, a dispute with the third party, or a quiet loss of trust that the employer doesn't notice until it's too late to repair.
The second cost is the employer. A court or a regulator that finds the employer has failed to apply a valid order, or has applied an invalid one, or has disclosed the order to a third party inside the organisation, can require correction, can levy a penalty, and can require the employer to pay the costs of the other side. None of these are theoretical. They're the ordinary outcomes of contested garnishments that aren't handled correctly, and they land on the employer rather than on the payroll lead personally, which is why the organisation has an interest in making sure the procedure is owned even when the person doing the work is competent.
So the question that reframes the decision isn't "how do we process garnishments correctly". It's "who in this organisation is on the hook when we don't, and is that person set up to do the job". If the answer to the second half is no, the procedure is the cheapest fix available.
When You Are Ready to Go Further
If the diagnostic above has surfaced gaps and you want to see how other organisations have closed them, HROpsLab's independent comparison work covers the providers and advisers that operate in this space. We are a review publication, not a vendor, and we sell nothing. Our comparisons are built around the questions a payroll lead should be asking before they sign, and our case studies are written with the teams who have lived through the migration.
If you would like to talk through a specific situation with someone who has seen the problem before, we can put you in touch with a practitioner who works on garnishments and deductions full time. The conversation is independent of any provider, and it's confidential.
Frequently Asked Questions
Who owns garnishment processing in a typical organisation?
The named owner should be one role, with a named deputy, and the procedure should say so. In practice, the owner varies by organisation: payroll owns it end to end in some, HR or legal owns the receipt and payroll owns the mechanics in others, and a shared service centre handles intake under a published standard in larger or multi-site employers. The model matters less than the documentation. Whoever is named must be reachable during a dispute and must have been trained on the procedure within the last year.
What happens when earnings will not cover every deduction?
A written priority order applies, set by the interaction of statutes, court orders, contractual terms, and voluntary arrangements. The employer applies the order, deducts in sequence, communicates the short-pay to the affected parties, and carries the residual to the next run in the same priority. The decision is the employer's, made against the written rule, and recorded. The employee isn't asked to choose who gets paid.
Should the employee's line manager be told about the garnishment?
In most contexts, no. The manager's knowledge isn't required for the deduction to be processed, and disclosure of the reason to a third party inside the organisation can itself be a breach of confidentiality. Treat the reason as a matter between payroll, HR if HR has a defined role, and the parties named in the order. The procedure should restrict the channel and the distribution list so that the rule is followed without relying on people being careful.
What should we do if a court order looks wrong?
You're entitled to ask the issuing party to confirm or correct it, and you should. Acting on a defective order is worse than pausing to clarify, provided the pause is short and documented. The named owner should be the role that decides to pause, the pause should be recorded with the reason and the time, and the clarification should be in writing. The instinct to process first and query later is the instinct that creates the contested-deduction file.
Can the employer charge a fee for processing a garnishment?
This is jurisdiction-specific and the answer depends on what the local rules permit and what the order itself says. Some jurisdictions allow a fixed administrative fee, some prohibit any charge, and some are silent. The employer should check the rule locally, check what the order says, and apply the answer in writing. Don't assume silence means permission, and don't assume silence means prohibition.
How long does a garnishment order last?
It lasts as long as the order says it lasts, which may be until a stated amount has been recovered, until a stated end date, or until further notice. The employer should not assume the order has ended without confirmation from the issuing party, and should keep a flag on the employee record until the order is explicitly closed. Tail obligations may apply when the employee leaves, and the leaver process is where many orders are finally closed without the closure being recorded.
What do we do when an employee leaves with an outstanding garnishment?
The leaver checklist should include a step that names the residual obligation, calculates the amount that can be deducted from the final pay within the local rules, processes that deduction, and pays the residual to the third party in the manner the order specifies. Any balance that can't be deducted from the final pay should be reported back to the issuing party, in writing, with the amount and the reason. The role that handles leavers should be named, and the step should be on the checklist, not in someone's head.
The payroll team that handles this well is the team whose ownership is visible on paper before anything goes wrong, and whose procedure holds when the named owner is on leave. That's the standard the rest of this article is built around.
Start for free with HROpsLab and see how your garnishments and deductions process compares to the standard.
