Skip to content
Founder TaxPartners

The R&D Additional Information Form: a Step-by-Step Guide

11 November 2026 · 11 min read

Get in touch

The Additional Information Form (AIF) is the gate between your company's qualifying R&D work and the relief you can claim on your Corporation Tax return. You submit it online, signing in with the company's Government Gateway account (or your agent's agent services account), and it's due before or on the same day as your CT600, with the form going first. It asks for your company references and R&D contacts, the accounting period, your qualifying costs and, project by project, the advance you were after, the uncertainties and how you tackled them. Without it, HMRC won't accept the claim. The project narratives carry the claim, so give them the time.

What the AIF is, and why it is not optional

The Additional Information Form is a detailed submission that must reach HMRC before, or on the same day as, the CT600 that carries the R&D claim. HMRC's guidance is blunt: without it, the claim "will not be accepted". So the form's the gate to any relief, not a supplementary document you attach afterwards.

It came in under regulations that the government says deliver its commitment to tackle error and fraud in R&D relief, by getting better information upfront in a form HMRC can risk-assess. The effect is that you have to set out the qualifying nature of your R&D work in structured form before the financial claim is processed. A missing form gets the claim rejected. A weak one gets questions.

You fill the AIF in online. A company representative signs in with the Government Gateway user ID the company used to register for Corporation Tax; an agent signs in through its agent services account, with the company's permission. In a group, each company needs its own Gateway account (a Group Tax Manager account won't work). You can't get back into the form once it's sent, so save a copy first and keep the reference number from HMRC's confirmation email. The form is separate from the CT600 itself.

Want this checked against your specific situation?

Leave your details and a one-line summary. One of our specialists will come back to you, with no obligation.

We'll only use your details to respond to your enquiry. We don't pass them to any other firm. See our Privacy Policy.

Where the AIF sits in the R&D claims process

If you're claiming for the first time, or your last claim was made more than 3 years before the last day of your claim notification period, there's a step before the AIF: a claim notification. Its window opens on the first day of the period of account and closes 6 months after that period ends. Miss it and the claim is invalid regardless of the AIF, so if this is your first claim, check that date before anything else. Our guide to the 6-month notification deadline takes you through the dates.

That step's due to go. From 1 April 2027 no claim notification form is due to be needed for claims made on or after that date (announced at Budget 2026, still to pass in the Finance Bill). The AIF stays.

Once notification is in place (or confirmed as not required for a repeat claimant), the sequence is:

  1. Submit the AIF through the HMRC portal.
  2. File the CT600 with the R&D claim box completed.

The AIF must come first. It can go on the same day as the return, but if the return gets to HMRC before the form, the claim is rejected.

Step What it is Deadline
1. Claim notification Tells HMRC you intend to claim (first-time claimants, and those whose last claim was made more than 3 years before the window closes) From the first day of the period of account to 6 months after it ends
2. AIF Detailed project and cost information submitted to HMRC Before or on the same day as the CT600 claim, form first
3. CT600 R&D claim The financial claim on your Corporation Tax return The return's due 12 months after the period ends; the claim can go in, or be added by amendment, until 24 months after a period of account of 18 months or less ends

For more on how the claim sits inside the wider R&D framework, see the merged R&D scheme explained and the ERIS route for R&D-intensive loss-making SMEs.

What HMRC asks for, section by section

The AIF has several distinct sections, and each one's there for a reason. Treat them as a single free-text box and the form won't support the claim the way it should. HMRC is due to simplify the information the form asks for from autumn 2027 (announced at Budget 2026); until then, these are the sections you'll fill in.

Contact and agent details

Your company's Unique Taxpayer Reference (it must match the one on your CT600), employer PAYE reference, VAT registration number and SIC code, plus contact details for the senior person in the company who's responsible for the claim, a director for example. Every agent involved goes in too, not just the one filing: anyone who gave advice, analysed costs, helped with the technical write-up or completed the forms. It's admin, but don't rush it.

You'll also give the start and end dates of the accounting period you're claiming for, matching the CT600. It's one AIF per accounting period, so a 16-month period of account, which makes two tax returns (12 months, then 4), needs two forms if you claim in both. That's different from the claim notification, where one form covers the whole period of account.

Project descriptions

For each R&D project you describe, you give a structured narrative. HMRC wants to understand: the field of science or technology it sits in, what advance the project was seeking, what the baseline state of knowledge was at the start, what specific scientific or technological uncertainties arose, and how you attempted to resolve them. How many projects you describe depends on how many you're claiming for. With 1 to 3, you describe every one. With 4 or more, you pick 3 or more that together account for at least half of the qualifying expenditure, and if you'd need more than 10 to reach half, you describe the 10 with the highest spend. Each one gets its own narrative.

The advance in science or technology

This is the qualifying test in HMRC's R&D manual. Your project must seek an advance in overall knowledge or capability in a field of science or technology, not just an advance for your company. The distinction matters. Implementing a known technique in a new context is not an advance. Developing a technique that did not previously exist, or combining existing knowledge in a way that was not previously known to work, can be.

