Papaya Global logo

Global Hiring & Contractor Compliance

IR35 Contractor Rules: What They Mean for You

A plain-English guide to IR35 contractor rules: what determines status, key terms, and how to build an audit-ready classification process.


PG
Written byPapaya Global
Last UpdateNov 17, 2026
IR35 Contractor Rules: What They Mean for You

IR35 is the UK's off-payroll working legislation, built to test whether someone providing services through a company or intermediary is, in practical terms, working like an employee. If the answer is yes, HMRC expects that person to pay roughly the same Income Tax and National Insurance as someone on payroll, regardless of how the paperwork is framed. That single idea drives everything else in this guide: status isn't decided by what a contract says, it's decided by what actually happens day to day.

For anyone running contractor engagements, or anyone signing one, that distinction matters more than most people realize until it costs them. A contractor can have a perfectly worded agreement, a limited company, and an invoice template, and still get reclassified because the real working relationship looked like employment. This guide walks through what the rules test, the vocabulary around them, and what it takes to build a process that holds up when HMRC actually looks.

What IR35 actually is and why it exists

IR35 exists to stop a specific kind of tax avoidance: people doing employee-type work while being paid through a company structure that lets both sides skip payroll taxes. The legislation applies whenever a worker supplies services to a client through an intermediary, usually their own limited company, and would have counted as an employee if they'd been engaged directly.

HMRC introduced the rules because without them, two people doing identical jobs, sitting at the same desks, taking instructions from the same manager, could end up with very different tax bills simply because one had incorporated and one hadn't.

The off-payroll working rules are designed to make sure a contractor pays broadly the same Income Tax and National Insurance as an employee would when the underlying relationship amounts to disguised employment. The name "IR35" comes from the original 1999 press release number, but the substance hasn't changed: it's a test of reality, not of job title.

That framing matters because it sets up the tension running through everything that follows. A business can write the most carefully worded contractor agreement in the world, and it still won't settle the question on its own. What settles it is how the work actually gets done.

Illustration: Why your contract can't settle the question on its own
Illustration: Why your contract can't settle the question on its own

Why your contract can't settle the question on its own

A written contract is evidence, not proof. HMRC looks past the document to how the engagement actually runs, because contracts can be drafted to say one thing while the day-to-day relationship operates completely differently.

This is the gap that catches most companies off guard. A business might have a contractor agreement that explicitly states the worker controls their own hours, can send a substitute, and bears financial risk for their own mistakes. But if that same contractor shows up at 9am every day, reports to a line manager, can't send anyone else to do the job, and gets paid a fixed day rate regardless of outcome, the contract's language becomes almost irrelevant.

HMRC has been explicit that there's no such thing as an "IR35-proof" contract, because they'll examine the actual working relationship rather than relying on what's written down. A written contract only counts as valid evidence when it accurately reflects how the engagement really works.

That single fact explains why so many companies get caught out. They treat the contract as the control, when the control is actually the operational pattern the contract is supposed to describe. If the definition raises an obvious follow-up, it's this: if the legislation exists to look past paperwork, what exactly does HMRC measure instead?

The core tests that decide inside or outside IR35 status

HMRC and tribunals weigh a handful of specific factors to decide whether an engagement looks like genuine self-employment or disguised employment. No single factor is decisive on its own; assessors build a picture from several tests applied together.

The factors that carry the most weight are generally grouped into four areas:

  • Control - Does the client dictate how, when, and where the work gets done, or does the contractor decide their own methods and schedule? Heavy client control over the "how" pushes toward inside IR35.
  • Substitution - Can the contractor send a qualified replacement to do the work, and would the client accept that substitute? A genuine, unrestricted right of substitution is one of the strongest indicators of outside IR35 status.
  • Mutuality of obligation (MOO) - Is the client obligated to keep offering work, and is the contractor obligated to accept it? Ongoing, open-ended obligation on both sides looks like an employment relationship.
  • Financial risk - Does the contractor bear risk for their own errors, fix problems unpaid, invest in their own equipment, or work for multiple clients? Risk-bearing and genuine business independence point outside IR35.

