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.
- HRMS + Payroll for SMB
- Features
- Payroll and benefits
Payroll and benefits
Prepare pay periods, review employee statements and keep benefit enrollments beside payroll.
OverviewPay run register×
HRMS + Payroll for SMB · Payroll and benefits
New
Pay run register
Approval conditions
| Run number | Calendar | Period start | Period end | Pay date | Employee count | |
|---|---|---|---|---|---|---|
| PR-64577 | PC-1063 | 23 Oct | 25 Oct | 10 Oct | 25 | |
| PR-44671 | PC-4704 | 08 Oct | 16 Oct | 23 Oct | 29 | |
| PR-81130 | PC-7229 | 27 Oct | 02 Nov | 09 Nov | 36 | |
| PR-56581 | PC-6359 | 17 Oct | 25 Oct | 27 Oct | 23 | |
| PR-89207 | PC-8534 | 22 Oct | 24 Oct | 28 Oct | 10 |
6 of 6 records
PC-1063Payroll runs · PR-64577
DraftPeriod start23 Oct
Period end25 Oct
Pay date10 Oct
Employee count25
Gross total430
What you can do
The pay period as the unit of work
A payroll calendar defines the entity, country, currency, frequency and cutoff days. Each employee connects to a calendar. Payroll Admin selects a calendar and creates a run with period start, period end, pay date and run type. Regular, off-cycle, Retro, Correction and Bonus identify why the run exists. The run carries employee count, gross total, net total and status, so reviewers can see the result for the period before it is posted or paid.
Pay statements belong to both a run and an employee. The statement identifies its period, payment method, currency, gross pay and total deductions. Pay statement lines divide the amount into Earning, pre-tax, post-tax, Tax and Employer categories, with code, quantity, rate, amount and jurisdiction where relevant. Payroll Admin can trace a total back to a line and an employee. That trace is especially important when overtime, a benefit contribution or a correction changes a person’s result.
How the work is organized
- Calendar. The schedule and cutoff rule group employees into compatible pay periods.
- Run. A payroll run holds the dates, type, approval point and aggregate totals.
- Employee detail. Statements and lines explain each employee’s pay; benefit enrollments identify the selected plan and contributions.
What to agree during setup
Agree who maintains base salary, pay grade and employee calendar assignments. Confirm each entity’s currency and pay frequency before creating a first run. Decide who reviews employee eligibility, approved overtime, leave and benefit enrollments at cutoff. Benefit plans include country, employee class, effective dates, carrier and contribution percentages; the enrollment adds a coverage tier and employee and employer amounts. These records should be checked against the pay statement lines for the same period.
The run’s pending approval state is the point for a human review of gross and net totals and individual outliers. The approver is recorded on the run. Once Approved, Payroll Admin can record Posted, Paid and Closed in sequence according to the operating procedure. The app stores the status and dates; banking and payment execution should be established as a separate connection. An off-cycle correction should carry its own run type so the normal cycle remains explainable.
Check the handoff on an actual case
Choose an employee with a benefit enrollment and approved overtime. Confirm the employee’s calendar, entity, currency and base salary. Open the selected run period and inspect its pay date and type. Check the employee statement for matching period dates. Review the earning, deduction and tax lines, then reconcile the statement’s gross and deductions to the run totals. Ask the approver to inspect an unusual change before recording Approved. After the pay outcome is confirmed, check the run status and the employee statement status together.
What your team sees
- Pay run register — Run dates, calendar, type and totals across the payroll cycle.
- Payroll approval inbox — Periods waiting for a pay decision.
- Pay statement detail — Employee pay components grouped under each statement.
Follow the work through
See payroll cycle for the run handoff and time and leave for its inputs.
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.
- Employees
- Central person record for every worker; all suite transactions tie back to Employees.
- Pay grades
- Salary bands tied to job titles and positions.
- Timesheets
- Weekly timesheet header per employee.
Who uses it
Permissions- Payroll Admin
- Prepares pay records and reviews the statements.
- CHRO / VP People
- Oversees totals.
- HR Business Partner
- Maintains employee context; Admin manages the configuration.
Set up HRMS + Payroll for SMB your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.