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.
- Security Services HRMS
- Features
- Payroll and benefits
Payroll and benefits
Review a pay period by calendar, employee statement and line, then retain posting, payment and filing status.
OverviewPayroll runs awaiting approval×
Security Services HRMS · Payroll and benefits
New
Payroll runs awaiting approval
Payroll runs
| Run number | Calendar | Period start | Period end | Pay date | Gross total | |
|---|---|---|---|---|---|---|
| PR-61551 | PC-2781 | 27 Oct | 01 Nov | 09 Nov | 100 | |
| PR-87798 | PC-4512 | 04 Oct | 07 Oct | 09 Oct | 510 | |
| PR-59997 | PC-5520 | 13 Oct | 19 Oct | 28 Oct | 170 | |
| PR-82176 | PC-6906 | 27 Oct | 02 Nov | 11 Nov | 840 | |
| PR-13763 | PC-1519 | 14 Oct | 20 Oct | 24 Oct | 810 |
6 of 6 records
PC-2781Payroll runs · PR-61551
Pending ApprovalPeriod start27 Oct
Period end01 Nov
Pay date09 Nov
Gross total100
Net total160
What you can do
Make the pay run inspectable
Payroll Admin starts from a payroll calendar associated with an employing entity, country, currency and frequency. A run holds its period, pay date, run type, status, approving employee and totals. Each employee statement belongs to the run and has period dates, currency, gross, deductions and net. Statement lines distinguish earnings, pre-tax and post-tax deductions, taxes and employer amounts. The line is where the reviewer can examine the code, description, quantity, rate and amount behind a total.
How the work is organized
- Calendar. Set the pay frequency and cutoff for the legal entity and country before preparing a period.
- Statement. Review each employee’s pay and the earning, benefit, deduction and tax lines that make up the result.
- Decision. Keep a named approver on the run and advance status through approval, posting, payment and close in order.
What to agree during setup
Payroll policy varies by entity and jurisdiction. Confirm pay calendars, employee assignment, tax jurisdictions and the earning and deduction codes with payroll specialists. A benefit plan has an effective range, country, employee class, carrier and contribution percentages. An enrollment records the employee, plan, tier, dates, contribution amounts and status. Agree when an active enrollment affects pay. Tax filing records have a jurisdiction, due date, amount and filing status; they need reconciliation to the applicable run.
Set a review of approved time, leave and employee changes before payroll calculation. The employee’s base salary and currency should match the current authorized employment terms. If a pay statement looks wrong, trace the affected line and source record before advancing the run. The run has separate statuses for calculation, approval, posting, payment and closure so the team can see what remains to do.
Check the handoff on an actual case
For a regular period, Payroll Admin selects the correct calendar and checks the period and pay date. An employee with approved overtime has hours on a timesheet and a corresponding earning line on the statement. An active benefit enrollment may produce a deduction or employer contribution line. The reviewer checks the jurisdiction tax line and the gross, deduction and net totals. When statements reconcile to the run totals, the approving employee records the decision. After approval, Payroll Admin records posting and then payment based on actual outcomes, rather than using an approval as proof of payment.
A correction or bonus uses its own run type so it can be distinguished from regular payroll. A filing due for the period should identify its jurisdiction and confirmation reference when filed. Review a paid run’s statements with the related filing and payroll calendar before closing the period.
What your team sees
- Payroll runs awaiting approval — Periods, pay dates, totals and approving employees needing a decision.
- Active employees — Worker records used to review entity, currency and payroll calendar placement.
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.
- Benefit plans
- Enrollable benefit plans such as medical, dental, retirement and life.
- 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.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
Who uses it
Permissions- Payroll Admin
- Prepares runs, statements and filings.
- Admin
- Controls setup.
- CHRO / VP People
- Reviews the wider workforce context.
- Employee
- Reviews pay and benefit records after access is scoped to their own entries.
Set up Security Services HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.