R&D Tax Credits UK: Eligibility, Costs and Claims Guide

R&D tax credits UK relief is Corporation Tax support for eligible companies that seek an advance in science or technology and work to resolve genuine technological uncertainty. A defensible claim connects a defined project to the technical work undertaken, qualifying costs, and evidence for the relevant accounting period. It is not a reward for using the word innovation or spending heavily on software.

Request a Consultation about your R&D project

What are R&D tax credits UK claims? R&D tax credits UK claims are Corporation Tax reliefs for eligible companies carrying out qualifying research and development. The project must seek an advance in the overall field of science or technology and address uncertainty that a competent professional could not readily resolve. The company must support its claim with an accurate technical account, eligible expenditure, and records that match the accounting period.

This guide explains the core eligibility test, examples of potentially qualifying work, the main scheme changes, cost categories, evidence expectations, common weaknesses, and the role of professional review. Rules depend on the accounting period, company profile, and facts of the project. Read the current GOV.UK R&D relief guidance alongside your own records and tax advice.

What Are R&D Tax Credits in the UK?

Answer: R&D tax credits UK relief is Corporation Tax support for a company that seeks an advance in science or technology. The company must work to resolve scientific or technological uncertainty that a competent professional could not readily resolve. The claim must connect qualifying activity and expenditure to the relevant accounting period and supporting records.

The test is based on the substance of the project. A business may be developing something commercially valuable, but that does not automatically make the work R&D. The project needs a technical objective that advances the wider field, not merely an improvement that is new to the company. It also needs a genuine uncertainty about whether the objective can be achieved or how it can be achieved.

For example, configuring an established platform, connecting familiar systems, or delivering a standard implementation may require skill without creating qualifying technological uncertainty. By contrast, a team that tests alternative technical approaches to overcome an unresolved processing, security, materials, or performance barrier may have a project that warrants closer review.

The four questions to ask at the outset

• What was the baseline? Identify the existing knowledge, capability, or method available to a competent professional at the start.
• What advance was sought? Describe the intended improvement to the overall field of science or technology, rather than only the company's commercial objective.
• What was uncertain? Explain why the answer was not readily deducible and what technical barrier prevented a straightforward solution.
• What work addressed the uncertainty? Trace the experiments, modelling, design iterations, tests, failures, and decisions used to investigate the problem.

A project can include both qualifying and non-qualifying work. R&D may end when the uncertainty is resolved, while subsequent routine production, maintenance, commercialisation, and customer delivery fall outside the technical project. Defining those boundaries early makes the claim more credible and prevents unrelated expenditure from being swept into the calculation.

Which Activities Qualify Under HMRC Rules?

Answer: Activities may qualify when they seek an advance in the wider field of science or technology and address a scientific or technological uncertainty that a competent professional could not readily resolve. The work must go beyond routine implementation, maintenance, or commercial development, and the technical account should show the project boundary, investigation, and outcome.

HMRC focuses on whether a project sought an advance in science or technology and addressed scientific or technological uncertainty. The description should therefore start with the technical problem, not a product name or a marketing phrase. A new service, feature, or process may be relevant, but novelty to one company is not the same as an advance in the wider field.

Examples that may warrant review

• Software and data: developing a new method to overcome a documented scalability, security, latency, or data-processing constraint may qualify where the solution was not readily available. Routine configuration, ordinary feature development, and standard integration need separate treatment.
• Fintech: testing an unfamiliar approach to transaction processing, fraud detection, or system resilience may involve technological uncertainty. The decision to launch a financial product does not create R&D by itself.
• Healthcare: work to resolve a technical barrier in a diagnostic, data, or treatment-support system may warrant assessment when the scientific or technological uncertainty is clearly recorded. A clinical or commercial objective alone is insufficient.
• Engineering and manufacturing: iterative design, modelling, and testing may qualify where the team is resolving an engineering uncertainty. Manufacturing an established design is ordinarily a production activity rather than the experimental project.
• Energy and sustainability: work to test a new technical method for performance, storage. Materials or system integration may be relevant where the project advances the field and the barrier could not readily be resolved from existing knowledge.

