For UK tech startups relying on contractors and freelancers to build products, scale engineering teams, and access specialist expertise, understanding IR35 and the off-payroll working rules represents one of the most significant compliance obligations affecting both financial exposure and workforce strategy. Getting contractor status determinations wrong can result in retrospective tax assessments, penalties, and interest stretching back years, potentially threatening the financial viability of early-stage companies operating on tight runways.
This comprehensive guide explores the IR35 framework as it applies to UK tech startups for the 2026/27 tax year, covering the distinction between inside and outside IR35 engagements, Status Determination Statement requirements and processes, limitations of HMRC’s CEST tool and alternative approaches, medium and large company obligations under the off-payroll rules, financial exposure quantification and risk management, blanket assessment risks and legal consequences, and key case law shaping current IR35 interpretation.

IR35 Inside vs Outside: What UK Tech Startups Need to Know
IR35 legislation, originally introduced by the Intermediaries Legislation (Chapter 8, Part 2, ITEPA 2003), determines whether a contractor operating through a personal service company (PSC) would be considered an employee if engaged directly. Where IR35 applies (inside IR35), the engagement is treated as employment for tax purposes, with income tax and National Insurance Contributions due at employment rates rather than the more favourable combination of salary, dividends, and corporation tax available to PSC directors.
Three Employment Status Tests That Determine IR35 Status
Three fundamental tests determine employment status, derived from decades of case law rather than statutory definition.
| Test | Inside IR35 (Employee) | Outside IR35 (Self-Employed) | Key Evidence |
|---|---|---|---|
| Personal service | Must perform work personally; no genuine right of substitution | Genuine, unfettered right to send a substitute | Contract terms and practical reality |
| Mutuality of obligation | Employer must offer work; worker must accept | No obligation to offer or accept future work | Pattern of engagement, gaps between projects |
| Control | Client controls what, how, when, and where work is done | Worker controls method, timing, and location | Day-to-day working practices |
Beyond these three primary tests, HMRC and tribunals consider additional factors including financial risk borne by the contractor (using own equipment, bearing cost of correcting defective work, opportunity for profit and risk of loss), the degree of integration into the client’s organisation, provision of own equipment and tools, the existence of an office or business premises, and whether the contractor has other clients simultaneously.
IR35 Practical Indicators: Inside vs Outside for Tech Engagements
In technology engagements, certain patterns commonly indicate inside or outside IR35 status.
| Factor | Likely Inside IR35 | Likely Outside IR35 |
|---|---|---|
| Working pattern | Fixed hours (9–5), mandatory attendance at stand-ups | Delivers agreed output, chooses own hours |
| Equipment | Uses client laptop, client email, client Slack | Uses own equipment, own development environment |
| Integration | Appears on org chart, has company job title | Operates under own business name |
| Substitution | Client would reject a substitute developer | Contract permits substitution; has been exercised |
| Financial risk | Paid hourly/daily regardless of outcome | Fixed-price deliverables, bears cost of rework |
| Other clients | Works exclusively for one client, full-time | Multiple concurrent clients demonstrable |
| Direction | Assigned tasks via sprint planning by client PM | Agrees scope; determines approach independently |
Status Determination Statements: UK Tech Startup IR35 Obligations
Since April 2021, medium and large companies (the “client” in IR35 terminology) bear responsibility for determining the employment status of contractors operating through PSCs.
This obligation replaced the previous regime where PSCs self-assessed their own IR35 status.
SDS Requirements
The client must issue a Status Determination Statement to the contractor’s PSC and to any agency in the contractual chain before the contractor begins work. The SDS must contain the determination conclusion (inside or outside IR35), the reasons for that conclusion demonstrating genuine consideration of the engagement’s specific circumstances, and information about the client’s status disagreement process.
A determination that provides no reasons, or reasons that are generic and not specific to the engagement, is not a valid SDS. This exposes the client to liability for unpaid tax as if no determination had been made.
IR35 Small Company Exemption: 2026/27 Thresholds and What Changed
Small companies are exempt from the off-payroll rules. The PSC remains responsible for determining its own IR35 status. A company qualifies as small if it satisfies two of three conditions for the 2026/27 tax year: turnover not exceeding £10.2 million, balance sheet total not exceeding £5.1 million, and not more than 50 employees. This is assessed using Companies Act 2006 criteria, and group company rules apply where the client is part of a group structure.
Critical point for scaling startups: A company that crosses the small company threshold must begin issuing SDS determinations from the start of the following tax year. Founders approaching these thresholds should prepare IR35 compliance frameworks in advance rather than scrambling when obligations commence.
HMRC’s CEST Tool: Limitations UK Tech Startups Must Understand
HMRC’s Check Employment Status for Tax (CEST) tool provides a free, online mechanism for making IR35 determinations.
HMRC states it will stand behind CEST results provided information is entered accurately. However, the tool has significant limitations that tech startups should understand.
| CEST Limitation | Impact | Mitigation |
|---|---|---|
| Does not consider mutuality of obligation | Ignores a fundamental employment status test | Supplement CEST with separate MOO analysis |
| Binary questioning misses nuance | Real-world engagements rarely fit neat categories | Document detailed reasoning beyond CEST answers |
| Returns ‘unable to determine’ frequently | Leaves client without clear guidance | Seek specialist advice for indeterminate cases |
| No consideration of wider working practices | Contractual terms may differ from reality | Assess actual working practices, not just contract |
| Historical accuracy questioned | Tribunal decisions have contradicted CEST outcomes | Use CEST as starting point, not sole determinant |
Recommended approach: Use CEST as an initial filter, then conduct a detailed assessment for any engagement where the determination is uncertain or the financial exposure is significant. For engagements exceeding £100,000 annually, professional IR35 status review (£500–£1,500 per assessment) represents prudent risk management relative to potential tax exposure.
Off-Payroll Working Rules: Obligations for UK Startups That Have Outgrown Small Company Status
Companies classified as medium or large under Companies Act 2006 criteria must comply with the full off-payroll working rules. This creates a chain of obligations affecting multiple parties.
IR35 Compliance Obligations: Client, Agency and PSC Responsibilities
| Party | Obligation | Penalty for Non-Compliance |
|---|---|---|
| Client (end user) | Make status determination, issue SDS, maintain disagreement process | Becomes the ‘fee-payer’ – liable for all PAYE/NIC |
| Agency (if applicable) | Pass SDS down the chain, operate PAYE if inside IR35 | Becomes fee-payer if fails to pass SDS |
| PSC (contractor’s company) | Comply with determination or use disagreement process | Limited – obligation shifted to client/agency |
| Fee-payer (deducting party) | Deduct income tax (20/40/45%) and employee NIC (8/2%), pay employer NIC (15%) | Retrospective PAYE/NIC assessments plus interest |
IR35 Financial Exposure: What a Wrong Determination Costs UK Tech Startups
Understanding the financial cost of an incorrect outside-IR35 determination helps startups assess the risk they are managing.
| Component | Rate (2026/27) | Example: £600/day contractor (230 days = £138,000 p.a.) |
|---|---|---|
| Income tax (higher rate) | 40% | £55,200 |
| Employee NIC | 8% (basic) / 2% (higher) | £7,090 (approx.) |
| Employer NIC | 15% | £20,700 |
| Apprenticeship Levy | 0.5% (if payroll > £3M) | Potentially applicable |
| Interest on underpayment | HMRC late payment rate | Compounds over assessment period |
| Penalties | 0–70% of tax due | Depending on behaviour (careless vs deliberate) |
| Total annual exposure per contractor | – | £83,000–£100,000+ |
For a tech startup engaging five contractors at similar rates, a retrospective IR35 assessment covering three years could generate a liability exceeding £1 million before penalties and interest. This represents an existential risk for most Series A and Series B companies.
Why Blanket IR35 Assessments Expose UK Tech Startups to Maximum HMRC Risk
Some companies adopt blanket assessments, determining all contractor engagements as either inside or outside IR35 without individual assessment. This approach is explicitly non-compliant with the legislation and HMRC guidance, which requires each engagement to be assessed on its own merits.
Blanket ‘inside’ assessments result in loss of contractor talent (experienced contractors will not accept inside-IR35 terms at the same rates), increased costs (gross-up required to maintain contractor take-home), and potential challenge by contractors through the disagreement process.
Blanket ‘outside’ assessments create maximum HMRC risk, as HMRC can assess all engagements retrospectively. The client cannot rely on the ‘reasonable care’ defence because no individual assessment was conducted. This approach also attracts higher penalties as HMRC may view blanket determinations as careless or deliberate behaviour.
Key IR35 Case Law UK Tech Startups Should Know in 2026
Several landmark cases provide guidance on how tribunals approach IR35 determinations in technology contexts.
| Case | Key Issue | Outcome | Relevance to Tech Startups |
|---|---|---|---|
| Atholl House (2022) | Substitution clause and control | Outside IR35 (Upper Tribunal) | Genuine substitution clauses carry weight even if not exercised |
| PGMOL (2024) | Mutuality of obligation and control for match officials | Inside IR35 (Supreme Court) | MOO remains central; CEST’s omission is significant |
| Kickabout Productions (2022) | Personal service company in media | Outside IR35 | Business-like conduct and multiple clients strengthen outside position |
| Eamonn Holmes (2021) | Presenter through PSC | Inside IR35 | Labels don’t matter; substance over form |
How to Build an IR35 Compliance Framework for UK Tech Startups
Tech startups should implement a structured IR35 compliance framework proportionate to their contractor usage and risk profile.
Recommended Framework Components
Step 1: Contractor audit. Catalogue all current contractor engagements, identifying those operating through PSCs. Record contract terms, working practices, and daily/annual values.
Step 2: Individual assessments. Conduct status determinations for each engagement using CEST as a starting point, supplemented by detailed analysis of actual working practices. Document reasoning thoroughly.
Step 3: Issue SDS. Provide compliant Status Determination Statements to contractors and any agencies in the chain before engagement commences (or immediately for existing engagements not yet assessed).
Step 4: Establish disagreement process. Create and document a formal process for contractors to challenge determinations. Respond within 45 days. Escalate internally if determination is disputed.
Step 5: Ongoing monitoring. Review determinations at least annually, or whenever engagement terms change materially. Changes in working practices (e.g., contractor begins attending daily stand-ups) may alter the determination.
Professional Costs
| Service | Cost Range | When Required |
|---|---|---|
| CEST-based self-assessment | Internal time only | All contractor engagements |
| Specialist IR35 review (per engagement) | £500–£1,500 | High-value or borderline engagements |
| IR35 insurance (per contractor) | £300–£800 p.a. | Risk mitigation for outside determinations |
| Compliance framework setup | £3,000–£10,000 | First implementation |
| Annual compliance review | £2,000–£5,000 | Ongoing maintenance |
Conclusion: Contractor Compliance as Strategic Priority
IR35 compliance represents a material financial risk for UK tech startups relying on contractor workforces. The combination of retrospective HMRC assessments, substantial per-contractor tax exposure, and the complexity of genuine status determination means that ad hoc or blanket approaches create unacceptable risk.
The most effective tech startups treat IR35 compliance as a strategic workforce planning exercise rather than a pure compliance burden. This means designing engagement models that genuinely reflect outside-IR35 working practices where appropriate, rather than attempting to re-label employment relationships. It also means budgeting appropriately for inside-IR35 engagements where the working relationship genuinely resembles employment, and accepting the higher cost rather than risking retrospective assessments.
For startups approaching or exceeding the small company threshold, building IR35 compliance frameworks before obligations commence prevents the scramble that catches many scaling companies. The investment in professional advice and robust processes (£5,000–£15,000 for initial setup) represents a fraction of the potential exposure from a single incorrectly determined engagement.
This blog post is intended as general guidance only and does not constitute legal or tax advice. IR35 determinations involve complex factual assessments and the interaction of employment law, tax law, and case law. You should always consult with qualified tax advisers and employment lawyers before making contractor status determinations or implementing IR35 compliance frameworks.
FAQ
Q: What is IR35 and how does it affect UK tech startups?
Ans: IR35 is UK tax legislation that determines whether a contractor working through a personal service company should be taxed as an employee. For UK tech startups, it is one of the most significant compliance obligations affecting contractor workforce strategy, with incorrect status determinations creating retrospective HMRC tax assessments that can reach £83,000–£100,000+ per contractor per year.
Q: What changed with IR35 for UK startups in April 2026?
Ans: From April 2026, the small company thresholds increased — a company now qualifies as small if it meets two of three conditions: turnover under £10.2 million, balance sheet under £5.1 million, and fewer than 50 employees. This reclassified approximately 14,000 UK businesses from medium to small, shifting IR35 status determination responsibility back to the contractor’s PSC for those newly exempt engagements.
Q: What is a Status Determination Statement and when is it required?
Ans: A Status Determination Statement is a written document that medium and large UK companies must issue to a contractor’s PSC and any agency in the contractual chain before work begins. It must state whether the engagement is inside or outside IR35 and give specific reasons for that conclusion. A generic or reasoning-free SDS is invalid and leaves the client liable for all unpaid PAYE and National Insurance.
Q: What are the risks of blanket IR35 assessments for UK tech startups?
Ans: Blanket assessments — determining all contractors as either inside or outside IR35 without individual review — are explicitly non-compliant. Blanket outside determinations leave the company unable to claim the reasonable care defence, attracting maximum HMRC penalties. Blanket inside determinations cause talent loss, as experienced contractors will not accept inside-IR35 terms at the same rates.
Q: What are the limitations of the HMRC CEST tool for IR35 determinations?
Ans: The CEST tool does not consider mutuality of obligation — one of the three fundamental employment status tests confirmed by the Supreme Court in PGMOL (2024). It uses binary questions that miss real-world nuance, frequently returns an “unable to determine” result, and has been contradicted by tribunal decisions. UK tech startups should use CEST as an initial filter only, supplemented by detailed analysis of actual working practices.
Q: How much does IR35 non-compliance cost a UK tech startup?
Ans: A single incorrectly determined outside-IR35 engagement for a £600/day contractor can generate £83,000–£100,000+ in annual tax exposure, including income tax, employee NIC, employer NIC, interest, and penalties. For a startup with five contractors assessed retrospectively over three years, the total liability can exceed £1 million — an existential risk for most Series A and Series B companies.
Meet Serkan

Serkan is the Co-Partner of M.Tatar & Associates, a chartered accountancy, tax advisory, and statutory auditor practice in North London. He specialises in helping tech start-up founders and CEOs make informed financial decisions, with a sustainability-focused agenda and expertise in all things investment property. He regularly shares his knowledge and best advice on his blog and other channels, such as LinkedIn. Book a call today to learn more about what Serkan and M.Tatar & Associates can do for you.




