R&D tax credits for UK startups (2026 rules)
The merged scheme, ERIS for loss-making R&D-intensive SMEs, what counts as R&D, what HMRC challenges, and how to keep a claim defensible.
R&D tax relief gives UK companies a credit (or a bigger tax deduction) for qualifying scientific and technological R&D. For accounting periods beginning on or after 1 April 2024, most companies claim through the merged scheme: a 20% taxable expenditure credit, worth about 15p to 16.2p per £1 of qualifying spend after tax. Loss-making SMEs that spend at least 30% of their costs on R&D can claim the more generous enhanced R&D intensive support (ERIS) instead. HMRC checks claims closely, so the work must genuinely qualify and be well evidenced. This guide is educational, not advice — use a specialist before claiming.
The 2026 landscape
For accounting periods beginning on or after 1 April 2024, the two old schemes (the SME scheme and the large-company RDEC) were replaced by a single merged scheme. It pays a 20% R&D expenditure credit, accounted for "above the line" and taxable as trading income. After that tax, the net benefit is about 15p per £1 of qualifying spend for a company paying the 25% main rate, and about 16.2p for a loss-maker, because loss-makers have the credit reduced at the 19% small profits rate rather than 25%.
Loss-making SMEs that are R&D-intensive can choose ERIS instead. To qualify, the company's relevant R&D spend must be at least 30% of its total expenditure (including connected companies). ERIS gives an extra 86% deduction (186% in total), and the resulting loss can be surrendered for a payable credit of up to 14.5%. That's worth up to about 27p per £1 of qualifying spend. There's a one-year grace period for companies that met the intensity test in their previous 12-month period and made a valid claim for it. You can't claim both schemes on the same expenditure.
For comparison, the old SME scheme, at its most generous before April 2023, could return around 33p per £1 to a loss-making company. The change was driven by HMRC's concern about error and abuse in the old SME scheme, including claims for routine software work and "claim factory" agents. The current regime asks for more detail up front and is challenged more often.
Two caps worth knowing for startups: the payable credit is limited to £20,000 plus 300% of the company's relevant PAYE and National Insurance liabilities for the period (under the merged scheme, any excess carries forward), and companies with a registered office in Northern Ireland follow separate rules in some cases.
What actually qualifies as R&D
HMRC's definition: an activity that seeks to achieve an advance in science or technology by resolving scientific or technological uncertainty. The advance must be in the field generally, not just in your business. Three tests:
- Advance — your project aims to push the field forward, even incrementally. Building a better recommendation algorithm than what's in any public paper might qualify. Wiring together known APIs almost certainly doesn't.
- Uncertainty — a competent professional in the field can't look at your problem and immediately know how to solve it. If the answer is googleable, it's not R&D.
- Systematic investigation — you had hypotheses, tested them, learned from failures. You can describe what didn't work and why.
What HMRC commonly challenges
Work that often fails the tests above:
- SaaS feature work. "We built a checkout flow" isn't R&D, no matter how clever it felt. The technological uncertainty test fails.
- App development with mature stacks. React, Rails, AWS — putting these together doesn't resolve technical uncertainty.
- Routine integrations. Connecting Stripe to your CRM doesn't qualify, even if it took 3 months and was hard.
- Cosmetic / UX work. Even substantial design refresh doesn't qualify.
- Over-claimed staff time. Especially "our developer is the CTO and writes code, so 100% of his time is R&D".
What still qualifies (for tech startups)
- Novel ML/AI work — training a model on proprietary data with architectures not directly available off-the-shelf.
- Performance breakthroughs — getting a known algorithm to run 100x faster, with the technique not being public knowledge.
- Cross-platform challenges — making something work on a new hardware configuration where the path isn't obvious.
- Distributed systems research — solving concurrency / consistency problems where the field doesn't have an established answer.
- Bioinformatics, genuine scientific computation, robotics control.
What costs qualify
| Cost | Counts? |
|---|---|
| Staff salaries, bonuses (R&D time) | ✓ Yes — typically the biggest line |
| Employer NIC + pension on R&D staff | ✓ Yes (proportionate) |
| Contracted-out R&D (merged scheme) | ✓ If your company decided the R&D was needed and planned it. 65% of payments to unconnected contractors; connected contractors have different rules |
| Externally provided workers (agency staff) | ✓ 65% of payments to unconnected providers |
| Contractors or workers overseas | ✗ Mostly no, from April 2024 — only where the conditions needed can't be replicated in the UK (cost and staff availability don't count) |
| Consumables (materials, fuel, power, water used up in R&D) | ✓ Yes, proportionate |
| Software licences directly used for R&D | ✓ Yes (a reasonable share if only partly used for R&D) |
| Cloud computing + data licences for R&D | ✓ Yes, for accounting periods beginning on or after 1 April 2023 |
| Office rent, rates, general admin | ✗ No |
| Marketing, sales | ✗ No |
| Patents and trademarks | ✗ No |
| Capital equipment | ✗ Not in the R&D claim (separate R&D allowances) |
Staff costs flow straight from your payroll, so the PAYE and National Insurance records behind them need to be right, not least because they also set the cap on any payable credit.
The claim process (briefly)
- Identify qualifying R&D projects for the accounting period.
- Compute qualifying expenditure (staff time × salary, plus other categories).
- Write a project narrative — what was the advance sought, what uncertainty existed, what investigation was done, what was the outcome.
- Submit the additional information form to HMRC, then claim in your CT600 Corporation Tax return. Every claim needs the form.
- Wait. HMRC can normally open an enquiry up to 12 months after you file the return, and it increasingly does.
The advance-notification trap
For accounting periods beginning on or after 1 April 2023, you must send HMRC a claim notification if you're claiming for the first time, or if your last claim was made more than 3 years before the end of the notification window. The window starts on the first day of the period of account and closes 6 months after the period ends. Miss it and the claim is invalid — you lose the year's relief entirely.
This catches a lot of founders. If you're thinking about claiming for the first time, file the notification proactively, even before deciding to claim. It costs nothing and preserves the option.
Should you use a specialist?
For most early-stage tech startups, yes. The claim narrative is genuinely difficult to write defensively, the cost-apportionment requires judgement, and HMRC enquiries are a material risk. Many specialists charge a percentage of the claim, so compare the fee with the likely benefit and agree it in writing. That feels expensive until your claim gets challenged.
Red flags in specialists:
- "We'll claim 100% of your developers' time" — rarely true; HMRC scrutinises.
- Contingent fee with no fixed minimum — incentive is to claim aggressively.
- Won't share the narrative with you before submission.
- Promises a specific number before reviewing your projects.
Maintaining defensibility
Whatever you claim, HMRC's enquiry follows the trail back to your books and your development history. To make your books defensible:
- Tag R&D-relevant expenses consistently, with clear lines in your chart of accounts such as "R&D software".
- Keep time-tracking that shows the apportionment is rooted in reality, not retrofitted.
- Keep technical documentation (commit history, design docs, dead branches) that shows the uncertainty existed and was investigated.
- Don't backdate. Don't round.
- Keep your books reconciled and signed off monthly. A signed audit trail from before the claim was contemplated is the strongest evidence of good faith.
R&D relief often sits alongside other startup reliefs. If you're raising from angels, see SEIS and EIS explained, and Ledgers for startups for how the books behind both stay audit-ready.
This is the part you read twice
This guide is educational. Do not file an R&D claim based on it alone.Rates, eligibility rules, and specifically which expenses qualify change frequently — the rules above were checked in October 2026, but HMRC updates its guidance often, and the merged-scheme and ERIS rules are still being tested in enquiries. Engage an R&D specialist or your accountant before claiming. They will earn their fee.