Holding Company HR Operating Model: Multi-Entity HRIS for Indonesian Groups

Most Group HR Directors in Indonesia did not inherit a clean HR architecture. They inherited a stack of HR systems — one per PT subsidiary — each chosen by a different entity HR head at a different point in time, with different vendors, different payroll cycles, and incompatible reporting formats. The result is vendor fatigue, fragmented data, and a group leadership team that cannot answer a basic question like “how many people work for us this month” without three weeks of spreadsheet stitching.

This pattern is structural, not accidental. Indonesian conglomerates typically evolved HR by entity — each PT subsidiary built its own HR team, payroll process, and employment policies independently. That made sense when the group was small. Once the group scales to 5, 10, or 20 entities with 3,000 to 30,000+ employees, the fragmentation produces compounding operational and governance costs.

The central question is no longer whether to consolidate HR — it is how much holding company HR should centralize, and how much should remain with each entity. There is no universal answer. The right operating model depends on the group’s business model diversity, regulatory footprint, and talent strategy. What follows is a structured decision framework for Indonesian conglomerate HR — a peer-to-peer view from senior practitioners running HR across multiple PT entities.

Three HR Operating Models for Holding Groups

Indonesian holding groups generally operate one of three HR models: Centralized, Federated, or Hybrid. The hybrid model is the most defensible default for diversified Indonesian conglomerates because PKB (Perjanjian Kerja Bersama) is a per-entity legal obligation that cannot be fully centralized, while talent and reporting cannot be effectively managed at entity level alone.

According to AIHR’s review of HR operating models, the federated / business partner model is prevalent in roughly 75% of North American organizations (citing Mercer). That dominance reflects a global preference for distributed execution, but in the Indonesian context federated structures often drift into uncontrolled fragmentation if not bounded by group governance.

A practical heuristic: if your group spans more than two industries or more than two PKB regimes, the centralized model will collapse under its own exception list. The hybrid model is rarely the easiest path, but it is the only one that holds at scale.

For a deeper view on the platform requirements behind a hybrid structure, see our guide to Enterprise HRIS for multi-entity organizations.

Where to Standardize and Where to Localize

The standardize-vs-localize decision is not a philosophical debate — it is a compliance and operational question with a clear cut line. Anything that drives group-level consistency, equity, or visibility must be standardized. Anything that carries a per-entity legal obligation or location-specific operational reality must stay local.

Standardize at Group Level (Non-Negotiable)

• Job grading and compensation band framework — ensures internal equity and enables cross-entity mobility pricing.
• Performance management methodology — rating scales, calibration, and review cycles aligned across entities.
• Talent review and succession planning process — gives the group visibility of high-potentials regardless of entity.
• HR data schema and reporting format — single employee ID, uniform cost-centers, and shared dimension structure.
• Ethics, anti-harassment, and code of conduct policies — group-wide baseline, non-negotiable.
• Learning & development curriculum for the leadership pipeline — protects group culture and bench depth.

Localize at Entity Level (Indonesian Legal Requirement or Operational Necessity)

• PKB (Perjanjian Kerja Bersama) — each PT entity must negotiate and register its own PKB with Disnaker independently.
• UMK/UMP compliance — each entity applies the minimum wage of its operational kabupaten/kota (e.g., Bekasi vs. Jakarta).
• BPJS contributions — contribution administration is a per-entity legal employer obligation; accounts cannot be merged across entities.
• Payroll cut-off dates — entities may use different cycles based on workforce type (shift, daily, monthly).
• Leave policy nuances — PKB often grants additional entitlements beyond UU Ketenagakerjaan minimums.

The implication is operational, not theoretical. A group that tries to enforce a single payroll cut-off across a manufacturing PT and a corporate PT will either break the manufacturing payroll cycle or create constant exception handling. The hybrid principle accepts variation where the law or operation demands it, and forces standardization where the group has discretion.

Our companion piece on multi-location workforce management explores how this split plays out across geographies within a single entity.

Designing HR Shared Services for a Holding Group

Shared services exist because duplicated transactional work is the single largest source of waste in multi-entity HR. According to the Deloitte 2025 Global Business Services Survey, HR is the #2 most prominent shared services function — present in more than 60% of surveyed enterprise companies. The question for Indonesian groups is not whether to build an HR SSC, but what to place inside it and what to keep at the entity.

What Belongs in Group HR Shared Services