Evidence of uncertainty is more useful than labels

Technical evidence might include competing approaches, prototypes, failed tests, performance constraints, design decisions, test results, issue records, or contemporaneous project notes. The record should show what the team did not know, why the uncertainty mattered, and how the work reduced it. Commercial risk, customer demand, funding pressure, or a launch deadline is not the same as technological uncertainty.

HMRC's official eligibility guidance provides the governing framework. Companies should also review their wider corporate tax position, because the project assessment, cost calculation, tax return, and accounting period need to be consistent.

Which R&D Tax Credits UK Scheme Applies to Your Company?

Answer: Scheme selection depends first on the accounting period start date, then on company size, ownership, connected companies, losses, R&D intensity, and the nature of the expenditure. For periods beginning on or after 1 April 2024, the merged scheme is generally the starting point, while intensive support has additional conditions.

Scheme selection begins with the accounting-period start date. The rules changed for accounting periods beginning on or after 1 April 2024. A company should not carry forward an old claim method without checking the current legislation, its ownership position, its size, and the nature of its expenditure.

R&D relief route by accounting period and company profile

Potential route

When it may be relevant

What to check

Merged scheme

Generally relevant to accounting periods beginning on or after 1 April 2024.

Confirm the qualifying project, expenditure, company status, connected-company position, and any subcontracting restrictions.

Enhanced R&D Intensive Support

May be relevant to qualifying loss-making small or medium-sized enterprises that meet the applicable intensity and other conditions.

Test the company's SME status, loss position, R&D intensity, accounting period, and all conditions in force for the claim.

Earlier SME treatment

May be relevant to claims for accounting periods beginning before 1 April 2024.

Confirm the period start date, scheme conditions, notification requirements, and expenditure treatment that applied at that time.

This table is a starting point, not a calculation of the benefit. The applicable treatment can depend on accounting-period timing, connected companies, contracted work, grants, subsidised expenditure, and the company's Corporation Tax position. Review the tax advisory service context alongside the current GOV.UK rules before filing.

A practical scheme checklist

• Record the exact start and end dates of the accounting period.
• Check whether the period began before or on or after 1 April 2024.
• Assess SME status, ownership, connected companies, and subcontracting relationships.
• For a loss-making SME, test the intensive support conditions rather than assuming that a loss creates a cash outcome.
• Map each proposed cost to a defined R&D project and retain the technical reason for including it.
• Reconcile the technical narrative, cost schedule, tax computation, and additional information submission.

Which Costs Can You Include in an R&D Claim?

Answer: Potentially qualifying costs can include staff costs, relevant employer costs, software, cloud computing, data, subcontracted work, utilities, and other categories permitted for the accounting period. Each cost must support qualifying R&D, fall within the project period, and have a reasonable, documented allocation where it also serves non-qualifying activity.

Cost eligibility follows the qualifying activity. A familiar expense category does not qualify simply because it appears in an innovative product budget. The company must show that the cost supported qualifying work during the relevant project period and that the calculation is reasonable, consistent, and supported by records.

Qualifying costs should be traced from the technical project to the accounting records.

Common categories requiring careful review

• Staff costs attributable to the qualifying technical work, with a supportable basis for allocating time.
• Relevant employer costs where the rules for the accounting period permit them.
• Software used in the R&D activity, including an evidence-based allocation where it serves wider business purposes.
• Cloud computing, data, subcontracted work, utilities, and other categories where the current rules and facts allow inclusion.

General administration, sales, routine customer support, ordinary maintenance, and commercial activity should not be included merely because they relate to an innovative product. The GOV.UK cost guidance should be checked for the relevant period and category.

Build the calculation from the project record

Link payroll records, time records, technical tickets, project plans, supplier invoices, engineering notes, and accounting entries to the defined project. When a person, software licence, or supplier supports both qualifying and non-qualifying activity, document the allocation method and the source data behind it. An unsupported percentage is difficult to defend, even where the underlying project is technically eligible.

