United Kingdom — Startups · tax

How to Respond to an HMRC R&D Enquiry Letter as a UK Startup

HMRC has intensified compliance checks on UK tech startups, frequently issuing aggressive, templated enquiry letters that challenge legitimate R&D tax relief claims. If your company has received a check under Schedule 18 of the Finance Act 1998, you must respond methodically to substantiate your technological advances, defend your qualifying expenditure, and prevent punitive penalties.

The Statutory Basis of HMRC Enquiries in the United Kingdom

In the United Kingdom, HMRC initiates a formal compliance check into a startup's Corporation Tax Return (CT600) under Paragraph 24, Schedule 18 of the Finance Act 1998. HMRC generally has a statutory window of 12 months from the date your return was filed on time to deliver this notice. An enquiry freezes pending cash credits and places the legal burden on your company to prove that your work meets the statutory threshold for Research and Development.

R&D tax relief is defined in law under Section 1138 of the Corporation Tax Act 2010 and Part 13 of the Corporation Tax Act 2009. These provisions incorporate the Department for Science, Innovation and Technology (DSIT) Guidelines (formerly the BEIS Guidelines). Under paragraphs 3 and 4 of the DSIT Guidelines, an activity qualifies as R&D only if it directly seeks an advance in overall science or technology through the resolution of scientific or technological uncertainty. Crucially, the advance cannot be readily deducible by a competent professional working in the field.

Understanding HMRC's 'Volume Compliance' Tactics

Recent enforcement by HMRC's Individual and Small Business Compliance (ISBC) unit relies heavily on standardized, volume-driven enquiry letters that often dismiss software architecture, custom engineering, or proprietary data models as routine commercial development. Caseworkers often argue that because commercial off-the-shelf tools exist, no technological uncertainty was present.

This approach disregards the legal reality: under paragraph 6 of the DSIT Guidelines, adapting existing technologies or combining systems in a novel manner qualifies as R&D if the integration creates technical uncertainties that standard engineering principles cannot resolve. HMRC may also threaten inaccuracies penalties under Schedule 24 of the Finance Act 2007. To defeat these boilerplate challenges, your reply must reframe the dispute around strict statutory tests rather than high-level pitch-deck language.

Constructing an Evidentiary Defense and Managing Escalation

Your rebuttal must feature technical documentation authored by your lead technical staff (the statutory 'competent professionals'). Point to specific code commits, architectural design documents, failed iterations, and benchmark tests from the accounting period in question. If HMRC issues an informal request or escalates to a formal information notice under Schedule 36 of the Finance Act 2008, you must strictly meet or formally extend statutory deadlines.

If an HMRC caseworker refuses to engage with technical merits, you are not trapped. You have the right to request an Alternative Dispute Resolution (ADR) process, demand a formal statutory review by an independent HMRC officer, or appeal a Closure Notice to the First-tier Tribunal (Tax Chamber). You can use Caunsel to research the exact DSIT guidance applicable to your software stack, organize technical contemporaneous evidence into a structured case, or connect with an independent UK tax lawyer to draft your formal response before the statutory deadline lapses.

Steps

• Verify the statutory validity and deadline of the notice: confirm the letter references Paragraph 24 of Schedule 18, Finance Act 1998, and verify it was served within the 12-month window from your filing date.
• Request a formal deadline extension immediately in writing if the typical 30-day response window is insufficient to gather deep engineering evidence.
• Identify your 'competent professionals' under the DSIT Guidelines: document the qualifications, employment history, and peer-standing of the key engineers or scientists who led the project.
• Draft technical project narratives addressing the exact statutory questions: establish the industry baseline, detail why the solution was not readily deducible, and document the specific uncertainties resolved.
• Reconcile qualifying expenditure line-by-line: provide clean payroll apportionments, contractor invoices, and software license records that tie directly to qualifying project activities.

Common mistakes

• Providing high-level marketing, investor, or grant pitch decks instead of low-level technical documentation showing technological uncertainty and failed attempts.
• Relying solely on an unregulated R&D claims boutique that prepared the initial claim without involving your actual software engineers or CTO in the enquiry response.
• Ignoring the letter or missing statutory deadlines, which risks HMRC issuing a Revenue Amendment or formal discovery assessment removing the claim and imposing maximum Schedule 24 penalties.
• Conceding that work was 'routine development' simply because the project was commercially successful or delivered on time.

Questions people ask

Can HMRC open an enquiry if our R&D tax credit has already been paid out?

Yes. Processing a payable tax credit does not mean HMRC has formally accepted your claim. Under Paragraph 24 of Schedule 18, Finance Act 1998, HMRC can open an enquiry up to 12 months from when your return was filed, and claw back funds with interest if the claim is disallowed.

What happens if our R&D project failed?

Project failure actually strengthens your defense. Under paragraph 38 of the DSIT Guidelines, projects that fail to achieve their technological objective or are aborted due to insurmountable technical hurdles are fully eligible, as failure demonstrates genuine technological uncertainty.

What penalties can HMRC impose if they reject our startup's R&D claim?

Under Schedule 24 of the Finance Act 2007, HMRC can impose penalties ranging from 0% to 30% for 'careless' errors and up to 70% or 100% for 'deliberate' inaccuracies. Demonstrating that you took 'reasonable care'—such as consulting qualified advisors and maintaining engineering records—is vital to eliminate penalties.

General information only, last updated 2026-11-05. Caunsel is not a law firm and does not practise law. AI answers and this guide are not legal advice. Verify filings, deadlines, and statutes with a licensed lawyer in United Kingdom — Startups.