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.
Feature · Payroll
Example screen with sample data
Payroll
Prepare dated pay runs, inspect statements and track tax filings.
OverviewPayroll approval inbox×
HRMS with Employee Engagement · Payroll
New
Payroll approval inbox
Approval waits for the payroll admin
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-23144 | PC-2443 | 22 Oct | 25 Oct | 02 Nov | 310 | |
| PR-66692 | PC-4727 | 17 Oct | 19 Oct | 26 Oct | 630 | |
| PR-10659 | PC-4037 | 06 Oct | 10 Oct | 14 Oct | 630 | |
| PR-86932 | PC-3645 | 13 Oct | 16 Oct | 18 Oct | 680 | |
| PR-68097 | PC-5887 | 04 Oct | 13 Oct | 21 Oct | 330 |
6 of 6 records
PC-2443Payroll runs · PR-23144
Pending approvalPeriod start22 Oct
Period end25 Oct
Pay date02 Nov
Gross total310
Net total220
What you can do
Pay the right population for the period
Payroll Admin prepares a run against a payroll calendar. The calendar fixes entity, country, currency, frequency and cutoff days. The run then carries period dates, pay date, type, status and totals. Each employee’s pay statement belongs to that run; statement lines distinguish earnings, deductions, tax and employer amounts. A status change is a decision point: inspect the statements and totals before the run is approved, posted and paid.
The employee record has base salary, currency, entity and calendar. Benefits, approved leave and weekly time can affect the review, but Payroll Admin should verify how they are reflected in statement lines. Keep the source record and the pay statement together when resolving an exception. Tax jurisdictions and filings hold the authority, due date, amount and filing state; payment and filing confirmation must follow the real external event.
How the work is organized
- Schedule. Payroll calendars identify the legal entity, country, currency, frequency and cutoff.
- Calculation record. Payroll runs group the period and pay date; statements and lines show each worker’s gross, deductions and net.
- Tax record. Jurisdictions and filings connect the pay run to amounts due and filing status.
What to agree during setup
Confirm the employee population for each calendar, including workers on leave and recently hired or terminated. Agree the cutoff and the permitted use of off-cycle, retro, correction and bonus runs. Payroll Admin should compare a representative statement with base salary, approved time, benefits and the tax jurisdiction. The run total should reconcile with the statement population before a decision. Identify who will approve pay; the configured Payroll Admin role can prepare records, while the run stores an approving employee.
Arrange payment rails and statutory submission as external connections. A paid status in the register should follow confirmed payment. A filed status should follow a filing event and its confirmation reference. Where a calculation needs jurisdiction-specific rules, test them with the responsible finance and payroll specialists before releasing a period.
Check the handoff on an actual case
A monthly calendar covers one employing entity. Payroll Admin checks the period start, end and pay date, then verifies employee assignments to the calendar. A worker has approved overtime and an active benefit enrollment. The statement shows gross pay and deductions, while its lines explain earnings and benefit or tax amounts. Payroll Admin compares the statement with the approved inputs and checks the gross and net run totals. An authorized person then decides whether the run can move from pending approval to approved.
After approval, reconcile posted statements with the run and record payment when it is confirmed. For a tax filing, review the jurisdiction, due date, amount and confirmation reference. Rehearse a late timesheet and a correction run so the team knows which open period will receive the change. Keep the earlier run’s record intact.
What your team sees
- Payroll approval inbox — Periods and totals awaiting the payroll decision.
- My pay statements — An employee’s own dated statements and pay status.
Follow the work through
Follow Time to pay from approved inputs to the pay run.
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.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run and remitted to an authority.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with dependents and dates.
Who uses it
Permissions- Payroll Admin
- Prepares and reconciles payroll and filing records.
- Employee
- Views their own statements.
- Admin
- Manages setup.
- CHRO / VP People
- Reads payroll results within configured access.
Set up HRMS with Employee Engagement your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.