The most expensive line item nobody puts on a startup pitch deck is the back-payroll bill from misclassifying a long-term contractor. Headline misclassification cases against companies like Uber, FedEx, and Lyft have produced settlements running into nine figures over the past decade — companies with armies of employment lawyers in-house who still ended up writing massive checks. For a 12-person startup hiring its first overseas senior engineer as "a contractor," the same underlying legal logic applies, just with smaller numbers — until the IRS, the DOL, or the state attorney general comes asking.
This post is the practical answer to: when is a contractor relationship genuinely a contractor relationship, when is it really employment, and when does an Employer of Record (EOR) make the question moot? Aimed at US founders and CFOs evaluating their first one to ten cross-border hires.
We covered what an EOR actually does and when you need one in a separate post. This one is the more specific question: assuming you're not opening a foreign entity, when does the contractor structure work, and when does it create real legal exposure?
The three tests that matter
US worker classification doesn't run on one test. It runs on three, and they can disagree.
Test 1: The IRS Common Law test
The IRS uses a common-law test that looks at three categories of evidence (IRS source):
- Behavioral control — does the company direct how the worker does the work? When? Where? With what tools? Following what process?
- Financial control — who provides the equipment, who bears the financial risk of the work, can the worker work for other clients, does the worker have a real opportunity for profit and loss?
- Type of relationship — written contract terms (though these aren't dispositive), provision of benefits, permanence of the relationship, whether the work is a key part of the company's regular business.
No single factor is determinative. The IRS weighs the totality of evidence. A worker who is "officially a contractor" by contract but works 40 hours a week exclusively for one client, takes direction from that client's manager, uses that client's laptop and Slack, has worked for that client for two years, and bills by the hour with no opportunity for profit beyond hours worked — that worker is almost certainly an employee in the IRS's view, regardless of what the contract says.
Test 2: The DOL six-factor "economic reality" test (FLSA)
The Department of Labor governs the Fair Labor Standards Act (minimum wage, overtime, recordkeeping). For FLSA purposes, the DOL's Final Rule effective March 11, 2024 restored an "economic reality" test using six factors with no preset weights (Federal Register publication):
- Opportunity for profit or loss depending on managerial skill — can the worker increase earnings through their own judgment, not just by working more hours?
- Investments by the worker and the potential employer — does the worker have meaningful capital investment in their own business?
- Degree of permanence of the work relationship — indefinite or open-ended relationships lean toward employment.
- Nature and degree of control — including reserved rights of control, not just exercised ones.
- Extent to which the work performed is an integral part of the potential employer's business — core revenue-generating work leans toward employment.
- Skill and initiative — does the worker use specialized skills in a way that demonstrates business-like initiative?
The bottom line of the DOL test, in the DOL's own words: "Economic dependence is the ultimate inquiry, meaning that a worker is an independent contractor as opposed to an employee under the Act if the worker is, as a matter of economic reality, in business for themself" (DOL FAQ).
A note for 2026: a Notice of Proposed Rulemaking was issued in February 2026 to revisit this framework again. The 2024 rule remains in effect at the time of writing; consult counsel for the current status if you're reading this much later than May 2026.
Test 3: California's ABC test (and other state variants)
If your worker is in California — or if you're a California company hiring anywhere — you also face the ABC test, codified by California AB 5 (signed September 2019, in effect since January 2020, amended by AB 2257). Under the ABC test, a worker is presumed to be an employee unless the hiring entity proves all three of:
- A: The worker is free from the control and direction of the hiring entity in connection with the performance of the work.
- B: The worker performs work outside the usual course of the hiring entity's business.
- C: The worker is customarily engaged in an independently established trade, occupation, or business of the same nature as the work performed.
Prong B is the killer for most startup engineering relationships. If you're a software company hiring a software engineer, that engineer's work is the usual course of your business. Prong B fails. ABC test fails. Worker is an employee.
AB 5 has carve-outs (a long list of professions, some Business-to-Business safe harbors), but for cross-border tech engineering hires they generally don't help. Other states (Massachusetts, New Jersey, Illinois, Virginia, Vermont, others) have adopted varying versions of the ABC test for state-level wage/UI purposes (California DIR overview).
Where the tests usually agree, and where they disagree
The three tests agree more than they disagree on the obvious cases:
- Clear contractor: A freelance designer who builds three logos a month for you, also has six other clients, charges per project not per hour, works from her own studio, uses her own software, and bills you when finished. All three tests: contractor.
- Clear employee dressed as contractor: A "contractor" who works 40 hours/week exclusively for you, takes daily direction from your engineering manager, uses your laptop, attends your standups, has been with you 18 months. All three tests: employee.
Where they disagree is the middle:
- A part-time embedded engineer who works ~20 hours/week for you, has two other concurrent clients, but receives daily direction during your overlap. The IRS test might lean contractor (multiple clients, profit opportunity); the DOL test depends on the permanence and control mix; the California ABC test might fail prong B regardless.
- A fractional CTO who advises you 10 hours/week, has multiple clients, sets her own schedule, makes architectural decisions independently. IRS: contractor. DOL: contractor. California ABC: probably contractor (provided she's not directing core operational work).
The honest takeaway: if you're trying to thread a needle and the relationship is genuinely close to employment, the tests will mostly catch you. The cost of misclassification grows with the duration and the headcount, which means startups often get away with it for the first few months and then discover the problem when they raise a Series A and a diligence accountant flags the contractor invoices.
What misclassification actually costs
When a worker is reclassified from contractor to employee — whether by the IRS, the DOL, a state department of labor, or a private lawsuit — the typical bill includes:
- Back federal payroll taxes — both the employer's 7.65% (Social Security + Medicare) and the employee's 7.65% that the company should have withheld. Plus penalties and interest. Going back up to the statute of limitations (typically 3–6 years federally, longer in some cases).
- State unemployment insurance back-payments, plus state-level penalties.
- State income tax withholding that should have happened.
- Workers' compensation premiums retroactively due.
- FLSA exposure — if the misclassified worker should have been overtime-eligible and worked hours that would have triggered overtime, back-pay for overtime owed. The DOL publishes enforcement data: hundreds of millions in back wages recovered annually.
- State labor code penalties — these are jurisdiction-specific. The California DIR lists civil penalties for willful misclassification under Labor Code section 226.8 (per-violation amounts; consult the current schedule). Other states (New York, New Jersey, Massachusetts, Illinois) have their own penalty regimes. The pattern across states is the same: per-violation penalty × number of violations × duration → headline figures that can dwarf the back-tax bill.
- Private right of action — in California and several other states, the misclassified worker can sue for unpaid wages, missed meal/rest breaks, and other Labor Code violations, with attorneys' fees shifted to the employer.
For a single misclassified contractor at $80K/year for two years, the total bill (back taxes + penalties + interest) can land in the $50K–$150K range federally + state, before any private lawsuit. For ten misclassified contractors at $100K/year for three years, the math gets ugly fast.
The defendable structure isn't "don't get caught." The defendable structure is: be a real contractor relationship, or be a real employment relationship.
How an EOR resolves the question
The EOR doesn't change the underlying tests. It changes the answer to them by changing the relationship.
When you engage a worker through an EOR:
- The worker is a W-2-equivalent employee of the EOR in the worker's country. The relationship between the worker and the EOR is straightforward employment under that country's law.
- Your relationship with the EOR is a services contract. You pay the EOR a monthly fee per employee plus pass-through compensation. You don't direct the worker as a worker; you direct the EOR's resource.
- The tax authorities of both countries see a legal employment relationship with a real employer who's actually filing payroll, withholding tax, paying social contributions. The misclassification question goes away.
A few important caveats:
EORs don't help with US-resident workers. If your "contractor" is in Austin, Texas, an EOR (which by definition operates in foreign countries) is the wrong tool. You need either a real US contractor relationship (which means treating them like one — multiple clients, project-based work, real independence) or you need to make them a US employee on your own payroll or through a US PEO.
EORs don't retroactively cure misclassification. Moving a worker from a contractor relationship to EOR employment is forward-looking. The previous period of misclassification — if it was misclassification — remains exposed until the statute of limitations runs out. Some companies handle this by also paying the worker a one-time payment that approximates the employer-side taxes they would have paid (and the worker would have had withheld), structured as a "settlement" so it's defensible. Get tax and employment counsel before doing this.
EORs are not a license to mistreat workers as if they were contractors. Local employment law applies to the worker through the EOR. You can't terminate at will, you can't skip overtime, you can't avoid statutory benefits. The EOR enforces these on the worker's behalf because it's the legal employer.
The decision matrix
| Situation | Right structure | Why |
|---|---|---|
| Freelance designer, 3 clients, project-based | Contractor (no EOR needed) | Genuine independent business |
| US engineer, 40 hrs/week for you, your laptop | US W-2 employee or US PEO | EOR doesn't apply to US-resident workers |
| Foreign engineer, 40 hrs/week for you, your laptop | EOR | Misclassification risk eliminated; no entity needed |
| Foreign senior architect, 10 hrs/week, multiple clients | Contractor (with caution) | Could be genuine; document the multi-client reality |
| Foreign engineer working 20 hrs/week, exclusively for you | EOR or restructure relationship | Part-time exclusive looks like part-time employment |
| You've been paying a foreign contractor full-time for 2+ years | EOR (and consult counsel on past period) | Almost certainly misclassified; cure forward, evaluate past exposure |
How to evaluate your own situation honestly
A five-question audit. If you answer "yes" to three or more, the contractor relationship is probably already misclassified:
- Does the worker spend at least 80% of their working hours on your company?
- Has the relationship been continuous for 12 months or more?
- Do you set or substantially influence the worker's working hours?
- Do you provide the equipment (laptop, software licenses, dev tools)?
- Does the worker's work product become an integral part of your company's revenue-generating output (e.g., your product, your service delivery)?
If yes ≥3, talk to employment counsel. Don't wait for the IRS to call.
A note on contractor agreements that "fix" misclassification
You will see contractor agreements full of clauses meant to insulate the company from misclassification: the worker affirms they're a contractor, waives employment claims, agrees to indemnify the company, acknowledges they have other clients, etc. These clauses have limited weight. The IRS, DOL, and state labor agencies look at the actual facts of the relationship, not the contract language. A worker who "affirms" they're a contractor while functioning as an employee is still an employee for tax purposes.
The contract clauses do matter on the margin. Documenting that the worker has other clients (and they actually do), that they set their own hours (and they actually do), that they bear financial risk (and they actually do) — these can help on close cases. But they can't transform an employment relationship into a contractor one through paperwork alone.
When you genuinely don't need an EOR
We're an EOR, so we're biased toward EORs being the answer. The honest contrary cases:
- The contractor really is independent, with multiple clients, project-based billing, real autonomy. Leave the relationship alone.
- You have a US worker — EORs don't apply.
- The engagement is genuinely short-term — a 4-week scoped project with a clear deliverable, then ends. Even if it's "full-time" for those 4 weeks, that's a project, not employment.
- The worker is in a country where you already have an entity — use your entity, not an EOR.
For the case where you have one to ten foreign contractors who look more like employees than contractors and you don't want to open ten entities: that's exactly what an EOR exists to solve.
What to do this week
If you're a US founder reading this and you're not sure whether your foreign contractors are properly classified:
- Run the 5-question audit above for each contractor.
- For the ones that score 3+ "yes" answers, get a 30-minute consult with an employment lawyer who handles cross-border (most do; ask if they've handled IRS misclassification audits before).
- For the ones that look risky, evaluate the EOR vs entity-setup math (most start-ups land on EOR for the first ~15 employees).
- For the ones that are genuinely contractors, document the multi-client reality so you can defend it if asked.
We're happy to walk you through your specific situation in a 30-minute call — no obligation, honest answer if EOR isn't the right fit. Book one.
FAQ
Q: Can a worker request to be classified as a contractor? The worker's preference is one factor but not dispositive. If the relationship functions as employment, the IRS will reclassify regardless of what the worker wanted. Many startups discover this when a former contractor files for unemployment and the state classifies them as an employee, triggering the audit chain.
Q: What's the statute of limitations on IRS misclassification audits? Generally 3 years for federal employment taxes, but 6 years if the IRS finds substantial under-reporting and indefinite for willful misclassification or fraud. State statutes vary; California is generally 4 years.
Q: We use a global "contractor management platform" — does that protect us? Not by itself. A contractor management platform handles invoicing and payments; it doesn't legally employ the worker. The IRS still looks through the platform to the underlying relationship between you and the worker. If you want the platform to legally protect you, you need to confirm whether they actually provide EOR (legal employment) services or just contractor-management.
Q: I've been paying my foreign engineer through Stripe for 18 months. Am I OK? Probably not — but it depends on the facts of the relationship, not the payment rail. The IRS doesn't care whether you paid through Stripe, ACH, wire transfer, or PayPal. They care about behavioral control, financial control, and the nature of the relationship.
Q: Does using a 1099 form make someone a contractor? No. The 1099 reports payments to someone you've classified as a contractor; it doesn't determine the classification. If the IRS reclassifies the worker, the existence of a 1099 is irrelevant to the underlying liability.
Last reviewed: May 2026. Employment law is jurisdiction-specific and changes frequently; this post is general information, not legal advice. Email info@merot.com for corrections or questions.