• Payroll processing — where entities have aligned payroll cycles and compatible workforce types.
• BPJS registration and administration coordination — vendor relationship at group level, legal employer remains per entity.
• HR data management and master data maintenance — single source of truth for employee records.
• Recruitment process coordination — employer branding, job posting aggregation, background check vendor management.
• HR reporting and analytics for group leadership — consolidated dashboards for the board and management committee.
• Policy development and legal template management — employment agreement and PKB templates per entity.

What Must Stay at Entity Level

• Day-to-day employee relations and disciplinary processes — requires Disnaker knowledge specific to the entity’s location.
• PKB negotiation and bipartite/tripartite representation — legal standing belongs to the PT, not the holding.
• Local government reporting — Laporan Ketenagakerjaan and Wajib Lapor are filed per legal entity.
• On-site attendance and workforce management for operational sites — production floor reality cannot be run remotely.

Governance of the SSC Model

An SSC without governance becomes a complaints desk. Three artefacts decide whether the model holds:

• A formal HR Service Catalog with SLAs per service type — e.g., payroll run completion within 2 business days of cut-off.
• A defined escalation path from entity HR to SSC to Group HR Director — no informal WhatsApp routing.
• A Group HR Governance Council that meets quarterly, attended by entity HR heads, reviewing policy compliance and group KPIs.

Research from Mercer on HR transformation found that high-performing HR functions are 4x more likely to align HR governance with business strategy, and that HRBPs in those organizations are 9.5x more likely to be seen as strategic partners. The governance charter is what turns an SSC from a back-office cost into a strategic instrument.

Payroll Across Entities: Cut-Offs, PKB Rules, and PPh 21

Payroll is where the multi-entity model is stress-tested every month. Indonesian payroll across a holding group is not a scale problem — it is a parallel-processing problem with per-entity legal obligations, different PKB compensation structures, and PPh 21 calculations that interact across entities for employees with cross-entity roles.

Different Payroll Cut-Off Dates

Manufacturing entities with shift workers often run a 21st-to-20th cycle, while corporate office entities use end-of-month. Group payroll runs cannot be fully synchronized when cut-offs differ. The SSC must operate parallel cycles, with separate approval workflows and disbursement windows per entity, while still feeding a single consolidated cost view to group finance.

PKB Compensation Variations Across Entities

Different PKB agreements mean different salary components, allowance structures, and bonus formulae per entity. A shift premium in a manufacturing PT is not the same as the transport allowance in a services PT. Group HR must maintain a cross-entity compensation matrix to detect inequity and to price internal mobility moves correctly. Tracking PKB expiry dates at group level also prevents the operational shock of multiple renegotiations falling in the same quarter.

PPh 21 Complexity in Multi-Entity Structures

An employee who holds dual roles or receives income from multiple PT entities must be handled carefully under PPh 21 TER. Each entity is a separate taxpayer, which creates a real risk of under-withholding or duplicate calculation if remuneration data is not coordinated. Cross-entity secondments require an explicit inter-company cost-transfer agreement and a clear determination of which entity is the employer of record for tax purposes. This is operational complexity rather than software complexity — and it does not go away with a better payroll engine alone.

BPJS Across Entities

Each PT entity registers independently with BPJS Kesehatan and BPJS Ketenagakerjaan as the legal employer. Group HR can standardize vendor coordination and onboarding workflows, but cannot consolidate BPJS accounts across legal entities. The SSC’s role here is coordination, not consolidation.

For a detailed walkthrough of how cross-entity payroll cycles can be operated in parallel, see our multi-entity payroll guide, and explore the underlying enterprise payroll software capabilities purpose-built for Indonesian groups.

Talent Mobility Across Subsidiaries

Internal mobility is where most Indonesian groups underperform — not because there is no talent to move, but because there is no architecture to move it. The cost shows up indirectly: external hires for roles an internal candidate could have filled, and high-potentials who leave the group because they cannot see a next role within it.

Why Inter-Entity Mobility Stalls in Indonesian Conglomerates

• No cross-entity visibility of talent — each entity’s performance data stays in its own HRIS or in spreadsheets.
• Compensation band mismatches between entities with different PKB structures make pricing a move difficult.
• Entity HR leads are reluctant to release high performers to other subsidiaries when there is no replacement pipeline.
• No formal secondment policy or Inter-Company Services Agreement (ICSA) framework exists at group level.

Mechanisms for Enabling Cross-Entity Mobility

Three legal mechanisms cover most cross-entity moves in an Indonesian holding context. They are not interchangeable — each has different employment, tax, and operational implications.

