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.
- Attendance Management
- Features
- Benefits and pay records
Benefits and pay records
Keep enrollment dates, contribution and pay statement lines connected to the employee record and the next decision.
OverviewPay statements for review×
Attendance Management · Benefits and pay records
New
Pay statements for review
Pay statements
| Statement number | Person | Run | Period start | Period end | Gross pay | |
|---|---|---|---|---|---|---|
| PS-31319 | PR-85741 | 15 Oct | 18 Oct | 640 | ||
| PS-27216 | PR-21182 | 18 Oct | 23 Oct | 450 | ||
| PS-97359 | PR-97415 | 24 Oct | 27 Oct | 900 | ||
| PS-71713 | PR-56658 | 15 Oct | 18 Oct | 330 | ||
| PS-57857 | PR-90431 | 05 Oct | 07 Oct | 170 |
6 of 6 records
PR-85741Pay statements · PS-31319
DraftPeriod start15 Oct
Period end18 Oct
Gross pay640
Total deductions580
What you can do
Keep enrollment dates, contribution and pay statement lines together
Benefits and pay records brings the relevant source records into one operating path. An employee changes coverage tier after a qualifying event. Admin checks the enrollment and effective date. Payroll Admin then checks that the contribution amount appears in the right period and that the employee can read the resulting statement. The person link, effective date and current status give the next team a way to understand the decision without relying on a typed name or an email thread.
A preparer should check the record before handing it off. The reviewer needs the source dates and amounts in context, plus the authority to return a disputed item. When a correction is needed later, the team should retain the original record and explain the new effective value.
How the work is organized
- Prepare. Payroll Admin starts with enrollment dates, contribution and pay statement lines and checks the employee link.
- Review. The assigned reviewer checks the record and its dates before a downstream team relies on it.
- Follow through. An employee changes coverage tier after a qualifying event. Admin checks the enrollment and effective date. Payroll Admin then checks that the contribution amount appears in the right period and that the employee can read the resulting statement.
What to agree during setup
Agree plan eligibility by country and person class, active dates, enrollment events and who verifies contributions. Check a waived or terminated enrollment against each later statement line before approving the period. Define which person owns initial entry, who makes the decision, and which point closes further routine edits. Review the same rule for a normal cycle and a late correction. If the relevant employee changes role or department, keep the source period understandable to the next reviewer.
Use a representative worker and one pay period to settle the convention. Enter a real date range, assign a responsible reviewer and inspect the resulting status. The team can then compare the source against the next record before broadening access to everyone.
Check the handoff on an actual case
An employee changes coverage tier after a qualifying event. Admin checks the enrollment and effective date. Payroll Admin then checks that the contribution amount appears in the right period and that the employee can read the resulting statement. Ask the recipient to find the source record using the person and period, then explain what was accepted and what would be returned. Rehearse a rejected or corrected version as well. A decision is useful only when the preparer can see what to change and the next team can tell which value is final.
What your team sees
- Benefit enrollments by state — Coverage tier, effective dates and contribution for each person.
- Pay statements for review — Statements by person and run.
Follow the work through
Read hours and leave, payroll, the data model and roles to rehearse the complete path.
What it keeps track of
Data model- Benefit plans
- Enrollable benefit plans such as medical, dental, retirement and life.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with dependents and dates.
- Pay statements
- Per-employee pay statement for a given payroll run.
- Pay statement lines
- Earnings, benefit deductions, taxes and garnishments on a pay statement.
- People
- Central person record for every worker; all suite transactions tie back to Employees.
Who uses it
Permissions- Admin
- Maintains benefit plans and enrollments.
- HR Business Partner
- Maintains employee context, Payroll Admin checks the pay-period consequence, and Admin handles configured access and corrections.
- Each handoff should preserve the named preparer and decision maker.
Set up Attendance Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.