The technological uncertainty

You must identify the specific uncertainty that a competent professional in the field could not readily resolve using existing knowledge. This framing is precise and deliberate. The test is not whether it was hard for your team; it is whether someone who knew the field well would have found the answer readily available. If the answer was in a textbook, a framework's documentation, or a Stack Overflow thread, it is not a qualifying uncertainty.

Qualifying cost breakdown

The AIF requires a breakdown of your qualifying costs by category: staff costs (salary, employer NIC, pension contributions for employees directly engaged in R&D), subcontractor costs, consumables, and cloud computing costs. You don't need to submit payroll schedules at AIF stage, but the figures must be supportable. Confirm detailed apportionment rules for your specific cost mix with us before filing, as the rules differ between cost types and between connected and unconnected contractors.

AIF section-by-section checklist

AIF section What HMRC wants Common pitfall
Contact and agent details Company UTR, PAYE reference, VAT number and SIC code; the senior R&D contact and every agent involved A UTR that doesn't match the CT600, or listing only the agent who files
Accounting period Start and end dates matching the CT600; one form per accounting period Sending one form for a period of account longer than 12 months, which needs one per accounting period
Project name and description A plain label and a brief summary of what the project was trying to achieve technically Describing the product or feature rather than the underlying technical work
Advance in science or technology The specific advance in overall knowledge or capability being sought Framing the advance as "new to us" rather than as an advance in the field
Baseline state of knowledge What was already known at the start; why the advance was not already available Skipping this section, which makes the uncertainty claim unsupportable
Technological uncertainty The specific uncertainty a competent professional could not readily resolve Describing integration complexity or project risk rather than scientific/technical uncertainty
Resolution attempt What you tried, including what did not work Describing only the successful outcome; HMRC expects to see the investigative process
Qualifying cost breakdown Staff, subcontractors, consumables and cloud costs apportioned to R&D Including non-qualifying costs (e.g., marketing, product management time) in staff apportionment

How to describe a software project so it reads as genuine R&D

Software companies often hit the same structural problem on the AIF. The work that qualified as R&D (the technical investigation, the failed attempts, the uncertainty) happened months before anyone thought about the tax claim. By the time the AIF is being drafted, what people remember is the shipped feature, not the process of figuring out how to build it.

HMRC's test, set out in CIRD100000, requires an advance in science or technology and a technological uncertainty that a competent professional could not readily resolve. Routine software development does not qualify. That phrase is doing a lot of work.

What routinely does not qualify for a software project:

  • Integrating third-party APIs using published documentation
  • Building UI components or product features using established frameworks
  • Choosing between off-the-shelf solutions or configuring known software
  • Performance tuning within known parameters
  • Bug fixing on known software behaviour

What can qualify:

  • Developing a novel algorithm where the computational approach was not previously known to work at the required scale or accuracy
  • Solving a problem in distributed systems where no existing technique could reliably handle the failure modes you faced
  • Developing a new machine-learning approach where the architecture or training method was genuinely experimental and the outcome uncertain to a competent professional
  • Combining existing techniques in a way that was not documented to work in your specific technical context

The honest framing in the AIF is not "we built X". It is "we sought to advance the state of knowledge in area Y, the baseline was Z, the specific uncertainty was A, and here is what we tried and what we found." See also the guide on software R&D eligibility in detail.

Worked example: an AIF project narrative for a software company

This example is illustrative. It shows the structure and framing HMRC expects, not a template to be copied verbatim. Your narrative must reflect your actual project.

Project name: Real-time anomaly detection engine for distributed event streams

Advance sought: The project sought to advance the state of knowledge in statistical anomaly detection applied to high-velocity, schema-variable event streams. Existing published techniques for real-time anomaly detection assumed fixed schema and moderate data velocity. Our stream involved events whose schema changed dynamically and arrived at sustained rates that exceeded the throughput bounds documented for existing open-source implementations.

Baseline state of knowledge: At the outset, available anomaly detection libraries (including well-documented open-source implementations) operated on fixed schemas and had published throughput ceilings that were below our target operating parameters by an order of magnitude. No published technique addressed the combination of schema variability and the required throughput simultaneously.

Technological uncertainty: It was uncertain whether a sliding-window statistical model could be adapted to handle dynamic schema changes without model retraining, and whether the adapted model could sustain the required throughput without unacceptable false-positive rates. A competent professional in statistical data processing could not have determined in advance whether this combination was achievable within the latency and accuracy constraints we needed, because it had not been demonstrated in the literature or in production systems we could reference.

Resolution attempts: We first trialled a fixed-schema model with a schema-mapping layer. This produced unacceptable false-positive rates when schema changes were rapid. We then developed a lightweight schema-fingerprinting mechanism that allowed the model to treat schema changes as a signal variable rather than an error condition. This required a novel adaptation of the base model's feature vector, which was not documented in prior work. We iterated through four model variants, two of which failed to meet throughput targets, before the fourth variant met both the throughput and accuracy requirements. The work involved genuine scientific and technical uncertainty throughout and was not derivable from existing documentation.

