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 · Benefits enrollment
Example screen with sample data
Benefits enrollment
Check plan windows and employee elections before applying payroll contributions.
OverviewPay statement schedule×
HRMS · Benefits enrollment
New
Pay statement schedule
Pay statements
| Statement number | Employee | Run | Period start | Period end | Currency | |
|---|---|---|---|---|---|---|
| PS-95689 | PR-70919 | 22 Oct | 26 Oct | USD | ||
| PS-36868 | PR-82728 | 17 Oct | 25 Oct | CAD | ||
| PS-95093 | PR-58902 | 22 Oct | 31 Oct | INR | ||
| PS-84181 | PR-52203 | 26 Oct | 01 Nov | SGD | ||
| PS-24215 | PR-50494 | 15 Oct | 24 Oct | GBP |
6 of 6 records
PR-70919Pay statements · PS-95689
USDPeriod start22 Oct
Period end26 Oct
Gross pay500
Total deductions350
Net pay70
What you can do
Put the election beside the applicable plan
A benefit plan defines the offering by country, employee class and effective window. The employee’s enrollment records the election, coverage tier and enrollment event with effective dates and contribution amounts. The benefits workflow checks the plan and enrollment window before activating the internal election.
Employees and payroll reviewers need the same understanding of which elections apply to a pay period. HRMS retains enrollment and contribution details. Configure the carrier connection separately so its coverage confirmation can be reconciled with the employee’s election and any payroll deduction.
How the work is organized
- Plan availability. A plan identifies its benefit type, carrier, effective dates and contribution percentages. Compensation-affecting plans await CHRO / VP People sign-off through the master-data workflow before activation. Other plans can activate through the internal setup route.
- Election context. The enrollment links the employee to the plan and records coverage tier, dependents and enrollment event. New hire, open enrollment and qualifying life event identify different timing rules. Pending, Active, Waived and Terminated distinguish the recorded participation states.
- Payroll contribution. Validated enrollment calculates employee and employer contributions. Payroll preparation reads active elections for benefit deductions. Review the effective dates and contribution basis before accepting the amount on a statement.
What to agree during setup
Choose a pilot plan and agree its country, employee class, coverage options and contribution percentages. Map employee eligibility to the plan’s class rules. Define the evidence for new-hire and qualifying-life-event elections, and agree how the annual November 1 opening fits the team’s enrollment cycle.
Confirm who maintains plans and how Employee submits an election. Test these actions with the intended accounts. Configure access to personal enrollments and check another employee’s record remains private. Agree how dependent details reach the carrier, which confirmation is retained and who handles a rejected or corrected election.
Check the handoff on an actual case
Record a new-hire election inside the plan’s effective window. Inspect the plan, coverage tier and employee, then follow the pending election through validation to Active. Compare the calculated employee and employer amounts with the agreed plan basis. Ask Payroll Admin to locate the resulting deduction on the applicable statement.
Try an election outside the plan window and an off-cycle election without an eligible event. Keep invalid timing unresolved until corrected. Rehearse a Waived election so reviewers can distinguish a deliberate decline from preparation still in progress. If the carrier rejects delivery, have the connection owner retain the response in the carrier system and match it to the employee and plan. Confirm how the corrected election reaches both the carrier and payroll review.
What your team sees
- Benefit elections — Review pending, active and waived participation with effective dates and contribution amounts.
- Payroll pre-check — Check prepared pay totals after reviewing the applicable benefit deductions.
Follow the work through
Use benefits and employee development for election rehearsal. Agree carrier responsibilities through integrations.
What it keeps track of
Data model- Benefit plans
- Enrollable benefit plans by country and employee class.
- Benefit enrollments
- Per-employee enrollment in a benefit plan, with dependents and effective dates.
- Employees
- The central person record that every transaction in the suite ties back to.
- 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.
Who uses it
Permissions- Employee
- , Payroll Admin, HR Business Partner (HRBP), CHRO / VP People.
- Employee
- Uses the scoped election route and reads personal enrollment.
- Payroll Admin
- Reviews deductions; HR Business Partner (HRBP) reads lifecycle context.
- CHRO / VP People
- Approves compensation-affecting plan activation.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.