5 Records to Keep for R&D Tax Relief Compliance

Filing an R&D tax relief claim isn’t just about identifying qualifying activities. You need solid, detailed records to back up your claim and meet HMRC's strict requirements. Without proper documentation, your claim could face rejection or scrutiny. Following an R&D tax claim checklist can help ensure you meet all requirements. HMRC can investigate claims up to six years after the relevant accounting period, so keeping accurate records is critical.

Here’s what you need to maintain:

• Project and Technical Documentation: Explain the technical challenges, uncertainties, and methods used. Include design notes, test results, Git logs, or Jira tickets.
• Staff Time Records: Track employees' time spent on R&D activities and justify their roles with CVs, contracts, and relevant expertise.
• Cost Breakdowns: Keep invoices, contracts, and bank records for subcontractors, EPWs, software, and consumables. Show how costs link directly to R&D.
• Contracts and Correspondence: Ensure contracts specify R&D activities and keep supporting communications like emails and meeting notes.
• Specialist Support: Consider working with an R&D tax relief expert to ensure your records meet HMRC standards and streamline the process.

Strong, contemporaneous records not only support your claim but also reduce the risk of compliance issues. Start documenting as you go to avoid gaps later.

Understanding R&D Tax Credits

sbb-itb-8ea0335

1. Project and Technical Documentation

Clear and detailed project and technical documentation is the backbone of a solid R&D tax relief claim. It's not enough to simply show HMRC what you created; you need to explain why the project was technically challenging and how you tackled those challenges.

Your documentation should establish three key points: the baseline knowledge at the start of the project, the technical uncertainty you faced, and the systematic approach you used to resolve it. HMRC defines a qualifying uncertainty as one where "an expert on the subject cannot say if something is technologically possible, or how it can be done, even after referring to all the available evidence". This means you need to clearly outline the specific technical hurdles and why they couldn’t be solved using existing knowledge or standard methods.

Avoid vague statements like "we weren't sure if it would work." Instead, detail the exact scientific or technological sub-field involved, the specific problem encountered, and why it wasn’t straightforward. Don’t shy away from documenting failures - test results that fell short, discarded methods, or dead-end iterations. These demonstrate that the solution wasn’t "readily deducible" by a competent professional, which is a crucial criterion for qualifying R&D activities.

To meet HMRC’s requirements, use natural business records. These might include design notes, lab notebooks, and version control logs. For software projects, tools like Git logs, architecture notes, or Jira tickets are particularly useful. Tagging R&D-related tasks in project management tools (e.g., labelling Jira issues as "R&D – ML Engine") can create an effortless and contemporaneous audit trail.

"It is in the nature of R&D that it should be conducted systematically, and this should leave its trace in the records available." – HMRC Internal Manual

The table below outlines the types of documentation you should maintain and what to include:

Aligning your documentation with the Advance Information Form (AIF) simplifies the claims process. By keeping thorough and systematic records, you not only meet HMRC’s standards but also make the entire process of claiming R&D tax relief far smoother.

2. Staff Time Records and Role Evidence

Staff costs often make up the bulk of an R&D tax relief claim, making them a key focus for HMRC. To support your claim, you’ll need to provide a "just and reasonable" basis for the percentage of each employee's time spent on qualifying activities.

"HMRC knows engineers don't spend 100% of their time on qualifying activity. You don't need minute-by-minute timesheets, but you do need a reasonable basis for your apportionments." - Daniel Scott, Partner & Head of Accounting, OnTheGo Accountants

One effective approach is to use R&D-specific tags in tools like Jira, Linear, or Monday.com to generate reliable, real-time records. If such tools aren’t part of your workflow, consider conducting quarterly time reviews, signed off by technical leads. The key is to maintain records as events occur, as these hold far more weight than reconstructions created months later. This is especially important given HMRC’s extended review window.

