These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Payroll Processing System
- Features
- Benefits and garnishments
Benefits and garnishments
Review effective employee deductions, employer contributions and garnishment limits against the pay detail.
OverviewActive Benefit Deductions×
Payroll Processing System · Benefits and garnishments
New
Active Benefit Deductions
Benefit deductions
| Employee | Deduction code | Employee amount | Employer amount | Effective from | Effective to | |
|---|---|---|---|---|---|---|
| DC-8840 | 630 | 580 | 18 Oct | 22 Oct | ||
| DC-6067 | 640 | 130 | 27 Oct | 02 Nov | ||
| DC-6189 | 900 | 320 | 08 Oct | 11 Oct | ||
| DC-5364 | 130 | 690 | 26 Oct | 28 Oct | ||
| DC-9381 | 820 | 610 | 25 Oct | 28 Oct |
6 of 6 records
DC-8840Benefit deductions · BD-66445
Benefits appEmployee amount630
Employer amount580
Effective from18 Oct
Effective to22 Oct
StatusActive
What you can do
Explain each deduction against its instruction
A benefit deduction carries the employee’s election and the dates it applies. Employee and employer amounts remain separate, with a deduction code describing the payroll treatment. Payroll Specialist checks the election against the period being paid and reviews its effect on the employee’s calculated result. The source identifies manual entry, a benefit import or annual enrollment.
A garnishment carries a different instruction. Its order number, ordering authority and recipient identify why money is withheld and where it is owed. Payroll Manager reviews the original order and maintains its dates, priority and limits. Payroll Specialist checks the result in the pay detail before the whole cycle goes to approval.
How the work is organized
- Effective benefit elections. Compare the election’s start and end dates with the payroll period. Check the employee and employer amounts independently. Pending, Active, Suspended and Ended states help the team distinguish the instructions it needs to review.
- Deduction treatment. Follow the deduction code to its category, pre-tax setting and employer-match information. Payroll Admin maintains the code and account target. Review the calculated lines against the agreed treatment before accepting the employee total.
- Ordered withholding. Check the garnishment’s remaining balance, period limit and disposable-earnings percentage limit against the source order. Priority and recipient matter when an employee has competing instructions or a balance approaching completion.
What to agree during setup
Choose the authoritative benefit source and the person who resolves election differences. Configure the benefit connection where it is needed, with agreed employee matching. Rehearse an election that starts near a period boundary and an earlier election that ends. Payroll Specialist should be able to show which dated instruction supports the deduction.
Payroll Manager agrees how garnishment priorities and limits apply to the customer’s orders. Check a suspended order and a remaining balance smaller than the usual deduction. Assign responsibility for balance updates and external remittance evidence. The person reviewing payroll needs to distinguish the calculated withholding from the later payment to the named recipient.
Check the handoff on an actual case
An employee changes a benefit election while a garnishment remains active. Payroll Specialist compares the earlier and replacement election dates, checks the active instruction and follows its deduction code to the tax treatment. Payroll Manager reviews the garnishment balance and limits before calculation, using the original order to explain the expected withholding.
After calculation, inspect the employee’s pre-tax deductions, withheld taxes, post-tax deductions and net pay. Follow each disputed amount into the detailed lines. Explain the change using the election and order, then bring any unresolved difference to Pay Run Holds with a reason the decision owner can act on.
Repeat the case with the benefit election marked Ended and the garnishment Suspended. Compare the employee result with the agreed expectations. When a balance changes, retain the operating evidence for that change and identify who checked it. At the next cycle, Payroll Manager should be able to explain the opening balance without reconstructing the previous payroll from memory.
What your team sees
- Active Benefit Deductions — Review current elections, effective dates and contribution amounts.
- Active Garnishments — Compare order limits, priorities and remaining balances.
- Pay Run Holds — Investigate an employee deduction that needs attention before approval.
Follow the work through
Begin with inputs to calculation and continue through review to payslips. Agree benefit and remittance responsibilities in integrations.
What it keeps track of
Data model- Benefit deductions
- Per-employee benefit elections feeding the deduction side of each pay run.
- Deduction codes
- Catalog of deduction categories with pre-tax, employer-match and GL targets.
- Garnishments
- Court-ordered and statutory deductions with caps, priority and remaining balance.
- Employees
- Workforce master for payroll: who is paid, in which department and location, who approves them, and their employment status. Landing table for the Core HR inbound feed.
- Pay run items
- One row per employee per pay run: the gross-to-net header that drives the payslip.
- Payslip lines
- The exploded gross-to-net detail per employee per pay run: the audit grain.
- GL account map
- Maps earning and deduction codes to GL accounts so pay-run posting is deterministic.
Who uses it
Permissions- Payroll Specialist
- , Payroll Manager, Payroll Admin.
- Payroll Specialist
- Manages benefit elections, Payroll Manager maintains orders, and Payroll Admin maintains deduction codes and account references.
Set up Payroll Processing System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.