Contractor or Employee in the Philippines? The Label Won’t Save You
An Australian law firm wrote "independent contractor" into its agreement 52 times. The Fair Work Commission read past every one of them, ruled the worker an employee, and ordered the firm to pay her out. If you hire Filipino talent directly, the gap between the word on the page and the substance of the work is exactly what an employer of record in the Philippines is built to close. Here's how the case fell apart, an interactive way to test your own arrangement, and where the safer structure sits.
The short version
- A written "independent contractor" label doesn't decide the relationship — the contract's real rights and duties do, and since 2024, so does how the work is actually performed.
- In Pascua v Doessel, a Philippines-based paralegal was found to be an employee, not a contractor. The employer's appeal was refused, and she was awarded A$10,800 — about 15 weeks' pay — for unfair dismissal.
- The risk runs on two fronts at once: reclassification under Philippine law, and the reach of a foreign company's employment law.
- An employer of record (EOR) settles the question in advance — the worker is a correctly documented local employee from day one, and you engage the EOR as a client.
The agreement said "contractor." The Commission read the fine print.
Joanna Pascua worked from her home in the Philippines as a legal assistant for MyCRA Lawyers, a Queensland credit-repair firm run by Doessel Group. She was engaged on 21 July 2022 under an "Independent Contractor's Agreement," paid A$18 an hour, invoiced weekly, and allocated work daily. She did the job for roughly 20 months. On 20 March 2024 the firm ended the engagement by email, alleging she had copied company and client information to a personal drive — which she denied. She filed for unfair dismissal in Australia.
The firm's defence came in two parts: she wasn't an employee, so the Act didn't cover her; and she worked in the Philippines, so the Commission had no business hearing it. Representing herself, Ms Pascua argued the opposite. The first question the Commission had to settle was the threshold one — employee, or contractor? Everything else depended on the answer.
"independent contractor"
"employee"
The Commission counted the substance, not the synonyms.
At first instance the Deputy President found she was an employee — [2024] FWC 2669. The firm appealed; the Full Bench refused permission to appeal and let the finding stand ([2025] FWCFB 43). The "she's a contractor" objection failed, twice. The merits hearing followed, and the firm was ordered to pay compensation. The label did no work at all.
For anyone hiring offshore on a contractor basis, that's the unsettling takeaway: the firm did the thing most companies assume is enough — it had a written agreement, it called the arrangement contracting, it paid by invoice — and none of it held. The protection people believe they're buying with a contractor template is largely imagined. What actually decides the outcome is the shape of the working relationship, which is why the rest of this guide focuses on that, and on the one structure that takes the question off the table.
Why the label didn't matter: the test the High Court set in 2022
For years, telling an employee from a contractor meant weighing a long list of factors about the day-to-day relationship. In 2022 the High Court narrowed that in two decisions — Personnel Contracting [2022] HCA 1 and Jamsek [2022] HCA 2. Their rule: where the relationship is captured in a comprehensive written contract that isn't a sham, you characterise it from the rights and obligations the contract actually creates, not from a loose review of how things played out, and certainly not from the name on the cover.
There's a logic to that. A contract both sides signed is the clearest evidence of what they agreed, so the courts start there rather than re-litigating every day of the relationship. But the approach has limits the High Court was careful to keep. It applies where the agreement is genuinely comprehensive and in writing, and it doesn't rescue a contract that's a sham — a document built to disguise the true relationship. Where the writing and the reality diverge, the reality can still win. A label is only ever as strong as the rights and duties sitting beneath it, which is why this firm's 52 careful repetitions bought it nothing.
The question underneath the test
Strip away the label and one question decides it: was the person carrying on their own business, or working inside someone else's? Courts look for the markers of a real enterprise — a genuine right to delegate the work, control over how it's done, providing your own tools, and taking on profit and risk. No single factor is decisive; the overall picture is.
A label that contradicts that picture carries almost no weight. As the Commission put it in this case, work done to another's direction, inside their operation, reads as employment — not an independent business.
The Deputy President applied exactly that test and walked the clauses. Three of them did the most damage.
She had to do the work herself.
No genuine right to delegate or subcontract. A real contractor can put someone else on the job; an employee is hired for their personal service. The contract bound her, personally — a hallmark of employment.
Control ran through the whole day.
The contract set daily output expectations and key performance targets, required her to notify a supervisor if she couldn't finish, and obliged her to take on ad-hoc duties as directed. Administration, chasing clients, and "duties as required" are the texture of being managed, not engaged.
"Salary all inclusive as a Full Time Employee."
The agreement's own words cut against its cover. And at A$18 an hour she sat below the Legal Services Award rate for the work — which the Commission read as a sign she wasn't a specialist contractor commanding a premium, but a staff member being paid a wage.
No single clause was fatal on its own; the finding came from the weight of them together. That's the feature of the test most easily missed — you can point to a delegation clause here or an independence recital there and still lose, because the decision-maker stands back and asks what the document, read as a whole, actually creates. A handful of contractor-flavoured phrases can't outweigh a structure that, in substance, describes a managed employee.
The signals that turn a "contractor" into an employee
The tell was never one clause; it was the accumulation. Drawn from this case specifically, here is what read as employment — and law firms writing on the decision catalogued the same cluster: control, integration, exclusivity, and a below-award rate.
A phone account that displayed the Queensland law office's number, so callers saw an Australian line.
An email signature identifying her as a MyCRA Lawyers paralegal — she presented as the firm, not as her own business.
Work allocated and reviewed every day, against daily targets.
Close supervision by the firm's principal and its practice manager.
Pay set below the relevant Australian award rate.
That last point is the sharp one. The discount wasn't just thrifty — it became evidence. A rate well under the award read as a sign she wasn't an outside specialist at all. The saving the firm thought it was banking turned into an argument against it.
Contractor vs employee: the full comparison, and a test for your own setup
The signals above came from one case. The table below generalises them into the factors that actually separate an independent contractor from an employee — filter by what you're unsure about, and tap any row for what a tribunal reads into it. Then run your own arrangement through the quick checker underneath to see where it sits.
Interactive comparison
Independent contractor vs employee
Tap a row for what a tribunal reads into it.
| Factor | Independent contractor | Employee |
|---|
Risk checker
Is your "contractor" actually an employee?
Answer about the arrangement as it works in practice — not what the contract says.
Answer all seven to see your misclassification risk.
A guide, not legal advice — classification turns on the full facts of your arrangement.
Want the pay side of the picture too? The salary tool compares Philippine and Australian rates for the same role — useful context, since a below-market rate is one of the signals above:
The other half of the story: when the claim doesn't attach
Here is the part that gets missed. Australian law could reach Ms Pascua at all because of structure, not geography: she held a contract directly with an Australian business, which is what let the Commission treat her as an "Australian-based employee" of an "Australian employer" under the Fair Work Act. Change the structure and the result changes with it.
Outsourcing providers point to the mirror-image situation from the same period: a full-time worker placed with an Australian company, but employed through a Philippine firm, who could not pursue a Fair Work claim — because there was no direct employment relationship with the Australian business to anchor it. Same kind of work; entirely different exposure. That gap — a direct contract on one side, employment by a separate local entity on the other — is the whole basis of the employer-of-record model, and it's the reason the structure matters as much as the paperwork. Whether Australian law reaches a worker 5,000 km away is its own slippery question, which we unpack in does australian employment law apply to overseas workers.
The lesson isn't that one worker was lucky and the other wasn't — it's that the outcome tracked the structure each was placed in. Pascua's direct contract with an Australian business is what gave the Commission something to grip; the other worker's employment by a separate Philippine entity is what left nothing to attach to. Nothing about the work itself decided it. That's an uncomfortable truth if you're relying on a contractor agreement, and a reassuring one if you've put the right entity between your company and the role.
What this means if you hire Filipino "contractors"
Two systems can reach the same arrangement, and the Philippine one runs its own test. Under Philippine law, whether someone is an employee turns mainly on the four-fold test, and it's worth seeing each element, because they map almost exactly onto the signals in Pascua.
First, selection and engagement: did you choose and hire the person directly? Second, payment of wages: do you pay them a regular wage, rather than settling invoices for delivered results? Third, the power of dismissal: can you end the relationship and discipline them as you would an employee? And fourth — the strongest factor — the power of control: do you direct not just what is to be done, but how, when and where it's done? A complementary economic-reality test asks whether, in practice, the worker depends on your business for their livelihood. Apply those four questions to a full-time, supervised, integrated remote role and "contractor" becomes very hard to sustain.
There's a second trap on the Philippine side: labor-only contracting. If an arrangement really just supplies manpower for your core business, and the contractor lacks substantial capital and genuine control over the work, the law can treat you — the principal — as the real employer, with the contractor reduced to a mere agent (Labor Code arts. 106–109; DOLE Department Order 174). The label on the invoice doesn't save the arrangement; the substance controls, just as it did across the Tasman.
Run a familiar arrangement through the four questions. Suppose you engage a full-time virtual assistant in Cebu: you interviewed and chose them (selection), you pay them a fixed amount every fortnight rather than against project invoices (wages), you can end the engagement at will (dismissal), and you set their hours, assign their tasks each morning and review the output (control). That's four for four — and the "independent contractor" heading on the agreement is doing none of the work the four-fold test actually weighs. Now contrast a brand designer you brief for a single launch, who quotes a project fee, works to their own schedule with their own tools, and has three other clients that month: the same four questions point the other way. The test isn't trying to trap genuine freelancers; it's built to catch employment wearing a contractor's coat.
What getting it wrong actually costs
Misclassification is cheap right up until it isn't, and the bill is usually retrospective — it reaches back over the whole engagement, not just the day the question is raised. On both sides of the arrangement, the costs stack.
On the Philippine side
If a "contractor" is found to be an employee, they generally become a regular employee with security of tenure, which changes everything about how the relationship can end. The employer can be liable for the differential between what was paid and what was owed — unpaid wage and benefit entitlements, pro-rated 13th-month pay, service incentive leave — plus arrears on SSS, PhilHealth and Pag-IBIG contributions, often with penalties. And if the engagement was ended the way a contract is ended, with no just or authorized cause and no due process, that can amount to illegal dismissal, exposing the employer to reinstatement with full back wages, or separation pay in lieu. Where labor-only contracting is involved, the principal can be held solidarily liable alongside the contractor.
On the foreign-company side
For an Australian business, reclassification can mean back-pay to the correct award rate, unpaid leave and other National Employment Standards entitlements, and unpaid superannuation recovered through the superannuation guarantee charge. Deliberately disguising employment as contracting can also trigger sham contracting penalties under the Fair Work Act, on top of any unfair dismissal remedy. In Pascua, that remedy was A$10,800 — about 15 weeks' pay — and that was only the dismissal payout, before the management time and legal fees of fighting the case. Set against a rate chosen to save money, the economics invert quickly.
What makes the exposure dangerous is its shape. Because reclassification reaches back across the engagement, a role you ran for two years carries two years of differentials, arrears and accrued entitlements — all crystallising at once, and usually at the worst moment, when someone has already been let go and has every reason to test it. None of it shows up on a budget line until it lands. The longer a misclassified arrangement runs, the larger that contingent bill quietly grows in the background.
Why careful companies still get this wrong
Most misclassification isn't reckless — it's the product of reasonable-sounding assumptions that don't survive contact with the law. A founder downloads a solid contractor template and assumes the wording does the protecting. A finance lead reasons that paying against invoices, with no payslip and no withholding, must make the person a contractor by definition. Someone concludes that because the worker sits in another country, their own employment law can't possibly apply. And almost everyone underestimates drift: a role that genuinely began as a short, independent project quietly hardens, month by month, into a full-time, supervised seat on the team — without anyone revisiting the paperwork that described the original arrangement.
Each of those beliefs is wrong in the same direction. The template can't change the substance; invoicing is one small factor among many; distance is about structure, not geography; and the relationship that gets tested is the one that exists today, not the one you signed eighteen months ago. The companies that avoid the trap aren't the ones with the most elaborate contracts — they're the ones who matched the structure to the reality of the work from the start.
How an employer of record in the Philippines removes the question
A misclassification fight only happens when the classification was left open. An employer of record settles it in advance. With Zero-Ten Park as the EOR, your hire is a properly documented Filipino employee of our local entity from day one — SSS, PhilHealth, Pag-IBIG, 13th-month pay and BIR withholding all handled — while you direct their work as our client.
Because they're employed by our Philippine entity and not by you, the "Australian employer" chain that pulled Pascua under the Act doesn't attach — and the Philippine classification is settled too, because they're a genuine local employee with full statutory benefits. There's no "is my contractor secretly an employee" landmine, because the answer is built in: they're an employee, employed correctly, locally.
It's one of three ways to put a Filipino on your team — compared in full in our guide to employer of record Philippines vs contractor vs your own entity. Our teams sit in real offices at Cebu IT Park, Mandaue and Makati — not a mailbox.
If the checker flagged your arrangement, here's how to fix it
A high-risk result isn't a crisis; it's a prompt. There are really only two clean ways to resolve a "contractor" who is functioning as an employee, and which one fits depends on the role.
The first is to make the arrangement genuinely independent — and mean it in practice. That means stepping back from directing the day-to-day method, allowing a real right to delegate, dropping any expectation of set hours and exclusivity, and treating the person as the outside business they're billed as. For a one-off project or a specialist who serves several clients, that can be entirely legitimate. For a full-time role embedded in your team, it usually isn't realistic, because the control is the whole point of the hire.
The second is to employ the person properly — which, for a company without a Philippine entity of its own, means an employer of record. Converting an at-risk contractor into a compliant EOR employee is routine: the EOR engages them as a documented local employee going forward, the statutory benefits switch on, and the misclassification question disappears prospectively. You keep the same person doing the same work; you simply put the relationship on the footing it was always going to be tested against.
Either way, the move is forward-looking. Converting a contractor doesn't unwind the past on its own, so where an arrangement has run long or hot, it's worth taking advice on the historical exposure at the same time — but the conversion stops the clock and removes the risk from that point on. In practice, most companies that reach a high-risk result and don't have a genuine, bounded project on their hands choose the EOR route, because it's the only option that delivers a compliant employee without standing up a Philippine entity first.
Get a compliant quote in 24 hours
Tell us the role. We'll send back an EOR proposal — salary, statutory costs and our fee on one clear line — within 24 hours, and your "contractor" question goes away.
Frequently asked questions
Does calling someone an independent contractor make them one under the law?
No. Where the agreement is wholly in writing, the Fair Work Commission and the courts read the relationship from the contract's real rights and obligations, following the High Court's 2022 rulings and, since August 2024, a statutory test focused on substance and how the work is actually performed. A label that contradicts the substance carries almost no weight.
What is the four-fold test in the Philippines?
Philippine law mainly asks four things to decide if someone is an employee: who selected and engaged them, who pays their wages, who can dismiss them, and who controls how the work is done. Control is the strongest factor. A complementary economic-reality test asks whether the worker depends on the business for their livelihood.
What separates a contractor from an employee in practice?
Independence. A genuine contractor controls how they work, can delegate, uses their own tools, takes on profit and risk, and serves their own clients. An employee follows your direction, works personally on set hours, is integrated into your team, and is paid a wage. The comparison tool above lays out each factor side by side.
What is "labor-only contracting" and why does it matter?
In the Philippines, if a contractor merely supplies workers for the principal's core business without substantial capital or genuine control, the law can treat the principal as the real employer (Labor Code arts. 106–109; DOLE D.O. 174). The consequence is regularisation and liability for wages, benefits and statutory contributions — which is why structuring matters.
Can an Australian company be on the hook for a Filipino it hired as a "contractor"?
Potentially on two fronts. Under Philippine law, a controlled, integrated, ongoing role can be treated as employment whatever the paperwork says. Separately, Australian employment law can reach an offshore worker where the contract was formed in Australia — the question raised in Pascua.
What does misclassification cost if we get it wrong?
On the Philippine side, it can mean regularisation, back wages and benefit differentials, statutory contribution arrears, and illegal-dismissal exposure if the role was ended without cause or process. On the Australian side, back-pay, unpaid entitlements and superannuation, possible sham-contracting penalties, and an unfair dismissal remedy. The costs are retrospective across the whole engagement.
How does an employer of record prevent misclassification?
The EOR is the legal employer. The worker is engaged as a local employee with full statutory entitlements, and you contract with the EOR for their services. There's no misclassification question because the classification is correct from day one — on both the Australian and the Philippine side.
Can we convert an existing contractor into an EOR employee?
Usually yes, and it's a common reason companies move. The EOR engages the person as a properly documented local employee going forward, which switches on statutory benefits and resolves the misclassification question prospectively. Discuss the transition with the provider.
In the Pascua case, did the worker win compensation?
Yes, ultimately. After the Commission confirmed she was an employee and the appeal was refused, her unfair dismissal claim was heard on its merits: in [2025] FWC 1833 she was found to have been unfairly dismissed and awarded A$10,800 — about 15 weeks' pay. The broader question of how far Australian law reaches other offshore workers was not settled by the case.
General information, not legal advice. The Pascua decisions are summarised here for general guidance only; for your situation, get advice from a qualified Philippine or Australian employment lawyer. Primary sources: [2024] FWC 2669 · [2025] FWC 1833; appeal refused in [2025] FWCFB 43. Philippine classification principles derive from the Labor Code and DOLE Department Order 174. Last updated 23 June 2026.