In addition to time records, role evidence is essential. This involves outlining why each team member was involved, detailing their qualifications, relevant expertise, and the critical decisions they made during the project. HMRC needs to see that the work required a skilled professional capable of addressing complex technical challenges - not just someone following an established process. Supporting documents like employment contracts, CVs, and internal memos explaining individual contributions should be kept alongside time records.

Staff turnover can complicate matters. HMRC can initiate a compliance check up to six years after the end of an accounting period. If key team members have left the company, written records may be your only remaining evidence. The table below highlights the types of documentation you should maintain:

3. Cost Breakdowns and Allocation Records

When preparing an R&D claim, it’s not just about staff costs and technical details. HMRC requires a clear and traceable record of all other expenditures. This means you’ll need to keep source documents like invoices, contracts, itemised bills, and bank records for every qualifying cost category. Plus, you must be able to demonstrate how each cost ties directly to your R&D activities.

The main cost categories to focus on include subcontractors and Externally Provided Workers (EPWs), software and cloud computing, and consumables like materials, water, fuel, and power. For subcontractors, you’ll need to provide contracts, statements of work, itemised invoices, and bank records confirming payments. Importantly, your documentation must show that your company directed the work and took on the technical risks, rather than simply outsourcing routine tasks. For EPWs, you’ll also need to demonstrate active supervision by your team. If payments involve a connected company, flag these separately since different rules for subcontracting limits and transfer pricing apply.

When it comes to software and cloud services, a key distinction must be made between experimental or test environments (which qualify) and live production infrastructure (which doesn’t). Itemised bills and usage logs can help clarify this. Using internal cost codes in accounting software like Xero or QuickBooks can help you separate R&D-related expenses from non-R&D costs.

For costs that span both R&D and non-R&D activities, you’ll need to apportion them carefully. This requires documented evidence to support your calculations.

"If you make estimates, you should arrive at the estimate using evidence and reason. You will need to show that you incurred the expenditure and that your estimate of the amount of qualifying expenditure is based on facts." - GOV.UK

Consistency is key. Fergus Watson, Head of Compliance at Kene Partners, explains: "The goal is not perfection. The goal is a method you can explain and repeat." To ensure long-term auditability, document your apportionment method alongside related invoices. Combining this with technical documentation and staff records will strengthen your claim.

Here’s a quick overview of the essential records needed for each cost category:

Lastly, every figure in your claim must reconcile neatly with your trial balance, payroll reports, and general ledger. HMRC expects this level of detail, and any gaps in the audit trail can trigger extended compliance checks.

4. Contracts, Agreements, and Supporting Correspondence

When it comes to R&D claims, contracts and communications with subcontractors and collaborators play a pivotal role. HMRC expects clear evidence of both the expenditure and the specifics of the work undertaken, including who is accountable for what.

Starting from 1 April 2024, contracts must explicitly state that R&D activities will be carried out. This clarity is essential to determine which party is eligible to claim relief. It’s worth noting that the likelihood of an HMRC enquiry into R&D claims is now about five times higher than it was just two years ago. Transparent contracts not only help establish accountability but also strengthen your overall R&D evidence by tying together technical, financial, and administrative records.

Your contracts shouldn’t just list deliverables - they need to specify the technical uncertainties subcontractors are expected to address. Alongside this, it’s crucial to keep supporting documents such as invoices, proof of payments, and correspondence that demonstrates your team’s active involvement in directing the work. Don’t forget to include EPW verification for UK PAYE and Class 1 National Insurance compliance. All these should be compiled into a consolidated R&D evidence pack.

"It would be prudent for a company to identify and retain information such as, contracts, confirmatory letters or emails from contractors and invoices." - HM Revenue & Customs

In addition to technical and financial records, timely correspondence can significantly bolster your claim. Emails, meeting notes, and even Slack or Teams threads that document discussions about technical challenges, decisions, or setbacks act as contemporaneous evidence - records created in real time. HMRC values these far more than any retrospective explanations. By organising contracts, invoices, bank records, and key correspondence into a single R&D evidence pack for each accounting period, you’ll be better prepared to respond promptly if a compliance check arises and submit your R&D claim with confidence.