Also consider timing. The claim should distinguish costs incurred within the R&D period from expenditure before the technical work began or after the uncertainty was resolved. Keep payment and ledger evidence with invoices and the technical explanation. A clear audit trail lets finance and technical teams challenge the calculation before submission.

Brief us on your R&D project and evidence trail

How Does the UK R&D Claim Process Work?

Answer: A UK R&D claim process starts by scoping the project, documenting the advance and uncertainty. Interviewing technical staff, reconciling eligible costs, checking the scheme and reporting requirements, and reviewing the submission before filing. The company should retain the technical and financial evidence needed to explain its position if HMRC asks questions.

A defensible claim is built from the project record outward. The technical work, qualifying costs, scheme treatment, additional information, and Corporation Tax return should tell the same story. Filing a claim does not mean HMRC has accepted every project or cost, so the company should retain the supporting file and be ready to explain its position.

1. Scope the project. Define the baseline, advance, uncertainty, technical activities, and start and end points. Separate experimental work from routine development, production, maintenance, and administration.
2. Interview the technical team. Ask the people who performed the work to explain what was not readily deducible. Which alternatives were tested, what failed, and when the technical uncertainty was resolved or the work stopped.
3. Prepare the technical narrative. Use a project-by-project structure. Explain the advance in the wider field, the uncertainty, the work undertaken, and the technical outcome without overstating what the records show.
4. Reconcile the costs. Map eligible expenditure to the projects and accounting records. Apply supportable allocations where resources served more than one purpose, and retain the workings.
5. Check the scheme and reporting requirements. Apply the rules for the accounting period, company profile, connected parties, and any required notification or additional information. Do not rely on an outdated template.
6. Review before filing. Compare the technical account, cost schedule, tax computation, and submission data. Check that project names, dates, figures, and company details agree.
7. Retain the evidence file. Keep technical notes, test records, project plans, payroll and ledger data, invoices, payment records, allocation workings, approvals, and the filed return in an organised location.

Companies preparing for an investment, transaction, audit, or board review may also benefit from linking the claim to their wider corporate finance planning. That does not change the eligibility test, but it can improve governance around assumptions and evidence. Companies assessing the wider control environment can also review the firm's audit and assurance services. For broader planning context, see Corporation Tax planning guidance and the firm's tax advisory services.

What Mistakes Increase HMRC Enquiry Risk?

Answer: Common weaknesses include using broad innovation labels, confusing commercial difficulty with technical uncertainty, including every cost connected to a product, applying unsupported allocations, and relying on outdated rules. Clear project boundaries, technical evidence, current scheme checks, and reconciled cost records reduce avoidable weaknesses, but no adviser can guarantee HMRC acceptance.

An enquiry is not proof that a claim is invalid, and no adviser can guarantee acceptance. Weak claims are often difficult to understand because the technical narrative, project boundary, and cost allocation are not supported by the same evidence. The following issues deserve attention before submission.

Using broad labels instead of defined projects

Words such as innovation, transformation, platform development, and product improvement are not enough. Replace them with a defined technical objective, a baseline, an uncertainty, and the work undertaken. One development programme may contain several projects with different eligibility and end dates.

Confusing commercial difficulty with technical uncertainty

A project can be commercially risky without being technologically uncertain. Customer adoption, market size, price, funding, staffing, or a launch deadline should not be presented as the technical barrier. Explain what a competent professional could not readily determine and why experimentation or analysis was needed.

Including every cost connected to the product

Revenue, marketing, general management, routine support, and ordinary implementation do not become qualifying costs because a product contains technical features. Trace each cost to the work that addressed the uncertainty, and exclude the surrounding commercial activity.

Using unsupported allocations

Apportionment should reflect the underlying activity. A round-number percentage without source data may weaken an otherwise credible claim. Preserve the time records, usage data, project plans, or other evidence that explains the allocation.

