Outsource Payroll CompanyPowered by StealthAgents
Table of contents
  1. Research finding
  2. Methodology
  3. Key takeaways
  4. Question and scope
  5. Population and unit
  6. Intake record
  7. Order validation
  8. Employee matching
  9. Protected wage floor
  10. Priority order
  11. Fixed and percentage claims
  12. Multiple orders
  13. Employee notice
  14. Remittance matching
  15. Case closure
  16. Access and confidentiality
  17. Provider handoff
  18. Retroactive correction
  19. Small-team exceptions
  20. Sampling
  21. Findings and severity
  22. Limitations
  23. Conclusion
  24. Sources
  25. Prepare a garnishment evidence pack
  26. FAQs
  27. Related research

Research brief · Published

Garnishment intake and withholding evidence review

A review design for testing whether withholding orders are logged on receipt, verified against the employee record, calculated under the protected floor, and remitted with a closed case file.

Research finding

Build the population from orders received, not from deductions that appear on a register.

FiveHeadline measureSee numbered sources below.

Methodology

This brief triangulates the headline measure against official Philippine government, regulatory, development, and labor sources. It translates evidence into an operating control and separates context from recommendations.

Key stats and interpretation
MeasureInterpretation
Five evidence points checked per withholding case.Context signal for planning, not a promise about an individual worker or provider.
4 source recordsPrimary source links are listed and numbered below for review.

Key takeaways

  • Build the population from orders received, not from deductions that appear on a register.
  • Test the intake date against the payroll cutoff and the first withholding.
  • Verify the employee match and the protected floor before judging the amount.
  • Match each remittance to the case number, period, and issuer.
  • Classify findings by whether an employee was over-withheld or a payment was missed.

Question and scope

This review asks whether each withholding order was logged on receipt, verified against the employee record, calculated within the applicable limit, and remitted with evidence. The scope covers garnishments, child support orders, levies, and similar legal deductions for the review period. The unit is one order and one employee, followed from intake to closure. The design tests process evidence rather than the legal validity of the order. Record the jurisdictions and the case sources included; keep the case list and the document index in one workbook so the count can be rebuilt.

Population and unit

Build the population from the order intake log, legal correspondence, provider deduction reports, and remittance records. Include orders that were received but never withheld, and orders that closed during the period. The unit is one order tied to one employee and one case number. A population built only from active deductions will miss an order that was lost before payroll saw it. List the source and extraction date for each case; mark any order that lacks a source document before the sample is drawn.

Intake record

Check that a dated intake record exists for every order and that it names the issuer, case number, employee, amount or percentage, and effective date. Confirm where the original document is stored and who received it. A record created after the payroll cutoff loses the timing evidence. Compare the intake date with the date the order arrived in the mail or the legal inbox. An intake record without a time of receipt cannot show whether the cutoff was met.

Order validation

Confirm that someone reviewed the order for the issuing body, the signature, the case number, and the stated amount. Check whether a questionable document was sent to legal counsel before any withholding. Payroll should not decide authenticity alone. Record the reviewer, the advice received, and the date the decision was made. A verbal legal opinion should be confirmed in writing before withholding begins.

Employee matching

Test how the order was matched to the payroll record, including the name, address, and identifying information. Confirm that an ambiguous match was resolved with the employee or the issuer before withholding. A partial name match can attach an order to the wrong person. Record the evidence used for the match and the person who approved it. A match that relies on a nickname alone is not enough to attach a court order.

Protected wage floor

Recalculate the amount the employee must retain under the applicable federal and state rule. Use the current gross pay and the work location, not a prior period or a company-wide formula. Compare the hand calculation with the system result and record the rule source and date. A correct percentage applied to the wrong base can still breach the floor. Use the same pay figure that the live run will use, including overtime and bonuses.

Priority order

Document the order the payroll system applies when tax withholding, a legal order, a benefit premium, and a voluntary deduction compete for the same check. Compare the configured order with the applicable rule and the employer's written policy. Test a case with two orders and one voluntary item. A correct total with the wrong allocation can still violate a priority rule. Record the priority rule source and the date it was confirmed.

Fixed and percentage claims

Test a fixed amount that exceeds the available protected pay and a percentage claim applied to a check with overtime or a bonus. Confirm whether the system caps, skips, or carries the amount, and whether the employee notice explains the treatment. Check the base used for a percentage order. A rate that is correct on a plain salary period can fail on a premium week. A skipped fixed amount needs a carry-forward balance and an owner.

Multiple orders

Review employees with more than one active order and confirm that each new order triggered a recalculation of the full stack. Check the effective date and whether a backdated order required a correction in a closed period. Test one case where the combined claims exceed the available pay. Record how the shortfall was allocated and who approved it. An allocation that no one approved is an exception even when the total is right.

