Can Your Software Development Costs Qualify For R&D Tax Relief in The UK?
- Adil Akhtar
- 2 days ago
- 15 min read
Can Your Software Development Costs Qualify for R&D Tax Relief in the UK?
Software development costs can qualify for R&D tax relief in the UK, but only where the work involves resolving genuine scientific or technological uncertainty. Routine development, configuration, or adaptation of existing tools does not qualify. The distinction turns on whether the project sought to advance overall knowledge or capability in a field of science or technology, not merely the company's own knowledge.
The Merged R&D Scheme for 2026/27
From 1 April 2024, the previous two-scheme structure (SME scheme and Research and Development Expenditure Credit) was replaced by a single merged scheme for most companies. For accounting periods beginning on or after 1 April 2024, the merged R&D expenditure credit scheme applies, with an above-the-line credit rate of 20% of qualifying R&D expenditure.
The one exception to the merged scheme is the Enhanced R&D Intensive Support scheme (ERIS), which applies to loss-making companies that are R&D intensive, defined as those where qualifying R&D expenditure is at least 30% of total expenditure. ERIS provides a higher credit rate of 27% and remains available to qualifying companies alongside the merged scheme.
For 2026/27, companies undertaking software development R&D will almost all be claiming under the merged scheme at 20%, unless they qualify as R&D intensive loss-makers under ERIS.
The credit is calculated on qualifying R&D expenditure, is taxable (it is an above-the-line credit), and reduces the corporation tax liability. Where the credit exceeds the tax liability, the excess is payable to the company as a cash payment, subject to certain restrictions.
What this Widget is About: This interactive widget is designed to help UK software development companies quickly determine if their projects qualify for the highly scrutinised R&D tax relief schemes for the 2026/27 tax year. To begin, simply answer the three straightforward questions in the initial quiz to assess whether your recent development work meets HMRC’s strict criteria for genuine technological uncertainty. Based on your responses, the tool will instantly evaluate your eligibility and provide a preliminary indication of whether your activities count as qualifying research or merely routine commercial development. Once you have your result, you can navigate through the intuitive tabs below to explore the detailed rules surrounding the Merged Scheme, ERIS rates, and eligible expenditure like staff and cloud computing costs. Ultimately, this guide empowers you to understand complex compliance requirements, such as overseas subcontractor restrictions and advance notification deadlines, ensuring your future claims are robust and fully compliant.
What Makes Software Development Qualify as R&D?
HMRC's guidelines for the purposes of R&D tax relief are the Department for Science, Innovation and Technology guidelines, most recently updated for accounting periods beginning on or after 1 April 2023. These guidelines apply to the merged scheme.
Under the guidelines, R&D occurs when a project seeks to achieve an advance in overall knowledge or capability in a field of science or technology. For software, this means the advance must be in software science or technology generally, not simply new functionality for the company or a specific client.
The key qualifier is technological uncertainty. A company working on software that extends the known boundaries of what software can do, or that must resolve a problem for which no solution exists in the public domain, is engaged in R&D. A company building a standard e-commerce platform, implementing a known API, or customising off-the-shelf software to specific business requirements is not.
The guidelines are specific on this point. Routine analysis, copying, or adaptation of existing software are not R&D. Work that would be done by a competent professional working from existing knowledge, without any unresolved technical challenge, does not qualify.
Where qualifying R&D does occur within a software project, only the costs attributable to the qualifying activities are included in the R&D claim. A project that has both qualifying and non-qualifying elements requires a proportionate allocation, which HMRC expects to be reasonable and documented.
What Costs Can Be Included?
Qualifying R&D expenditure for software development typically includes:
Staff costs, being the salary, employer NIC, and employer pension contributions of employees directly engaged in the qualifying R&D activities. Where a software engineer spends 40% of their time on qualifying R&D and 60% on other work, 40% of their cost is qualifying.
Subcontractor and externally provided worker costs, subject to the rules applicable from 1 April 2024 under the merged scheme. The merged scheme restricts subcontractor costs to those where the work is performed in the UK, with very limited exceptions for overseas subcontractors where equivalent expertise is not available domestically or the work is geographically required to be performed outside the UK.
Consumables, including cloud computing costs used directly in the R&D process. HMRC confirmed from April 2023 that costs for cloud computing services used in direct R&D activity are qualifying expenditure. This is relevant for software companies that use cloud platforms for testing, running experiments, or processing data as part of the technical development process.
Software licences and datasets purchased and used directly in qualifying R&D also qualify under specific conditions.
What does not qualify: general overheads not directly attributable to R&D, capital expenditure (which is dealt with through the capital allowances system), and the cost of producing a working product, as opposed to the qualifying research and development activity that precedes or underlies it.
The Technological Uncertainty Test in Practice
This is where the analysis requires honest assessment rather than optimism. HMRC's compliance focus on software R&D claims has increased considerably since 2022, and the technological uncertainty test is the primary point of challenge.
A company developing a machine learning model that requires it to solve a previously unsolved problem in training efficiency, or that pushes the boundaries of what neural architecture can achieve, may well have a qualifying project. A company implementing a third-party machine learning framework to classify customer data in a known way is not resolving technological uncertainty; it is applying existing technology.
The question to ask is: did a competent professional in the field know, at the start of the project, how to achieve the intended technical outcome? If yes, there is no technological uncertainty and the work does not qualify. If no, because the solution was not known and required investigation and testing to develop, there may be qualifying R&D.
A SaaS company that built a new recommendation algorithm that had to solve a performance bottleneck for which no published solution existed had qualifying activity for the duration of that investigation. Once the solution was found and the development moved into routine implementation, the qualifying R&D activity ended.
The contemporaneous documentation of this boundary matters. HMRC expects companies to maintain records that show what the technical uncertainty was, what approaches were tried, what worked and what did not, and when the uncertainty was resolved. Attempting to reconstruct this narrative at the time of claiming, rather than keeping records as the work progresses, is one of the patterns HMRC identifies in enquiries.
The 2026/27 Advance Assurance and Pre-Notification Requirement
From 1 April 2023, companies that have not claimed R&D tax relief in the previous three years and intend to claim must notify HMRC in advance of the claim, using the claim notification form. This notification must be submitted within six months of the end of the accounting period in which the R&D activity took place.
For a company with an accounting period ending 31 March 2027, the notification deadline is 30 September 2027. Missing this deadline means the claim cannot be made, regardless of how clear-cut the qualifying activity is.
For companies already within a three-year claiming history, the notification is not required. But first-time claimants, or companies returning to R&D claims after a gap, must plan around this deadline.
The claim itself must be submitted with an additional information form containing specific details of the R&D projects, the qualifying costs, and the technical narrative. HMRC introduced this requirement to reduce the volume of speculative or poorly evidenced claims that had become a compliance concern.
The PAYE Cap on Payable Credits
Where a company's R&D credit exceeds its corporation tax liability and generates a payable (cash) credit, the amount of that payable credit is capped. The cap is set at three times the company's total PAYE and NIC liability for the accounting period, plus £20,000.
For most software companies with a substantive UK payroll, the PAYE cap is not a binding constraint. A company paying £300,000 in PAYE and NIC in a year can receive payable credits of up to £920,000 (three times £300,000, plus £20,000). Few software R&D claims of a sensible size would approach this.
The cap becomes relevant for companies with low UK payroll costs. A company that relies heavily on overseas subcontractors, uses few UK employees, or has shareholder directors whose remuneration is primarily taken as dividends rather than salary, may find the cap limits the cash credit available.
For a company where the director-shareholder takes £12,570 in salary and the rest of their extraction is dividends, the PAYE contribution is minimal. If the R&D credit exceeds the tax liability, the payable credit is capped at £20,000 plus three times a very small payroll, which could be a significant constraint on the recoverable cash.
This interaction between extraction strategy and R&D credit is one that many owner-managed technology companies encounter unexpectedly. Where the R&D claim is a meaningful part of the business's tax planning, the salary level needs to be considered alongside the claim rather than in isolation.
Not Sure If Your Software Development Costs Qualify For R&D Tax Relief?
The general rule is one thing. What it means for you is another. Tell us your circumstances and one of our UK tax specialists will give you a straight answer on your own position. Free, no obligation.
Overseas Subcontractors and Software Development Teams
The merged scheme rules from 1 April 2024 introduced a UK-first restriction on subcontractor costs. Under the merged scheme, payments to subcontractors are qualifying expenditure only where the R&D work is carried out in the UK.
The exceptions are narrow. Overseas subcontractor costs qualify only where the work must be undertaken outside the UK for reasons of geography or environment (not relevant to most software work), or where the same expertise is not available in the UK (a difficult test to satisfy in a competitive software market).
For software companies with development teams in Ukraine, India, Eastern Europe, or other offshore locations, this is a material restriction. Work that would previously have qualified under the RDEC scheme or the SME scheme when carried out by overseas subcontractors now falls outside the qualifying expenditure under the merged scheme.
The practical consequence is that some companies restructured their arrangements following the April 2024 change. Using overseas subcontractors through an employment model (where the individual is employed by a UK entity) rather than a direct subcontractor relationship may bring costs within the staff cost category rather than subcontractor costs, which has a different qualifying test.
Whether this restructuring is appropriate depends on the specific arrangement, employment law considerations, and the actual relationship between the company and the overseas developers. The reclassification must reflect the genuine legal and commercial reality, not merely a repackaging for tax purposes.
Connected Party Restrictions in the Merged Scheme
Where a company claims for costs paid to connected parties (related companies, or companies under common control), the qualifying amount is restricted. Under the merged scheme, the amount that qualifies for a connected party subcontractor is the lower of the payment made and the cost incurred by the connected party in performing the R&D.
This matters for group structures. A UK technology company that pays its overseas parent or subsidiary for R&D work cannot simply include the full intercompany charge in its claim. It is limited to the actual underlying cost incurred by the connected entity. Transfer pricing documentation and the underlying cost structure of the group become directly relevant to the quantum of the R&D claim.
For owner-managed businesses, the connected party restriction is less commonly an issue because the company is typically not paying related companies for subcontracted R&D. But any arrangement where development work is contracted to another entity with common ownership should be reviewed against this rule.
What this Widget is About: This interactive visual explainer helps UK software companies and tech businesses understand whether their development costs can qualify for Research and Development (R&D) tax relief under the current rules. It clearly sets out the critical distinction between genuine technological uncertainty and routine coding or configuration, explains the merged R&D scheme (20% credit) and the Enhanced R&D Intensive Support route for loss-making intensive SMEs, and covers eligible costs such as staff time, cloud computing and UK subcontractors. You can navigate the content using the tabs at the top to explore overviews, qualification tests, cost categories, scheme rates, key compliance rules and HMRC’s main areas of scrutiny. An on-page calculator also lets you enter your estimated qualifying expenditure to generate a quick illustrative credit figure. Simply click through the sections at your own pace for a practical, up-to-date guide created by Pro Tax Accountant — always seek tailored professional advice before making a claim.
What HMRC Focuses on When Reviewing Software R&D Claims
HMRC's compliance activity in software R&D has been substantial since 2022. The areas that consistently attract scrutiny are:
Claims that cover routine software development rather than genuine technological uncertainty. HMRC's compliance teams are technically trained and will probe the technical narrative to identify whether the uncertainty described was genuine and unresolved at the time, or whether the work was more accurately a known development task.
Inflated staff time allocations. Where a claim attributes 80% of a senior developer's time to qualifying R&D, HMRC will ask what the remaining 20% covered and how the qualifying percentage was determined. Reasonable and documented allocation methodologies are more defensible than round-number estimates.
Claims that do not reflect the practical development timeline. If a company claims R&D relief for a project that was completed and launched two years earlier, but the claim attempts to characterise the entire development as continuous R&D, HMRC may ask why the uncertainty extended so long after the product was in use.
Missing additional information forms or insufficient detail in the technical narrative. Since the introduction of the additional information form requirement, claims without adequate technical substance are being returned or queried earlier in the process.
A Worked Example for a Software SME
A UK-based software company with a 31 December 2026 accounting year end has 12 developers, of whom three spend approximately 60% of their time on a project developing a novel natural language processing component for an application where no published solution achieves the required performance threshold for their use case.
The company's total staff cost for those three developers is £240,000. The qualifying proportion at 60% is £144,000.
The company also uses cloud computing services costing £36,000, of which £18,000 is directly attributable to running tests and training models for the qualifying project.
Total qualifying expenditure: £162,000. Merged scheme credit at 20%: £32,400.
If the company has a corporation tax liability of £40,000, the £32,400 credit offsets the majority of that liability, leaving £7,600 payable. There is no payable cash credit in this scenario; the credit is fully absorbed against the tax.
If the company's corporation tax liability were £20,000, the remaining £12,400 would be payable as a cash credit, subject to the PAYE cap. With a payroll of £240,000 (for the three developers) plus other staff, the PAYE and NIC liability for the year is likely well above £12,400 divided by three (approximately £4,133), so the cap is not a constraint.
The company must file the additional information form with the project details, the technical narrative explaining the uncertainty, and the cost breakdown, before or at the same time as the company tax return.
Key Takeaways
Software development qualifies for R&D tax relief only where it involves genuine technological uncertainty, defined as a technical problem that a competent professional could not resolve using existing knowledge. Routine development, configuration, and known-method implementation do not qualify.
For accounting periods beginning on or after 1 April 2024, the merged scheme applies at a 20% above-the-line credit rate. Loss-making R&D-intensive companies may qualify for ERIS at 27%.
Cloud computing costs used directly in qualifying R&D activity are qualifying expenditure from April 2023.
Under the merged scheme, overseas subcontractor costs are qualifying only in very limited circumstances. Most companies with offshore development teams cannot include those costs in a merged scheme claim.
The PAYE cap restricts payable (cash) credits to three times the company's PAYE and NIC liability plus £20,000. Director-shareholders with low salaries may find this limits the recoverable cash credit.
First-time claimants (or those returning after a gap of more than three years) must file a claim notification form within six months of the accounting period end. Missing this deadline means the claim cannot be made.
HMRC's compliance focus on software R&D is active. Technical narrative quality, contemporaneous documentation, and defensible cost allocation are the primary factors that determine whether a claim survives enquiry.
FAQs
Q1: Can someone claim software development as R&D if the work only improved their own product, not the wider market?
A1: Well, that is usually where the first mistake happens. HMRC’s test is not whether the code felt impressive or commercially useful; it is whether the project sought an advance in computer science or software engineering by resolving a genuine technological uncertainty. If the work was only a sensible rebuild, a nicer interface, or a better version of something already known, that normally falls short. I have seen this with SaaS teams who were sure they had “innovated”, but once you strip out the design polish, there was no real technical unknown left.
Q2: Can a project still qualify if the software was never launched or was later abandoned?
A2: Yes, it can. HMRC is clear that R&D does not have to succeed for the work to count, and abortive projects can still qualify if they were genuinely aimed at resolving scientific or technological uncertainty. In practice, that is useful for software teams because prototypes often fail for exactly the right reason: they exposed that the chosen approach would not work. A Manchester startup that scrapped a build after discovering its architecture could not handle the load may still have a valid claim, even though there is nothing to show the customer in the end.
Q3: Do routine bug fixes, refactoring, or migrations qualify?
A3: Usually not on their own. HMRC says routine analysis, copying, or adaptation of existing software does not amount to R&D, and its examples make it plain that business-as-usual IT updates do not become qualifying work just because they are awkward or time-consuming. That said, a migration or refactor may still contain a qualifying element if the team had to solve a real technical uncertainty, such as how to move legacy components into a new architecture without a known route. The pitfall is claiming the whole job when only a small part was actually experimental.
Q4: Can website builds, apps, and internal tools qualify for R&D relief?
A4: Yes, but only when they go beyond standard build work. HMRC’s software guidance says creation of new functionality alone is not enough if it is just routine replication of existing methods in a new context. A bespoke internal app, for example, may fail as direct R&D if it simply provides a convenient in-house workflow; however, if the team had to solve a real technical problem to make it work, that is the sort of uncertainty HMRC is looking for. In other words, the “what” matters far less than the technical “how”.
Q5: Which software-related costs are usually worth reviewing first?
A5: In practice, the most common spend lines are staff time, employment-agency or other supplied-worker costs, contractor payments, software licences, and, for accounting periods beginning on or after 1 April 2023, data licence and cloud computing costs. HMRC also allows qualifying indirect activities in some cases, so work such as project-specific admin, maintaining R&D equipment, or preparing the technical findings report can sometimes sit in scope. The trick is to apportion costs carefully instead of pulling in whole invoices by habit.
Q6: Can cloud, data, and software-platform costs be included in a claim?
A6: Yes, and this is one of the bigger practical changes for software businesses. HMRC says cloud computing includes data storage, hardware facilities, operating systems, and software platforms, and qualifying data licence costs can also be included where they are used for R&D. For a team building machine-learning or API-heavy systems, that means the cost split matters a lot: production hosting, shared tools, and project-specific experimentation need to be separated cleanly. Costs used only for qualifying indirect activities are excluded.
Q7: Can contractors, agency developers, and outsourced teams be counted?
A7: Yes, but the rules turn on who decided to do the R&D and where the work took place. For accounting periods beginning on or after 1 April 2024, HMRC says only the company that made the decision to carry out the R&D can claim the relief for contracted-out work, and there are restrictions on overseas activity. That means your paperwork should show who planned the project, not just who wrote the code. In real terms, a founder who outsourced the hard bits to a specialist dev shop cannot assume the invoice is automatically claimable unless the structure and evidence line up.
Q8: Can customer funding, grants, or a Northern Ireland base change the claim?
A8: Not automatically. Under the current merged scheme and enhanced R&D intensive support, HMRC says there is no general restriction on claiming subsidised costs, which is a big change from the older regime. The more important question is still who took the R&D decision and who is really contracting whom. Geography mainly affects administration rather than the technical test; for example, HMRC’s current claim forms include extra prompts for Northern Ireland companies, and there is specific overseas-restriction clarification for ERIS claimants there.
Q9: Can a sole trader or partnership claim for software development?
A9: No, not under this relief. HMRC is explicit that only companies chargeable to UK Corporation Tax can qualify for R&D relief. A sole trader or partnership can still claim normal business deductions and, where relevant, capital allowances under the usual rules, but the R&D relief itself sits with a company. In practice, many one-person developers only become eligible once the work is carried on through a limited company and the project genuinely meets the R&D test.
Q10: What records should a company keep before submitting the claim?
A10: Keep a simple project trail: what the technical uncertainty was, why it was not readily deducible, what alternatives were tried, who worked on each part, and which costs belong to which stage. HMRC now requires an additional information form for new claims, and it must be submitted before or on the same day as the Company Tax Return; if the return goes in first, the claim can be rejected. That is why tidy evidence is not just nice to have, it is part of getting the claim accepted in the first place.
About the Author:
Adil Akhtar, ACMA, CGMA, FCMA (membership ID is 990250923) serves as CEO and Chief Accountant at Pro Tax Accountant, bringing over 18 years of expertise in tackling intricate tax issues. As a respected tax blog writer, Adil has spent more than eighteen years delivering clear, practical advice to UK taxpayers. He also leads Advantax Accountants (registered with Companies House), combining technical expertise with a passion for simplifying complex financial concepts, establishing himself as a trusted voice in tax education.
Email: adilacma@icloud.com
Disclaimer:
The content provided in our articles is for general informational purposes only and should not be considered professional advice. Pro Tax Accountant strives to ensure the accuracy and timeliness of the information but makes no guarantees, express or implied, regarding its completeness, reliability, suitability, or availability. Any reliance on this information is at your own risk. Note that some data presented in charts or graphs may not be 100% accurate.
.png)