R&D Tax Credits for Software Companies: A Practical Guide for UK Developers

Most software developers assume R&D tax credits are for pharmaceutical companies, engineering firms, or manufacturing businesses. That is a costly mistake.

HMRC receives thousands of R&D claims from software companies every year. The key question is not whether you write code. It is whether you resolved technical uncertainty that a competent professional in your field could not solve by standard practice.

If you build software products, platforms, or tools in the UK, you could be leaving tens of thousands of pounds on the table. This guide explains exactly what qualifies, what does not, and how to structure a robust claim for R&D tax credits for software companies.

What HMRC Actually Looks For in Software R&D

HMRC defines R&D for tax purposes using the BIS guidelines (now BEIS). The definition is consistent across all industries. It is not about whether your project succeeded or failed. It is about whether you attempted to overcome technical uncertainty.

For software companies, HMRC wants to see three things:

• Technical uncertainty. You did not know at the outset whether the solution was achievable or how to achieve it within time or cost constraints.
• A systematic approach. You worked through the problem methodically, testing hypotheses, iterating, and documenting your process.
• A competent professional could not have solved it. The solution was not obvious to someone with equivalent experience in your field.

If your project involved building something that already existed in a standard form, it is unlikely to qualify. If you adapted existing technology in a genuinely novel way to solve a problem with no known solution, you likely have a claim.

What Qualifies as R&D in Software Development

Let us get specific. The following activities commonly qualify for R&D tax credits for software companies when they involve technical uncertainty:

Building a Novel Algorithm or Data Processing Method

If you developed a new algorithm to process data faster, more accurately, or at greater scale than existing methods, and there was no off-the-shelf solution, that is R&D. A six-figure SaaS consultancy in Manchester built a proprietary matching engine for recruitment platforms. No existing tool handled their specific matching logic at the required speed. That qualified.

Developing a New Software Architecture or Platform

Creating a new software architecture from scratch to solve a problem that existing architectures could not handle qualifies. For example, a fintech startup in Leeds built a real-time transaction processing system for a niche payment type. The standard banking APIs could not handle the latency requirements. Their custom architecture resolved technical uncertainty.

Integrating Multiple Systems in a Novel Way

Standard API integration does not qualify. But if you had to build custom middleware to connect systems that were not designed to work together, and no existing integration tool could achieve the result, that can qualify. A logistics software company in Birmingham integrated warehouse management systems with carrier APIs in a way that required novel data transformation logic. That qualified.

Overcoming Performance or Scalability Constraints

If your software needed to handle a specific volume of data, users, or transactions that existing technology could not support, and you had to develop a new approach to achieve it, that is R&D. A cloud-based analytics platform in Bristol needed to process 10 million data points per second. Standard database solutions could not do it. They built a custom in-memory processing layer. That qualified.

Solving a Technical Problem with No Known Solution

This is the most common qualifying scenario. You encountered a technical problem, researched possible solutions, found none that worked, and developed your own. The uncertainty is the key factor. If you knew how to solve it from the start, it is not R&D.

What Does Not Qualify

HMRC rejects many software R&D claims because the work was not genuinely uncertain. The following activities rarely qualify:

• Routine bug fixing or maintenance. Fixing a known issue using standard debugging techniques is not R&D.
• Standard web development. Building a standard ecommerce site, brochure site, or CRM using existing frameworks like WordPress, Shopify, or Salesforce is not R&D.
• Using existing libraries or APIs in a standard way. Even if the combination is new, if the integration was straightforward for a competent developer, it does not qualify.
• Business model innovation. Changing your pricing model or target market is not technical R&D.
• UI/UX design. Improving user interface design is not R&D unless it involves novel technical solutions to achieve the design.
• Customisation of existing software. Configuring off-the-shelf software to meet client requirements is not R&D.

A common mistake we see at Holloway Davies is companies claiming for general software development work. HMRC looks at each project individually. If the work was routine for a competent developer, it will be rejected.

The Financial Benefit: What You Can Claim

R&D tax credits for software companies come in two forms depending on your company's profitability and size.

For Profitable SMEs (Under 500 Employees)

You can claim an enhanced deduction of 186% of qualifying R&D expenditure against your profits. This reduces your corporation tax bill.

Example: A software company in Edinburgh spends £100,000 on qualifying R&D staff costs. The enhanced deduction gives them £186,000 of allowable expenditure. At 19% corporation tax (small profits rate), the tax saving is £35,340. At 25% (main rate), it is £46,500.

For Loss-Making SMEs

If your R&D spend puts you into a loss position, you can surrender the loss for a cash payment. The repayable credit is 14.5% of the enhanced loss. For the example above, the cash payment would be approximately £26,970.

For Loss-Making R&D Intensive SMEs (ERIS)