Relying on outdated rules

Scheme treatment, reporting requirements, and eligible categories can change. Confirm the accounting period before applying rates, thresholds, or assumptions from an earlier claim. When the business has connected companies, contractors, grants, or cross-border activity, obtain a specific review rather than relying on a prior template.

When Should You Use an R&D Tax Adviser?

Answer: Use an R&D tax adviser when technical teams and finance records are difficult to reconcile. Projects combine experimental and routine work, scheme selection is unclear, or the business lacks experience preparing claims. A focused review can test eligibility, evidence, project boundaries, and cost allocations before submission without replacing the technical team's own knowledge.

Specialist review is most useful when the project sits between technical delivery, finance, and tax compliance. An adviser should not replace the engineers or scientists who understand the work. The value is in bringing the perspectives together, testing the narrative against the current rules, and identifying unsupported assumptions before the figures are submitted.

• Use a focused pre-submission review when the project is probably eligible but the narrative or cost allocation needs challenge.
• Consider broader support when projects span several technical teams, sites, accounting periods, or expenditure categories.
• Seek independent input where the work may be routine implementation, commercial development, or new only to the company.
• Build a stronger governance file when the claim may be reviewed alongside an audit, investment, financing, or transaction.

Look for a firm that can involve technical staff, reconcile the claim to accounting records, explain its assumptions, and apply current HMRC guidance. Aureliant Global is an ICAEW-regulated chartered accountancy firm with a partner-led model and wider ICAEW-aligned compliance standards. Its R&D tax credits advisory work can be considered alongside professional tax advisory support where the claim forms part of a wider finance or tax position.

Request a Consultation about your claim

Frequently Asked Questions

Answer: The questions below address common issues for companies assessing R&D tax relief. Eligibility depends on the technical project, the advance sought, the uncertainty addressed, qualifying expenditure, the accounting period, and the evidence retained. Check the current HMRC rules and obtain advice on the facts of your claim.

What type of work can qualify for R&D tax relief?

Work may qualify when a company seeks an advance in science or technology and resolves a scientific or technological uncertainty that a competent professional could not readily determine. The advance must relate to the wider field, not simply be new to the company. Routine development, standard integration, maintenance, and commercial activity need separate treatment.

Can a loss-making company claim R&D tax relief?

Potentially, but a loss does not establish eligibility or guarantee a cash outcome. The company must satisfy the project, company, cost, accounting-period, and reporting conditions. Loss-making SMEs should check the applicable intensive support rules and current HMRC guidance rather than assume that the same treatment applies to every period.

Which R&D scheme applies after 1 April 2024?

For accounting periods beginning on or after 1 April 2024, the merged R&D Expenditure Credit is generally the starting point. Enhanced R&D Intensive Support may apply to qualifying loss-making, R&D-intensive SMEs that meet the relevant conditions. Confirm the accounting period and company facts before choosing a route.

What evidence should support an R&D claim?

Keep records that connect the technical uncertainty, work performed, people involved, project dates, and qualifying expenditure. Useful evidence can include design notes, test results, issue records, project plans, payroll data, invoices, ledgers, allocation workings, and payment records. The file should show how the technical narrative and cost calculation were prepared. Costs must also be checked against the rules for the relevant accounting period.

When should a company seek specialist advice?

Consider a review when technical teams and finance records are difficult to reconcile. A project includes routine and experimental work, the scheme choice is unclear, or the business has limited experience preparing claims. A structured review can test the advance, uncertainty, project boundaries, evidence, and cost allocation before submission. It cannot guarantee HMRC acceptance.

Discuss Your R&D Claim with Aureliant Global

If you want a clearer view of eligibility, qualifying costs, project boundaries, or claim governance. A focused discussion can help you identify the right questions before preparing a submission. Aureliant Global provides partner-led advisory support for UK and international businesses, with a clear, evidence-based approach.

Request a Consultation

Call Aureliant Global on +44 20 7967 1177