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 with Employee Self-Service
- Features
- Pay and benefits
Pay and benefits
Read employee pay statements and benefit enrollments beside payroll periods.
OverviewMy pay statements×
HRMS with Employee Self-Service · Pay and benefits
New
My pay statements
Pay statements
| Statement number | Employee | Period start | Period end | Gross pay | Total deductions | |
|---|---|---|---|---|---|---|
| PS-87847 | 25 Oct | 03 Nov | 880 | 130 | ||
| PS-75092 | 07 Oct | 13 Oct | 60 | 670 | ||
| PS-26891 | 20 Oct | 29 Oct | 600 | 600 | ||
| PS-87521 | 17 Oct | 19 Oct | 400 | 120 | ||
| PS-89304 | 18 Oct | 20 Oct | 710 | 930 |
6 of 6 records
NP-440Pay statements · PS-87847
DraftPeriod start25 Oct
Period end03 Nov
Gross pay880
Total deductions130
What you can do
Keep the work anchored to a person
Payroll Admin maintains payroll calendars and runs for a defined period and pay date. Each pay statement links an employee to a run and period. Statement lines hold earnings, deductions, tax and employer amounts by category. Employee access is scoped to their own statement records, while Payroll Admin can inspect the run and its inputs.
Benefit plans hold a plan type, effective window, country and employee class. A benefit enrollment connects an employee to a plan with coverage tier, effective dates, contribution amounts and status. HR Business Partner (HRBP) can read the enrollment context when answering a question about a deduction shown on a statement.
How the work is organized
- Check the source. Payroll Admin checks each run against its calendar, entity, currency, period and pay date. A statement belongs to an employee and run for that period.
- Record the decision. Statement lines explain earnings and deductions. Benefit enrollment dates and contribution amounts give Payroll Admin the source context for a benefit deduction.
- Keep the trail. An internal Approved or Paid status needs its own matching record and external confirmation before anyone treats money as settled. Keep period and employee references visible through corrections.
What to agree during setup
Agree the payroll calendar, cutoff days, currency and entity before the first run. Identify which benefit enrollments should affect the period. Confirm who approves a run and how a correction is recorded. Carrier exchange, tax calculation and payment execution need an agreed connection and owner during implementation.
Open a statement for an employee with an active benefit enrollment. Compare its gross pay and deductions with the lines, then check the enrollment dates and contribution for that period. Trace the statement back to its run and calendar.
Check the handoff on an actual case
Take one employee with an active medical enrollment and a pay statement for the pilot period. Open the statement, compare its gross pay and deductions with the detailed lines, then inspect the enrollment and plan effective dates. Payroll Admin should be able to trace the statement to its run and calendar. The employee should see only their own statement and enrollment information. If a difference remains, leave the run in its current review state until the source is resolved.
Have the next person find the same employee and period, explain the current status, and identify the source detail behind it. Correct a mismatched reference before the case moves forward.
What your team sees
- My pay statements — Employee reads personal statements by period and status.
- Active benefit enrollments — Employee reads plan, tier and effective dates within personal access.
Follow the work through
See pay statement review for the period check.
What it keeps track of
Data model- Pay statements
- Per-employee pay statement for a given run.
- Pay statement lines
- Each earning, benefit deduction, tax and garnishment on a pay statement.
- Payroll runs
- A scheduled execution of payroll for a calendar and period.
- Payroll calendars
- Named pay schedules.
- Benefit enrollments
- Per-employee enrollment in a benefit plan with coverage and contributions.
- Benefit plans
- Enrollable benefit plans such as medical, dental, retirement and life.
Who uses it
Permissions- Payroll Admin
- Maintains run and statement records.
- Employee
- Reads permitted personal statements and enrollments.
- HR Business Partner
- (HRBP) reads enrollment and statement context.
Set up HRMS with Employee Self-Service your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.