None of these exist in isolation. A contractor might have a strong substitution clause but still get caught inside IR35 if, in practice, control and mutuality dominate the relationship. Tribunals have gone both ways on cases that looked similar on paper, which is exactly why status determinations require a considered look at the whole picture rather than a box-ticking exercise against one test.

The terms you'll keep running into: PSC, fee-payer, status determination

Wondering how global hiring & contractor compliance plays out in your countries?

A Papaya specialist can map this to your actual workforce instead of the general case.

Understanding IR35 in practice means knowing a short list of terms that get used constantly and rarely explained. Here's what they mean, roughly in order of how often they come up in a real engagement.

  • PSC (Personal Service Company) - not a defined legal category, but typically a limited company that a worker controls and has some financial interest in, through which they supply their services to clients. Most contractors operating through their own company are, for IR35 purposes, running a PSC.
  • Fee-payer - whichever party in the supply chain pays the PSC directly, usually a recruitment agency or the end client. Since 2021, for medium and large private-sector clients, the fee-payer is responsible for deducting tax and National Insurance if the engagement is ruled inside IR35.
  • Status Determination Statement (SDS) - the formal written conclusion a client must produce explaining whether a contractor is inside or outside IR35, and the reasoning behind it. Clients are required to share this with the contractor and the fee-payer.
  • Inside IR35 - the engagement is judged to be disguised employment; tax and National Insurance get deducted at source, broadly as if the contractor were a payroll employee.
  • Outside IR35 - the engagement is judged to be genuine self-employment; the PSC can be paid gross and manage its own tax affairs.
  • Deemed employment - the technical status of an inside-IR35 engagement: the contractor isn't legally an employee, but is treated as one for tax purposes on that specific contract.

With the tests named and the vocabulary defined, it's worth looking at what this actually looks like when a real engagement gets assessed.

What evidence actually proves your status, in practice

Status determinations in the real world come down to documented, consistent evidence that the written contract and the working relationship match. Assessors look at calendars, email instructions, expense claims, substitution history, and how similar roles are structured elsewhere in the business, not just the contract's wording.

Common mistakes that flip a contractor from outside to inside tend to be operational rather than contractual. A contractor whose contract allows substitution but who has never actually sent anyone else, who receives detailed task-level instructions rather than outcome-based briefs, or who gets added to internal org charts and appraisal cycles, starts to look like an employee in every way that matters except payroll. Line managers who treat contractors identically to permanent staff, assigning fixed hours, requiring approval for time off, or including them in staff-only meetings, create exactly the pattern HMRC is trained to spot.

How IR35 status changes your tax treatment and take-home pay

Being ruled inside IR35 means Income Tax and National Insurance get deducted at source by the fee-payer, much like a standard payroll employee, before the contractor's company ever sees the money. That typically reduces take-home pay compared to an outside-IR35 arrangement, where the PSC is paid gross and the contractor manages extraction of salary and dividends through their own company, often at a more favorable effective tax rate.

How IR35 plays out for limited company contractors specifically

Contractors who operate through their own PSC face the sharpest version of this problem, because the structure itself invites scrutiny. The company exists specifically to supply the individual's services, there's usually only one client at a time, and the worker is both the sole employee and the sole decision-maker. That's exactly the profile HMRC built the legislation to examine.

Why this gets harder once a company scales contractor headcount

The individual case is hard enough to assess correctly, and it gets structurally harder once a company is running dozens or hundreds of contractor engagements across multiple roles, teams, and countries at once. A single contract reviewed by a careful manager is manageable. Fifty contracts reviewed inconsistently by fifty different managers, some of whom have never heard of IR35, is a liability problem waiting to surface.

The risk compounds in a few specific ways as headcount grows:

  • Inconsistent classification across teams means two functionally identical roles can end up with opposite IR35 determinations, which is exactly the kind of inconsistency that invites an HMRC inquiry.
  • Drift between contract and practice accumulates silently: a contractor classified outside IR35 on day one can slide into an inside-IR35 working pattern eight months later without anyone updating the paperwork.
  • Cross-border complexity adds another layer entirely, since a company engaging contractors across several jurisdictions is juggling different tests, different filing obligations, and different evidence standards at once, often without a central place to track any of it.