Cost apportionment in the AIF

The AIF requires you to attribute qualifying costs to R&D activity by category. At a high level, the categories are:

  • Staff costs: Salary, employer NIC and pension contributions for employees directly and actively engaged in R&D. Where a staff member splits their time between R&D and other work, only the R&D proportion counts.
  • Subcontractor costs: Payments to external parties carrying out R&D work on your behalf. You can claim them only if your company decided to do and planned the R&D, and the amount depends on whether the contractor's connected to you (an unconnected one counts at 65% of the payment). Work done abroad is generally excluded. Confirm your specific position with us before including subcontractor costs.
  • Consumables and cloud computing: Materials consumed in R&D, and cloud computing costs attributable to R&D activity. Data licence and cloud computing costs count for accounting periods beginning on or after 1 April 2023; confirm the apportionment approach for your infrastructure.

The AIF does not require payroll schedules or invoice lists at submission stage. But the figures you enter must be supportable if HMRC opens an enquiry. Maintain the underlying records (timesheets, payroll reports, cloud billing exports, subcontractor agreements) before filing, not after.

Detailed apportionment percentages and caps (particularly for subcontractors and split-role staff) are fact-specific. Confirm the right approach for your cost mix with our R&D claims service before finalising the AIF figures.

Common AIF mistakes that get claims rejected or queried

These are the patterns that do the damage, either by triggering an HMRC enquiry or by getting the claim rejected outright.

  • Filing the CT600 before the AIF. The claim's rejected. The same day is fine, but the AIF has to go first.
  • Describing product features instead of technical uncertainty. "We built a recommendation engine" is a product description. "We sought to advance the accuracy of collaborative filtering under sparse data conditions, where existing techniques produced unacceptable cold-start error rates" is a technical description of an advance and an uncertainty.
  • Treating project risk as technological uncertainty. Budget overruns, schedule slippage and market risk are not technological uncertainty in HMRC's sense. The uncertainty must be scientific or technological.
  • Including routine development costs in the staff apportionment. Product management, UX design, content work and testing of known functionality are not qualifying activities. Attributing a full engineering headcount to R&D when only a fraction of their time was on qualifying work will not survive an enquiry.
  • One narrative for multiple distinct projects. If you worked on two or three genuinely separate R&D workstreams, each needs its own narrative. Bundling them into a single vague description makes it harder to defend any of them.
  • Describing the wrong projects. With 4 or more projects, the ones you describe have to account for at least half of the qualifying expenditure between them. Picking the three that are easiest to write up won't meet that rule.
  • Omitting failed attempts. HMRC expects to see the investigative process, including what did not work. A narrative that describes only success reads as a product description, not a scientific investigation.

If you are preparing your first AIF or if a previous claim has been queried, the right point to get input is before the AIF is submitted, not after. The R&D claims service covers AIF preparation as part of the claim process. To pin down which of your workstreams generate qualifying costs in the first place, read software R&D eligibility: what qualifies.

Frequently asked questions

Yes, for every R&D claim. It has to reach HMRC before or on the same day as the CT600, and HMRC's guidance says that without it the claim will not be accepted. Source: gov.uk/guidance/submit-detailed-information-before-you-claim-research-and-development-rd-tax-relief

The claim is rejected, and HMRC writes to tell you. It isn't a delay or a correction request. To put it right, send the AIF and then make the claim again by amending the return. For a period of account of 18 months or less, that has to happen within 24 months of the period's last day, so leave it late and you may not be able to make a valid claim for that period at all.

Your company's UTR, PAYE reference, VAT number and SIC code; the senior R&D contact and every agent involved; the accounting period dates, matching the CT600; your qualifying costs; and, for each project you describe, the field of science or technology, the baseline, the advance sought, the uncertainties and how you tried to resolve them. ERIS claims also give the R&D intensity figures.

No. They're two separate submissions. The claim notification tells HMRC you plan to claim. It's needed if you're claiming for the first time, or your last claim was made more than 3 years before the last day of your claim notification period, and it goes in between the first day of the period of account and 6 months after that period ends. The AIF holds the detail and goes in before or on the same day as the CT600. From 1 April 2027 no claim notification form is due to be needed for claims made on or after that date (announced at Budget 2026, still to pass in the Finance Bill). The AIF stays.

Before or on the same day as the CT600 with the R&D claim. If both go the same day, send the AIF first: HMRC's guidance says that if the return arrives before the form, the claim will be rejected.

Frame it around the scientific or technological advance you were seeking, state the baseline knowledge at the start, explain the specific technological uncertainty that a competent professional could not readily resolve, and describe what you tried. Leave out product features, market fit, and anything that amounts to routine integration or configuration.

Need specialist startup tax advice?

Speak to an accountant who works with funded and scaling UK startups. R&D relief, SEIS/EIS, EMI, founder salary and dividend planning.

Step 1 of 2 · About you

Optional: a bit more detail (helps us prepare)

Related reading