Contractor or Employee: Not Your Classification

You Don't Get to Decide Who's a Contractor

Here's something that catches a lot of multi-entity founders off guard: you can call someone a contractor in your agreement, pay them on a 1099, and still be wrong. The classification isn't yours to make. It belongs to the jurisdiction where the worker sits.

I've seen this play out firsthand. You hire someone in the UK through your US LLC, structure it as a contractor relationship, and everything looks clean from your side. Then HMRC applies IR35 and decides that person is an employee for tax purposes. Now you have an employment relationship you never intended, in a country where you thought you had no obligations.

Why Multi-Entity Structures Make This Worse

Most multi-entity setups weren't designed. They grew. A US LLC here, a UK Ltd there, maybe a HK holding company layered on top. When entities accumulate like that, nobody stops to ask: "Which jurisdiction's employment law governs this contractor?"

Worker classification isn't an HR detail. It determines who owes payroll tax, who holds liability, and who owns the IP that person produces. Get it wrong across three jurisdictions and you've created exposure in all three.

Every Country Has a Different Test

The same working arrangement produces different legal outcomes depending on where the worker lives.

In the US, the IRS uses a multi-factor test looking at behavioral control, financial control, and the nature of the relationship. The Department of Labor runs a separate "economic reality" test under the FLSA. These two federal tests don't always agree with each other, and state tests (California's ABC test, for example) add another layer.

In the UK, IR35 asks whether the contractor would be an employee if engaged directly. Germany has Scheinselbständigkeit — literally "fake self-employment" — and they're aggressive about enforcing it.

So the same person, doing the same work, under the same contract, can be a contractor in one country and an employee in another. That's not a hypothetical. It happens constantly.

What Goes Wrong When You're Reclassified

When a jurisdiction decides your "contractor" is actually an employee, the consequences stack up fast. Back payments for benefits. Unpaid employer-side payroll taxes. Penalties. And the clock runs backward — you owe for the entire period, not just going forward.

Either party can file IRS Form SS-8 to request a formal determination of worker status. Contractors sometimes file it themselves during tax disputes, which means you might not even see it coming.

In a multi-entity structure, one reclassification can cascade. The entity decision framework maps how these risks propagate across connected entities. And when a cross-border tax audit starts pulling threads, worker classification is usually the first thing they examine.

The IP Ownership Trap

This is the part that keeps me up at night. In many jurisdictions, an employee's work product belongs to the employer by default. A contractor's doesn't — they retain ownership unless a written assignment says otherwise.

Now think about what happens when a contractor gets reclassified as an employee. Does the IP ownership default retroactively change? It depends on the jurisdiction, and the answer is rarely clean. If that contractor built your core product, you may have an ownership dispute on your hands that predates the reclassification.

The IP assignment gap analysis maps how default ownership rules shift by jurisdiction and why agreements that look airtight can still leave gaps.

Your Invoices Tell a Story You Might Not Intend

Every invoice between your entities contains an implicit classification. When a US LLC invoices a UK Ltd for "consulting services" performed by someone who works 40 hours a week exclusively for that entity, the invoice tells one story while the working arrangement tells another.

Authorities in multiple jurisdictions can look at the same invoice trail and reach different conclusions. The US might accept the contractor framing. The UK might not. Germany almost certainly won't.

The documentation gap analysis maps what authorities actually look for when they examine these arrangements. The gap between what founders document and what authorities expect is usually wide.

Classification and Tax Residency Compound Each Other

Worker classification feeds directly into tax residency. A contractor working from Germany on behalf of your US LLC can create a permanent establishment there without anyone realizing it. If German authorities then reclassify that contractor as an employee, you've simultaneously established taxable presence in Germany.

Two separate exposures, triggered by a single working arrangement. And when different parts of your structure tell different stories to different institutions, it gets worse.

What You Can Actually Do About This

The honest answer: if you're hiring across borders, you probably can't manage classification yourself. Every jurisdiction runs different tests with different penalties and different enforcement attitudes. Keeping track of all of them while actually running a business isn't realistic.

This is exactly why Employer of Record services exist. The Deel vs Oyster vs Remote comparison breaks down how each one handles classification on your behalf. They take on the employer liability in the worker's jurisdiction, which is the cleanest way to eliminate the risk.

For consultants whose own work crosses borders, the permanent establishment risk analysis maps how physical presence in a client's country creates tax obligations that misclassification compounds.

---

Same Worker, Three Different Outcomes

Key Takeaways

• The jurisdiction where the worker sits determines their classification, not your contract or your intent. The same person can be a contractor in the US and an employee in the UK.
• Reclassification is retroactive. You owe back taxes, benefits, and penalties for the entire engagement period.
• IP ownership defaults flip depending on contractor vs. employee status. A reclassification can retroactively muddy who owns the work product.
• Classification and permanent establishment compound each other. A reclassified employee in a foreign jurisdiction can simultaneously create taxable presence there for your entity.

References

• IRS — Independent Contractor (Self-Employed) or Employee? — IRS multi-factor classification test
• IRS Form SS-8 — Determination of Worker Status — Request for official worker status determination
• DOL — Misclassification of Employees as Independent Contractors — Federal enforcement under the FLSA
• UK HMRC — Understanding Off-Payroll Working (IR35) — UK rules for contractor vs. employee determination
• IRS — 1099-NEC Instructions — Reporting requirements for non-employee compensation
• OECD — Model Tax Convention, Article 15 — International framework for employment income taxation

Check your risk profile →