Why Would a Specialist Turn Down Your R&D Claim?

Most R&D tax credit specialists market themselves on getting you the maximum cash back. Some promise claims for projects that clearly don't qualify. A reputable firm will refuse a claim when the project genuinely doesn't meet HMRC's definition of R&D.

That refusal might feel frustrating, especially if you have seen competitors claim for similar work. But a specialist who says no is doing you a favour. A weak claim that HMRC rejects triggers an enquiry that can cost thousands in professional fees and tie up your finance team for months.

Here are the legitimate reasons an R&D tax credit specialist will turn down your project.

The Project Lacks a Qualifying Advance

HMRC's R&D rules require a project to seek an advance in science or technology. That does not mean building a better product. It means working on something where the outcome was not known in advance to a competent professional in the field.

A software developer building a standard ecommerce site using well-known frameworks is not doing R&D. A civil engineering firm using standard reinforced concrete techniques is not doing R&D. A manufacturing business improving production efficiency by applying known methods is not doing R&D.

Your specialist will look for the technological uncertainty. If you cannot point to a specific technical problem that had no obvious solution at the start, the claim fails the first test.

HMRC's glossary defines a competent professional as someone with relevant technical knowledge in the field. If a qualified engineer or developer in your sector would have known the solution in advance, your project does not qualify.

The Work Is Routine Development

R&D tax credits are not available for routine development work. HMRC draws a clear line between advancing the field and applying existing knowledge.

A plumbing company that installs a new type of boiler for the first time is not doing R&D. A marketing agency building a standard CRM integration is not doing R&D. A construction firm using a pre-existing building method on a new site is not doing R&D.

The distinction matters because many businesses genuinely believe they are innovating when they are simply applying known techniques to a new context. An honest R&D tax credit specialist will explain the difference before you submit a claim that HMRC will reject.

Consider a real example. A Manchester-based precision engineering firm spent six months developing a new cutting tool for aerospace composites. The materials existed. The cutting techniques existed. Combining them in a specific configuration was difficult but not scientifically uncertain. The specialist refused the claim. The firm later confirmed that HMRC had opened an enquiry into a competitor who had claimed for identical work.

The Project Is Entirely Software Development Without Technical Uncertainty

Software R&D claims are the most common area of HMRC challenge. Many software businesses assume that building any new feature qualifies. It does not.

HMRC's guidelines specifically exclude:

  • Standard web development using known frameworks
  • Business logic implementations where the outcome is predictable
  • Integration of existing APIs or third-party tools
  • User interface improvements that do not involve technical uncertainty
  • Performance optimisation using known techniques

A genuine software R&D project involves a technical problem where the solution was not known. Examples include developing a new encryption algorithm, building a real-time data processing system at unprecedented scale, or creating a novel machine learning model where existing approaches failed.

If your project involves writing code that a competent developer could have written with standard documentation and training, an R&D tax credit specialist should refuse the claim. Accepting it would expose you to an enquiry where HMRC would demand repayment plus interest and penalties.

The Project Is a Direct Copy of Existing Work

R&D must be new to the field, not just new to your business. If the technology already exists in the public domain, you cannot claim for rediscovering it.

This trips up businesses that work in isolation. A small engineering firm in Birmingham might genuinely believe it has developed a novel manufacturing process. But if a Japanese competitor published the same technique in a trade journal three years ago, the advance is not qualifying.

Your specialist should conduct a basic prior art check. They should ask whether you searched existing patents, academic papers, or trade publications. If you did not, and the work looks similar to known techniques, the claim is high risk.

As ICAEW qualified accountants, we have seen HMRC open enquiries specifically because a claimant failed to demonstrate that the advance was genuinely new. The enquiry letter typically asks for evidence of the prior art search. If you cannot produce it, the claim collapses.

The Costs Are Not Qualifying Expenditure

