Would HMRC Consider What You’re Doing R&D? A Practical Guide for UK Businesses
Find out more
Research and development is often associated with laboratories, scientists and groundbreaking inventions. In reality, R&D for tax purposes can happen across a much wider range of industries — including software, engineering, manufacturing, construction and other technology-led businesses.
But there is an important distinction between developing something new for your business and carrying out R&D that meets HMRC’s definition.
A project can be commercially innovative, expensive or technically challenging and still fall outside the scope of R&D tax relief.
So, how can a business tell the difference?
What does HMRC mean by R&D?
For R&D tax relief purposes, a project must seek to achieve an advance in science or technology.
The project must also involve resolving scientific or technological uncertainty — essentially, a problem where the solution is not readily available or easily deduced by a competent professional working in the relevant field.
HMRC therefore looks beyond whether something is simply “new” to the business.
The key question is whether the project is attempting to overcome a genuine scientific or technological challenge and, in doing so, advance knowledge or capability in the wider field.
This means that something can be completely new to your company without necessarily qualifying as R&D.
Start With the Technical Story
A useful way to approach an R&D project is to ask four simple questions.
1. What were you trying to achieve?
The project should have a clearly defined technical objective.
“We wanted to improve our product” is unlikely to tell the full story.
A stronger explanation might identify a specific performance, reliability, material, processing or software constraint that needed to be overcome.
2. What prevented you from achieving it immediately?
This is where technological uncertainty becomes important.
The issue should be more than a commercial preference or an unfamiliarity with existing technology.
The business needs to be able to explain what was technically difficult or uncertain.
3. What did you actually do about it?
This is the experimental or developmental process.
It could involve modelling, prototyping, software development, physical testing, material trials, simulations, process changes or repeated iterations.
4. What did you learn?
Not every experiment needs to succeed.
Failed approaches can actually be valuable evidence because they demonstrate that the solution was not obvious at the outset.
A failed prototype, unsuccessful material combination or architecture that could not handle the required workload can help demonstrate the existence of genuine technical uncertainty.
Examples: R&D or not R&D?
The boundary can sometimes be easier to understand through examples.
Developing a new manufacturing process
-Potentially R&D
A manufacturer wants to significantly increase production speed while maintaining a particular level of quality.
The existing process cannot achieve both objectives, and the technical team needs to experiment with machinery settings, materials and process parameters to determine whether a viable solution exists.
The work involved in resolving the underlying technological uncertainty could potentially qualify.
Introducing an existing technology
-Usually not R&D
A business introduces an established software system that is already widely available.
The implementation may require time, configuration and internal training, but if the technology itself is not being advanced and there is no technological uncertainty to resolve, this would not normally constitute R&D.
HMRC specifically distinguishes between seeking a technological advance and applying existing knowledge or techniques in a routine way.
Developing bespoke software
-Potentially R&D
A software company is attempting to create a technically novel system and encounters problems that cannot readily be solved using existing knowledge or commonly available techniques.
The developers investigate different approaches, test prototypes and ultimately develop a solution to the underlying technological uncertainty.
The relevant technical work may qualify.
However, simply creating new functionality or adapting existing software does not automatically make a project R&D. HMRC’s guidance makes clear that software development is subject to the same fundamental R&D criteria as other areas of technology.
Improving an existing product
-Potentially R&D
A company wants to make a product substantially more efficient but encounters a technical limitation that cannot be overcome using established methods.
The team develops and tests several approaches before finding a way to achieve the required performance.
The technical work undertaken to resolve that uncertainty could potentially fall within R&D.
Making a product look different
-Usually not R&D
Changing a product’s colour, appearance, packaging or other non-technological characteristics may involve design and development work, but that does not necessarily mean the work is R&D.
HMRC distinguishes technical advances from commercial, aesthetic and other non-scientific or non-technological improvements.
Where businesses can get caught out
One of the biggest risks is assuming that “we created something new, therefore it must be R&D.”
That isn’t the test.
HMRC distinguishes between:
Commercial innovation
“This is new for our business and gives us a competitive advantage.”
and:
R&D for tax purposes
“We are attempting to achieve an advance in science or technology and have encountered a scientific or technological uncertainty that requires investigation to resolve.”
The two can overlap — but they are not automatically the same thing.
Similarly, a project can involve highly skilled employees, significant expenditure and months of development work without necessarily containing qualifying R&D.
The technical nature of the challenge matters.
R&D isn’t limited to laboratories
One common misconception is that R&D has to look like traditional scientific research.
It doesn’t.
HMRC’s guidance applies across different fields of science and technology. This can include areas such as software engineering, manufacturing, engineering and other technology-led activities.
A business does not necessarily need to have a dedicated “R&D department” either.
The work may be carried out by engineers, developers, technical specialists or other employees as part of a wider commercial project.
What matters is whether the relevant activities meet the definition of R&D for tax purposes.
The Bottom Line
R&D does not have to mean inventing something that has never existed before.
It can involve developing or appreciably improving an existing product, process or technology where achieving the desired outcome requires the resolution of genuine scientific or technological uncertainty.
The key is to look beyond the finished product and understand what technical challenges the business had to overcome along the way.
If your business has undertaken technically challenging development work, it may be worth taking a closer look at the projects involved rather than assuming they are either automatically eligible — or automatically excluded.
Ready to Maximise Your R&D Tax Relief?
Book a free 15-minute review with our specialist team. We’ll assess your technical eligibility and help you claim back your innovation costs—with zero hassle.