RDEC Documentation: What HMRC Requires

The Research and Development Expenditure Credit (RDEC) scheme helps large companies offset innovation costs by offering tax relief. To ensure compliance with HMRC rules, proper documentation is mandatory. Here’s what you need to know:

• Key Requirements:
  • Maintain detailed project records to show advancements in science or technology and address uncertainties.
  • Keep financial records, including payroll, timesheets, subcontractor invoices, and cost apportionment methods.
  • Submit the mandatory Additional Information Form (AIF) before or alongside the Corporation Tax return (CT600).
• Important Deadlines:
  • Notify HMRC of your intent to claim within six months of the accounting period’s end.
  • Claims without timely notification or AIF submission will be rejected.
• Changes to the Scheme:
  • From 1 April 2024, the RDEC scheme will merge with a new R&D scheme, but robust record-keeping remains essential.

Accurate documentation and adherence to deadlines are critical to securing tax relief and avoiding compliance issues.

sbb-itb-8ea0335

What HMRC Requires for RDEC Claims

HMRC requires companies to keep detailed records that clearly identify qualifying projects and their associated costs. This ensures claims are accurate and can withstand compliance checks. The necessary documentation falls into three main categories: project records, financial documentation, and the Additional Information Form (AIF).

Project Records

You need to show that your projects aimed to advance science or technology and tackled scientific or technological uncertainties through systematic investigation. HMRC may ask for evidence such as project charts, design documents, test results, prototype photos, meeting minutes, email communications, and project plans.

A "competent professional" should provide a written opinion for each claim. This statement should detail their qualifications, experience, and reasoning for why the work addressed specific uncertainties and aimed for an advance in science or technology. It's crucial to document these at the project's start, as retrospective justifications may not be accepted. If the professional leaves the company, ensure their opinion and reasoning are fully recorded to address any future HMRC queries.

The level of detail in your documentation should match the project's scale. For smaller projects, a single page of bullet points might be enough, but larger projects require more comprehensive records. Gather evidence like test results, photos, and meeting notes as the project progresses - this avoids relying on memory later.

Financial Documentation

Accurate financial records are just as important as technical ones. HMRC expects costs to be broken down into categories like staffing costs, externally provided workers (EPWs), contracted-out R&D, and consumable items. These costs must be organised by individual project, with the total qualifying expenditure for each project clearly stated.

If costs aren’t automatically tracked, you’ll need a clear apportionment method. Keep a written record of your claim methodology, including any sampling methods used. For larger businesses, it’s recommended to agree on sampling methods with your HMRC Customer Compliance Manager (CCM) before submitting the claim. This financial transparency works hand-in-hand with technical records to meet HMRC’s standards.

Additional Information Form (AIF)

As of 8 August 2023, the AIF is a mandatory online submission for all R&D claims, including RDEC. It must be filed before or on the same day as your Company Tax Return (CT600). If both are submitted on the same day, the AIF must be sent first, or your claim will be rejected. Filing the CT600 without the AIF will result in the claim being invalid.

The AIF requires detailed company identifiers (UTR, VAT number, PAYE reference, SIC code), contact details for a senior R&D representative, information about any agents or advisors involved, and a financial breakdown of costs. Categories include staffing, EPWs, software licences, cloud computing, data licences, and qualifying indirect activities. Ensure the total R&D expenditure figures in the AIF match exactly with those in the CT600 and supporting schedules. All figures should be rounded consistently (no pence) to avoid triggering automated checks.

For technical project descriptions, the AIF requires details based on the number of projects in your claim:

For each selected project, you’ll need to answer five key questions: the scientific field, the baseline knowledge (existing technology before the project), the intended advancement, the uncertainties faced (and why they couldn’t be resolved through routine methods), and the methods used to overcome them (e.g., testing, software creation, or analysis).

Once submitted, you won’t be able to access the form again, so save a copy of all details. After submitting the AIF, make sure Box 657 on the CT600 is ticked to confirm the form has been provided. Keep the email confirmation reference number for future discussions with HMRC if needed.

Advance Notification Process

Keeping accurate records is just part of the equation when making an RDEC claim - notifying HMRC on time is equally important.

From 1 April 2023, companies must digitally pre-notify HMRC of their intention to claim RDEC before submitting the actual claim. This notification must be sent within six months of the end of the accounting period. The rule applies to first-time claimants, companies that haven’t made a valid R&D claim in the past three years, or businesses whose only recent claim relates to a period starting before 1 April 2023 but was amended and submitted after this date.

Here’s how the notification window works: it spans 2½ years before and 6 months after the close of your current accounting period. For example, if your accounting period ends on 31 March 2026, you’ll need to notify HMRC by 30 September 2026. In this case, the three-year window would cover claims for periods between 1 October 2023 and 30 September 2026. Importantly, HMRC treats companies within a group as separate entities, meaning each company must adhere to the notification requirements individually - a claim by one group company doesn’t cover the others.

"Missing this deadline will mean you are not eligible to claim R&D relief for that accounting period. There is no legislative recourse or statutory right of appeal, so it is essential to act in time." - Emma Hussey, Associate Director, Azets

If your company is under an HMRC enquiry that could jeopardise a previous claim, it’s wise to submit a "protective" notification for the current period. As Azets explains: "If someone is in an enquiry, we recommend a 'protective' PCN. If, down the line, a claim is removed and no PCN was submitted, the company may have passed their 6-month window to file one." This ensures you retain the right to claim if the earlier claim is ultimately invalidated.

