Over the last few years, anyone working seriously in the Research and Development (R&D) tax relief space has seen the writing on the wall. HMRC has fundamentally shifted its focus. It is no longer just about calculating numbers; it is about governance, technical credibility, absolute accountability and the quality of claim preparation.
With the transition to the unified RDEC / Merged Scheme framework, HMRC is using its digital infrastructure to rigorously gatekeep claims. Two critical operational developments within the Additional Information Form (AIF) submission process signal exactly how HMRC is profiling risk.
In this news item I use my insights as an R&D professional consultant to assess what this means for claimant companies. (Published May 2026)
One of the most telling updates to the mandatory AIF online form is the expansion of the senior officer declaration section.
Previously, the AIF required a nominated senior officer to merely confirm the submission and agree to receive email communications. Today, HMRC explicitly requires confirmation that the signing senior officer has personally read HMRC’s formal R&D guidance before clicking submit. This seems designed to dismantle a defense used in the past to avoid penalties for invalid claims, where directors were able to make the case that they had acted with "reasonable care" by hiring a specialist advisor.
The Takeaway: HMRC is actively trying to end the era of "hands-off" sign-offs. They want to ensure directors cannot claim ignorance if a submission is found to be non-compliant.
Personally, I have always believed that any director signing off on an RDEC claim must thoroughly understand four core areas:
The Scope: The exact nature of the projects being claimed.
The Science: The precise technical basis on which the work qualifies.
The Math: The exact cost breakdowns included in the submission.
The Liability: The legal weight of the declaration regarding R&D being made to HMRC.
This shift highlights why the Competent Professional (the technical expert leading the project) can no longer be a passive figure whose name is simply added to a report for credibility. HMRC expects genuine, collaborative technical input. A robust claim must explicitly detail:
The specific scientific or technological uncertainties encountered.
Why the solution was not readily deducible to another experienced professional in that field.
How the project actively sought to achieve an overall advance in science or technology.
The second development is the introduction of automated Standard Industrial Classification (SIC) code challenge questions directly within the AIF submission workflow.
If a company’s primary SIC code falls outside of traditionally tech-heavy or scientific sectors, the portal triggers an explicit prompt stating the code is "not usually associated with qualifying R&D activity." The user must then provide a dedicated, explicit justification of why the work qualifies before the form can even be submitted.
This is a clear window onto one aspect of HMRC’s automated risk-profiling algorithms.
Check Company SIC Code ──► Outside Traditional R&D Sector?
▼ (Yes)
Triggers AIF Challenge Block
▼
Requires Explicit Technical Justification to Proceed
Many genuinely innovative businesses operate in sectors that don’t look like "white-lab-coat" R&D at first glance. Over years of helping companies claim, it's been demonstrated over and over that qualifying R&D can be successfully uncovered in many sectors:
Manufacturing process optimisations
Proprietary software systems and architecture
Materials development and structural engineering challenges
Food production techniques and shelf-life advancements
A SIC code alone does not dictate your eligibility. However, to pass this automated scrutiny, your submission strategy must adapt.
Audit Your SIC Codes - Ensure your primary code accurately reflects your trading activity, and utilise supplementary SIC codes (up to four) if you undertake distinct technical activities.
Align Narratives Exactly - Ensure your technical write-ups explicitly cross-reference how a business in your sector is performing work that meets the strict statutory definition of R&D.
Proactively Contextualise - Treat the SIC challenge not as an obstacle, but as an early opportunity to clearly frame the technical boundaries of your project.
We are also seeing a rise in automated emails sent by HMRC shortly after an AIF is filed. These communications often use urgent language surrounding compliance risks or prompt the business to "review" aspects of their recent filing.
For a director unfamiliar with the current, aggressive compliance environment, these emails can cause immediate panic.
It is important to understand that in the vast majority of cases, these are automated, system-wide process communications—not a formal compliance enquiry.
Currently, formal HMRC enquiries are still opened via official letters rather than immediate automated emails. Part of my role as a specialist is preparing clients for these automated touchpoints so that no one is unnecessarily alarmed after submitting a thoroughly compliant, peer-reviewed claim.
These systemic tightening measures shouldn't worry companies undertaking legitimate R&D. The RDEC regime remains incredibly robust for businesses driving technical advancements.
What has changed permanently is the margin for error. The days of lightly prepared, boilerplate claims with minimal technical substance are gone. Governance, documentation and expert technical oversight are now mandatory components of a successful submission.
Navigating the modern AIF portal, managing automated risk triggers and defending your technical narratives requires specialised expertise.
If you want to ensure your claim is structured to withstand intense HMRC scrutiny while maximising your legitimate return, let’s talk. At RandDTax we work directly with your financial and technical teams to build robust, compliance-led submissions that protect your business and your directors.