This is where company structure starts to matter as much as individual judgment. A business operating across many countries needs classification, records, and payment history to live somewhere consistent rather than in scattered folders and inboxes.

Platforms built for governed workforce engagement, including Papaya's coverage across 180+ supported countries, exist precisely because ad-hoc contract review doesn't scale past a certain headcount without creating audit gaps.

Illustration: Building an audit-ready, governed classification process
Illustration: Building an audit-ready, governed classification process

Building an audit-ready, governed classification process

Once the stakes of scale are clear, the fix is to turn status assessment from a one-off judgment call into a repeatable workflow with records attached at every stage. That means capturing the status determination, the reasoning behind it, and evidence of actual working practices at the point of engagement, then revisiting it whenever the role changes, rather than discovering gaps during an HMRC inquiry. A determination made on day one and never looked at again is not a safeguard — it's a liability waiting for the next contract renewal or change in reporting line to expose it.

A governed process typically includes a standard questionnaire for every new engagement, a documented SDS stored centrally rather than in someone's inbox, and scheduled reviews whenever contract terms, reporting lines, or working patterns shift. Each of these pieces matters because HMRC doesn't just ask what the contract says — it asks what actually happened day to day, and that evidence has to exist somewhere other than memory. Worker records, invoices, and approval history should sit in one system that's queryable on demand, not reconstructed after the fact from emails and spreadsheets scattered across whoever managed the relationship at the time.

That's the operating model behind Papaya's contractor management approach: engagement, classification workflow, records, and payments governed in one place instead of handled case by case across different tools and teams. Centralizing these steps removes the gap between what a manager believes about a worker's status and what the paper trail can actually prove months or years later.

For companies weighing whether a given engagement calls for contractor management, an Agent of Record structure, or full employment, it helps to start from the guide to EOR companies to understand where the employment route actually applies versus where it doesn't. Getting that distinction wrong at the outset is usually what turns a routine engagement into a compliance problem down the line.

Unsure about your status? Take our free IR35 assessment today.

Frequently asked questions

How do I know if my contract is inside or outside IR35?

Status depends on how the engagement actually works, not just contract wording. Assessors weigh control, substitution rights, mutuality of obligation, and financial risk together, and the off-payroll rules test whether the relationship resembles employment regardless of what the contract claims on paper.

What evidence do I actually need to prove my IR35 status?

You need evidence that your day-to-day working relationship matches your contract, not just the contract itself. HMRC has stated plainly that there's no such thing as an "IR35-proof" contract, so records of actual substitution use, scheduling independence, and financial risk carry more weight than contractual language alone.

How does being inside IR35 change my tax treatment?

Inside IR35, the fee-payer deducts Income Tax and National Insurance before paying your company, similar to standard payroll deductions, because the off-payroll rules require broadly the same tax treatment as employment once a role is classified as disguised employment. That generally reduces take-home pay compared to being paid gross outside IR35.

Does IR35 work differently if I operate through my own limited company?

The rules apply the same tests regardless of structure, but a Personal Service Company draws particular scrutiny because it's typically a company the worker controls and uses specifically to supply their own services, which is the exact structure the legislation was written to examine.

Can a contract be written to make me "IR35-proof"?

No. HMRC has confirmed there's no such thing as an IR35-proof contract, because any written agreement is only treated as valid evidence if it accurately reflects how the work is actually carried out day to day.

How can a company keep contractor records audit-ready for IR35?

Centralize status determinations, evidence, and payment history in one system rather than scattered contracts and emails, and review classifications whenever working patterns change. Platforms offering workforce coverage across 180+ supported countries are built to keep that record-keeping consistent as contractor headcount and cross-border complexity grow.

The next step is global hiring & contractor compliance in your own setup

Bring your countries, worker mix and payment cycles to a Papaya specialist and get a straight answer on what changes.

See how Papaya manages contractors at scale