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 and filings
Example screen with sample data
Payroll and filings
Prepare calendar-based pay statements and keep tax, payment and posting outcomes explicit.
OverviewPayroll pre-check×
HRMS · Payroll and filings
New
Payroll pre-check
Approval conditions
| Run number | Calendar | Period start | Period end | Pay date | Employee count | |
|---|---|---|---|---|---|---|
| PR-29914 | PC-2534 | 19 Oct | 22 Oct | 31 Oct | 36 | |
| PR-69807 | PC-2892 | 26 Oct | 28 Oct | 04 Nov | 2 | |
| PR-32592 | PC-2013 | 21 Oct | 29 Oct | 04 Nov | 5 | |
| PR-29184 | PC-5516 | 13 Oct | 19 Oct | 23 Oct | 2 | |
| PR-50823 | PC-4100 | 13 Oct | 16 Oct | 18 Oct | 35 |
6 of 6 records
PC-2534Payroll runs · PR-29914
Pending approvalPeriod start19 Oct
Period end22 Oct
Pay date31 Oct
Employee count36
Gross total750
What you can do
Bring the run to a reviewable pre-check
Payroll Admin begins with a payroll calendar and a dated run. The calendar identifies frequency, entity, country, currency and cutoff. The run identifies its period, pay date and type. Together they define the pay cycle being prepared, from Draft through Calculating to Pending approval.
The calculation prepares earnings for active employees using the calendar frequency and deductions from active benefit enrollments. Configure tax calculation with the payroll owner before live use. Review prepared net pay against the agreed calculation and keep unresolved pay items assigned to the responsible person.
How the work is organized
- Run preparation. The run tracks employee count, gross total and net total. Payroll Admin compares the intended population with the resulting statements and resolves omissions or unexpected employees before following the agreed approval route.
- Statement detail. Each statement connects an employee to the run and its period. Lines explain earnings, deductions, tax and employer amounts through their category, quantity, rate and amount. Account and jurisdiction references support the accounting and tax handoffs.
- Later outcomes. Approved, Posted, Paid and Closed distinguish later run states. Entry to Posted records the posting date. Filing records retain the type, period, due date, amount and confirmation reference for work coordinated with the tax service.
What to agree during setup
Choose the pilot calendar and verify its employee population, currency and earnings basis. Agree the person who authorizes the run and test their decision action. Review how leave and approved timesheets reach Payroll Admin, including any time-based pay treatment configured for the customer.
Establish the country-specific tax calculation and review requirement with the payroll owner. Bank delivery, accounting journals and authority filings need separately configured connections. Name the person who reconciles each result. Keep Payroll Admin within the agreed preparation permissions and direct filing delivery through the responsible tax service owner.
Check the handoff on an actual case
Create a regular pilot run and follow it to Pending approval. Inspect the statement population, then choose an employee with an active benefit deduction. Compare the line amounts, gross pay, deductions and net pay with the run totals. Keep currencies separate and compare tax amounts with the agreed calculation before advancing the run.
Resolve outstanding items and follow the agreed approval route. Rehearse entry to Posted and inspect the posting date. Then rehearse a failed bank or accounting handoff: retain the actual outcome and assign the next action to its connection owner. Ask Payroll Admin to trace a filing record to the tax service confirmation and explain any unresolved submission.
What your team sees
- Payroll pre-check — Review pending runs with their pay period, employee population and prepared totals.
- Pay statement schedule — Inspect employee statements by period and follow their recorded processing status.
Follow the work through
Rehearse leave and time to payroll pre-check, then agree the external connections and their reconciliation owners.
What it keeps track of
Data model- Payroll calendars
- Named pay schedules with frequency, entity, country and cutoff.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Pay statements
- Per-employee pay statement for a given run.
- Pay statement lines
- Each earning, benefit deduction, tax and garnishment on a pay statement.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run, remitted to an authority.
- Employees
- The central person record that every transaction in the suite ties back to.
- Benefit enrollments
- Per-employee enrollment in a benefit plan, with dependents and effective dates.
- Leave requests
- Employee-submitted leave requests requiring manager approval.
- Timesheets
- Weekly timesheet header per employee.
Who uses it
Permissions- Payroll Admin
- , CHRO / VP People, Employee.
- Payroll Admin
- Prepares and reviews runs and statements.
- CHRO / VP People
- Has read-only oversight.
- Employee
- Reads permitted personal statements.
- Configure run approval responsibility with the customer before release.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.