Payroll, HR & labor compliance
Payroll for multiple branches and companies in the Philippines
How to run payroll across many branches and legal entities: separate employers, regional wages, transfers, access control and consolidated reporting.
Running payroll for many branches or several companies is a different problem from running payroll for one office. Each legal entity is a separate employer for SSS, PhilHealth, Pag-IBIG and the BIR. Branches in different regions may follow different regional minimum wages and local holidays. Employees transfer between branches and companies mid-cutoff. And management still wants one view of total labor cost.
This guide covers the structure, controls and system capabilities that make group payroll work.
Structure: employers, branches and pay groups
Model your organization in three layers:
| Layer | What it controls | Example |
|---|---|---|
| Employer (legal entity) | Government registrations, TIN, statutory reports, bank accounts | ABC Retail Corp., ABC Logistics Inc. |
| Branch or location | Regional wage rules, local holidays, cost center, approvers | Cebu IT Park store, Davao warehouse |
| Pay group | Frequency, cutoff calendar, pay rules | Monthly-paid staff, daily-paid store crew |
Every employee belongs to exactly one employer, branch and pay group at any time, and changes are effective-dated.
Centralized or decentralized?
| Model | Strengths | Risks |
|---|---|---|
| Central payroll team for all companies | Consistent rules, specialized staff, easier audits | Bottlenecks if inputs from branches are late |
| Payroll per company | Close to local operations | Inconsistent policies, duplicated effort, harder consolidation |
| Hybrid: central processing, branch inputs | Branches own attendance and approvals; head office owns computation | Needs clear deadlines and good systems |
Most medium and large groups land on the hybrid model. Branch HR and supervisors approve attendance and requests; a central team computes, reviews and files.
Regional wages and local holidays
Minimum wages are set by Regional Tripartite Wages and Productivity Boards and differ across regions and sometimes by sector and establishment size. When a wage order takes effect:
- Identify affected branches and employees.
- Update rates with the correct effective date.
- Recompute any related items, such as allowances tied to the minimum wage.
- Verify the first payroll after the change for every affected branch.
Local special non-working days apply only to branches in that city or province. Assign them in the holiday calendar per branch, not company-wide. See holiday pay rules.
Transfers between branches and companies
- Branch transfer within one company: the employer does not change; cost center, approvers and possibly wage rules do. Split the cutoff by effective date.
- Transfer to another company in the group: legally a separation from one employer and hiring by another. The first employer issues BIR Form 2316 and settles final pay items according to group policy; the second includes previous compensation in annualization. Statutory remittances move to the new employer.
Access and confidentiality
Payroll data is among the most sensitive data a company holds. Configure role-based access so branch HR sees only their branch, company HR sees their company, and only designated head-office roles see group-wide data. Log access and changes. Our guide on the Data Privacy Act and business systems covers the principles.
Group reporting
Management usually needs:
- Labor cost by company, branch, department and pay component
- Headcount and turnover by location
- Overtime and night differential trends by branch
- Statutory remittance status by employer and month
Produce these from the payroll system rather than by combining spreadsheets, so numbers match the registers.
Checklist for a multi-entity payroll system
- Separate employer setups with their own statutory reports and filings
- Branch-level wage rules, holiday calendars and approvers
- Effective-dated transfers with automatic cutoff splitting
- Role-based access by company and branch
- Consolidated management reports without merging legal records
- One employee record across HR, timekeeping and payroll
Cirquolus supports one or several companies with multiple branches, module selection and page permissions. Cirquolus Payroll connects with HRIS and timekeeping so group payroll runs from one set of employee records.
Frequently asked questions
Can one payroll system handle several companies?
Yes, if it keeps each employer's registrations, filings and reports separate while letting authorized users see consolidated figures.
How do I handle employees transferring between companies in a group?
Treat it as separation from one employer and hiring by another for statutory and tax purposes. Issue Form 2316 from the first employer and include it in the second employer's annualization.
How are different regional minimum wages handled?
Assign each branch to its region and apply wage orders by branch with effective dates.
Should branches run their own payroll?
Most groups get better accuracy with branches owning attendance and approvals, and a central team owning computation, review and filings.
Bring this workflow to a Cirquolus demo.
Show us your current process, companies and branches. We will map it to the modules you need and propose a realistic rollout.