Multi-Entity HRIS for Philippine Holding Companies: Managing Multiple TINs Under One System

The problem with managing group payroll in separate systems

A Philippine holding company with five subsidiaries typically has five separate BIR TINs, five SSS employer numbers, five PhilHealth employer IDs and five Pag-IBIG employer IDs. Each entity has its own DOLE obligations, its own payroll register, its own alphalist due in January.

Companies that run each entity on a separate HRIS — or worse, on separate spreadsheets — pay the administrative cost five times over: five payroll runs to approve, five R3 reports to file, five alphalists to reconcile, five sets of employee records to maintain.

A multi-entity HRIS reduces this to one system with multiple companies inside it.

What makes multi-entity different from multi-branch

Multi-branch means one company with offices in different locations. Employees belong to one legal entity. One TIN. One SSS employer number. One alphalist. The HRIS needs to track which office each employee works at, but payroll and compliance reporting roll up to one company.

Multi-entity means separate legal companies. A subsidiary is a distinct legal person under Philippine law. It has its own TIN, its own SEC registration, its own DOLE establishment number. Employees of Subsidiary A are not employees of Subsidiary B even if both are owned by the same holding company.

An HRIS that cannot separate entities cleanly produces alphalists with the wrong employer TIN, SSS R3 reports that mix employees across companies, and pay registers that do not match the legal entity's books.

Common group structures in the Philippines

What a multi-entity HRIS needs to handle

Separate employer registrations per entity. Each company's SSS employer number, PhilHealth employer number, Pag-IBIG employer ID and BIR TIN must be stored and used correctly when generating remittance reports. An alphalist filed with the holding company's TIN instead of the subsidiary's TIN is an incorrect filing.

Independent payroll runs per entity. Company A's payroll must be approvable and lockable independently of Company B's. A delay in finalizing Company B's payroll should not block Company A from running.

Separate leave and attendance policies per entity. Two subsidiaries may have different leave entitlements, different holiday schedules (if they operate in different regions or sectors) and different overtime policies. The HRIS must enforce each entity's rules for its own employees.

Consolidated reporting across the group. After each entity runs its own payroll independently, HR leadership at the holding company level needs to see the group headcount, total payroll cost and turnover metrics in one view — without having to log into five different systems.

Inter-company transfers. When an employee moves from Company A to Company B, the employee's history, 201 file and leave balances must transfer cleanly. The government IDs stay the same; what changes is the employer TIN. The transfer must be recorded correctly for both companies' alphalists: Company A issues a BIR Form 2316 for the months the employee worked there; Company B picks up from the transfer date.

Role access scoped to entity. An HR officer of Company A should see only Company A's employees. A group HR director may need read access across all entities. Access control must be configurable at the entity level, not just at the company-wide level.

BIR compliance for multi-entity groups

Each entity files its own BIR Form 1604C (alphalist) by January 31 of the following year, covering only the employees who worked for that entity during the year. An employee who transferred mid-year appears in two alphalists: one for each employer, each covering the months of employment.

For the year-end tax adjustment, each employer adjusts based on compensation paid by that employer only. If an employee worked for two entities in the same year, neither entity has visibility into what the other paid. The employee is responsible for filing their own annual income tax return (BIR Form 1700 or 1701) to consolidate income from multiple employers. This is one reason employees who transfer mid-year are tagged as "non-substitution filing" on their Form 2316.

SSS, PhilHealth and Pag-IBIG for multi-entity groups

Each entity remits contributions independently under its own employer number. An employee who transfers between entities in the same group must be reported as separated by the old employer (via R1A) and as a new hire by the new employer.

Contribution continuity for the employee is not disrupted — their individual SSS, PhilHealth and Pag-IBIG numbers stay the same — but the employer changes. A multi-entity HRIS should automate the R1A separation record for the old entity and the new hire record for the new entity when a transfer is processed.

Practical questions to ask an HRIS vendor

When evaluating whether a system can handle your holding company's needs:

1. Can each entity have its own TIN, SSS number, PhilHealth ID and Pag-IBIG ID? Ask to see how these are stored separately per company.

2. Can payroll be locked per entity independently? A group payroll run that locks all entities together is a limitation, not a feature.

3. How does the system handle an inter-company transfer? Ask for a demo of the transfer flow and what records it produces for the old and new entity.

4. Can I generate a consolidated headcount and payroll cost report across all entities? This is the group-level view the holding company CFO or CHRO needs.

5. How are government reports (alphalist, R3, RF-1, MCRF) generated? They must be generated per entity, not for the group as a whole.

6. Can access be restricted so Company A's HR cannot see Company B's employees? Entity-level access control is essential for data privacy compliance.

Minimum wage complexity in multi-entity groups

Philippine minimum wage rates are set by region and, within some regions, by sector (agriculture, non-agriculture) and establishment size. A holding company with subsidiaries in NCR, Cebu and Davao faces three different regional minimum wage orders. A subsidiary in the agricultural sector faces different rates from one in the services sector.

The HRIS must store the applicable minimum wage rate per entity and apply it when computing whether employees are minimum wage earners — which affects their withholding tax treatment.

OneHRIS and the Group of Companies module

OneHRIS supports multi-entity setups through its Group of Companies module. Each entity in the group is configured as a separate company with its own government registration numbers, payroll policies, leave rules and holiday calendar. Payroll runs are independent per entity. Government reports (SSS R3, PhilHealth RF-1, Pag-IBIG MCRF and the BIR alphalist) are generated per entity using that entity's employer numbers.

Inter-company transfers are handled as a separation from the old entity and a new hire in the new entity, with the employee's 201 file and history preserved across both.

Group-level reporting — consolidated headcount, payroll cost by entity and turnover trends — is available to users with group-level access, while entity HR officers see only their own company's data.

For more on government reporting, see generate the BIR alphalist (Form 1604C Annex A) and generate government contribution reports.