• Secondment — the employee remains on the origin entity’s payroll, and costs are charged to the receiving entity via inter-company invoice. Requires an ICSA with clear duration and scope.
• Transfer — full employment contract novation to the receiving entity. Triggers termination and rehire obligations under UU Ketenagakerjaan; UPMK and pesangon calculations may apply.
• Dual employment — the employee holds simultaneous employment at two PT entities. Creates complex PPh 21 obligations and should not be used without explicit legal and tax review.

Tax Implications of Inter-Entity Assignments

Secondment cost recharges between PT entities must be structured either as services fees (subject to PPN) or as employment cost recharges — each route has different transfer pricing implications. Where the secondee’s remuneration is partly borne by the receiving entity, each entity must reflect the correct split in its PPh 21 withholding. The technology layer can capture the assignment record and apportion cost; the legal and tax structuring still belongs to specialist advisors.

Groups designing inter-entity moves at scale should review our talent mobility framework for the policy scaffolding that complements the operating model.

Group-Level HR Reporting Consolidation

Consolidated reporting is the test of whether the operating model actually works. If the Group CHRO cannot answer headcount, payroll cost, and attrition questions for the board within a working day, the operating model has failed regardless of how clean the org chart looks.

What the Group CHRO Needs to See

Why Fragmented Systems Make Group Reporting Impossible

When Entity A runs one HRIS, Entity B runs on spreadsheets, and Entity C uses a different payroll vendor, there is no common data schema. Consolidation is done by hand — and it is always at least three weeks late. By the time the group view is ready, the operating decisions it was meant to inform have already been made with worse information.

The Architectural Solution

• A single HRIS with multi-entity architecture — one platform, entity-specific configuration, group-level consolidated dashboard.
• A uniform employee master data schema enforced across all entities at the point of onboarding — not retrofitted later.
• Automated payroll cost allocation by cost center, enabling direct integration with Group Finance reporting.

Group HR teams formalizing their analytics layer can start with our HR analytics guide, and review the consolidated reporting capabilities built into our HRIS for large enterprises and holding groups.

Indonesian Conglomerate HR Patterns

Three archetypes describe most Indonesian conglomerate HR realities today. None is a textbook case — each imposes a different sequencing on the operating model journey.

Common Archetypes

• The diversified group — property, manufacturing, and financial services under one holding. Workforce profiles are entirely different: office professionals, blue-collar factory workers, licensed financial advisors. A pure centralized HR model fails here. Hybrid with strong entity HR leads is the standard.
• The family-business-to-professional-management transition — second or third generation brings in a professional Group HR Director to formalize what was previously relationship-based. Priority: build the data infrastructure before attempting policy harmonization.
• The post-M&A integration — the holding acquires a new subsidiary and must decide how quickly to integrate HR operations. Indonesian practice: 12–24 months is a realistic harmonization timeline given PKB obligations and workforce culture differences.

What Mature Indonesian Holding HR Functions Have in Common

A cross-entity talent review process (at minimum annual) to identify high-potentials for group-level development programs.

A Group HR Director with a seat on the holding management committee — not reporting through a subsidiary CEO.

Centralized payroll processing for entities with compatible workforce types; separate payroll for manufacturing entities under different PKB.

A Group HR data team of 2–4 analysts consolidating monthly headcount, payroll cost, and attrition data for the board.

How Mekari Talenta Supports Multi-Entity HR Operations

Mekari Talenta is designed for the operational reality of Indonesian holding groups: one platform, multiple legal entities, configurable per subsidiary, consolidated at the group level. The architecture supports the Hybrid operating model directly — governance and reporting at the group, execution and PKB-specific configuration at the entity.

For multi-entity payroll, Talenta’s enterprise payroll software handles parallel cycles, entity-specific earning and deduction codes, PPh 21 TER calculation with cumulative reconciliation across entities, and BPJS submission per legal entity — all from a single payroll engine.

Consolidated HR Reporting

Talenta Insights provides group-level workforce dashboards that aggregate headcount, attrition, payroll cost, and attendance data across entities — closing the three-week lag that manual consolidation creates.

Employee Master Data

A single employee profile architecture with entity-level employment records supports secondment tracking and cross-entity movement without duplicating employee records — a prerequisite for any meaningful talent mobility program.

Book a demo with our team to see how Mekari Talenta supports multi-entity Indonesian holding groups — from PT-level payroll and BPJS to consolidated group reporting. Or start a 14-day free trial to explore the platform for yourself. Talk to Mekari Talenta.