ICAEW & ACCA

Web Design

Your content goes here. Edit or remove this text inline.

Logo Design

Your content goes here. Edit or remove this text inline.

Web Development

Your content goes here. Edit or remove this text inline.

White Labeling

Your content goes here. Edit or remove this text inline.

VIEW ALL SERVICES 

Merged RDEC Scheme UK: How Software Companies Maximise R&D Tax Relief

For UK tech startups investing heavily in product development, R&D tax relief represents one of the most valuable tax incentives available – yet it remains widely underclaimed, frequently misclaimed, and increasingly scrutinised by HMRC. The merged Research and Development Expenditure Credit (RDEC) scheme, fully operative from April 2024 onwards, fundamentally changed how relief is calculated and claimed. 

 

Understanding the mechanics, qualifying criteria, and documentation requirements for the 2026/27 tax year is essential for software companies seeking to maximise legitimate claims whilst avoiding the compliance pitfalls that trigger HMRC enquiries. 

 

This guide covers the merged RDEC scheme mechanics, what qualifies as R&D for software development, common claim errors, documentation best practice, and the interaction between R&D relief and other tax incentives. 

Merged RDEC Scheme UK R&D tax relief

The Merged RDEC Scheme: 20% Credit Explained

From April 2024, the previous dual-scheme system (SME scheme and RDEC scheme) was replaced by a single merged scheme for most companies. The merged scheme operates as an above-the-line tax credit, meaning the benefit appears as income in the profit and loss account rather than as a reduction in taxable profits. 

Merged RDEC and ERIS Rates for 2026/27

Company Type Credit Rate Effective Benefit (Profitable, 25% CT) Effective Benefit (Loss-Making) Key Condition
Standard (merged RDEC) 20% 15% net of CT on the credit 16.2% (payable credit after CT offset) Default for all companies
R&D intensive (loss-making) 27% N/A (must be loss-making) Up to 27% payable credit R&D spend ≥30% of total expenditure

 

How the calculation works for a profitable company: A company spending £500,000 on qualifying R&D receives a 20% credit of £100,000. This credit is taxable income, so at the 25% corporation tax rate, the net benefit is £75,000 (15% effective rate). The credit is offset against the company’s corporation tax liability first, with any excess payable in cash. 

Loss-making R&D intensive companies: Companies where qualifying R&D expenditure represents at least 30% of total expenditure qualify for the enhanced 27% rate. This is particularly relevant for pre-revenue startups where development costs dominate the cost base. The R&D intensity threshold is assessed on a period-by-period basis. 

What Software Development Qualifies for R&D Tax Relief?

The qualifying test for R&D tax relief is set out in the Department for Science, Innovation and Technology (DSIT) guidelines, which define R&D as work that seeks to achieve an advance in science or technology through the resolution of scientific or technological uncertainty. Both elements must be present. 

The Advance and Uncertainty Tests for Software R&D

Element Definition Software Example That Qualifies Software Example That Does NOT Qualify
Advance in science or technology Extends overall knowledge or capability in the field, not just the company’s own knowledge Developing a novel machine learning algorithm that outperforms existing published approaches Implementing an off-the-shelf ML library in a new application
Scientific or technological uncertainty Uncertainty about whether something is achievable, how to achieve it, or the optimal approach Building a real-time data pipeline processing 1M+ events/second with sub-100ms latency – uncertain whether architecture can achieve this Building a standard CRUD application with well-established frameworks
Not readily deducible A competent professional in the field could not readily determine the solution Creating a novel compression algorithm for video streaming with specific quality/bandwidth trade-offs Using FFmpeg with standard settings for video processing

 

Qualifying R&D Expenditure: Staff, EPWs, Cloud and Software

Not all software development qualifies. HMRC distinguishes between innovative development (which can qualify) and competent professional work (which cannot, regardless of complexity or commercial value). 

Activity Typically Qualifies Typically Does Not Qualify
Algorithm development Novel algorithms solving previously unsolved problems Implementing well-documented algorithms from academic literature
System architecture Novel approaches to scalability, reliability, or performance beyond known solutions Standard microservices architecture using established patterns
Data engineering Processing data at scales or speeds where existing techniques fail ETL pipelines using standard tools (Airflow, dbt)
Machine learning Developing new model architectures or training methodologies Fine-tuning pre-trained models with standard techniques
Security Novel cryptographic implementations or threat detection approaches Implementing standard security frameworks (OAuth, TLS)
UI/UX development Rarely qualifies unless involving novel interaction paradigms with technical uncertainty Standard frontend development in React/Vue/Angular
DevOps/infrastructure Novel approaches to deployment, monitoring, or infrastructure automation Standard CI/CD pipelines using GitHub Actions or Jenkins
Testing Developing novel automated testing frameworks for specific technical challenges Writing unit tests and integration tests using standard frameworks

 

