IR35 makes UK contractor classification a tax-status question, not a contractual one. The wrong call costs back-tax, employer NIC, and penalties for up to 6 tax years. EOR doesn’t solve it.
· United Kingdom guide
IR35 is HMRC’s off-payroll working rules. They reclassify a contractor as a “disguised employee” for tax purposes when the working arrangement looks like employment. Since the 2021 private-sector reform, the client (not the contractor) is usually liable for getting the classification right and for paying employment tax if it’s wrong. An EOR doesn’t solve IR35. Putting an at-risk contractor through an EOR can be HMRC’s evidence the worker was already deemed an employee.
IR35 (formally the off-payroll working rules) is a tax anti-avoidance regime. It tests whether a worker engaged via their own limited company would, ignoring that company, look like an employee of the client. If yes, the engagement is “inside IR35”, employment taxes apply.
The rules were originally introduced in 2000 under Schedule 12 of the Finance Act and rewritten into Chapter 8 of the Income Tax (Earnings and Pensions) Act 2003. The objective then and now: stop workers from disguising employment income as dividends to dodge employer National Insurance and the income-tax-vs-dividend-tax differential.
The rules apply when:
If the arrangement is “inside IR35”, the entity paying the worker’s PSC must deduct PAYE income tax and employee NIC, and the engager pays employer NIC. The contractor still operates through the PSC commercially, but tax flows as if they were an employee.
Until 2017, the contractor assessed and paid IR35 tax. The 2017 public-sector reform shifted assessment to the public-sector client. The 2021 private-sector reform did the same for medium and large private clients. Liability for getting IR35 wrong now sits with the fee-payer, usually the client or an agency in the chain.
The reforms moved the “deemed employer” status from the contractor’s PSC to the entity paying the PSC. That entity must operate PAYE and employer NIC on the engagement, even though the worker isn’t their employee.
If you, the end client, contract directly with a contractor’s PSC: you are the deemed employer for IR35 purposes (assuming you’re a medium or large business, see Small Company Exemption below).
If there’s an agency between you and the PSC: the agency closest to the PSC is usually the deemed employer, but the end client retains liability for issuing the Status Determination Statement and can be liable if the SDS is incorrect.
End clients qualifying as “small” under the Companies Act 2006 definition (2 of: turnover ≤£10.2m, balance sheet ≤£5.1m, employees ≤50) are out of scope of the 2021 reform. For small clients, the IR35 assessment and tax liability stay with the contractor’s PSC, as under the original 2000 rules.
The SDS is the formal IR35 determination the client must give to both the contractor and the next party in the supply chain. It states whether the engagement is inside or outside IR35 and the reasons. Failure to issue an SDS = client becomes the deemed employer by default.
The SDS must:
HMRC’s own CEST tool (Check Employment Status for Tax) can be used to support an SDS, but only if the answers honestly reflect the working arrangement. Plenty of CEST determinations have been overturned at tribunal because the inputs were optimistic.
If the contractor disagrees with the SDS, they have a statutory right to challenge it. The client must consider the challenge and respond within 45 days. Failure to follow the process = the client takes on deemed-employer liability.
HMRC publishes CEST and says it will stand behind determinations made via the tool, but with the proviso that the answers reflect the true working arrangement. Many tribunal cases have found CEST-supported determinations to be wrong because the inputs were aspirational rather than actual.
Specific weaknesses:
Best practice: use CEST as a starting point, then run an experienced IR35 specialist over the engagement contract and the day-to-day working pattern. Run the Contractor Classifier. If they disagree with CEST, weight the specialist’s view higher.
Putting an at-risk contractor through an EOR creates a textbook PAYE arrangement, which HMRC reads as confirmation that the worker should have been an employee. The EOR move can become the evidence used against you.
The reasoning: IR35 asks whether the working arrangement looks like employment. If you move a contractor onto an EOR, the working arrangement becomes employment, same role, same client, same hours, just routed through a different employer. HMRC’s likely view: the arrangement was already employment, you just made it explicit.
This matters because HMRC’s lookback period for IR35 enquiries is 6 tax years (longer for deliberate behaviour). Moving someone to an EOR doesn’t prevent HMRC opening an enquiry into the prior 6 years of PSC engagement.
If the contractor relationship is honestly assessed as inside IR35 from the start, i.e., the worker is genuinely a disguised employee and the client is content to engage them as such, EOR is one of three options:
EOR is cleanest for sub-12-month engagements or when you don’t want to add to your own entity’s payroll. It does not retroactively cure prior IR35 risk.
Four pillars: personal service, mutuality of obligation, control, and integration. The first two are necessary for an employment finding; the second two are weighty but not decisive. The contract terms matter; the actual working arrangement matters more.
Is the worker personally required to perform the service, or can they send a substitute? Genuine, unfettered substitution rights are strong evidence of self-employment. “The client must approve the substitute” or “substitute must be qualified” clauses weaken the defence considerably.
Does the client have to offer work and does the worker have to accept it? Continuous obligation over time, even informally, indicates employment. Genuine ability to refuse work or finish an engagement without further obligation indicates self-employment.
Who controls what work is done, where, when, and how? A self-employed contractor is engaged for an outcome; an employee is directed on method. Day-to-day supervision, fixed working hours, and required attendance at internal meetings push toward employment.
Is the worker part of the client’s organisation or genuinely external? Internal email addresses, line management of/by other staff, performance reviews, attendance at all-hands, these push toward employment. Branded as part of the team in customer-facing materials is the most-cited example.
Teamed Guard and Teamed Protect are purpose-built for UK contractor classification risk. Guard layers misclassification cover on top of contractors you engage directly. Protect transfers the liability to Teamed by routing the engagement through us. Pick by how much risk you want to retain.
| Teamed Guard | Teamed Protect | |
|---|---|---|
| Price | $130 / contractor / month | From $189 / contractor / month |
| Engagement model | Direct, you contract with the contractor | Teamed-direct, Teamed contracts under our agreement |
| Liability cap | $10,000 per case | Full coverage, Teamed carries the risk |
| Classification review | Quarterly | Continuous |
| Audit trail | Documented per contractor | Documented per contractor |
| Best for | Lower-risk engagements you want a backstop on | Higher-risk engagements where you want the liability off your books |
Use Guard when the contractor relationship is genuinely outside IR35 in your honest assessment, you want to keep the direct commercial relationship with the contractor (often because they prefer it), and you want quarterly independent review plus a defined liability cap if HMRC challenges. Guard sits over the top of your existing PSC arrangement; the contractor invoices you, you pay them, and Teamed runs the classification review on the cadence.
Use Protect when you want full liability transfer to Teamed. Mechanically: Teamed engages the contractor under our agreement, the contractor delivers the work to you, and we carry the IR35 risk in full. You get the work; we hold the deemed-employer position. This is the right answer for high-stakes engagements where the cost of an IR35 finding would be material to the business.
Beyond Guard and Protect, Teamed supports:
Teamed’s view on IR35: it’s a tax-status question, not a contractual-magic question. If the working arrangement looks like employment, structure it as employment via EOR. If it’s genuinely external, use Guard or Protect to back the position. Don’t buy synthetic outside-IR35 status through clever contracting; HMRC looks through it.
Genuinely outside IR35 + lower-risk engagement → Guard. Genuinely outside IR35 + higher-risk engagement → Protect. Looks like employment in substance → EOR. Crossover point coming up → Graduation Model to your own entity.
The single most common IR35 mistake we see is treating it as a contracts problem. It isn’t. It’s a working-arrangements problem. You can write whatever you like into a contract, if the day-to-day reality looks like employment, HMRC reads it as employment.Teamed Pod, 28 April 2026
IR35 isn’t complicated. It just rewards honesty.
If the engagement is employment, structure it as employment. If it’s genuinely external, prove it day-to-day, not just in the contract.
Either is fine. Pretending it’s neither isn’t.