Employee notice

Confirm that the employee received the required notice with the case number, amount, effective date, and contact for questions. Compare the notice date with the first affected pay date. Check that the notice matches the amount that was actually withheld. A notice sent after the deduction creates a dispute that is harder to resolve. Keep a copy of the notice with the first affected pay stub.

Remittance matching

Match each remittance to the case number, employee, pay period, and amount withheld. Confirm the payment method and the deadline for the issuer. Check that a payment posted to the correct case rather than a similar one. Investigate any difference before the next withholding cycle. A remittance that posts to a similar case is still an open item until the match is confirmed.

Case closure

Confirm that a case closes only after the final remittance posts and the issuer confirms the balance. Check that the employee is told withholding has ended and that the next pay stub reflects the change. A case with no end date can continue after the obligation is satisfied. Record the confirmation and the closure date in the file. A closure with no issuer confirmation is a status change, not a closed case.

Access and confidentiality

Review who can see the order documents, the calculation worksheet, and the remittance record. Confirm that access is limited to payroll, legal, and the named owner, and removed when the case closes. Check that the documents are stored outside a general payroll inbox. A sensitive order copied to a wide distribution list is a confidentiality finding. A shared drive with open access is not a confidential case file.

Provider handoff

When a provider calculates or remits the withholding, confirm that the employer approved the order and the calculation before the first deduction. Compare the provider's effective date with the employer's intake date. Ask how the provider prevents a second order from bypassing the recalculated floor. Record any case where the provider acted before approval. A provider that acts before employer approval is a finding even when correct.

Retroactive correction

Test what happens when the review finds an earlier over-withholding or a missed deduction. Identify who calculates the correction, who approves it, and how it is separated from the current run. Confirm that the correction uses the same evidence and authority as the original. Record the correction period, the employee notice, and the approver. A correction that skips review creates a second uncontrolled event.

Small-team exceptions

A small payroll team may not have a separate reviewer for every calculation. Record the exception and the compensating check, such as an owner review before the first withholding. The check should leave evidence that it happened before the deduction. A second signature from the same person is not independent review. Name the compensating reviewer and the date the check was completed.

Sampling

Sample cases across issuers, order types, pay periods, and work locations, including one closed case and one order received near a cutoff. Compare the sample with the full intake population to see what was missed. Record the selection rule so another reviewer can repeat the work. Include a case with more than one active order. Include a case that was received but never withheld if one exists.

Findings and severity

Classify each gap by whether an employee was over-withheld, a remittance was late, or an order was never applied. A missed withholding that exposes the employee to collection is more severe than a missing acknowledgment. Tie each finding to a case number, a pay period, and a named owner who accepted the correction. Rank the exposure by whether the employee faces collection action.

Limitations

The review depends on court and agency documents whose timing may be recorded outside the payroll system. A provider may not expose its calculation detail, and an employee may not report a wrong deduction. The design cannot decide the legal validity of an order. State these limits and separate observed gaps from missing evidence. A missing document is an evidence gap, not proof that no order arrived.

Conclusion

Use the review to confirm that every order is logged on receipt, verified, calculated within the floor, and remitted with a closed file. Fix the intake path, the calculation rule, or the evidence trail before the next order arrives. Rerun the sample after any provider or jurisdiction change. The control is a case file that a stranger can follow. Set the next sample date and the trigger that will force an earlier review.

Sources

  1. DOL Wage and Hour Division, Wage Garnishment Law Fact Sheet
  2. DOL Wage and Hour Division, Deductions from Wages Fact Sheet
  3. IRS Publication 15, Circular E
  4. NIST Special Publication 800-53 Revision 5

Prepare a garnishment evidence pack

A Philippines-based payroll support specialist can open case records, collect order documents, prepare the calculation worksheet, and match each remittance to the case. The specialist can also maintain the intake log and the closure checklist. Your payroll owner and qualified adviser still decide the withholding and any correction.

Review payroll operations support

FAQs

Can this review decide whether an order is valid?

No. It tests whether the employer logged, verified, calculated, and remitted the order with evidence. Validity and legal interpretation belong to counsel. A clean review is not a legal opinion.

What if the order arrived after the payroll cutoff?

Record the arrival date and apply the order from the first pay period the rule requires. A late arrival is a timing finding, not a reason to hide the date. Check the notice requirement for that first affected period.

How should a correction be evidenced?

Use the same case number with a correction entry that shows the original amount, the corrected amount, the period, the approver, and the employee notice. Keep it separate from the current run while linking both records.

For adjacent operating context, see Payroll Preparation and the payroll operations guide library.

Related research