Qualifying Expenditure Categories 

Even where R&D activity qualifies, only specific categories of expenditure can be included in the claim. 

Expenditure Category What’s Included Rate Key Rules
Staff costs Salary, employer NIC (15%), pension contributions, bonuses for R&D staff 100% Apportion by time spent on qualifying R&D activities
Externally provided workers (EPWs) Agency staff and contractor costs for R&D work 65% of cost Must be individuals, not subcontracted companies
Subcontracted R&D R&D work subcontracted to third parties 65% of cost Unconnected parties; contract must be for R&D specifically
Software and data licences Licences for software and datasets used directly in R&D 100% Must be consumed or transformed in R&D process
Cloud computing costs AWS/Azure/GCP costs directly attributable to R&D 100% Must be apportioned between R&D and production workloads
Consumable items Materials consumed or transformed in R&D 100% Rare for pure software companies

Overseas Developers and the Merged Scheme: What Still Qualifies

Under the merged RDEC scheme, expenditure on overseas workers and subcontractors generally does not qualify unless the R&D conditions (such as UK regulations requiring the work to be done overseas, or practical conditions that prevent it being done in the UK) are met. This is a significant restriction for tech startups with offshore development teams. 

Practical impact: A UK SaaS company with a 10-person development team in Eastern Europe and a 3-person UK team can only claim for the UK team’s costs (and potentially a portion of the overseas team’s costs if the qualifying conditions are met). This should influence decisions about team location and structure. 

 

R&D Tax Relief Documentation: What HMRC Expects

HMRC has significantly increased its scrutiny of R&D claims since 2023, with compliance enquiry rates rising materially. Robust documentation is no longer optional – it is essential for surviving an HMRC enquiry. 

 

What HMRC Expects to See 

Documentation Element Content When to Prepare Importance
Project descriptions Narrative explaining the technological uncertainty, the advance sought, and the approach taken Contemporaneously (during the project) Critical – retrospective narratives attract scepticism
Technical competent professional baseline Description of existing technology and why the advance goes beyond it During claim preparation High – establishes the ‘uncertainty’ threshold
Time records Evidence of time spent by qualifying staff on R&D activities vs non-qualifying Monthly or sprint-based Critical – apportionment must be evidenced
Cost allocation Methodology for attributing costs to specific R&D projects During claim preparation High – must be reasonable and consistent
Technical records Git commits, Jira/Linear tickets, architecture documents, technical specifications Contemporaneously (already exist) Strong supporting evidence for genuine R&D
Outcome documentation What was achieved, what failed, what uncertainties were resolved At project completion or review points Moderate – demonstrates genuine investigation

 

Best practice for software companies: Integrate R&D documentation into existing development workflows. Tag Jira or Linear tickets that involve qualifying R&D. Use sprint retrospectives to capture uncertainty resolution. Maintain a quarterly R&D log summarising projects, uncertainties addressed, and outcomes. This contemporaneous evidence is far more credible to HMRC than retrospective narratives prepared solely for the claim. 

 

Common R&D Claim Errors That Trigger HMRC Enquiries

Understanding the most frequent errors helps companies avoid the triggers that prompt HMRC enquiries. 

 

Claiming routine software development. The most common error. Building a new feature using established frameworks, integrating third-party APIs, or migrating databases does not qualify simply because it is technically complex or commercially valuable. Complexity and innovation are not synonymous. 

 

Overclaiming staff time. Claiming 100% of a developer’s time as R&D when they also perform production support, customer implementations, and routine maintenance. HMRC expects honest time apportionment, and blanket claims attract scrutiny. 

 

Including non-qualifying overseas costs. Claiming costs of offshore development teams without meeting the qualifying conditions for overseas expenditure under the merged scheme. 

 

Retrospective claim fabrication. Preparing R&D narratives after the project is complete, describing uncertainties that were not genuinely uncertain at the time. HMRC inspectors are technically competent and can distinguish genuine uncertainty from post-hoc rationalisation. 

 

Confusing commercial risk with technological uncertainty. The uncertainty must be technological, not commercial. Not knowing whether customers will adopt a new feature is commercial uncertainty. Not knowing whether a specific algorithmic approach can process data at the required speed within acceptable accuracy tolerances is technological uncertainty. 

