A Financial Controller’s Guide to R&D Tax Claims

Research and Development tax relief is one of the most valuable government incentives available to UK companies, and one of the areas where a Financial Controller can add direct, measurable financial value to the business. A well-prepared claim returns real cash or a meaningful reduction in the corporation tax charge; a poorly prepared one either leaves money on the table or, increasingly, invites an HMRC enquiry that costs far more in time and risk than the relief is worth. For the Financial Controller, who sits at the intersection of the technical project knowledge held by the operational teams and the tax treatment that turns that knowledge into a claim, R&D relief is a responsibility worth understanding properly.

This guide is written for Financial Controllers and senior finance professionals who are responsible for, or contribute to, their company’s R&D tax claim. It is not a substitute for specialist tax advice on a complex claim, and it does not attempt to turn a Financial Controller into a tax adviser. What it does is set out what the Financial Controller needs to understand to manage the process well: what qualifies, how the schemes work, how to identify and quantify eligible costs, how to prepare a claim that withstands scrutiny, and where the real risks lie in the current, considerably tougher HMRC environment.

Why R&D Relief Matters to the Financial Controller

The Financial Controller occupies a uniquely well-placed position in the R&D claim process. The technical teams understand the projects but rarely understand the tax rules or the cost identification; the external adviser understands the rules but does not have day-to-day visibility of the projects or the cost base; and the company’s tax position, payroll data, and cost ledgers all sit within the finance function. The Financial Controller is the person who can connect the technical narrative to the financial substantiation, and the quality of that connection largely determines the quality of the claim.

This matters more than ever because the R&D regime has changed substantially. HMRC has significantly increased its scrutiny of claims following a period of widespread abuse, error rates in the SME scheme have been a matter of public concern, and the rules themselves have been reformed with the merger of the two historic schemes. A Financial Controller who treats the R&D claim as a once-a-year box-ticking exercise handed wholesale to an adviser is exposing the company to risk. One who understands the substance is in a position to ensure the claim is both maximised and defensible.

How the R&D Schemes Work

For accounting periods beginning on or after 1 April 2024, the UK operates a single merged R&D expenditure credit scheme for most companies, replacing the previous split between the SME scheme and the separate Research and Development Expenditure Credit (RDEC) for larger companies. A separate, more generous regime — enhanced R&D intensive support — applies to loss-making, R&D-intensive SMEs that meet a qualifying threshold. The Financial Controller’s first task on any claim is to establish which regime applies to the company for the period in question, because the mechanics, the rates and the accounting treatment differ.

The merged scheme operates as an above-the-line expenditure credit: the credit is taxable and is recognised in the accounts as income, which affects the presentation in the profit and loss account in a way the old SME super-deduction did not. Understanding this presentation difference is squarely within the Financial Controller’s remit, because it changes how the relief flows through the management accounts and the statutory accounts. The current rules, rates and definitions are set out in HMRC’s R&D relief guidance, which should be the reference point for any claim rather than a half-remembered version of the old rules.

The Merged Scheme in Detail

Under the merged scheme the expenditure credit is calculated as a percentage of qualifying R&D expenditure and is itself taxable, producing a net benefit after corporation tax. Because the credit is recognised above the line, it increases reported profit before tax, and the Financial Controller needs to model the net cash or tax effect carefully rather than quoting the headline credit rate as if it were the benefit. The distinction between the gross credit and the net benefit is a frequent source of confusion when finance communicates the value of a claim to the board, and getting it right is part of presenting the numbers honestly.

Enhanced Support for R&D-Intensive SMEs

Loss-making SMEs whose qualifying R&D expenditure exceeds a defined proportion of their total expenditure qualify for a more generous regime, designed to protect the most research-intensive smaller companies through the transition from the old SME scheme. For a Financial Controller at a loss-making, research-heavy business — a typical early-stage technology or life sciences company — establishing whether the company meets the intensity threshold is a material financial question, because the difference in the relief available is significant. The calculation of the intensity ratio, and the treatment of connected companies within it, is an area where specialist input is genuinely warranted, but the Financial Controller should understand enough to know when the question is live.

Periods Spanning the Transition

For accounting periods that straddle the introduction of the merged scheme, transitional rules determine which regime applies, and a Financial Controller dealing with a claim for an earlier period must apply the rules that were in force at the time rather than the current ones. This is a practical trap: the rules, rates and even the qualifying cost categories have changed over recent years, and a claim for a prior period is not prepared under today’s regime. Establishing the correct period and the correct ruleset is the unglamorous first step that prevents a fundamentally misconceived claim.

What Actually Qualifies as R&D