5. Working with a Specialist to Support Record Keeping

Keeping R&D records that meet HMRC's exact standards can be a real challenge for many businesses. Technical teams often understand the innovation side but might not document it in the precise way HMRC expects. On the other hand, finance teams may struggle to identify which costs qualify. Using an R&D qualifying expenditure checker can help clarify these expenses. This is where a specialist can make all the difference, bridging the gap between technical details and financial accuracy.

A pre-submission review by a specialist can highlight weak points in your documentation and help establish processes for real-time, repeatable record-keeping. This proactive approach minimises the risk of compliance issues and avoids the stress of last-minute gaps at year-end.

Instead of rushing to gather evidence when filing deadlines loom, specialists can help embed record-keeping into your daily operations. For example, tagging Jira tickets with R&D project codes or making R&D a regular agenda item in management meetings ensures that evidence is captured as you go. These practical steps make it easier to maintain accurate records and set the stage for a specialist's effective input.

Specialists like Zest R&D Tax Advisors can strengthen your record-keeping efforts. Their team helps draft the technical narratives required for the Additional Information Form (AIF) and compiles a structured evidence pack for each accounting period. By addressing both the technical and financial sides of your claim, they reduce the risk of errors and ensure you're well-prepared in case HMRC decides to review your submission.

Conclusion

Strong record-keeping is the backbone of any successful R&D tax relief claim. It all boils down to one crucial factor: evidence. Since HMRC operates on a self-assessment basis, the responsibility to prove eligibility rests entirely with your business. Without clear evidence that your work qualifies and your costs are accurate and traceable, your claim could be in jeopardy.

It's worth noting that HMRC can initiate a compliance enquiry up to six years after the relevant accounting period. This means the records you maintain today must stand the test of time - even if key team members have moved on.

The good news? Keeping robust records doesn't have to be complicated. As GOV.UK explains:

"If we check your claim the process is likely to be quicker and simpler if you have good written records."

Contemporaneous records - those created as work happens - carry far more weight than summaries written after the fact. Detailed project logs, staff time tracking, cost breakdowns, and contracts all contribute to making your claim both credible and defensible.

If you're unsure about the quality of your documentation, Zest R&D Tax Advisors can help. They specialise in reviewing records, preparing the AIF, and creating structured evidence packs - saving you time and helping you avoid unnecessary compliance headaches.

FAQs

How long should we keep R&D claim records for HMRC?

HMRC has the authority to review an R&D tax relief claim for up to six years following the conclusion of the relevant accounting period. To remain compliant, it’s crucial to keep all supporting documents - like project descriptions, cost breakdowns, staff time logs, and contracts - for at least six years. If you want to ensure your claims are properly prepared and align with HMRC’s guidelines, Zest R&D Tax Advisors can provide the expertise you need.

What counts as good evidence of technical uncertainty?

Good evidence highlights challenges that even skilled professionals couldn’t solve with existing knowledge or standard methods. HMRC places a strong emphasis on contemporaneous records - documents created during the course of the project. These might include:

• Technical specifications
• Problem statements
• Design notes
• Lab notebooks
• Simulation outputs
• Test reports
• Version control history
• Emails detailing roadblocks

Even records of failed experiments and meeting minutes can be valuable, as they showcase the trial-and-error process involved in tackling technical obstacles.

How do we apportion shared costs fairly for an R&D claim?

To fairly split shared costs, focus on identifying the portion of expenses directly tied to qualifying R&D activities. Use a method that's justifiable and reasonable, supported by clear evidence like sprint plans or technical notes to allocate staff time accurately. Avoid using flat percentages, as HMRC favours consistent and well-documented approaches. Ensure you maintain a written record of your methodology, including any sampling or estimation techniques, to provide transparency in case of compliance checks.

Related Blog Posts

• Qualifying R&D Activities: Key HMRC Guidelines
• RDEC Documentation: What HMRC Requires
• Common RDEC Eligibility Mistakes
• 5 Green R&D Projects That Claimed Tax Relief