If your company is loss-making and R&D expenditure exceeds 30% of total costs, you qualify for the enhanced R&D Intensive Scheme (ERIS). The payable credit rate is higher. You can claim up to 27% of the enhanced loss as a cash payment. This is a significant benefit for early-stage software companies spending heavily on development.

For Large Companies (RDEC)

Companies with 500+ employees use the RDEC (Research and Development Expenditure Credit) scheme. The credit rate is 20% of qualifying expenditure. After tax, the net benefit is approximately 15%. This is less generous than the SME scheme but still valuable.

What Costs Qualify

You can claim for the following costs directly related to your R&D project:

• Staff costs. Salaries, employer NI, and pension contributions for employees directly working on R&D. This includes software developers, testers, and project managers where their time is spent on qualifying projects.
• Subcontractor costs. If you subcontract R&D work to third parties, 65% of the payment qualifies (or 100% if the subcontractor is a connected party).
• Software licenses. If you used specific software tools directly for the R&D project, the license costs can qualify. General business software like Office 365 does not.
• Consumables. Materials consumed in the R&D process. For software companies, this typically means cloud computing costs (AWS, Azure, Google Cloud) used for testing, prototyping, and development.
• Externally provided workers. If you hire contractors through an agency, the costs qualify, subject to the 65% rule.

For a typical software company, the largest qualifying cost is staff time. You need to track how much time each developer spent on qualifying R&D projects. This is where many claims fall down. HMRC expects detailed time records, not estimates.

How to Structure Your Claim

As ICAEW qualified accountants, we advise software companies to prepare their R&D claim alongside their annual accounts. Do not leave it until the corporation tax return is due.

Here is the process we recommend:

Step 1: Identify qualifying projects. Review your development work from the last accounting period. Identify projects that involved technical uncertainty. Document the uncertainty, the approach you took, and the outcome.

Step 2: Track qualifying costs. Separate staff time, subcontractor costs, software licenses, and cloud costs that relate directly to R&D projects. Use timesheets or project management tools to capture this data.

Step 3: Prepare a technical report. HMRC does not require a formal report for every claim, but we recommend preparing one. It should describe the technical uncertainty, the work done, and why a competent professional could not have solved it using standard practice. A good technical report can prevent HMRC enquiries.

Step 4: Calculate the claim. Apply the enhanced deduction to your qualifying costs. For profitable companies, this reduces your corporation tax liability. For loss-making companies, calculate the payable credit.

Step 5: Submit with your CT600. The R&D claim is made on your corporation tax return (CT600) and the Additional Information Form (R&D AIF). The AIF must be submitted before you file the CT600.

Common Mistakes Software Companies Make

We see the same errors repeatedly. Avoid these:

• Claiming for all development work. Only projects with technical uncertainty qualify. Routine development does not.
• Poor time tracking. HMRC expects accurate records. Estimates based on "about 50% of my time" will not withstand an enquiry.
• Ignoring cloud costs. Many software companies miss cloud computing costs. If you used AWS or Azure for R&D, those costs qualify as consumables.
• Not documenting the uncertainty. If you cannot explain what was technically uncertain at the start, HMRC will reject the claim.
• Filing late. You must submit the R&D AIF before the CT600. Late claims are possible but harder to process.

Do You Need an Accountant for R&D Claims?

You can file an R&D claim yourself. The HMRC guidance is publicly available. But the claim process is detailed, and HMRC enquiries into R&D claims are increasing. A poorly prepared claim can trigger an enquiry that takes months to resolve.

Working with an accountant who understands software R&D claims is usually worthwhile. At Holloway Davies, we have handled claims for software companies across every sector: SaaS, fintech, edtech, logistics, gaming, and bespoke development. We know what HMRC looks for and how to present a robust claim.

If you are unsure whether your software project qualifies, contact us. We can review your development work and give you a clear answer. There is no charge for an initial discussion.

How Far Back Can You Claim?

You can amend a corporation tax return to claim R&D tax credits for up to two years after the end of the accounting period. For example, if your year-end was 31 March 2024, you have until 31 March 2026 to amend the return and claim. Claims for periods before that are generally out of time.

If you have never claimed before, check your last two years of accounts. You might have qualifying R&D work that you missed.

Final Thoughts

R&D tax credits for software companies are not a niche loophole. They are a legitimate government incentive designed to encourage innovation. If your software business resolved technical uncertainty, you should claim.

The key is preparation. Track your time, document your uncertainty, and submit a well-structured claim. Do not assume your work does not qualify just because you are not building hardware or mixing chemicals. Software R&D is real R&D.

For more detail on the claim process, see our R&D tax credits overview page. If you want to understand the fundamentals of corporation tax and how R&D fits in, our fundamentals guide covers the basics.