Garnishments Are a Liability, Not an HR Task
The amount comes out of the employee's pay on time. Whether it reaches the right agency, in the right period, and clears the liability account is a separate question nobody owns.
A wage garnishment is an amount withheld from an employee's pay under a legal order and owed to a third party such as a court, agency or creditor. Between withholding and remittance it is a liability of the employer. The account should clear each cycle, and where it does not the cause is usually a remittance made in a different period, an order that ended without the deduction stopping, or a payment made outside the payroll process.
- The money is withheld from the employee and owed to a third party. Until it is remitted it is an employer liability with legal consequences attached.
- The liability account should clear every cycle. A persistent balance means withholding and remittance have separated.
- Orders end, are amended and are superseded, and a deduction that continues after an order ends is money taken from an employee without authority.
- Priority and limit rules mean the amount withheld can legitimately differ from the amount ordered, which the reconciliation must accommodate rather than flag.
- ChatFin reconciles deductions to remittances by order and employee, ages what has not cleared, and prepares the correcting entries.
Garnishment processing sits in an awkward place. It arrives as a legal document, is handled operationally by payroll, and creates an accounting liability that finance owns without seeing the underlying orders.
The withholding side generally works. Payroll systems handle the deduction accurately once the order is set up, and employees notice immediately if it does not. The remittance side is where problems accumulate: the payment to the agency is made on a different cycle, sometimes manually, sometimes by a service, and the reconciliation between what was withheld and what was paid over is frequently nobody's assigned task.
This page covers what the liability account should look like, the three reasons it stops clearing, how priority and limit rules complicate the comparison, and how to reconcile without needing access to the orders themselves.
What the account should look like
A garnishment liability account is a clearing account with a legal dimension. Amounts enter when withheld from pay and leave when remitted to the recipient, and in a well run process the balance at any point represents only amounts withheld but not yet due for remittance.
| Entry | One credit per employee per order per pay period, matching the deduction on the register |
| Exit | One debit per remittance, ideally traceable to the specific orders it covers |
| Expected balance | Only amounts withheld since the last remittance date, which should be predictable |
| Ageing | Any amount older than one remittance cycle, which is the exception population |
| Reconciling detail | By employee and by order, since a net balance across employees conceals offsetting errors |
The last row is the discipline that makes the rest work. Reconciling the account in total will show a small balance and hide an employee whose deduction has been withheld for a year without being remitted, which is the outcome with the most serious consequences.
Why the account stops clearing
Three causes account for nearly all persistent balances, and they have different consequences.
Timing
Withholding and remittance cycles differ, so a balance at period end is expected. Legitimate, but it must be quantifiable rather than assumed.
Order ended, deduction continued
The order was satisfied or released and the deduction was not stopped. This is money taken from an employee without current authority and requires refund, not just correction.
Remittance outside payroll
A payment made directly by accounts payable rather than through the payroll remittance process, so the liability is cleared by an entry the payroll records know nothing about.
Cause two is the most serious and the least likely to be discovered by a finance reconciliation, because the amounts continue to match between the register and the liability account. It is found by comparing active deductions against active orders, which is a different test entirely.
Priority and limit rules complicate the comparison
The amount withheld is not always the amount ordered, and a reconciliation that treats any difference as an error will produce noise that causes the whole exercise to be abandoned.
The reconciliation therefore compares withheld to remitted rather than ordered to remitted. Whether the correct amount was withheld is a payroll compliance question handled by the payroll system's own rules engine, and conflating the two makes both harder.
What the payroll platforms handle
Payroll platforms handle garnishment calculation well. ADP, UKG, Paylocity and Workday all apply priority and limit rules, calculate the permissible deduction and produce the deduction detail, and several offer garnishment remittance as a service that handles payment to the recipient directly.
Where a remittance service is used, the reconciliation is usually straightforward because withholding and remittance are handled by the same party. Where remittance is handled internally, or partially internally, the gap opens: payroll knows what was withheld, accounts payable knows what was paid, and nobody holds both views at order level.
Bringing deduction detail, remittance evidence and the liability account together at order level is cross system reconciliation, which is what ChatFin performs across ChatFin use cases.
The two tests that matter
This reconciliation has an unusual property: the routine test and the serious test are different, and only the routine one is usually performed.
| Test one, financial | Withheld equals remitted by employee and order, with any balance explained by remittance timing |
| Test two, authority | Every active deduction corresponds to a current order, and every current order has an active deduction |
| Cadence | Test one every pay cycle, test two at least quarterly and on every order status change |
| Escalation | Any amount withheld and not remitted beyond one cycle, and any deduction without a matching current order |
| Refund process | A defined route for returning amounts withheld without authority, which needs to exist before it is needed |
Test two is the one with legal and employee relations consequences, and it is the one that no financial reconciliation will ever surface, because a deduction against an ended order looks entirely correct in the ledger.
How ChatFin reconciles the two sides
ChatFin reads the payroll register and the remittance evidence, including agency confirmations, remittance advice and payment records, and reconciles them at employee and order level rather than in total.
The autonomous reconciliation agent matches withheld amounts to remittances and ages anything that has not cleared within an expected cycle. The pattern recognition agent identifies deductions continuing at a steady amount over an extended period without variation, which is the signature of an order that may have been satisfied, and flags remittances made outside the payroll process that cleared the liability without a corresponding deduction record.
| Document processing | Reads payroll registers, remittance advice and agency confirmations in their native formats |
| Reconciliation agent | Matches withheld to remitted at employee and order level and ages unmatched amounts |
| Pattern recognition | Flags long running unchanged deductions and remittances made outside the payroll process |
| Data query agent | Answers questions such as which deductions have been withheld and not remitted for more than one cycle |
| Governed write back | Prepares clearing and correcting entries, including refund entries, for a person to approve |
Refund entries in particular are prepared rather than posted, because returning an amount to an employee requires a decision and a communication rather than an accounting action alone.
Reconciling this properly once
The first pass should cover both tests, because doing only the financial one gives false comfort.
Reconcile at employee and order level
For a recent quarter, match every deduction to a remittance. Do not net across employees.
Age the unmatched
Anything outstanding beyond one remittance cycle is the exception population and needs an explanation per item.
Compare active deductions to current orders
This is the authority test. Any deduction without a current order is an immediate issue requiring refund and correction.
Identify remittances made outside payroll
Payments to garnishment recipients through accounts payable, which clear the liability without a matching deduction record.
Step three is the one worth doing first if time is short. A financial difference is a correction, whereas a deduction taken without current authority is an obligation to the employee that grows every pay period it continues.
A deduction against an order that ended looks entirely correct in the ledger. No financial reconciliation will ever find it.
ChatFin
Frequently Asked Questions
Why does the garnishment liability account not clear?
Three causes. Legitimate timing, where the withholding and remittance cycles differ so a predictable balance exists at period end. An order that ended without the deduction being stopped, which means amounts are still being withheld from an employee without current authority. Or a remittance made outside the payroll process, typically through accounts payable, which clears the liability with an entry the payroll records know nothing about.
Should the garnishment reconciliation compare withheld to ordered?
No, it should compare withheld to remitted. The amount withheld legitimately differs from the ordered amount because of disposable earnings limits, priority rules between multiple orders, arrears carried forward from earlier periods and any permitted employer fee. Whether the correct amount was withheld is a payroll compliance question handled by the payroll system's rules, and conflating the two makes the reconciliation produce noise.
How do you find deductions continuing after an order ended?
By comparing active deductions against current orders rather than by reconciling the liability account, because a deduction against an ended order looks financially correct in the ledger. A useful indicator is a deduction running at an unchanged amount over an extended period without variation, which can suggest an order that has been satisfied. This test should run at least quarterly and on every order status change.
Can ChatFin reconcile garnishments without access to court orders?
Yes. ChatFin reconciles the payroll register against remittance evidence at employee and order level, ages anything that has not cleared, and flags remittances made outside the payroll process. It also identifies long running unchanged deductions as candidates for an order that may have ended. Where order documents are available it can read them, but the financial reconciliation works from payroll and remittance records alone.
This article is general information for finance and accounting teams. It is not accounting, tax or legal advice. Confirm the treatment of your own facts with your auditors and advisers.
See ChatFin match withheld amounts to remittances at order level.
ChatFin reads your payroll register and remittance evidence, matches deductions to remittances by employee and order, and ages anything that has not cleared within a cycle.
Long running unchanged deductions are flagged as possible ended orders, and every clearing, correcting or refund entry is prepared for a person to approve.
Book a DemoBring a quarter of registers and remittance records.
ChatFin will reconcile at employee and order level, age what has not cleared, and flag deductions that may relate to orders no longer in force.