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
- Who it's for
- Multi-entity employers
Multi-entity employers
Employers working across different entities and countries need employee context that stays consistent with the calendar, position and benefit arrangement. HRMS connects each employee to a department, location, manager, pay grade and payroll calendar. The team can coordinate recruiting and ongoing people work while preserving the local contribution rules, currency and separately configured provider responsibilities.
How HRMS is set up for you
Keep employment context clear
HR Business Partner (HRBP) checks entity, country, position and location before applying a transfer or compensation change. Employment history retains the event and effective values so payroll and recruiting can understand the resulting arrangement.
Use the appropriate pay calendar
Payroll Admin reviews frequency, country, currency and period boundaries before preparing a run. Different currency values remain separate in totals review. Configure country-specific tax calculation with the payroll owner before live use.
Review local elections
Each benefit plan carries its country, employee class and effective dates. Employee elections use the matching plan window and enrollment event. Internal activation and contribution calculation are separate from the carrier's confirmed coverage outcome.
Assign decisions to the intended person
The employee's manager supplies the default leave approver, while compensation exceptions route to CHRO / VP People. Verify account mapping, subject scope and workflow action authority rather than assuming that a table grant applies the correct organizational boundary.
Employers working across different entities and countries need employee context that stays consistent with the calendar, position and benefit arrangement. HRMS connects each employee to a department, location, manager, pay grade and payroll calendar. The team can coordinate recruiting and ongoing people work while preserving the local contribution rules, currency and separately configured provider responsibilities.
Start with an entity, location and pay calendar whose responsible people can rehearse the whole handoff. Import the organizational masters and employee references, then run an approved vacancy through offer acceptance and employee provisioning. Add a leave request and a valid benefit election before preparing the internal pay pre-check. Confirm the expected active employee population and the statement deductions against that pilot data.
Expand after the team can explain an out-of-band offer, a missing leave balance and a failed external handoff. The same records support broader coordination, but provider connections and country-specific tax review need their own configuration and evidence. Use [implementation](/hrms-suite/implementation) to agree the next population and [integrations](/hrms-suite/integrations) to assign the provider owners.
Features to start with
Employee records
Keep current employment and salary-band decisions connected to the employee history.
Recruiting and offers
Follow approved headcount through candidate review, offer decisions and accepted hiring.
Onboarding and offboarding
Assign joining and leaving work with named employees, evidence and payroll handoffs.
Roles on the team
- Employee
- Self-service access to own record. Record entry on Leave Requests, Timesheets, Time Entries and Goals (draft); read only on Pay Statements, Benefit Enrollments, Leave Balances, Performance Reviews and Training Records. Own-record scope is required and is not expressible as a native table grant, so it must be supplied by the own-record table scope before these grants are relied on.
- Recruiter
- Owns the requisition pipeline from intake through offer. Record entry on Job Requisitions, Candidates, Applications, Interviews and Offers; read only on Employees for hiring-manager and referral context. No pay statement, payroll run, pay statement line, tax filing or benefit enrollment access.
- Payroll Admin
- Runs payroll end to end and owns tax filings and GL handoff. Record entry on Payroll Calendars, Tax Jurisdictions, Payroll Runs, Pay Statements, Pay Statement Lines and Tax Filings; read only on Employees, Benefit Enrollments, Leave Requests and Timesheets. No delete or bulk edit; filings stay at Draft.
- CHRO / VP People
- Executive oversight across the people function. Read-only (View + View records) on all HRMS tables, including Pay Statements with no create or edit. Approves org-wide change and cross-entity decisions through workflows, not by editing rows.
Set up HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.