UK R&D Tax Credits: £50K Back From HMRC That Most SMBs Leave Unclaimed
UK companies spending money on qualifying R&D — developing new products, improving processes, solving technical uncertainties — can claim back 33p per £1 under the SME R&D scheme (or 20p under RDEC for larger firms). Average SME claim: £50K+. Most never claim because they don't know their work qualifies. AskBiz identifies R&D-eligible expenditure across your accounts.
- The Missed Claim Problem
- What Qualifies as R&D?
- AskBiz R&D Spend Identification
- Real Example: UK Food Manufacturer
- HMRC's Increased Scrutiny: Why a Weak Claim Now Gets Rejected Rather Than Waved Through
The Missed Claim Problem#
Tom runs a 10-person software firm in Leeds. Last year he spent £180,000 on developer salaries building a new AI-based stock forecasting feature. He also spent £20,000 on cloud computing costs for testing. Total qualifying spend: £200,000. Under the SME R&D scheme (enhanced deduction + payable credit): tax benefit worth approximately £66,000. Tom never claimed. His accountant didn't specialise in R&D tax. Result: £66,000 left with HMRC that legally belonged to Tom's business.
What Qualifies as R&D?#
HMRC's definition is broader than most expect. Qualifying work must: (1) Seek an advance in science or technology. (2) Involve resolving technical uncertainty — you don't know at the start if it's technically possible. (3) Not be routine or standard industry practice. Qualifying costs include: (1) Staff salaries, NI, and pension contributions for staff working on R&D. (2) Subcontractor costs (65% of cost). (3) Software licences used directly in R&D. (4) Materials consumed in R&D. (5) Cloud computing used for R&D. Common qualifying activities: developing new software features, improving manufacturing processes, creating new products, testing new formulations. Common mistake: assuming only scientists qualify. A food manufacturer reformulating a recipe to eliminate allergens qualifies. A factory automating a production process qualifies. A salon brand creating a new hair treatment formula qualifies.
AskBiz R&D Spend Identification#
AskBiz analyses your accounts and flags potential R&D expenditure: "Your payroll includes 3 developers totalling £145,000. If any worked on new feature development, this spend may qualify for R&D tax credits. Review with your accountant to confirm and claim." It also tracks: cloud hosting bills, software licence costs, materials used in development. Provides a categorised report ready to hand to an R&D specialist. Reduces the accountant prep time (and cost) significantly.
Real Example: UK Food Manufacturer#
A Midlands food manufacturer spent two years developing a gluten-free biscuit with a new binding agent. Staff costs during development: £95,000. Ingredient trials (consumed, not sold): £18,000. External food scientist (subcontractor): £30,000. Total qualifying spend: £143,000. SME R&D claim: approximately £47,000 tax credit. Received as a cash payment from HMRC (they were loss-making). Owner had no idea the development work qualified — thought R&D was "lab stuff." AskBiz flagged the spend, accountant filed the claim, £47,000 received within 6 months.
HMRC's Increased Scrutiny: Why a Weak Claim Now Gets Rejected Rather Than Waved Through#
For years, UK R&D tax credit claims from SMBs were processed with relatively light-touch review, and a culture grew up around this — some claims were submitted with thin technical justification, prepared quickly by advisers optimising for volume rather than depth, on the assumption that HMRC's checking capacity was limited. That environment has changed substantially. HMRC has invested significantly more resource into compliance checks on R&D claims in recent years, and SMBs that submit claims today should expect a materially higher chance of the claim being queried, checked, or enquired into than would have been typical previously. The practical consequence is that a claim built on vague, generic technical descriptions — the kind of boilerplate language that could describe almost any software project or product development effort without saying anything specific about what uncertainty was actually being resolved — is now far more likely to be challenged, delayed, or rejected outright than it would have been in the past. HMRC's stated expectation is that a legitimate claim be supported by a clear, specific technical narrative written by someone with genuine competence in the field — described in the guidance as evidence from a competent professional who can articulate what scientific or technological uncertainty existed, why the answer was not readily deducible by a professional in the field, and what work was done to resolve it. This is precisely why working with a specialist adviser, whether an R&D-focused accountant or a technical consultant experienced in HMRC's evidentiary expectations, matters more now than it did previously — not because the underlying qualifying activity has changed, but because the standard of proof required to defend a claim under enquiry has risen. An SMB attempting a claim without that kind of specialist input risks two failure modes: claiming for activity that does not actually qualify because the boundary between routine development and genuine technological uncertainty was misjudged, or under-claiming out of excess caution because the business was unsure how to frame genuinely qualifying work in the technical language HMRC's reviewers expect to see. Either way, the cost of getting professional input upfront is generally far lower than the cost of a claim being challenged, delayed for months during an enquiry, or rejected after the fact.
Building the Evidence Trail as You Go, Not Six Months Later#
The single biggest practical mistake SMBs make with R&D claims is treating documentation as a year-end task — waiting until the claim is being prepared to try to reconstruct, from memory and old emails, what technological uncertainties the business actually grappled with over the previous twelve months. This retrospective approach produces weaker claims for a simple reason: contemporaneous evidence is inherently more credible and more complete than evidence reconstructed after the fact, and HMRC reviewers can generally tell the difference between a technical narrative built from real-time project records and one built from a hurried attempt to recall what happened months earlier. The fix is to treat R&D documentation as an ongoing operational habit rather than a compliance exercise bolted on at year end. Three types of contemporaneous record matter most. Project logs, ideally updated weekly or at each significant milestone, that describe in plain terms what problem the team was trying to solve, what approaches were tried, and what did or did not work — this is the raw material for the eventual technical narrative, and it is far easier to write while the details are fresh than to reconstruct later. Technical uncertainty notes, captured at the point a genuine unknown is identified — not a vague note that a new feature was built, but a specific record that the team did not know whether a given integration approach would handle the required transaction volume without data loss, and that existing published approaches did not address that specific combination of constraints. And timesheets or time allocation records that map staff hours specifically against R&D-qualifying projects rather than against the business in general, since HMRC claims are ultimately quantified in cost terms and a claim without a defensible basis for the proportion of staff time allocated to qualifying activity is vulnerable regardless of how strong the technical narrative is. For an SMB already using AskBiz to track jobs, projects, or production batches, this same underlying data structure can double as the R&D evidence trail with very little extra effort — job and project logs that capture what work was done and when, combined with staff time tracked against specific projects, already contain much of the raw material a technical narrative and cost claim need. Rather than building a separate documentation system purely for R&D purposes, an SMB can tag qualifying projects within their existing operational tracking and let that record accumulate naturally throughout the year, turning claim preparation into a matter of compiling and refining existing records rather than reconstructing a year of work from scratch each time a claim is due.
People also ask
Can loss-making companies claim R&D tax credits?
Yes. Under the SME scheme, loss-making companies can surrender losses for a cash credit from HMRC — up to 10% of qualifying R&D expenditure as a payable credit (rising to 14.5% for intensive R&D companies).
How far back can I claim R&D tax credits?
You can claim for the current accounting period and the previous two years, as long as you submit the claim within two years of the end of the relevant accounting period.
Do I need to be a tech company to qualify?
No. Any sector qualifies: food manufacturing, engineering, construction, retail (product development), software, textiles. The test is technical uncertainty, not industry.
What changed in R&D tax credits from April 2024?
HMRC merged the SME and RDEC schemes for accounting periods starting on or after 1 April 2024 into a single merged scheme at a 20% credit rate. Intensive R&D companies (R&D spend >30% of total expenditure) still get an enhanced rate.
How long does it take HMRC to process an R&D claim?
Typically 4–6 months for straightforward claims. Complex claims or those requiring HMRC queries can take 9–12 months. Filing early (within 6 months of year end) speeds processing.
Our team combines expertise in data analytics, SME strategy, and AI tools to produce practical guides that help founders and operators make better business decisions.
Find Your R&D Tax Credit — Average SME Claim £50K
AskBiz scans your payroll, software, and materials costs to identify qualifying R&D spend. Gives you a categorised report ready for your accountant to file. Don't leave £50K+ with HMRC. Start free at askbiz.co/signup.
Connects to Shopify, Xero, Amazon, QuickBooks, Stripe & more in minutes