How to claim R&D tax credits for software development in the UK

How to claim R&D tax credits for software development in the UK is a game-changer for tech teams pushing boundaries. It puts real cash back in your pocket for the risky, uncertain work that routine coding skips.

US-based readers eyeing UK operations or subsidiaries: this relief rewards innovation under UK Corporation Tax rules. Here’s the quick rundown:

• What it covers: Projects resolving tech uncertainties in software, like novel algorithms or system integrations that advance the field.
• Why it matters: You can recover 15-27% (depending on scheme and tax position) of qualifying spend—staff, cloud costs, subcontractors (with limits).
• Big wins: Cash flow boost for scaling teams, even on failed experiments.
• Key shift in 2026: Merged RDEC-style scheme dominates, with ERIS for intensive loss-making SMEs.
• Timeline: Claim within two years of your accounting period end.

Software firms grab a huge slice of these claims. The kicker? Many leave money on the table by missing eligibility nuances.

Why Software Development Fits R&D Tax Relief

Software work qualifies when it seeks an advance in science or technology by tackling technological uncertainty. Think: not just building an app, but figuring out how to make it scale in ways no one has reliably done before.

HMRC looks for competent professionals in the field who couldn’t easily predict the outcome. Your team hits uncertainty? Document the experiments, dead ends, and breakthroughs. That’s gold.

Examples that work:

• Developing new AI-driven optimization that beats current benchmarks.
• Integrating legacy systems with modern cloud in novel ways.
• Creating proprietary data processing tools that push performance limits.

What doesn’t: Routine bug fixes, standard implementations of known frameworks, or pure UI tweaks without tech uncertainty.

Pure mathematics counts since 2023, and cloud/data costs joined qualifying expenses. Perfect for modern dev stacks.

Step-by-Step: How to Claim R&D Tax Credits for Software Development in the UK

Start here if you’re new. Treat it like shipping solid code—plan, document, test, submit.

1. Identify qualifying projects: Review sprints or quarters for uncertainty. Grab input from lead devs. Was there a problem no Google search fixed easily?
2. Track qualifying costs: Staff (including time apportionment), externally provided workers, cloud computing, data licenses, consumables. Keep timesheets or project logs.
3. Appoint a competent professional: Usually your tech lead. They sign off on the technical narrative.
4. Submit Additional Information Form (AIF): Mandatory online before or with your claim. Details projects, costs, uncertainties. Do this early.
5. File via Company Tax Return (CT600): Include in your Corporation Tax return. Use CT600L supplementary pages. Notify HMRC if first claim.
6. Handle the credit: Under merged scheme, it’s a taxable 20% expenditure credit. ERIS offers higher payable relief for qualifying loss-making SMEs (30%+ R&D intensity).
7. Review and submit: Two-year window. Get specialist help for complex claims to avoid queries.

What I’d do if leading a dev team: Build R&D logging into your Jira or Linear workflow from day one. Saves headaches later.

Pro tip: Claims average solid six figures for active software houses. Don’t guess—evidence wins.

Qualifying Costs and the Merged Scheme in 2026

The landscape simplified. Most companies now use the merged RDEC scheme (20% credit) for periods starting on/after 1 April 2024. Loss-making R&D-intensive SMEs tap ERIS for up to ~27% effective relief.

Overseas subcontracting tightened—focus on UK activity where possible, with narrow exceptions.

Common qualifying spend for software:

• Developer and QA salaries (apportioned).
• Cloud platforms used in R&D.
• Prototyping tools and data sets.

Common Mistakes & How to Fix Them

Mistake 1: Claiming routine work. Fix: Tie every project to specific uncertainties and advances. Use HMRC case studies as benchmarks.

Mistake 2: Poor records. Fix: Contemporaneous notes. “We tried X, failed because Y, pivoted to Z” beats vague summaries.

Mistake 3: Ignoring AIF. Fix: Submit it promptly. It forces clarity and speeds processing (often 40 days if clean).

Mistake 4: Overlooking ERIS eligibility. Fix: Calculate your R&D intensity percentage. Many growing teams now qualify at the 30% threshold.

Mistake 5: Going solo on complex claims. Fix: Partner with specialists for the first one. The learning curve is steep.

Ever wonder why some claims sail through while others trigger endless HMRC questions? Documentation separates them.

Key Takeaways

• How to claim R&D tax credits for software development in the UK starts with proving technological uncertainty and advance.
• Document everything—your competent professional is your best witness.
• Merged scheme offers straightforward 20% credit; ERIS supercharges for intensive SMEs.
• Cloud and data costs are now fair game.
• Two-year claim window—don’t delay.
• Evidence trumps assumptions every time.
• Specialist review maximizes legitimate recovery without red flags.
• Even failed projects count if the intent was genuine innovation.

Nail this process and you turn innovation risk into reliable funding. Software teams that claim consistently outpace those that don’t.

Ready to move? Review your last two accounting periods for overlooked projects, gather your dev leads, and start the AIF. Or consult a UK R&D specialist familiar with tech claims. The relief is there—go claim it.

Further reading:
HMRC Guidance on R&D Relief
DSIT Guidelines on Meaning of R&D
Forrest Brown Software R&D Insights

FAQs