HMRC Compliance, AIF Filing & Pre-Notification Rules: A CFO Guide to UK R&D Tax Relief

HMRC Compliance, AIF Filing & Pre-Notification Rules

For UK SaaS, software and technology businesses, calculating the R&D tax benefit represents only part of the process.

HMRC compliance starts before the claim reaches the Corporation Tax return.

The current framework requires companies to manage two important reporting requirements:

• Additional Information Form (AIF)
• Claim Notification Form (CNF), where the notification rules apply

Missing either requirement can create a serious problem. HMRC states that a company must submit the AIF before, or on the same day as, its Company Tax Return (CT600). If the company submits the CT600 first, HMRC will reject the R&D claim.

For CEOs and CFOs, the practical objective is simple:

Build the R&D claim around the HMRC filing timetable, not around the year-end tax return deadline.

What Is the Additional Information Form (AIF)?

The Additional Information Form gives HMRC detailed information about the R&D claim before the company submits its Corporation Tax return.

Companies must submit an AIF for each accounting period in which they claim R&D tax relief or R&D Expenditure Credit.

The AIF captures information such as:

• Company details
• Accounting period
• R&D expenditure
• Qualifying projects
• Project descriptions
• R&D adviser details, where applicable
• Senior officer details
• Relevant expenditure categories

The form requires the company to explain its R&D projects clearly enough for HMRC to understand the technical work and the expenditure claimed.

The Critical AIF Rule

Submit the AIF before or on the same day as the CT600.

If you submit both on the same day, submit the AIF first and the CT600 second. HMRC specifically states that submitting the CT600 before the AIF can result in the R&D claim being rejected.

For finance teams, this creates a simple control:

AIF submitted → confirmation retained → CT600 submitted

Do not reverse that sequence.

What Is the Claim Notification Form (CNF)?

The Claim Notification Form applies to certain companies that plan to claim R&D tax relief.

A company generally needs to submit a claim notification if it is making its first R&D claim or if its previous claim falls outside HMRC’s three-year look-back rule.

The notification period runs from the first day of the relevant period of account until six months after the end of that period of account.

Example

Suppose a company’s period of account ends on:

31 December 2026

If the company falls within the CNF rules, it must submit the notification by:

30 June 2027

Missing the notification deadline can make the subsequent R&D claim invalid.

Important: It Is Not Simply a “Six Months After the Year-End” Rule

CFOs should pay attention to HMRC’s terminology.

The deadline relates to the period of account, rather than simply assuming that every company can calculate the deadline from the accounting period shown on its CT600.

This distinction becomes particularly relevant where the period of account exceeds 12 months and contains multiple accounting periods.

AIF vs CNF: Know the Difference

The two forms perform different functions. A company should not treat the AIF as a replacement for the CNF.

Why AIF Quality Matters for SaaS & Tech Businesses

Technology companies often operate several R&D projects simultaneously.

A single SaaS business could work on:

• New software architecture
• Machine-learning systems
• API infrastructure
• Cybersecurity technology
• Data-processing systems
• Automation platforms
• Cloud optimisation
• Proprietary algorithms

The AIF requires the company to identify and describe its R&D projects and expenditure.

That makes project-level evidence valuable.

A CFO should be able to connect:

Technical project → technological uncertainty → R&D activity → qualifying costs → AIF description

This structure gives the finance team a clearer basis for the final claim.

Don’t Leave the AIF Until the CT600 Deadline

Year-end reconstruction creates avoidable compliance pressure.

Instead, build the evidence during the R&D cycle.

Maintain:

• Project descriptions
• Technical reports
• Development tickets
• Engineering records
• Staff allocation records
• Cloud and software invoices
• Subcontractor invoices
• R&D cost calculations
• Project start and end dates
• Evidence of technical uncertainty

When the AIF becomes due, the finance team can use these records to prepare a concise and evidence-based submission.

This approach also helps prevent a common problem: finance understands the expenditure, but cannot explain the underlying technical R&D clearly.

The CEO & CFO R&D Compliance Calendar:

A practical internal timetable can look like this:

During the R&D project

Engineering: Record technical uncertainty and development work.

Finance: Track potentially qualifying expenditure.

Management: Record project ownership and key decisions.

Before year-end

Finance: Reconcile R&D expenditure to the general ledger.

Technical team: Confirm qualifying projects and technical descriptions.

Management: Review the overall claim.

Before the CNF deadline

Finance: Check whether the company needs to submit a Claim Notification Form.

Management: Submit the CNF within the applicable notification period.

Before the CT600

Finance: Prepare and submit the AIF.

Finance: Submit the CT600 after the AIF has been successfully submitted.

This creates a controlled workflow rather than treating R&D relief as a last-minute tax adjustment.

Easy R&D vs Tax Software for R&D Claim Compliance

For UK SaaS and technology companies, specialist R&D platforms can help organise the technical and financial information required for a claim.

Easy R&D’s states that its platform helps UK limited companies access R&D tax relief and provides a complete pathway for eligible businesses.

Want to check your R&D claim?

Explore Easy R&D for your UK technology business

UK R&D Compliance Checklist

Before submitting an R&D claim, ask:

• Does the company need to submit a CNF?
• Has the CNF deadline been calculated from the correct period of account?
• Has the AIF been prepared for the relevant accounting period?
• Does the AIF accurately describe the R&D projects?
• Can the company reconcile claimed costs to its accounting records?
• Does the technical evidence support the claimed projects?
• Has the AIF been submitted before the CT600?
• Has the submission confirmation been retained?
• Does the CT600 correctly reflect the R&D claim?

These controls can help finance teams avoid an administrative error undermining an otherwise valid R&D claim.

The Key Line for UK IT, SaaS & Technology Businesses

The R&D tax relief process does not end when the finance team calculates qualifying expenditure.

AIF compliance and claim notification deadlines form part of the claim itself.

The essential sequence is:

Check CNF requirement → meet the notification deadline → prepare AIF → submit AIF → submit CT600 → retain evidence

For UK technology companies, the six-month claim notification window can become especially important when the company makes its first R&D claim or returns to R&D claiming after a long gap.

For CEOs and CFOs, the strongest approach combines technical evidence, financial controls and deadline management.

If your business develops software, builds technology or undertakes qualifying R&D, reviewing the claim process early can help your finance team avoid preventable compliance errors.

Explore Easy R&D for your UK R&D claim

This website provides general information and does not constitute tax, accounting or legal advice. HMRC R&D rules and filing requirements can change. Companies should check the current HMRC guidance and their specific circumstances before submitting an R&D claim.