(UNITED KINGDOM) — UK companies claiming R&D Tax Relief must now treat HMRC’s Additional Information Form as a required digital “gate” to their claim, because an R&D claim can be removed if the AIF is not filed first.
This filing guide is written for tax year 2026 activity (corporation tax returns typically filed in 2027, depending on your accounting period end). It explains what the AIF is, what goes into it, and how to file it without derailing your claim.
It also flags January 2026 U.S. immigration enforcement and H‑1B selection changes that raise the documentation burden for globally mobile R&D teams.
1) HMRC Additional Information Form (AIF): what it is and why it now matters for R&D Tax Relief claims
HMRC’s Additional Information Form (AIF) is a mandatory digital submission linked to an R&D tax relief claim. It is not optional supporting paperwork. It is a required step in the claim process.
The practical point many finance teams miss is sequencing. The AIF must be submitted before the company tax return that includes the R&D claim.
HMRC built the AIF as an operational control. If the AIF is missing when the return is filed, HMRC’s systems can treat the R&D claim as invalid and remove it.
HMRC’s policy goal is straightforward: standardize what companies disclose about R&D claims, improve claim quality and consistency, and reduce fraud and error by requiring structured, comparable disclosures.
HMRC also refreshed guidance in early 2026 on two areas that drive eligibility and claim route: SME status calculations and the intensity condition. The detailed thresholds and related parameters are shown in the system’s reference tool.
In practice, the update means you should re-check classification workpapers before filing.
⚠️ Warning: If your corporation tax return is filed with an R&D claim before the AIF is accepted, you risk the claim being removed procedurally. Fixing this later can be slow and costly.
2) What you must include inside the AIF: project narrative, SME status, and the intensity condition
The AIF is not a one-line attestation. It is a structured disclosure that asks for enough detail to let HMRC risk-assess your R&D claim quickly.
The technical narrative: what HMRC expects per project
For each project, you should be ready to explain—in plain, technical language—three core items. These are the advance sought, the uncertainties, and how you addressed those uncertainties.
- The advance sought or achieved in science or technology
- The uncertainties that competent professionals could not readily resolve
- How you addressed those uncertainties, including testing and iteration
This narrative is not marketing copy. It should match what your engineers and scientists wrote in design docs, test reports, or lab notes.
Defining a “project” without overdoing it
Project definition is a frequent failure point. Striking the right balance avoids both over-fragmentation and over-aggregation.
- Over-fragmentation creates many thin narratives with repeated boilerplate. That can look like a template claim.
- Over-aggregation creates one vague narrative that fails to show eligible uncertainties for distinct workstreams.
A practical approach is to define projects around a clear technical objective and uncertainty set. Use internal artifacts, such as epics, work packages, or experiment plans, to keep boundaries defensible.
SME status: why classification changes the filing pathway
SME status influences which R&D regime you are in and how HMRC expects you to calculate and support the claim. Your AIF disclosures should be consistent with ownership, headcount, and financial measures.
Specifically, ensure consistency with ownership and group structure, headcount and financial measures used for SME testing, and any linked or partner enterprise analysis.
If you are close to the boundary, treat the SME memo like an audit-ready workpaper. Keep versions and sign-offs.
Intensity condition: what it measures conceptually
The intensity condition tests whether qualifying R&D spend is sufficiently high relative to total spend, using a percentage test. The system’s reference tool shows the current threshold and related parameters.
From a controls perspective, intensity testing forces two disciplines: a defensible definition of total spend used in the denominator and clear categorization of qualifying R&D and excluded costs.
Sequencing is still the control point
Even if your narratives are excellent, the claim can still fail procedurally if the AIF is not filed first. Build a calendar that treats the AIF as a filing prerequisite, not an add-on.
3) US DHS/USCIS developments (Jan 2026): what changes for R&D employers and sponsored researchers
While United Kingdom’s HM Revenue and Customs (HMRC) sets the AIF rules, January 2026 U.S. immigration actions matter for cross-border R&D teams because they raise the cost of errors and inconsistencies.
Operation PARRIS: stronger fraud posture and record re-checks
DHS and USCIS announced Operation PARRIS in January 2026, describing broader fraud investigations and re-examination of prior approvals in certain contexts. For employers, the tax takeaway is that “evidence discipline” is now a shared requirement across departments.
If your technical narratives say one thing to HMRC, but immigration petitions describe different duties, projects, or credentials, you create credibility risk.
H‑1B weighted selection rule: hiring strategy meets documentation reality
A final rule published in late 2025 and effective in early 2026 introduced a weighted selection approach for H‑1B registrations. Conceptually, this can push employers to tighten job leveling and wage setting documentation.
- Tighten job leveling and wage setting documentation
- Keep role descriptions consistent across HR, immigration counsel, and R&D leadership
- Maintain clear evidence of specialty occupation duties for research roles
This is not just an HR issue. It affects how you plan project staffing and timelines for deliverables that support R&D relief claims.
Operation “Catch of the Day”: workplace enforcement signal
ICE announced an enforcement surge in January 2026 under the “Catch of the Day” name. The broader signal is increased attention to workplace compliance.
- I‑9 and work authorization records must remain consistent
- Vendor and contractor documentation should be clean
- Internal role descriptions must align with actual work performed
The common theme with the AIF is simple: structured claims and structured evidence are becoming the norm.
4) Why this matters for high-skilled researchers: documentation load, mobility friction, and compliance risk management
R&D teams are often asked to “tell the story” three different ways: technical truth, tax eligibility narratives for the AIF, and immigration support evidence for visas and work authorization.
Each has a different purpose. But contradictions are where audits and investigations begin.
Researchers moving from academia to private R&D
In U.S. immigration contexts, researchers shifting from academia to private R&D can face higher expectations around credible evidence of impact and role clarity. That mirrors HMRC’s insistence on project narratives that show real technical uncertainty.
Dual-country documentation strategy
Build a single documentation spine that can support both systems without overstatement. Use engineering artifacts as the “source of truth” and derive the AIF narrative from those artifacts.
- Use engineering artifacts as the source of truth
- Derive the AIF narrative from those artifacts
- Keep immigration role descriptions aligned with the same project record
Do not inflate novelty claims for tax purposes. Do not exaggerate leadership claims for immigration purposes. Consistency is safer than rhetorical strength.
Cost and timeline planning
Immigration processing pauses, enforcement focus, and fee pressure can change staffing plans mid-project. That can affect who performed qualifying work, where the work occurred, and how you allocate and evidence costs.
If key staff rotate in and out of the UK or U.S., make sure time tracking, subcontractor statements, and experiment logs remain complete.
Governance practices that reduce risk
- Version control for narratives and calculations
- Dual sign-off: technical lead + finance/tax
- Retention of underlying calculations and key evidence
The system’s timeline tool shows the milestone dates that should anchor your internal review calendar.
5) Action plan for employers and applicants: building an AIF-ready R&D claim file while supporting cross-border mobility
This is the execution plan that keeps the AIF requirement from becoming a last-minute scramble. Follow the steps below to create a controlled, reviewable claim file.
Step 1 — Confirm your claim pathway and gate requirements
- Confirm whether you are claiming under the SME route or another regime.
- Re-check SME status workpapers using the refreshed guidance.
- Confirm whether intensity testing applies and document your methodology.
Step 2 — Define projects and assign narrative owners
- Create a project list with clear boundaries and dates.
- Assign one narrative owner per project, usually the technical lead.
- Set a style rule: no boilerplate, no marketing language, cite artifacts.
Step 3 — Build the evidence pack (technical + finance)
Collect both technical and financial support materials before drafting the AIF. Keep files organized and linked to each project narrative.
Technical support examples include design notes, architecture docs, lab notebooks, test plans, test results, failure analysis, and sprint artifacts showing iteration around uncertainties.
Finance support examples include cost categorization memos, payroll and time allocation reports, and subcontractor scopes, invoices, and deliverables mapping.
Step 4 — Draft the AIF narrative and run a consistency review
Run a cross-functional consistency check before filing. The goal is to remove contradictions between technical, finance, tax, and immigration records.
- R&D lead validates technical accuracy
- Finance validates cost logic and project mapping
- Tax lead checks eligibility statements and completeness
- HR/legal checks alignment with immigration role descriptions
Step 5 — File the AIF first, then file the corporation tax return containing the claim
Treat filing as a two-step sequence, not one combined act. Submit the AIF digitally and confirm acceptance before filing the corporation tax return.
- Submit the AIF digitally and confirm submission acceptance.
- Submit the corporation tax return that includes the R&D claim.
Step 6 — Create a retention and monitoring cadence
- Retain claim calculations and evidence in a controlled repository.
- Set a quarterly review of HMRC and DHS/USCIS updates.
- Escalate only changes that affect eligibility, thresholds, or filing steps.
Eligibility checklist (AIF + R&D claim readiness)
| Checkpoint | What “yes” looks like | Why it matters |
|---|---|---|
| UK company is making an R&D tax relief claim | You will include R&D figures in the corporation tax computation | The AIF requirement is linked to the claim |
| AIF is planned as a prerequisite filing | AIF will be submitted and accepted before the return is filed | Missing AIF can trigger claim removal |
| Projects are defined at a workable level | Each project has a clear objective and uncertainty set | AIF requires project-by-project narratives |
| Technical uncertainty is documented | Records show uncertainty and iterative work | Narrative must be supported by evidence |
| SME status is analyzed and documented | Group structure and metrics support classification | Route affects scrutiny and calculations |
| Intensity testing methodology is documented | Clear numerator/denominator logic and support | Threshold test affects eligibility in some cases |
| Cross-border roles are consistent | Immigration role descriptions align with real work | Inconsistency raises compliance risk |
Step-by-step filing process (with form names)
UK side (HMRC)
- Prepare your R&D claim calculations for the accounting period.
- Draft project narratives and complete SME/intensity analyses.
- Submit HMRC’s Additional Information Form (AIF) digitally.
- File the corporation tax return that contains the claim (commonly Company Tax Return CT600 with computations and accounts).
- Retain the full evidence pack and submission confirmations.
U.S. side (when your team is internationally mobile)
Even if the company claim is UK-based, internationally mobile staff may trigger U.S. individual reporting. U.S. tax residents generally report worldwide income and may have foreign account reporting obligations.
Relevant IRS materials include the items below.
- IRS Publication 519 (U.S. Tax Guide for Aliens) at IRS Publication 519 (PDF)
- The IRS international portal at International taxpayers
- IRS guidance on FBAR reporting (FinCEN Form 114 filing obligation)
- IRS forms and publications for Form 1040, treaty forms, and international disclosures
Deadlines and extension options (what to plan around)
You should plan on three clocks: AIF timing, UK corporation tax filing timing, and U.S. individual timing if applicable. Each has separate rules and deadlines.
1. AIF timing: must be submitted before the return containing the claim. 2. UK corporation tax filing timing: generally tied to the accounting period end and statutory filing window.
3. U.S. individual timing (if applicable): U.S. tax filing, extension rules, and foreign account reporting deadlines. The system’s quick-reference tool lists the exact milestone dates for the current policy and enforcement events.
📅 Deadline Alert: Build the AIF drafting schedule backwards from your corporation tax filing deadline. The AIF cannot be treated as a same-day attachment.
Documents you’ll need (checklist)
Organize documents into corporate & tax, project & technical, and people & mobility categories. Each category supports different parts of the AIF and the evidence pack.
Corporate and tax
- Group ownership chart and related-party list
- Annual accounts and trial balance
- Corporation tax computations and draft CT600 package
- R&D cost schedules with clear categories and mappings
Project and technical
- Project charter or statement of technical objective
- Uncertainty descriptions and why they were not readily solvable
- Experiment logs, test results, prototypes, and failure reports
- Change control records and version history
People and mobility (when applicable)
- Role descriptions and org charts for key researchers
- Work location records and assignment letters
- Immigration petition support narratives for consistency checks
- Time allocation support for cross-border staff
IRS resources and professional help recommendations
If your R&D workforce is internationally mobile, tax and immigration compliance often intersect in the documentation. For U.S. tax residency, treaty positions, and international reporting, start with the IRS hub and publications below.
- IRS international taxpayers hub: International taxpayers
- IRS Publication 519 (aliens): IRS Publication 519 (PDF)
- IRS forms and publications: Forms and publications
On the UK side, treat the AIF as a controlled filing with audit-ready workpapers. For cross-border teams, involve both a UK corporation tax adviser and U.S. immigration counsel early.
Keep a single evidence repository with disciplined version control to support both tax and immigration reviews.
Action items to close out your 2026 claim file
- Assign project narrative owners and set internal review deadlines now.
- Complete SME and intensity analyses before drafting narratives.
- Submit the AIF before filing the return that contains the R&D claim.
- For mobile researchers, confirm U.S. tax residency and foreign reporting duties using IRS Publication 519 and the IRS international portal.
⚠️ Disclaimer: This article is for informational purposes only and does not constitute tax, legal, or financial advice. Tax situations vary based on individual circumstances. Consult a qualified tax professional or CPA for guidance specific to your situation.