For accounting periods ending between 8 March 2024 and 31 May 2024, HMRC has introduced a limited option for companies that missed the deadline. You can contact HMRC’s R&D Policy team with the subject line "CIRD183000 notification" to check if a late claim is possible. Meeting these notification deadlines is a critical part of staying compliant with HMRC’s requirements and aligns with broader documentation and compliance efforts.

Preparing for HMRC Enquiries and Compliance Checks

HMRC's checks for the Research and Development Expenditure Credit (RDEC) scheme are generally less demanding than those for the SME scheme, with error rates recorded at 3.6% compared to 24.4%. The Large Business Directorate oversees around 2,000 of the largest businesses in the UK, most of which have a dedicated Customer Compliance Manager (CCM) to help manage R&D compliance risks. With HMRC doubling its compliance staff and establishing an Anti-Abuse Unit to handle complex cases, maintaining thorough and accurate documentation has never been more critical. To strengthen your compliance process, consider the following best practices.

Documentation Best Practices

As noted earlier, keeping contemporaneous records is vital. Here, we'll expand on the steps you can take to ensure your documentation meets HMRC's standards. Claims are viewed as more reliable when qualifying work is identified as it happens, rather than being assessed retrospectively. A written opinion from a "competent professional" - often an internal technical lead - should outline the scientific or technological advancement, the uncertainties faced, and why the solution was not straightforward. While this doesn't need to be a lengthy report, it must provide more than a simple assertion of eligibility.

For financial records, it's crucial to clearly document your claim methodology, particularly if you rely on sampling or apportionment to estimate costs. Large businesses are advised to agree on sampling methods with their CCM before submitting claims to avoid potential disputes later. Detailed project records captured in real time can significantly strengthen your claim. Examples include photos of prototypes at different stages, logs of failed experiments, and correspondence during the project.

"HMRC consider that claims to Research and Development (R&D) relief are more likely to be correct if the company is aware at the time that the work it is doing may qualify for tax relief." - GOV.UK

For smaller projects within an RDEC claim, a concise summary or existing business records, supported by staff recollections, might be sufficient. However, larger projects demand more comprehensive documentation.

Responding to HMRC Enquiries

Having robust documentation is your first line of defence during an HMRC enquiry. Be ready to justify your claim if questioned. HMRC may request site visits, inspect prototypes or final products, and interview employees involved in the R&D work. It's essential to explain the scientific field, baseline knowledge, and the boundaries of your R&D efforts with clarity and precision.

Support all cost estimates with clear evidence and a well-documented rationale. HMRC’s random enquiry programme revealed that 75% of claims exceeding £1 million in expenditure were fully compliant, indicating that well-prepared large businesses generally perform well under scrutiny. However, with over 90% of R&D claimants represented by tax agents, it’s important to remember that your company is ultimately responsible for the accuracy of the claim, even when working with advisers.

HMRC is bound by a duty of confidentiality, so you can provide sensitive technical and financial details during compliance checks without worrying about broader disclosure.

Conclusion

Strong RDEC documentation forms the backbone of a compliant and successful claim. Keeping accurate records ensures you can secure essential tax relief. It’s crucial to document technical uncertainties and advancements as they happen, while also detailing your claim methodology and cost allocations in your financial records. Since 8 August 2023, the Additional Information Form has been mandatory - claims submitted without it will be rejected.

Senior officers must confirm the accuracy of claims, as outlined in the Additional Information Form. Missing project-specific cost details can lead to heightened scrutiny, delays, or prolonged enquiries. Given that RDEC claims can account for 13–20% of qualifying expenditure, there’s a lot at stake.

Seeking expert help can simplify this process. Zest R&D Tax Advisors offers comprehensive support for RDEC claims, from initial preparation to ensuring compliance with HMRC requirements. Their team works alongside your existing accountants to help you meet all necessary criteria while maximising your relief.

Investing time in thorough documentation now can save you significant stress during HMRC reviews.

FAQs

What counts as a qualifying RDEC project?

To qualify as an RDEC (Research and Development Expenditure Credit) project, the work must aim to tackle scientific or technological uncertainties. In other words, it should involve solving problems where the solution isn’t immediately obvious or straightforward.

Expenses that can be claimed include:

• Wages for employees directly involved in the R&D work
• Materials used in the research process
• Utilities, such as electricity and water, necessary for the project
• Software essential for the development
• Subcontractor payments for outsourced R&D activities

It’s important to note that projects must focus on genuine innovation. Routine tasks or problems with clear, established solutions don't meet the criteria.

What evidence should a “competent professional” provide?

Detailed documentation is a must for any professional handling R&D activities. This should include clear project descriptions, identified technical uncertainties, the systematic methods applied, and the results achieved. To back this up, supporting records like reports, timesheets, invoices, and financial data are crucial. These help confirm the activities meet HMRC’s requirements for qualifying as legitimate R&D.

How do we avoid our AIF and CT600 being rejected?

To avoid having your AIF and CT600 rejected, ensure they are submitted on time and include precise, detailed records of qualifying R&D activities and costs. Double-check that the AIF is correctly linked to the CT600, as HMRC requires all documentation to be complete and compliant for your claim to be processed.

Related Blog Posts

• R&D Tax Claim Checklist: 10 Essential Steps
• How to Submit R&D Claims to HMRC Correctly
• RDEC Submission Checklist for HMRC
• How to Complete HMRC's R&D Additional Information Form