How to Read an HMRC R&D Enquiry Letter
- Feb 5
- 4 min read
A clear, structured guide to understanding what HMRC is signalling — and how to stay in control
An HMRC R&D enquiry letter doesn’t arrive gently. It interrupts your day, creates uncertainty, and forces you into a reactive mindset before you’ve even processed what the letter is actually saying. Even businesses with legitimate R&D activity feel the same initial spike of:
What does this mean
How serious is this
What do I do next
That reaction is normal. The risk comes from acting before you understand the signal.
This guide strips out the noise and shows you how to interpret the letter properly — so you can respond from a position of clarity, not panic.
Why HMRC sends enquiry letters (and why it’s not a judgement)
HMRC enquiries are triggered by patterns, not accusations. The system flags claims based on:
sector‑level risk
claim size relative to company size
narrative gaps
accountant or consultant ‑template language
missing or vague technical justification
cost anomalies
These are automated or semi‑automated triggers. They do not imply wrongdoing. They imply “we need more clarity.” An enquiry letter is a request for justification, not a verdict.
The first 24 hours: where most businesses make avoidable mistakes
The danger isn’t the letter — it’s the reaction to it.
Common early mistakes include:
handing it to someone who isn’t trained in enquiry defence
drafting a rushed reply
over‑explaining
ignoring it for a few days
assuming it’s a simple admin request
These actions create unnecessary risk because they happen before the letter has been properly decoded.
Your first step is not to respond. Your first step is to interpret the HMRC enquiry letter.
What an HMRC R&D enquiry letter actually is
HMRC is asking you to demonstrate that your claim is:
eligible
technically justified
evidence‑based
consistent
credible
The letter itself doesn’t explain this clearly. That’s why businesses misread it — and why responses often escalate enquiries instead of resolving them.
The anatomy of an HMRC R&D enquiry letter
Once you understand the structure, the letter becomes predictable. HMRC uses a consistent format because they’re testing specific weaknesses.
1. The opening paragraph
This sets the frame:
HMRC is reviewing your claim
They require additional information
They expect a response by a specific date
What this actually means: A risk signal was detected, and HMRC wants to see how you justify your position.
2. The “we need more information” section
This is the core of the enquiry. It tells you:
the scope of HMRC’s concern
whether the issue is technical, financial, or both
how deep the review may go
This section determines the entire defence strategy.
3. The technical questions
This is where most claims fail.
HMRC is testing:
whether genuine uncertainty existed
whether systematic work took place
whether competent professionals were involved
whether your explanation is coherent and defensible
If your original claim was narrative‑light or template‑driven, HMRC will detect it immediately.
4. The financial questions
HMRC may request detail on:
staffing costs
subcontractors
apportionments
consumables
qualifying vs non‑qualifying activities
They’re checking for inflation, inconsistency, or weak rationale.
5. The deadline
This is non‑negotiable. Missing it signals risk and can escalate the enquiry instantly.
What HMRC is signalling between the lines
HMRC’s language is formal, but the intent is clear if you know how to read it:
“Provide more detail” → Your narrative is too thin
“Explain the uncertainty” → Eligibility is in question
“Evidence of systematic work” → They suspect the project wasn’t structured
“Break down staffing costs” → They’re checking for inflation or poor apportionment
“Supporting documentation” → They want proof, not opinion
Understanding these signals is essential for a controlled response.
Risk indicators inside the letter
Some enquiries are routine. Some indicate deeper concern.
Routine indicators:
Broad questions
Requests for clarification
No mention of eligibility concerns
No specialist unit involved
Higher‑risk indicators:
Direct challenges to eligibility
Requests for detailed technical justification
Cost‑specific challenges
References to inconsistencies
Escalation to a specialist reviewer
Routine enquiries can be closed cleanly. Higher‑risk enquiries require structured defence.
What NOT to do in the first 24 hours
Avoid these actions:
replying immediately
sending raw technical documents
rewriting your project history
assuming anyone can handle it
ignoring the letter
treating it as a simple admin request
Your first 24 hours should be about interpretation, not action.
Before you go any further
If you’re unsure how serious your enquiry is, start with the Quick Risk Read — no charge. It gives you an immediate sense of:
the tone
the signals
the risk level
the likely reviewer concerns
If you already know you need a deeper assessment, the £595 Enquiry Audit gives you:
detailed risk mapping
technical + financial defensibility review
a structured response strategy
escalation guidance
And if you want the safest, most controlled route to closing the enquiry, you can book Full Enquiry Defence, where we take over:
drafting your full technical and financial response
structuring the narrative to HMRC standards
managing all communication with HMRC
guiding you through every stage until the enquiry is resolved
This three‑step pathway gives you clarity before you commit — and certainty when you need it.
Comments