R&D Relief and Patent Box, Capital Allowances and VGEC

 

Incentive Interaction with R&D Relief Can You Claim Both? Consideration
Patent Box R&D credits during development; Patent Box on commercialisation profits Yes Complementary – development phase R&D credits, exploitation phase 10% rate
Capital allowances Assets used in R&D may qualify for both Not double-counted Revenue expenditure = R&D; capital expenditure = capital allowances
Creative industry reliefs Video games, animation may qualify for both R&D and VGTR Restricted – cannot claim both on same expenditure Elect most beneficial relief
EMI share options No direct interaction Yes R&D claims improve cash position, supporting EMI scheme funding

 

How to Make a Merged Scheme R&D Claim: Step by Step

Step 1: Identify qualifying projects – Review development activities against the advance and uncertainty tests. Not every project will qualify; focus on genuine technological challenges. 

 

Step 2: Apportion costs – Allocate staff time, subcontractor costs, cloud computing, and software licences to qualifying projects using a defensible methodology. 

 

Step 3: Calculate the claim – Apply the 20% RDEC rate (or 27% for R&D-intensive loss-making companies) to qualifying expenditure. Model the cash benefit accounting for corporation tax treatment. 

 

Step 4: Prepare supporting documentation – Compile project narratives, time records, cost allocations, and technical evidence contemporaneously. 

 

Step 5: Submit via CT600 – Claims are made through the corporation tax return, with the Additional Information Form (AIF) mandatory from August 2023. The AIF requires detailed information about qualifying projects, a named technical officer, and a breakdown of qualifying expenditure by category. 

 

Professional fees: Specialist R&D tax advisers typically charge 15–25% of the claim value on a success-fee basis, or £5,000–£15,000 on a fixed-fee basis depending on claim complexity. For claims below £50,000, fixed-fee arrangements are generally more cost-effective. 

Merged RDEC Claims: Key Takeaways for Software Companies

R&D tax relief represents a substantial and legitimate benefit for UK software companies genuinely engaged in technological innovation. The merged RDEC scheme provides meaningful cash benefits – 15% net for profitable companies, up to 27% for R&D-intensive loss-making startups – that can materially improve cash runway and reduce effective tax rates. 

 

However, the era of aggressive, loosely documented R&D claims is definitively over. HMRC’s increased compliance activity, the mandatory Additional Information Form, and the requirement for a named senior officer to certify claims mean that companies must approach R&D relief with rigour and integrity. The companies that benefit most are those embedding R&D documentation into their development workflows from day one, rather than retrospectively constructing claims at year-end. 

 

This blog post is intended as general guidance only and does not constitute tax advice. R&D tax relief involves complex technical and legislative requirements that HMRC interprets actively. You should always consult with qualified tax advisers experienced in R&D claims before submitting claims or making decisions based on anticipated relief.

FAQ

Q: What is the merged RDEC scheme?
ANS: The merged R&D expenditure credit scheme is a taxable credit at a 20% rate for accounting periods beginning on or after 1 April 2024. It replaced the old SME and RDEC schemes for most companies.

Q: How much is the merged RDEC credit worth to a software company?
ANS: The 20% credit is taxable income. On £100,000 of qualifying R&D it nets £15,000 at a 25% corporation tax rate, or £16,200 at the 19% small profits rate.

Q: What is ERIS and who qualifies?
ANS: ERIS is a separate relief for loss-making SMEs whose R&D is at least 30% of total expenditure. It gives an extra 86% deduction (186% in total), and the resulting loss can be surrendered for a payable credit worth up to 14.5%.

Q: Is there a cap on payable R&D credits?
ANS: Yes. The payable credit is capped at £20,000 plus 300% of relevant PAYE and NIC liabilities. Startups with few UK payroll staff may receive much less than the headline rate suggests.

Q: Do I need to notify HMRC before making an R&D claim?
ANS: Possibly. First-time claimants, or those whose last claim was over three years ago, must submit a claim notification within six months of the period end. All claims also need an additional information form before the tax return.

Q: Can I claim for developers based overseas?
ANS: Generally not, unless the qualifying overseas conditions are met. Most overseas subcontractor and externally provided worker costs have been excluded from 1 April 2024. Check GOV.UK for the current conditions and how they apply to your team.

Meet Serkan

Serkan Tatar - Director at M. Tatar and Associates
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.

You May Also Like