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.
- Remote Teams HRMS
- Who it's for
- Multi-country people operations
Multi-country people operations
A people team supporting several countries needs each employee linked to the right entity, country, location and payroll calendar. Benefit plans and leave types can carry country and employee-class details. Payroll runs, pay statements and tax filings retain the period and jurisdiction context for follow-up.
How Remote Teams HRMS is set up for you
Entity context
HR Business Partner checks employee country and entity against the assigned payroll calendar.
Benefit scope
Admin maintains country and employee-class plan records; Payroll Admin reads enrollments for pay review.
Filing trail
Payroll Admin links tax jurisdiction and filing records to the run.
A people team supporting several countries needs each employee linked to the right entity, country, location and payroll calendar. Benefit plans and leave types can carry country and employee-class details. Payroll runs, pay statements and tax filings retain the period and jurisdiction context for follow-up.
CHRO / VP People can review the workforce picture. HR Business Partner maintains employee and position facts. Payroll Admin owns payroll and filing records. Recruiter keeps openings and offers tied to their intended locations.
Choose an employee in one country and compare entity, currency and calendar before preparing a run. Enter a benefit enrollment with dates covering the pay period. Payroll Admin checks the enrollment and statement lines, then Admin records the run decision. Inspect the tax filing record linked to the run and its jurisdiction. Repeat with another calendar after the first country’s references and approvals are clear.
During the rehearsal, check the Employees page by department and open an individual detail. Make sure the location classification reflects where the colleague works. Then inspect the related requests and pay statement from their owning records. The team should be able to answer who owns the next step and which record records the decision. Use [the implementation guide](/hrms-for-remote-teams/implementation) for the migration sequence and [the data model](/hrms-for-remote-teams/data-model) for the reference links.
Features to start with
Payroll and benefits
Review pay periods, employee statements, benefit enrollment and tax filing records.
People and locations
Keep employee, position and location records in agreement across remote and hybrid teams.
Hiring and offers
Keep the hiring request, candidate trail and offer tied to the same opening.
Roles on the team
- Employee
- Self-service record entry on leave, timesheets and goals; read-only on pay, benefits and performance.
- Hiring Manager
- Read-only visibility into requisitions and the hiring pipeline.
- Recruiter
- Record entry across the hiring pipeline; read-only on employees.
- Payroll Admin
- Record entry on payroll and tax tables; read-only on employees, benefits, leave and timesheets.
- HR Business Partner
- Record entry on people and performance tables; read-only on pay and benefits.
- CHRO / VP People
- Read-only oversight across all 33 HRMS tables.
- Admin
- Superuser: full record CRUD on all 33 HRMS tables, plus every view, report and app setting.
Set up Remote Teams HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.