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.
- HRMS with Exit Management
- Features
- Final pay
Final pay
Review the payroll period and employee statement at departure.
OverviewPay run approvals×
HRMS with Exit Management · Final pay
New
Pay run approvals
Approval conditions
| Run number | Calendar | Period start | Period end | Pay date | Status | |
|---|---|---|---|---|---|---|
| PR-87651 | PC-2716 | 10 Oct | 19 Oct | 23 Oct | Pending approval | |
| PR-30212 | PC-2335 | 25 Oct | 31 Oct | 05 Nov | Pending approval | |
| PR-28339 | PC-7906 | 14 Oct | 21 Oct | 30 Oct | Pending approval | |
| PR-89265 | PC-4136 | 16 Oct | 21 Oct | 28 Oct | Pending approval | |
| PR-35713 | PC-4260 | 21 Oct | 25 Oct | 03 Nov | Pending approval |
6 of 6 records
PC-2716Payroll runs · PR-87651
Pending approvalPeriod start10 Oct
Period end19 Oct
Pay date23 Oct
What you can do
Bring payroll into the exit review
Payroll Admin works from payroll runs, pay statements and pay statement lines. The run has a period, pay date, calendar and approval status. A statement links a worker to the run; its lines identify earnings, deductions and tax entries. Benefit enrollments, time and leave records supply context for the review.
A departing employee may have a current record, a dated employment change, an exit checklist and a payroll statement. Review the links between those records before treating one status as the whole answer. The manager and HR Business Partner should be able to identify the next owner from the assigned task and its due date.
How the work is organized
- Person. Keep the employee identifier and current manager with the departure record so the work is attached to the right worker.
- Date. Use the effective event date and task due dates to distinguish future work from overdue work.
- Result. Record the status and supporting evidence on the record where the work occurred.
What to agree during setup
Agree which payroll calendar applies, who reviews exceptions and who is authorized to approve a run. Match the effective departure to the period and any off-cycle run choice. Review statement lines and amounts before moving a run from pending approval to approved. Keep the record of who approved the run.
For the pilot, choose an employee with a normal departure and one with a change close to the payroll cutoff. Decide who reviews each case and where an exception will be recorded. The team should use the exact same owner for a task in the app and in its operating procedure.
Check the handoff on an actual case
Take an employee who leaves during a pay period with approved overtime. Payroll Admin opens the run, finds the employee statement and examines its lines. They compare the timesheet and benefit enrollment to the period. If the statement cannot be explained, keep the run in its review state while the source record is corrected.
Ask the next owner to open the record without relying on a separate message. They should see the relevant employee, dates, current status and who completed or still owns the work. If they cannot make the next decision from those records, improve the task description or review rule before expanding use.
What your team sees
- Pay run approvals — Open the relevant records and review the current result.
- Final statements — Open the relevant records and review the current result.
- Payroll review board — Open the relevant records and review the current result.
Follow the work through
See employee departure, payroll review and implementation for the handoffs around this module.
What it keeps track of
Data model- 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.
- Payroll calendars
- Named pay schedules per legal entity, country and currency.
- Timesheets
- Weekly timesheet header per employee.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with dependents and dates.
Who uses it
Permissions- Payroll Admin
- Manages payroll records and prepares the approval review.
- Admin
- Can manage configuration.
- HR Business Partner
- Reads the employee context.
Set up HRMS with Exit Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.