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
- Payroll handoff
Payroll handoff
Keep approved time, leave and pay-period totals connected to the employee record and the next decision.
OverviewPayroll approval queue×
Attendance Management · Payroll handoff
New
Payroll approval queue
Approval waits for the reviewer
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-54430 | PC-8014 | 04 Oct | 06 Oct | 10 Oct | 920 | |
| PR-84369 | PC-5342 | 26 Oct | 29 Oct | 01 Nov | 50 | |
| PR-63402 | PC-4453 | 08 Oct | 10 Oct | 15 Oct | 750 | |
| PR-22085 | PC-9911 | 04 Oct | 12 Oct | 16 Oct | 380 | |
| PR-58615 | PC-8840 | 25 Oct | 28 Oct | 06 Nov | 60 |
6 of 6 records
PC-8014Payroll runs · PR-54430
Pending approvalPeriod start04 Oct
Period end06 Oct
Pay date10 Oct
Gross total920
Net total490
What you can do
Keep approved time, leave and pay-period totals together
Payroll handoff brings the relevant source records into one operating path. A biweekly run includes an approved overtime week and approved leave. Payroll Admin checks the source records, records and checks statements, and inspects earnings and deduction lines. Admin records the approved state after the responsible reviewer compares gross and net totals. 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 approved time, leave and pay-period totals and checks the employee link.
- Review. The assigned reviewer checks the record and its dates before a downstream team relies on it.
- Follow through. A biweekly run includes an approved overtime week and approved leave. Payroll Admin checks the source records, records and checks statements, and inspects earnings and deduction lines. Admin records the approved state after the responsible reviewer compares gross and net totals.
What to agree during setup
Assign each person to a calendar and agree cutoff days, pay date, correction handling and the approval authority. Identify how payment and accounting results will be reconciled. 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
A biweekly run includes an approved overtime week and approved leave. Payroll Admin checks the source records, records and checks statements, and inspects earnings and deduction lines. Admin records the approved state after the responsible reviewer compares gross and net totals. 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
- Payroll approval queue — Pending runs with period dates and totals, with the person and current state in view.
- Pay statements for review — Employee statements tied to the period 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- Payroll calendars
- Named pay schedules per legal entity, country and currency.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Pay statements
- Per-employee pay statement for a given payroll run.
- Pay statement lines
- Earnings, benefit deductions, taxes and garnishments on a pay statement.
- Attendance sessions
- Weekly timesheet header per employee.
- Leave requests
- Employee-submitted leave requests requiring manager approval.
Who uses it
Permissions- Payroll Admin
- Owns the primary work.
- 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.