When an R&D Tax Credit Specialist Refuses Your Claim

You have a project that genuinely pushed technology forward. A new software algorithm. A novel manufacturing process. An engineering breakthrough. You approach an r&d tax credit specialist expecting a straightforward claim. And they say no.

That feels wrong. You have the technical work. You have the costs. Why would any firm turn down a legitimate claim worth thousands of pounds?

The short answer is this: the best specialists say no more often than you think. They do it because an aggressive claim that gets rejected by HMRC costs you far more than a declined claim ever will. An enquiry can run for 12 to 18 months, eat up your management time, and trigger a full review of your corporation tax returns going back several years.

As ICAEW qualified accountants working with UK businesses across every sector, we have seen both sides. We have submitted successful claims for software consultancies in Manchester, engineering firms in Birmingham, and biotech startups in Cambridge. We have also turned down work. This article explains the legitimate reasons a specialist would refuse a claim, and why that refusal is often the best outcome for you.

The Four Real Reasons a Specialist Says No

Every R&D tax credit specialist operates within the same legislative framework. HMRC's guidelines are clear, but interpretation varies. A firm that promises a claim for every client is either inexperienced or cutting corners. A firm that says no occasionally is doing its job properly.

Here are the four most common reasons a legitimate specialist will decline a claim.

1. The Project Does Not Qualify as R&D

This is the most frequent reason for refusal. Many business owners believe that any technical project qualifies. It does not. HMRC's definition of R&D for tax purposes is specific and narrower than common usage.

To qualify, the project must seek an advance in science or technology. That means resolving uncertainty that a competent professional in your field could not resolve using publicly available knowledge. It is not enough that the project was difficult, expensive, or time-consuming. It must have involved genuine technical uncertainty.

Common examples of work that does not qualify include:

• Routine software development using standard libraries and frameworks with no novel elements.
• Standard engineering design work where the outcome is predictable.
• Implementing an off-the-shelf system with standard configuration.
• Market research or customer surveys, even if technically complex to execute.
• Ongoing maintenance, bug fixes, or minor feature updates.

A specialist who reviews your project and finds no genuine technical uncertainty should tell you. It is far better to hear that before you submit a claim than after HMRC opens an enquiry.

We have had conversations with a six-figure freelance consultant in Bristol who was convinced their software project qualified. The project was well executed, profitable, and technically demanding. But it used established methods. There was no uncertainty. We explained why, and the client accepted it. That client still works with us on other tax matters because they trust us to be honest.

2. The Costs Are Not Qualifying Expenditure

Even if the project qualifies, the costs must meet HMRC's definition of qualifying expenditure. Many business owners overestimate what counts.

Qualifying costs are limited to:

• Staff costs (salaries, employer NI, pension contributions) for employees directly engaged in R&D.
• Consumable items used up in the R&D process (materials, energy, water).
• Software licence costs directly used in the R&D.
• Subcontractor costs (under specific rules that differ between the SME and RDEC schemes).
• Externally provided workers (agency staff under your supervision).

What does not qualify:

• General overheads, rent, rates, insurance.
• Marketing and sales costs.
• Capital expenditure on equipment (though capital allowances may apply separately).
• Dividends or profit share to directors.
• Costs incurred before the project started or after it finished.

A specialist who sees a claim built on non-qualifying costs will often refuse to submit it. The risk is not just that those costs get disallowed. HMRC may challenge the entire claim, including the genuinely qualifying elements.

3. The Supporting Evidence Is Inadequate

HMRC requires contemporaneous evidence. That means records created at the time the work happened, not reconstructed months or years later.

The minimum evidence package includes:

• Technical documentation showing the uncertainty, the work done to resolve it, and the outcome.
• Project records with dates, staff involved, and hours spent.
• Cost breakdowns linked to specific projects.
• Where applicable, evidence of failed approaches and why they were abandoned.

If you approach a specialist with a claim based on a single spreadsheet of costs and no technical narrative, they will likely refuse. Reconstructing evidence after the fact is risky. HMRC has seen too many claims where the documentation looks like it was written retrospectively to match the numbers.

