All applications611

Find your application

611 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Security Services HRMS
  2. Who it's for
  3. Multi-entity employers
Who it's for

Multi-entity employers

An employer with people in several legal entities needs each employee attached to the right entity, country, currency and payroll calendar. HR and payroll can share processes while keeping the decision and pay basis visible on the worker and period records. The model supports separate calendars and benefit plans for different populations.

How Security Services HRMS is set up for you

Entity placement

Confirm the legal employer and country on each employee before recording pay or enrollment.

Local pay cycle

Define calendar frequency, currency and cutoff by entity; select the matching calendar for each run.

Benefits

Use the plan's country and employee class with the employee's enrollment and effective dates.

Tax review

Keep jurisdictions and dated filing records tied to payroll runs for the relevant authority.

An employer with people in several legal entities needs each employee attached to the right entity, country, currency and payroll calendar. HR and payroll can share processes while keeping the decision and pay basis visible on the worker and period records. The model supports separate calendars and benefit plans for different populations.

Choose one country and one employing entity first. Load the people structure and verify an employee's manager, position and pay grade. Configure a calendar and one benefit plan that applies to that population. Rehearse a regular pay period with a statement, deduction line and filing. Only after the first cycle reconciles should the team add a second entity with its own calendar and relevant tax jurisdiction.

Review the entity choices available in the employee and calendar records against the actual legal organization. Some workers may be hired into a different entity from the team that recruits them. The offer carries currency and salary, but the employee and payroll calendar determine which legal books carry the pay. HR Business Partner and Payroll Admin should check that handoff together. If a worker transfers entity, keep an effective employment event and recheck benefits and pay placement.

A multi-country rollout also needs the local specialists to validate rates, payroll rules and filing obligations for each jurisdiction. Use a test period with representative worker types and review statement lines before approving a live cycle.

[Review payroll work](/hrms-for-security-services/modules/payroll-and-benefits) and [prepare the rollout](/hrms-for-security-services/implementation).

Features to start with

Roles on the team

HR Business Partner
Record entry on people and performance tables; read-only on pay and benefits.
Employee
Self-service record entry on leave, timesheets and goals; read-only on pay, benefits and performance.
Payroll Admin
Record entry on payroll and tax tables; read-only on employees, benefits, leave and timesheets.
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 Security Services HRMS your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started