Even a qualifying project can fail if the costs do not meet HMRC's rules. The most common issues are:

  • Staff costs for non-qualifying activities (administration, sales, routine testing)
  • Subcontractor costs where the subcontractor is not directly supervised by the claimant
  • Consumable items used outside the R&D project
  • Software licence costs for tools used across the whole business, not just R&D
  • Overhead costs allocated incorrectly

A specialist who reviews your cost breakdown and finds that 80% of the claimed spend relates to non-qualifying activities should tell you. They should not inflate the numbers to make the claim look bigger. HMRC has sophisticated data analytics that flag claims where the cost profile looks unusual for the sector.

For example, a Bristol-based biotech startup claimed £340,000 in staff costs for a team of five people. The specialist reviewed the time records and found that two of the five spent 70% of their time on regulatory compliance, not R&D. The specialist reduced the claim to £210,000. The startup was unhappy until they learned that a competitor who claimed the full amount was now in a full HMRC enquiry with legal fees exceeding £50,000.

The Claim Would Trigger an HMRC Enquiry

Some claims are technically valid but statistically risky. HMRC uses risk-based selection criteria to decide which claims to investigate. A specialist who knows the system will refuse a claim that is likely to trigger an enquiry, even if the project qualifies.

Common red flags include:

  • First-time claims above £50,000
  • Claims in sectors HMRC is actively targeting (software, construction, hospitality)
  • Claims where the narrative description is vague or inconsistent
  • Claims submitted late without reasonable excuse
  • Claims from companies that have previously had an enquiry

If your specialist believes the claim has a high probability of being selected for enquiry, they may refuse to submit it until the supporting evidence is stronger. That is not a rejection of your project. It is a risk management decision that protects you from the cost and disruption of an HMRC investigation.

You can read more about the fundamentals of R&D tax credits to understand how the process works before you approach a specialist.

The Company Structure Makes the Claim Invalid

R&D tax credits are available to limited companies that are within the charge to UK corporation tax. Sole traders, partnerships, and LLPs cannot claim under the main schemes.

If you are a sole trader or partnership doing genuine R&D, you may need to incorporate before you can claim. A specialist should tell you that upfront rather than taking your money for a claim that HMRC will reject on eligibility grounds.

Other structural issues include:

  • Companies that are dormant or non-trading
  • Companies that have not filed their accounts or corporation tax returns
  • Companies that are in liquidation or striking-off process
  • Companies that have changed ownership and the R&D was done under the previous owner

Each of these scenarios requires specialist advice. A good R&D tax credit specialist will assess your company structure before agreeing to work with you.

What to Do When a Specialist Refuses Your Claim

If a reputable specialist refuses your claim, do not simply go to the next firm. Ask why. Get a written explanation of the specific reasons the project does not qualify.

Then consider whether you can address those reasons. Can you gather better evidence of the technological uncertainty? Can you restructure your cost records to isolate qualifying expenditure? Can you wait until the project reaches a stage where the uncertainty is clearer?

If the refusal is based on genuine non-qualification, accept it. Claiming anyway through a less scrupulous firm will cost you more in the long run when HMRC opens an enquiry and demands repayment with interest and penalties.

Our services include R&D tax credit preparation and review. We will tell you honestly whether your project qualifies and, if it does not, explain exactly why. That honesty protects you from the far greater cost of a failed claim.

How to Choose an R&D Tax Credit Specialist

Look for a specialist who asks hard questions before agreeing to work with you. If they promise a claim without understanding your technical work, walk away. If they quote a fixed percentage fee before reviewing your project, walk away. If they tell you that everything qualifies, walk away.

A good specialist will:

  • Ask for technical documentation before quoting
  • Interview your technical staff to understand the project
  • Explain the qualifying tests and why they apply to your project
  • Tell you if the claim is borderline and what the risks are
  • Refuse the claim if it does not meet the criteria

If you are unsure whether your project qualifies, contact us for a no-obligation review. We will give you a straight answer, even if that answer is no.

Visit our contact page to arrange an initial discussion about your R&D project.