A specialist who insists on proper evidence before submitting is protecting you. If HMRC opens an enquiry, that evidence is your defence. Without it, you have nothing.

4. The Claim Is Too Aggressive Relative to Your Business Profile

This is the reason that surprises most business owners. A specialist may look at a technically valid project with qualifying costs and still say no.

HMRC uses risk profiling. If your claim is disproportionate to your business size, sector, or historical R&D activity, it flags for review. A sole trader in retail claiming £200,000 in R&D costs will get an enquiry. A 4-employee software consultancy in Manchester turning over £420,000 claiming £300,000 in R&D costs will get an enquiry.

The claim must be proportionate. A specialist who understands HMRC's risk models will assess whether your claim falls within an acceptable range. If it does not, they may recommend reducing the claim or declining it entirely.

This is not the specialist being cautious for no reason. An enquiry into an inflated claim can result in:

• Full disallowance of the R&D claim.
• Interest and penalties on the tax underpaid.
• A complete review of your corporation tax returns for multiple years.
• Significant management time and legal costs defending the position.

A refused claim is frustrating. An HMRC enquiry that costs you £30,000 in professional fees and six months of stress is worse.

What Happens When a Specialist Says No

A legitimate specialist will explain their reasoning clearly. They should provide a written explanation of why the claim does not meet HMRC's criteria, and where possible, suggest what would need to change for a future claim to succeed.

Some specialists will offer a second opinion service. If you believe your project genuinely qualifies, you can ask another firm to review it. But be cautious. A firm that says yes when others say no may be taking risks you do not want.

If you are turned down, ask these questions:

• Which specific part of the project fails the R&D definition?
• Which costs are being excluded, and why?
• What evidence would be needed to support the claim?
• Is the issue fixable for a future accounting period?

A good specialist will answer these questions without charging you for the conversation. They want you to understand why, even if the answer is disappointing.

How to Avoid a Refusal in the First Place

The best way to avoid a refused claim is to plan for R&D from the start of your project. Do not wait until year-end to think about documentation.

Practical steps you can take now:

• Maintain project logs with dates, objectives, and technical challenges.
• Record failed approaches and why they did not work.
• Track staff time against specific R&D projects using timesheets or project management software.
• Keep purchase records for consumables and software used in R&D.
• Review your claim with a specialist before the year-end, not after.

If you use accounting software like Xero, FreeAgent, or QuickBooks, set up a separate cost centre or tracking category for R&D projects from day one. That makes cost identification straightforward at year-end.

For limited company directors, remember that R&D tax credits are a corporation tax relief. They reduce your taxable profit or create a repayable credit if you are loss-making. The claim is submitted through your corporation tax return (CT600) with a supplementary form. Getting it right matters.

When You Should Worry About a Refusal

Not every refusal is legitimate. Some specialists lack the technical expertise to assess complex projects. Others are simply risk-averse to the point of being unhelpful.

You should be concerned if:

• The specialist cannot explain why your project does not qualify.
• They refuse to review your evidence or technical documentation.
• They give a blanket refusal without considering the specifics of your project.
• They have a track record of turning down every claim that requires more than minimal work.

In those cases, seek a second opinion from a firm with genuine technical expertise. Our R&D tax credit team regularly reviews claims that other firms have declined. Sometimes we agree with the refusal. Sometimes we find a claim that was missed.

The difference is that we explain our reasoning either way.

The Bottom Line on Refused Claims

An R&D tax credit specialist who refuses your claim is not failing you. They are doing their job. They are protecting you from the far greater cost of an HMRC enquiry.

If your claim is turned down, take it seriously. Ask for the reasoning. Fix the issues for next time. And if you genuinely believe the specialist is wrong, get a second opinion from a firm with the technical expertise to assess your work properly.

But do not shop around until you find someone who says yes. That is how businesses end up in enquiries that cost ten times what the claim was worth.

If you are unsure whether your project qualifies, speak to us. We will give you a straight answer, even if that answer is no.