.png)
What Is the IR35 Impact for UK Companies Hiring Offshore Team in India?
- Saransh Garg
- 18 hours ago
- 10 min read
Under UK tax law, IR35 formally the off-payroll working rules under Chapter 10, ITEPA 2003 determines whether a contractor is treated as an employee for tax purposes. Since April 2021, the liability for that determination shifted from the contractor to the end client for medium and large businesses. What most UK Finance Heads do not immediately realise is that this liability question becomes significantly more complex, but also more manageable, when the contractor sits offshore in India rather than in the UK.
The IR35 impact for UK companies hiring offshore team in India is no longer an operational question. It is a board-level compliance matter. In practice, misclassification has cost mid-market clients six-figure HMRC retrospective assessments. Understanding the exposure, and structuring around it correctly, is the only responsible position for any Finance Head signing off on offshore hiring budgets.
Why UK Tech Companies Are Actively Choosing Indian Offshore Talent
The UK technology sector has been running on a structural talent deficit for three consecutive years. There are over 1.7 million unfilled digital roles across the UK, concentrated in financial services, NHS digital transformation, and retail e-commerce infrastructure. In London and Manchester, a senior cloud architect costs between £85,000 and £115,000 per annum in permanent employment. Daily contract rates for the same profile have reached £650 to £850 on leading platforms.
UK companies are not turning to Indian talent because it is fashionable. They are doing so because a six-month search for a senior Kubernetes engineer in Leeds or Birmingham now routinely ends with zero hires, or with a contractor demanding inside-IR35 terms that increase the total cost of engagement by 20 to 35 percent. The IR35 impact for UK companies hiring offshore in India, when the structure is correct, is that offshore ceases to be a workaround and becomes the compliant, cost-efficient default.
Fintechs and insurtechs specifically request that Indian engineers be engaged through an offshore structure, not to sidestep IR35, but to legitimately sit outside its scope while maintaining delivery quality. That distinction matters enormously, particularly to a Finance Head preparing for an HMRC audit.
Which Indian Cities Provide the Strongest Bench for UK Tech Roles
When sourcing for backend engineers, DevOps leads, or QA automation specialists, the sourcing strategy is not uniform across India.
Bengaluru is the first call for cloud-native and DevOps roles. The density of AWS, Azure, and GCP certified engineers in Whitefield and Electronic City is unmatched. For UK financial services clients, Bengaluru also has the strongest pool of engineers with prior exposure to FCA-regulated environments through Global Capability Center (GCC) engagements.
Hyderabad dominates for cloud infrastructure talent, particularly around HITEC City, with deep Microsoft Azure and Oracle cloud skills built through years of enterprise systems integrator work.
Pune has the strongest Java and microservices talent for UK retail and logistics clients, with many engineers having worked on UK-facing products during tenures at major SIs.
Chennai provides the most reliable pipeline of QA and automation engineers, particularly Selenium, Cypress, and Playwright specialists that UK digital agencies require consistently.
What Indian engineers typically lack for UK mandates: familiarity with GDPR Article 28 obligations, DORA requirements in fintech, and the UK-specific interpretation of accessibility standards under WCAG 2.2. A mandatory compliance orientation session before first sprint addresses this directly. Client-facing communication under pressure is also assessed at screening stage. Engineers who do not meet the written escalation standard do not proceed regardless of technical score.
What ITEPA 2003 Chapter 10 Actually Says About Offshore Workers
IR35, governed by Chapter 10, Part 2, Income Tax (Earnings and Pensions) Act 2003 (ITEPA 2003), applies to deemed employment situations where a worker provides services through an intermediary, typically a personal service company (PSC), but would otherwise be treated as an employee of the end client.
Here is what the rules actually say about offshore:
IR35 applies where the end client is UK-based, regardless of where the worker is located. However, the off-payroll rules specifically require that the intermediary is subject to UK tax jurisdiction for the deemed employment income rules to activate. An Indian contractor engaged through an Indian entity, paid in INR by an Employer of Record in India, with no UK-registered PSC in the chain, sits outside the direct IR35 compliance scope as currently enforced.
The IR35 impact for UK companies hiring offshore in India shifts substantially when the engagement structure is correctly documented. The most common mistake: UK companies assume that any offshore engagement is automatically IR35-free and fail to document the structure. HMRC guidance clarifies that where a UK business substantially directs the work of an offshore contractor setting hours, controlling deliverables at a task level, requiring exclusive availability it may seek to treat the arrangement as UK-source employment income if the worker later spends time physically in the UK.
The correct structure: engage Indian engineers through a properly documented contract hiring arrangement with an Indian registered entity, with a clear Statement of Work rather than time-and-materials instructions, and no UK PSC in the chain.
IR35 Offshore Compliance Checklist for UK Finance Heads
This checklist is built from internal onboarding reviews conducted for UK clients by AnjuSmriti Global. Share it with your legal or tax counsel before any offshore India engagement goes live.
Checkpoint | What to Verify | Risk if Missed |
Engagement entity | Indian contractor is paid through an Indian registered company or EOR with no UK PSC | IR35 may apply to UK-side payments |
Contract structure | Statement of Work exists; not daily or hourly instruction-based | HMRC may treat as employment |
Mutuality of obligation | No guaranteed minimum hours or exclusivity clause | Key IR35 indicator triggered |
Direction and control | UK managers set outcomes, not methods or daily tasks | Control test failed means inside IR35 risk |
Equipment and tools | Indian contractor uses own or EOR-provided tooling | Increases outside-IR35 argument |
IP assignment | Separate IP deed executed under Indian law with UK law governing clause | Protects UK client regardless of structure |
GDPR and DPA 2018 | Data Processing Agreement in place with Indian entity | ICO enforcement risk, separate from IR35 |
Physical UK presence | Document any UK visit; apply HMRC's 30-day threshold guidance | UK-source income rules may apply |
Status Determination Statement | Issued internally even if technically outside scope | Demonstrates due diligence in audit |
IR35 annual review | Engagement structure reviewed annually as HMRC guidance evolves | Retrospective liability risk grows with time |
The three items UK finance teams most consistently miss are the mutuality of obligation clause in the Master Service Agreement, the physical UK presence protocol, and the annual review commitment. HMRC's approach to offshore arrangements has tightened following its compliance campaign targeting IT services firms. A clean paper trail is the first line of defence.
How a Real UK Client Mandate Was Structured and What Almost Went Wrong
London-based insurtech company at Series B, with approximately 180 employees, needed to scale a data engineering team quickly. Six months of UK agency searches had produced nothing. A competing agency proposed engaging Indian engineers through a UK umbrella company structure. The Finance Head reviewed it and flagged it immediately: the umbrella arrangement placed the engineers inside the UK PAYE chain, negating the cost benefit entirely.
AnjuSmriti Global proposed an alternative: a six-person offshore team in Pune, engaged through a remote contract hiring model with all engineers on Indian payroll, delivering under a fixed-scope Statement of Work. The engagement structure was reviewed by the client's UK tax advisors and confirmed as outside IR35 scope.
What almost went wrong: two of the six shortlisted engineers had previously worked on UK client projects through a UK-registered consultancy and had a dormant UK limited company on Companies House. This was caught during the pre-placement background check. Had those engineers been placed without flagging this, the client's SDS position would have been exposed. Both profiles were replaced within nine days.
Outcome: the team of six was live within 34 days. First sprint delivered in week five. Total annual cost including agency fee and EOR charges: £312,000. The equivalent UK permanent team would have cost an estimated £680,000. The client reinvested £180,000 of the saving into a cloud migration programme. The IR35 impact for UK companies hiring offshore in India, when managed proactively, does not just eliminate compliance risk. It creates meaningful budget headroom.
What Offshore Team Hiring in India Actually Costs UK Companies After IR35 impact
The table below shows the total cost comparison for UK companies engaging Indian engineers offshore versus hiring in the UK, based on current market rates.
Role Level | UK Permanent (all-in annual) | UK Contract (daily rate x 220 days) | India Offshore via EOR and Agency (annual) |
Mid-level engineer (3 to 5 years) | £72,000 to £85,000 incl. NI, pension, benefits | £88,000 to £110,000 | £28,000 to £36,000 |
Senior engineer (6 to 9 years) | £95,000 to £120,000 | £130,000 to £165,000 | £38,000 to £50,000 |
Lead or Architect (10+ years) | £130,000 to £160,000 | £165,000 to £200,000 | £52,000 to £68,000 |
The India offshore figures include: Indian salary in INR (converted at current GBP/INR rate), EOR fee typically 12 to 18 percent of gross Indian CTC, agency placement fee amortised annually, and mandatory Indian statutory contributions including PF, ESIC, and gratuity provision. There are no hidden costs when the engagement is structured correctly from day one.
What UK clients consistently reinvest the savings into: additional permanent hires at mid-management level in the UK, cloud infrastructure spend, or accelerating product roadmap delivery by funding a second offshore pod. Keeping the India comparison number visible in the budget model at all times sustains that discipline.
How HMRC's Direction-and-Control Test Applies to AI-Assisted Offshore Roles
Over the next 12 to 18 months, HMRC is expected to issue updated offshore guidance specifically addressing AI-assisted engineering roles, where UK companies are directing Indian engineers in real time through tools such as GitHub Copilot Enterprise and Linear. The direction-and-control test will come under new pressure as synchronous collaboration tools blur the line between contractor autonomy and managed employment.
The IR35 impact for UK companies hiring offshore in India is sharpest in this context. UK Finance Heads who have not documented their offshore engagement structures will face a harder compliance position as this guidance evolves. AnjuSmriti Global is already advising clients to move from daily standup models to weekly outcome reviews, and from tool mandates to tool recommendations, to ensure the substance of the engagement matches its legal form.
An uptick in UK-based scale-ups moving from informal offshore arrangements to properly structured international hiring frameworks is being driven in large part by Series B and C investors conducting due diligence on contractor classifications. IR35 compliance for offshore India teams is now a fundraising issue as much as a tax issue. Start the conversation here.
Interesting Reads:
FAQs
1.Does IR35 apply to Indian contractors who have never worked in the UK?
IR35 applies where the end client is UK-based and a UK-registered intermediary, typically a PSC, is in the contractual chain. If an Indian contractor is engaged through an Indian entity with no UK PSC and no UK-source payment, the off-payroll rules as currently enforced do not directly apply. However, if a UK business substantially controls daily tasks, HMRC may open an enquiry regardless of physical location. A written tax counsel opinion is always recommended before going live.
2.What should a Statement of Work include to protect a UK company from IR35 exposure?
A compliant Statement of Work for an offshore India engagement should specify deliverables and acceptance criteria rather than hours or methods, milestone-based payments rather than daily rates, no exclusivity clause, no guaranteed minimum engagement, and a genuine substitution right allowing the Indian entity to replace the named engineer without UK client approval. The substitution right is the single strongest indicator of outside-IR35 status under the HMRC control test.
3.Can HMRC's CEST tool be used to assess Indian offshore contractors?
CEST was designed for UK-domiciled contractor assessments and HMRC states it does not cover workers outside the UK tax system. Running an Indian offshore engagement through CEST is technically irrelevant, but doing it anyway and retaining the output is recommended. If HMRC opens an enquiry, a completed CEST demonstrates that the company actively considered IR35 implications. Store the output alongside the SoW, SDS memo, and GDPR documentation.
4.What happens to IR35 liability if an Indian engineer relocates to the UK during a project?
If an engineer on Indian payroll physically relocates to the UK, the Statutory Residence Test under Finance Act 2013 may apply. If the engineer spends more than 30 days working in the UK in a tax year, SRT thresholds begin to activate and HMRC could argue employment income is UK-source taxable. The IR35 position also becomes harder to defend once the engineer is working under UK client direction on UK soil. Any UK visit exceeding 15 days should trigger a structural review.
5.Is an Indian EOR enough to keep a UK company fully outside the IR35 chain?
An Indian EOR removes the UK-registered intermediary from the chain, eliminating the most direct IR35 trigger. But EOR alone is insufficient if the underlying engagement still resembles employment: UK managers setting hours, mandating tools, controlling daily tasks, and supplying all equipment. IR35 is a substance test, not purely a structure test. An EOR creates the correct legal form, but the working model must also reflect genuine contractor autonomy to satisfy HMRC.
6.Which UK industries face the highest IR35 scrutiny risk when engaging Indian contractors?
Financial services (banks, insurers, fintechs under FCA oversight), NHS and public sector digital programmes, and large retail and logistics firms with prior IR35 settlements carry the highest scrutiny. These are also the sectors with the greatest demand for Indian engineering talent. The risk is not a reason to avoid offshore hiring. It is a reason to apply greater precision to documentation and to conduct quarterly structure audits rather than annual ones.
7.What documentation should a UK Finance Head retain for an HMRC offshore contractor audit?
HMRC most frequently requests: the Master Service Agreement with the Indian entity, the Statement of Work for each engagement, the Status Determination Statement or equivalent internal memo, CEST tool outputs, the Data Processing Agreement, evidence of substitution rights and whether invoked, and communication records showing engineer-led task management rather than daily manager assignment. Retain all documents for a minimum of six years from the end of the relevant tax year under TMA 1970 Section 34.
8.How do Indian public holidays and timezone differences affect offshore delivery for UK clients?
India observes 14 to 17 public holidays per year compared to 8 in England and Wales. Unplanned festival holidays have disrupted sprint cycles for clients who did not plan around them. Providing UK clients with an annual Indian holiday calendar at engagement start, mapped against the delivery schedule, prevents this. On timezone, IST is 4.5 hours ahead of GMT and 5.5 hours ahead during BST. A working overlap of 12:00 to 17:00 IST provides five daily synchronous hours for standups, code reviews, and escalation calls without requiring unsustainable evening overlap from the India side.
Share
Comments