QuickBooks Online Payroll Garnishment Evidence Log

August 23, 2026

Bottom line: every payroll garnishment should be supported by the withholding order, a documented calculation, the payroll entry that shows the deduction, and a timely disbursement record, with any missing or changed item held as a visible exception.

Sidebar: Garnishments carry legal risk. The log separates evidence preparation from approval decisions.

Why garnishments need their own evidence lane

Payroll garnishments involve a legal order, a calculation, and a payment that the business must get right every time. The order dictates who must withhold, from which earnings, in what amount or formula, and with what priority. QuickBooks Online and the payroll provider handle the mechanics once the setup is correct, but the setup itself depends on a careful reading of the order and the right mapping of earnings, deductions, and payee. A small error such as basing withholding on gross pay when the order specifies disposable earnings, or failing to update a new limit after an amendment, can produce a sustained under or over withholding that is painful to correct.

For QBOAssistant clients, the VA often handles payroll preparation support: gathering payroll inputs, organizing deduction change notes, collecting garnishment orders as they arrive, and linking the withheld amount on the payroll register to the disbursement that follows. The assistant does not interpret the legal order, modify a withholding formula, or decide which garnishment takes priority. An evidence log preserves that boundary by keeping order, calculation, payroll entry, and disbursement visible together until the reviewer approves.

Without a dedicated garnishment lane, payroll support can treat a garnishment as just another deduction line. The deduction amount appears correct for one pay period, but no file proves why it changed the next period, whether an amended order arrived, or whether the disbursement to the agency actually cleared.

Define the population

Start by naming which garnishments and which employees the log covers. In QuickBooks Online and connected payroll workflows this typically includes active deduction setups flagged for garnishment, outstanding withholding orders on file, and employees with a garnishment code on their deductions. Exclude ordinary benefit deductions from this packet. They are reviewed elsewhere, even though they share the same payroll journal.

Save the population before updating calculations. Record the cutoff, the garnishment cases in scope, the employee references using a limited identifier appropriate for the working file, preparer, and reviewer. If the business uses a third party administrator for some garnishments, state which cases are administered externally and where that external confirmation is stored.

Group the log by garnishment case and then by payroll period. The useful structure shows one garnishment order with the affected employee or participant, the withholding formula, the limit, and each payroll run that applied the order. If an employee has two active garnishments, keep cases separate rather than merging them, because priority matters and each order has its own payee and verification requirement.

State exclusions. For example, tax levies handled through a different notice flow or internal loan withholdings that look similar but do not carry a court or agency order should be handled in their own lane. A clear scope note prevents a mix of legally required withholdings and voluntary deductions in the same evidence set.

Assemble the evidence for each garnishment and period

For each active garnishment case, capture the standing evidence once, then capture per period evidence for each payroll run. Standing evidence starts with the order itself: issuing agency or court, case or order reference, issue date, effective date, amount or formula, earnings base to which the formula applies, limit or cap, priority, payee name and remittance address or electronic payment setup, and the location of the controlled copy. Link the document location where the order is stored under restricted access. Do not paste full account numbers or sensitive personal data broadly into the working file when a controlled reference suffices.

Add order history. Record the last order received, any amendment, any release or satisfaction, and the communication that confirms the current status. If an amended order reduced the monthly withholding, link that amendment alongside the original so the reviewer does not hunt.

Per period evidence starts with the payroll register view: pay period dates, gross wages, the earnings components that contribute to the garnishment base, any excluded earnings or mandatory deductions that affect the base, the calculated withholding, the amount shown as deducted on the paycheck, and the net payment to the employee after other priorities.

Add the calculation trace. Show how the garnishment amount for the period was derived from the formula using the earnings base for that period. A reader who was not the preparer should be able to follow the math from earnings to withholding for that pay date without opening a separate calculator file. That trace is the core of the review.

Add the QuickBooks payroll entry evidence: payroll journal or paycheck detail that shows the deduction account credited, the withheld amount, and any fee the payroll service charged for processing. Add the disbursement proof for the withheld amount: the bill generated for the agency, the check or electronic payment confirmation, payment date, and amount.

Check three elements for every payroll period. First, the stated withholding formula should match the current order on file, not an outdated one. Second, the withheld amount on the payroll record should match the calculated amount unless the limit or priority produced a lower allowed withholding, which should be documented as limit applied. Third, the disbursement that follows the payroll should match the withheld amount and should be traceable to the correct payee and due timeframe, with no commingling.

Flag the exceptions that commonly appear

Order on file expired or superseded is the most significant exception. A new order arrives changing the monthly cap, but payroll still reflects the old formula because the setup was not updated. Flag the case as order updated pending setup. Record the new order reference, effective date, and what the next payroll should reflect.