The single most common cause of a defective claim is a misunderstanding of what qualifies. The statutory definition is narrower and more specific than most people assume. Qualifying R&D requires a project that seeks an advance in science or technology through the resolution of scientific or technological uncertainty — uncertainty that a competent professional in the field could not readily resolve. This is a meaningful test, and it excludes a great deal of work that businesses informally describe as “development”.

The Financial Controller’s role here is not to make the technical judgement — that belongs to the competent professionals on the projects — but to ensure that the judgement is genuinely made, properly documented, and applied consistently. A claim that sweeps in routine development, cosmetic product changes, or work that simply applies existing technology without resolving genuine uncertainty is the kind of claim that now attracts an enquiry. The Financial Controller who insists on a clear articulation of the scientific or technological uncertainty for each project, in the words of the technical team, is protecting the company from exactly that risk.

Identifying and Quantifying Qualifying Costs

Once the qualifying projects are established, the financial work begins, and this is where the Financial Controller’s contribution is most direct. Qualifying costs fall into defined categories — staffing costs for employees directly engaged in the R&D, a proportion of externally provided workers and subcontractors, consumable items including a proportion of power, water and materials consumed in the R&D, software, and certain data and cloud computing costs. Each category has its own rules and its own apportionment basis.

The most significant cost in most claims is staff time, and quantifying it correctly requires the Financial Controller to work from the payroll data and a defensible apportionment of each relevant individual’s time spent on qualifying activity. A robust claim rests on a methodical apportionment — ideally supported by timesheets or a contemporaneous record, not a retrospective guess. Where time records do not exist, the apportionment must be reasonable, documented and consistent, and the Financial Controller should be able to explain how each percentage was arrived at. The categories and apportionment rules are detailed in the HMRC guidance, and getting the cost identification right is the part of the claim where finance adds the most value and where errors are most common.

A Worked Approach to Staff Apportionment

Consider a software business with a development team of twelve engineers, of whom some spend the majority of their time on genuinely uncertain technical work and others spend most of their time on routine feature delivery and maintenance that does not qualify. The wrong approach is to claim a flat percentage of the whole team’s cost. The right approach is to work individual by individual: for each engineer, establish from the project records and the team lead’s input what proportion of their time over the period was spent on qualifying activity, document the basis for that proportion, and apply it to that individual’s total employment cost including employer’s National Insurance and pension. The result is a build-up that ties to the payroll, reflects the reality of who did qualifying work, and can be explained line by line if HMRC asks. That explicability is the whole point — a claim you can defend is worth more than a larger claim you cannot.

Preparing a Claim That Withstands Scrutiny

The current environment demands that every claim be prepared as if it will be enquired into, because a meaningful proportion now are. Since 2023 a claim must be accompanied by an Additional Information Form submitted to HMRC before the company tax return, setting out the projects, the qualifying expenditure and a technical narrative. The Financial Controller should treat this not as a formality but as the company’s first line of defence — a clear, specific, honest account of why the projects qualify and how the costs were determined.

The hallmarks of a defensible claim are specificity and substantiation. A technical narrative that describes genuine uncertainty in concrete terms, a cost computation that ties to the underlying ledgers and payroll, an apportionment methodology that is documented and reasonable, and a clear record of who made the qualifying technical judgements — these are what distinguish a claim that survives scrutiny from one that does not. The Financial Controller who maintains this discipline, and who keeps the supporting evidence in order rather than reconstructing it under enquiry pressure, is doing the single most valuable thing for the company’s R&D position.

If HMRC Opens an Enquiry

Given the current level of scrutiny, a Financial Controller should assume an enquiry is a realistic possibility and prepare accordingly rather than treating it as a remote contingency. If an enquiry is opened, the company’s position is determined almost entirely by the quality of the evidence assembled at the time of the claim. A claim supported by a clear technical narrative, a documented cost methodology, contemporaneous project records and a coherent account of the qualifying judgements is defensible. A claim where the narrative is vague, the costs were estimated retrospectively and the supporting evidence has to be reconstructed is exposed. The Financial Controller’s discipline at the point of claiming is therefore the determinant of how an enquiry, if it comes, will go — which is why the evidence-led approach is not bureaucratic caution but practical risk management.

The Most Common Errors Financial Controllers Should Guard Against

The pattern of defective claims is well established, and a Financial Controller who knows the common failure modes can design the process to avoid them. The first and most frequent is claiming for work that does not meet the uncertainty test — routine development, the application of existing technology, aesthetic or commercial improvements that involve no scientific or technological advance. The discipline that prevents this is insisting that each project’s qualifying uncertainty is articulated by a competent professional in concrete terms before any cost is attached to it.

