H2R 101A · OPERATING MODELS
Where does the employee lifecycle execute?
A multinational enterprise can share one workforce strategy, organisation, and Finance backbone without operating one global HR system. Employment is local; the H2R lifecycle is common, but system ownership and execution boundaries vary.
THE CONSTANT
One lifecycle; several legitimate operating models
Plan, recruit, onboard, manage, pay, and exit remain the same business lifecycle. The operating model determines where each transition is authorised, recorded, executed, propagated, and financially recognised.
THE H2R ARCHITECTURE QUESTION
Separate ownership, local execution, and financial consequence
Do not start with a product name. Start with the boundary that owns the employee fact, performs local employment work, and records the financial result.
Who owns the authoritative fact?
Identify the system of record for person, employment, organisation, position, manager, job, grade, compensation, and employment status.
Who executes local employment work?
Locate payroll, tax, social insurance, benefits, working time, leave, statutory reporting, employment documents, privacy controls, and local HR administration.
Where does the cost land?
Salary, bonuses, employer contributions, benefits, liabilities, accruals, payments, and cost-centre postings must reach the governed ERP and Finance backbone.
THREE COMMON MODELS
Choose the execution boundary deliberately
These models are not maturity levels. Each can be appropriate when its ownership, integration, and control model are explicit.
Global workforce record, localised employment execution. One enterprise platform standardises employee data and global processes as far as practical, with country configuration, payroll engines, regional modules, integrations, or specialists handling local requirements.
Strength: enterprise visibility and common data. Challenge: local complexity can overwhelm a global template.
Local HR execution, enterprise consolidation. Countries or regions retain systems suited to local payroll, statutory, language, benefits, time, and employment requirements; integration supplies the enterprise consistency.
Strength: local fit. Challenge: fragmented data, reporting, integrations, and controls.
External execution, enterprise control. A provider performs payroll, benefits, statutory reporting, employment administration, or service-centre work while the enterprise governs instructions, data, outcomes, and Finance hand-offs.
Strength: specialist execution. Challenge: control depends on service levels, data ownership, reconciliation, cut-offs, and exception management.
THE COMMON CHAIN
Business event to controlled financial evidence
The employee event is stable even when the system route changes.
ONE TRANSFER, THREE EXECUTION PATHS
The business change is the same; the execution boundary changes
An employee moves to another organisation and cost centre on an approved effective date.
- 01
Enterprise HRIS
Approved transfer → global HRIS → effective-dated employee change → payroll and downstream systems → ERP Finance.
- 02
Federated local HRIS
Approved transfer → country HRIS → local employee and payroll record → harmonised integration → ERP Finance.
- 03
Outsourced execution
Approved transfer → enterprise or provider instruction → provider employee and payroll update → controlled result interface → ERP Finance.
MODEL COMPARISON
What changes across the models
The lifecycle remains common. The main design work is making the execution and evidence boundary visible.
WHAT MUST REMAIN COMMON
Systems may differ; enterprise meaning cannot
Identity and employment
Person, employee ID, and employment relationship must be unambiguous across every connected system.
Organisation and Finance
Legal entity, business unit, department, position, manager, company code, cost centre, profit centre, and G/L mapping need governed meaning.
Governance and evidence
Ownership, effective date, approval, interface control, reconciliation, audit evidence, and exception accountability remain visible regardless of the operator.
PRACTITIONER LENS
Start with the authoritative business fact
When entering an unfamiliar H2R landscape, ask who owns each employee fact, who executes the local requirement, and where the financial result goes. Then trace the event through system ownership, propagation, and evidence.
- Global, federated, and outsourced models can coexist
- Hybrid is often a deliberate balance of standardisation and local compliance
- Integration quality does not replace accountable ownership
- Every model needs a controlled path into Finance
Use the capability topics to understand the records and controls within the selected operating model.