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.
- Staffing Agencies HRMS
- Features
- Payroll and tax
Payroll and tax
Prepare a company pay run from employee calendars through statements and tax filings.
OverviewPayroll approval queue×
Staffing Agencies HRMS · Payroll and tax
New
Payroll approval queue
Approval waits for the approver
| Run number | Period start | Period end | Pay date | Calendar | Gross total | |
|---|---|---|---|---|---|---|
| PR-83151 | 04 Oct | 13 Oct | 22 Oct | PC-1987 | 180 | |
| PR-17295 | 06 Oct | 15 Oct | 21 Oct | PC-3025 | 120 | |
| PR-60194 | 16 Oct | 25 Oct | 27 Oct | PC-1911 | 50 | |
| PR-21781 | 18 Oct | 24 Oct | 27 Oct | PC-7985 | 870 | |
| PR-42589 | 18 Oct | 20 Oct | 26 Oct | PC-5722 | 290 |
6 of 6 records
PC-1987Payroll runs · PR-83151
Period start04 Oct
Period end13 Oct
Pay date22 Oct
Gross total180
Net total290
What you can do
Run payroll for the firm's employees
Payroll Admin works from a named payroll calendar with an entity, country, currency, frequency and cut-off. Each payroll run covers a period and pay date. The run carries a status from Draft through calculation, approval, posting, payment and closure. Its statements belong to individual employees, and each statement can hold earnings, deductions, tax and employer lines. This creates a traceable connection between the run total and the employee-level result.
A staffing company can have its own internal recruiters, payroll staff and operations team on different calendars. The calendar selection on the employee record matters because it determines which pay period they belong to. Confirm an employee’s pay grade, salary and calendar before calculating. Approved leave and time should be reconciled with the relevant period; a submitted but undecided timesheet is a question to resolve before posting.
How the work is organized
- Calendar. A schedule names the employer entity, country, currency, frequency and cut-off days.
- Run. The period groups the employee statements and holds gross and net totals and approval state.
- Statement. Earnings and deduction lines explain each employee’s gross and net pay.
Payroll runs can be regular, off-cycle, retro, correction or bonus. Agree which cases warrant a separate run and who reviews the reason. A calculated statement can be checked before approval; an approved run can be posted, then marked paid and closed. The run’s approval is a human decision. Posting and payment should be recorded only after the corresponding operating checks have happened.
What to agree during setup
Set the payroll calendar for each entity and employee. Confirm pay dates, cut-offs, earning codes, deductions and the tax jurisdictions linked to employee locations. Make the review owner explicit for a run and for any correction. Decide how the team confirms payment outside the HRMS and how that confirmation is reflected in the run. Tax filings should use the jurisdiction and due date appropriate to the run, with a confirmation reference when filed.
Benefit enrollments can contribute employee and employer amounts. Leave and approved overtime can affect a statement. These inputs need a dated review before a run is approved. Payroll Admin should be able to trace a surprising amount from the statement line to the source person and period, then record a correction through the appropriate run type rather than editing a closed result.
Check the handoff on an actual case
For a biweekly internal payroll, Payroll Admin creates a regular run for the calendar and period. The team checks active employees assigned to that calendar, reviews approved timesheets and leave, then calculates statements. One employee’s overtime appears as an earning line; a benefit contribution appears as a deduction line. Payroll Admin reconciles the gross and net totals with the individual statements and resolves any discrepancy before seeking approval.
After the approver accepts the result, Payroll Admin posts the run, confirms that payment has occurred, and records the paid and closed states. A tax filing tied to the run retains its jurisdiction, due date, amount and filing confirmation. Rehearse a correction run for a missed adjustment so the team knows how it will avoid silently changing a prior closed pay result.
What your team sees
- Payroll approval queue — Runs ready for a financial decision, with period and totals.
- Active employees — The employee and calendar context behind the current pay population.
Follow the work through
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.
- 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.
- Tax jurisdictions
- Tax-authority records driving withholding and filings.
- Tax filings
- Payroll tax filings produced from a run and remitted to an authority.
Who uses it
Permissions- Payroll Admin
- Prepares runs, statements and tax filings.
- HR Business Partner
- Maintains employee context.
- Employee
- Reads their own pay statement.
- CHRO / VP People
- Reviews the outcome; Admin controls setup.
Set up Staffing Agencies HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.