The second is weak cost substantiation: apportionments pulled from the air, costs included that do not fall within a qualifying category, subcontractor and externally provided worker costs treated without regard to the specific rules that govern them. The remedy is a build-up that ties to the ledgers and the payroll with a documented basis for every apportionment. The third is treating the Additional Information Form as a formality, producing a generic narrative that could describe any company — precisely the kind of submission that signals a weak claim to HMRC. The fourth, particularly relevant since the regime reforms, is applying the wrong scheme or the wrong rates to the period, which produces a claim that is wrong at the most fundamental level. Each of these is avoidable with the methodical approach the controlling function is built to provide.

Record-Keeping and the Annual Cycle

The Financial Controller who manages R&D well does not treat it as an annual event but builds the evidence through the year. Where qualifying projects are identifiable in advance, light-touch contemporaneous records — a note of the qualifying activity, an indication of who is working on it and roughly how much of their time — transform the quality of the eventual claim and remove the retrospective guesswork that weakens it. This does not require an elaborate timesheet system; it requires a habit of capturing the relevant information close to when the work is done rather than reconstructing it months later under the pressure of a filing deadline.

Building this into the finance calendar — a periodic check-in with the technical teams on qualifying activity, a maintained record of qualifying projects and the people working on them, a folder of supporting evidence that grows through the year — turns the annual claim from a scramble into a straightforward assembly of material already gathered. It is the same principle that underlies every well-run part of the controlling function: do the work steadily through the cycle rather than in a panic at the deadline, and the output is both better and less stressful to produce.

Working With External Advisers

Most companies use an external adviser for their R&D claim, and a good adviser adds real value. But the relationship the Financial Controller should aim for is a collaborative one in which finance owns the cost substantiation and the company owns the technical judgement, with the adviser providing rules expertise and quality assurance — not one in which the claim is outsourced wholesale to a provider who promises a large number with minimal input. The aggressive, contingent-fee R&D claim providers that proliferated in recent years are precisely the ones whose claims have attracted scrutiny, and the Financial Controller is well placed to insist on a rigorous, evidence-led approach regardless of who prepares the paperwork. Managing this relationship well is part of the broader discipline of managing external tax advisers that sits within the controlling function.

R&D Relief in the Wider Financial Picture

An effective Financial Controller sees the R&D claim not in isolation but as one element of the company’s overall tax and cash position. The timing of the relief matters for cash flow planning — whether the benefit arrives as a reduction in a corporation tax liability or, for a loss-making company, as a payable credit, has direct consequences for the cash forecast that the Financial Controller maintains. A company relying on the R&D credit as a meaningful source of cash needs that timing reflected accurately in its forecasting, not assumed to arrive on a convenient date.

The claim also interacts with the company’s broader tax planning, its loss position, and its group structure where one exists. For a Financial Controller in a group, the interaction between R&D claims, group relief and the allocation of qualifying activity across entities adds a layer of complexity that warrants careful handling. The point is not that the Financial Controller must master every detail of this interaction unaided, but that they must see the connections and bring in specialist input where the stakes justify it — integrating the R&D claim into the financial picture rather than leaving it as a standalone exercise disconnected from the cash forecast and the tax position it actually affects.

The Accounting Treatment

The Financial Controller is responsible for the correct accounting treatment of the relief, which under the merged scheme means recognising the expenditure credit appropriately and presenting it correctly in the accounts. The credit affects the tax line and, for the above-the-line credit, the presentation within operating results, and it has implications for the deferred tax position and the effective tax rate that the Financial Controller must work through. This is the point at which the R&D claim stops being a tax exercise and becomes a financial reporting exercise — and it is squarely within the controlling function’s accountability. Getting the disclosure and the deferred tax interaction right is part of the broader month-end and year-end discipline covered in our guide on optimising the month-end close.

What Good Looks Like

A Financial Controller managing the R&D claim well runs a process that is methodical, evidenced and defensible. The qualifying projects are identified by the competent technical professionals with genuine uncertainty articulated; the costs are built from the payroll and the ledgers with a documented apportionment; the Additional Information Form is specific and honest; the accounting treatment is correct; and the supporting evidence is retained in an orderly way against the possibility of enquiry. Done this way, R&D relief is a genuine and recurring source of value to the business, claimed with confidence rather than anxiety.

Done badly — as an annual scramble handed to a contingent-fee provider with minimal finance input — it is a growing liability. The difference between the two is largely a matter of the Financial Controller’s engagement and discipline, which is exactly why this is a capability worth developing. The companies that claim well are the ones where finance treats R&D as part of the controlling function’s core responsibility rather than as someone else’s problem once a year.