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
- Timecards and one-time payments
Timecards and one-time payments
Review worked hours and variable pay requests with their employee, manager, earning code and approval state.
OverviewOpen Pay Runs×
Payroll Processing System · Timecards and one-time payments
New
Open Pay Runs
Pay runs
| Pay run number | Pay calendar | Period start | Period end | Pay date | Run type | |
|---|---|---|---|---|---|---|
| PR-45325 | PC-4161 | 17 Oct | 24 Oct | 31 Oct | Regular | |
| PR-55012 | PC-1831 | 17 Oct | 26 Oct | 01 Nov | Off cycle | |
| PR-79096 | PC-1331 | 25 Oct | 02 Nov | 07 Nov | Bonus | |
| PR-80529 | PC-8759 | 21 Oct | 30 Oct | 03 Nov | Correction | |
| PR-63924 | PC-2472 | 24 Oct | 28 Oct | 14 Oct | Year end |
6 of 6 records
PC-4161Pay runs · PR-45325
RegularPeriod start17 Oct
Period end24 Oct
Pay date31 Oct
Gross pay total700
Net pay total computed790
What you can do
Put the source decision beside the pay input
A timecard explains the work behind an employee’s earnings. Its work date, hours and earning code give Team Manager something concrete to review. The source distinguishes manual work from imported time or salary entries. Payroll Specialist follows those records into the pay cycle and checks that the work belongs to the intended period.
A bonus or reimbursement has its own one-time payment request. The amount, currency, effective date and reason explain what the employee should receive. The manager and payroll approval dates preserve the decisions, while the target pay run identifies the intended cycle. Keep the request review separate from the later confirmation that payroll settled.
How the work is organized
- Submitted hours. Employee prepares a Draft card and submits it. Team Manager compares the hours and earning code with the work evidence, then approves or rejects the card. The assigned approver keeps the review with the responsible manager.
- Calendar cutoff. The daily cutoff process uses each active calendar’s own cutoff days to identify the eligible period. Cards already manager approved become Locked, with the lock date recorded. Check the result against that calendar’s actual dates.
- Variable pay decisions. Team Manager makes the first-line decision on a submitted request. Above the $5,000 routing threshold, Payroll Manager receives an internal review notice. The required payroll decision must be recorded before the team schedules the payment into its target cycle.
What to agree during setup
Confirm the source of hours and how units are used for each earning code. Configure the attendance or timesheet connection your team needs. Agree employee matching and how a repeated source event is handled, then compare imported work with the original dates and approval evidence.
Assign the managers responsible for timecards and variable pay. Rehearse requests below, at and above the routing threshold so the team understands the decision path. Agree who records the Payroll Manager decision and who schedules the approved request. Show each person the queue they will use and test access to another manager’s work.
Check the handoff on an actual case
An hourly employee submits work shortly before the payroll cutoff. Team Manager checks the work date and earning code, approves the supported hours and rejects a disputed card. Payroll Specialist reviews the next cutoff result. The approved work should show its lock date; the disputed card should retain the recorded outcome while the manager resolves the source issue.
The same employee has a reimbursement above the routing threshold. Team Manager reviews the reason and amount, then Payroll Manager checks the routed request. Payroll Specialist compares the actual decision dates with the target pay run before scheduling it. During the rehearsal, stop after the internal notice and inspect the request: the team must still be able to identify whose decision is outstanding.
Repeat the cutoff review after the first lock. Check that the already locked work retains its original hours and approval context. This gives the payroll team a case it can use when a manager asks why a late change belongs in a later review.
What your team sees
- Pending Timecard Approvals — Review submitted work assigned to the signed-in approver.
- Pending One-Time Payment Approvals — Check variable pay requests with their reason and manager.
- One-Time Payment Board — Follow requests through preparation, approval and scheduling.
Follow the work through
Rehearse inputs to calculation, then continue with review to payslips. Agree source feeds in integrations.
What it keeps track of
Data model- Timecards
- Hours worked per period per employee per earning code, from the Time and Attendance feed or entered in app.
- One time payments
- Bonuses, commissions, awards, severance and reimbursements routed through Manager then Payroll approval.
- 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.
- Earning codes
- Catalog of earning categories with tax, pension and overtime flags and GL targets.
- Pay calendars
- Pay-period schedules that drive Pay Run cadence, cutoffs and pay dates.
- Pay runs
- A pay-period aggregation and the unit of payroll work: Draft through Reviewed, Approved, Paid and Posted.
Who uses it
Permissions- Employee
- , Team Manager, Payroll Specialist, Payroll Manager.
- Team Manager
- Decides source work.
- Payroll Specialist
- Prepares the cycle, and Payroll Manager decides routed payroll requests.
Set up Payroll Processing System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.