Calculation base mismatch is a second pattern. The business deducted based on gross wages while the order requires disposable earnings after specific mandatory deductions. Flag the period as base question. Preserve both calculations briefly in notes: one using gross and one using the stated disposable earnings definition, with source lines for each mandatory deduction.

Limit or priority not applied is a third pattern. The employee has two garnishments and the formula caps total withholding, but the register shows both deducted at full amounts. Flag the case as priority review. Record the two garnishments, their stated priority, the cap, and the calculated split the reviewer should approve.

Disbursement delayed or misdirected is an operational exception. The withholding was correct but the payment to the agency was delayed beyond the required window or sent to the prior payee after an address change. Flag the disbursement as timing or payee exception. Link the intended payee instruction, the payment confirmation, and the amount. Do not correct the payee by reissuing without documented approval.

Employee no longer eligible is a status exception. The employee was terminated, placed on extended leave, or switched to a pay group where no disposable earnings exist for the period. Flag the case as zero earnings available. Record the employment status source and the reviewer's instruction on whether the garnishment should pause, remain open with zero withholding for the period, or be reported as not collected with reason.

Setup not yet mirrored in QuickBooks Online is a common bookkeeping gap. The garnishment is correctly reflected in the payroll provider's dedicated screen but QuickBooks Online payroll import does not yet show the deduction account clearly. Flag the entry as mapping pending. Link the provider report that shows the withheld amount and ask the reviewer to confirm the GL mapping.

Build a packet the reviewer can actually approve

A useful packet fits on one file with restricted distribution and clear ownership. Start with a cover sheet that names the business, period, garnishments in scope, preparer, reviewer, total withheld for the period, total disbursed to agencies, and any withheld amount still awaiting disbursement. Show the mirror check on the cover: withholdings equal disbursements pending timing, or a disclosed amount remains in transit with an owner.

Follow with the case detail, one section per garnishment. Each section repeats the standing order summary, order history, and the period calculation with evidence links.

Add the exception table for that period. Useful columns include garnishment reference, employee reference, pay period, calculated amount, amount deducted on payroll, limit or priority effect, disbursement status, evidence locations, and exception type. Each row carries an impact note that is honest and brief: withheld correctly but agency payment pending, amount changed under amended order but setup still reflects prior formula, or base differs from order so correct amount is still in question.

Include a disbursement summary that lists the agency payee, case reference, amount collected from payroll, amount sent, disbursement date, confirmation ID, and status such as sent, in transit, or failed. That summary helps the reviewer see quickly whether withheld funds actually moved to the right agency.

Use simple statuses such as deducted and disbursed, deducted pending disbursement, calculation pending order confirmation, base pending clarification, limit applied, zero earnings no withholding, or setup mapping pending. Close an exception only when the order on file matches the payroll setup, the calculation ties to the posted deduction, and the agency disbursement is confirmed or has a documented owner and timing.

Cadence, access, and quality expectations

Run this log every payroll cycle for any client with active garnishments. The VA refreshes the calculation after payroll is processed, links the register and disbursement proof, drafts specific questions for any exception, and routes the packet on the same day rather than waiting for month end. For clients with no active garnishments, a quarterly confirmation that no new orders have been received is enough, with immediate activation whenever an order arrives.

Access control matters. Garnishment orders contain sensitive personal and legal information. Store the controlled order copies in a restricted location, reference them from the working file by ID and date, and avoid copying full personal identifiers into the review table when an internal case reference is sufficient.

Archive the packet with the order copies, calculation traces, payroll register extracts for the period, and disbursement confirmations so a later auditor or agency inquiry can be answered from one place.

A reviewer should be able to answer five questions after reading the packet: which garnishments are active, what each order requires this pay period, how much was withheld and why that amount is correct, how much was sent to the agency and when, and what exceptions remain with who owning them.

Helpful quality checks include asking whether each garnishment reflects the latest order, whether each calculation uses the correct earnings base, whether any limit or priority was missed, whether withholdings equal disbursements after timing, and whether any deduction was posted or withheld without documented order support.

The payroll support VA service describes preparation boundaries for payroll work. For period close alignment, pair this lane with the QuickBooks month-end close packet.

What good looks like

Good looks like garnishments that withhold exactly what the order requires, show their math transparently, post correctly in payroll, and disburse on time to the right agency. Questions are specific and early. Zero surprises appear after the fact. And the VA never has to interpret order language to decide the amount.

Next step

Pilot the log on one payroll cycle for each active garnishment. Build the standing order summary, lay out the per period calculation, link payroll and disbursement evidence, and draft one concise question per exception that would let the reviewer decide without rework. Review the packet for readability. Keep fields that made the withholding and payment verifiable, remove fields that added noise, and reuse the approved packet on every payroll cycle that carries a garnishment. That disciplined loop makes garnishment handling reviewable without changing approval authority for payroll in QuickBooks Online.