A staffing agency arrangement in the Philippines can become your company's employment liability in under 18 months — without a single document changing hands. That is not a hypothetical. It is the mechanics of DOLE Department Order 174, and most founders building Philippine teams have never read it.
- A staffing agency does not automatically transfer employment liability — DO 174's control test determines who DOLE considers the real employer.
- When a staffing arrangement fails that test, workers are deemed regular employees of the client — triggering separation pay, security of tenure, and NLRC exposure for the foreign company.
- Under a true EOR, every statutory obligation is owned by the EOR's Philippine legal entity. The client's exposure is contractual, not statutory.
- The cost difference between getting this right from Day 1 and cleaning it up after a DOLE complaint is not marginal — it is the difference between a compliance line item and a six-figure labor dispute.
The Staffing Agency Pitch Sounds Like EOR — It Isn't
Most Philippine staffing agencies present themselves as managing employment. What they actually do is supply labor under a service contract. Those are legally different things, and the gap between them is where foreign companies get hurt.
Under DO 174, a legitimate staffing arrangement requires two things from the agency: substantial capital (at minimum ₱5 million in paid-up capital for labor-only contracting arrangements, more for certain categories) and genuine control over how the workers perform their work. The capital requirement is the easy part. The control test is where the arrangement breaks down.
Control, in DOLE's reading, means the agency — not the client — directs the manner and method of work. If a US company's VP of Operations is setting daily priorities, reviewing outputs, and running performance conversations with Filipino workers, DOLE's control test points at the client. The agency becomes a conduit, not an employer. And a conduit does not absorb liability.
When the arrangement fails the DO 174 test, the legal consequence is automatic: workers are deemed regular employees of the client company. That triggers security of tenure under Article 294 of the Labor Code, separation pay obligations, and standing to file with the National Labor Relations Commission — all against the foreign principal, not the agency. The signed service contract with the agency does not change this. DOLE looks at the economic and operational reality of the relationship, not the label on the agreement.
Who DOLE Actually Holds Responsible: A FinTech Scenario
Consider a US FinTech that hires 12 Filipino compliance analysts through a Manila staffing agency. The engagement starts as a project — regulatory reporting support ahead of a product launch. Eighteen months in, the analysts are embedded in the company's daily compliance workflow, attending internal Slack standups, reporting to the FinTech's Head of Compliance, and being reviewed on the company's internal performance system. The agency handles payroll processing. That's the extent of its involvement.
Then the agency loses its DOLE registration — a not-uncommon event for mid-market Philippine agencies operating on thin margins. At that point, the FinTech is the employer of record by default. Workers file for regularization. The NLRC issues a notice to the foreign company. Back-pay liability accrues from Day 1 of engagement — not from the date of regularization. Eighteen months of back pay, 13th month contributions, and potential separation pay if the company tries to exit the arrangement.
Under a properly structured EOR, none of that notice goes to the FinTech. The EOR's Philippine legal entity is named as employer on every employment contract. DOLE complaints name the EOR. The client's exposure is defined by its commercial contract with the EOR provider — capped, documented, and governed by a service agreement, not the Labor Code. The Philippine state has a local entity to engage. The foreign company is not that entity.
That is the practical difference between the two models: one puts a Philippine legal entity between the client and DOLE; the other leaves the client exposed with no Philippine presence to absorb the complaint.
The Three Cost Lines That Catch Founders Off Guard
13th month pay. Mandatory under Presidential Decree 851, due by December 24 each year, equal to one month's basic salary. Under a staffing arrangement, who actually funds this depends on the service agreement — and many agencies pass the liability back to the client in the fine print. Read the indemnification clause before assuming the agency absorbs it.
Separation pay. If a worker is regularized — deemed a regular employee of the client — and the client later terminates the engagement, separation pay runs at 0.5 to 1 month per year of service. The clock starts from the original engagement date, not the date of regularization. A worker engaged for three years under a staffing arrangement who is then regularized and let go triggers three years of separation pay liability, not zero.
Statutory remittances. SSS, PhilHealth, and Pag-IBIG contributions are mandatory employer obligations. If the agency defaults on remittances — which happens when agencies hit cash flow problems — the Bureau of Internal Revenue and SSS can pursue the client as the indirect employer under Article 106 of the Labor Code. The agency's default becomes the client's problem.
EOR vs. Staffing Agency: Liability Ownership at a Glance
| Liability Type | Staffing Agency (who owns it) | EOR (who owns it) |
|---|---|---|
| DOLE complaint recipient | Client (if control test fails) | EOR provider |
| 13th month pay funding | Disputed — check service agreement | EOR provider |
| Separation pay obligation | Client (if workers regularized) | EOR provider |
| SSS / PhilHealth / Pag-IBIG remittance | Agency (client exposed if agency defaults) | EOR provider |
| Security of tenure trigger | Client (if engagement exceeds 6 months and control test fails) | EOR provider's entity |
| Philippine legal entity required | No (client has none) | Yes (EOR provides it) |
Under a properly structured EOR, every row in the ownership column reads the same: EOR provider. Under a staffing arrangement, most rows read “client” or “disputed.” That asymmetry is the entire argument for EOR when you are directing the work yourself.
When a Staffing Agency Is the Right Call (and When It Isn't)
Staffing agencies are not inherently problematic. They are problematic when sold as something they are not.
A staffing arrangement is defensible for short-term project work under six months, roles where the agency genuinely controls the work method (on-site facilities management, agency-run call center seats with the agency's own supervisors), and companies that already have a Philippine entity and need sourcing support rather than compliance coverage.
It breaks down for any engagement likely to exceed six months, any role where the client directs the work daily, and any foreign company with no Philippine entity that cannot absorb NLRC exposure. The honest test is simple: if you are telling workers what to do, when to do it, and how to do it — DOLE will say you are the employer. The contract with the agency is not a defense against that finding.
For FinTech and HealthTech companies, the risk compounds. A DOLE complaint against a foreign financial services firm does not stay in the Philippine labor system. It surfaces in due diligence, in regulatory filings, and potentially in conversations with home-country financial regulators. A labor dispute in Manila can become a compliance flag in New York or Singapore. That is not a reason to avoid the Philippines — it is a reason to structure the engagement correctly from the start.
How to Read an EOR Contract Before You Sign It
Not all EOR providers carry equal liability. The critical first question is whether the provider has its own Philippine legal entity — not a “partner network” or a “local affiliate.” If the EOR is contracting through a third-party local entity, there is an extra link in the liability chain that can break exactly when you need it to hold.
Four clauses to locate in any EOR agreement before signing:
- Who is named as employer on the employment contract. It must be the EOR's Philippine entity, not the client and not a generic “local partner.”
- Who is liable for statutory remittances if the EOR defaults. The agreement should explicitly indemnify the client against SSS, PhilHealth, and Pag-IBIG shortfalls caused by the EOR's failure to remit.
- What the termination indemnity cap is and who funds it. Some EOR agreements cap their liability at fees paid in the last three months. Separation pay for a three-year employee can exceed that in a single termination. Know the cap before you need it.
- Whether Philippine labor counsel is on retainer or billed separately. A DOLE inquiry that arrives on a Friday afternoon needs a response within days. “We can refer you to local counsel” is not the same as having a lawyer already briefed on your account.
DOLE enforcement of DO 174 has tightened materially since 2024, with increased audits of foreign-principal arrangements in the IT-BPM sector specifically. The cost of misclassification — back pay, separation pay, NLRC filing fees, and management time — is rising faster than the cost of structuring an EOR correctly from Day 1. The window to fix this cheaply is before the first DOLE notice arrives, not after.
