R&D Tax and Patent Box: Hiring the Right Capability

R&D tax relief and Patent Box are the two UK incentives most likely to be worth real money to an innovative business and least likely to have a clear owner inside it. Both sit between finance, tax and the technical teams who actually do the work; both have become considerably more demanding to claim in recent years; and both are usually handled by an external specialist whose fee is a percentage of the benefit. This piece is about the in-house side: what capability the work actually needs, who should own it, when a hire is justified, and when the adviser remains the right answer. For how claims are prepared, see our guide to the FC’s guide to R&D tax claims.

Why in-house capability has become more valuable

Three developments have changed the calculation.

Compliance requirements have tightened. Claims now require more documentation, more specific technical narrative and more advance notification than they once did, and HMRC’s R&D relief guidance sets out obligations that assume someone in the business is organised about it. A claim assembled retrospectively from memory is now materially weaker than one supported by contemporaneous records.

Enquiry activity has risen. More claims are challenged, and defending one requires the underlying evidence rather than a persuasive narrative. Businesses whose entire claim rationale lives in an adviser’s file find that uncomfortable.

And percentage-fee arrangements have become expensive at scale. A fee of fifteen to twenty per cent of benefit is reasonable on a £40,000 claim and considerable on a £600,000 one. At that point the arithmetic of bringing capability in-house changes entirely.

What the work actually requires

Four capabilities, and only one is tax technical.

Identifying qualifying activity. The hardest part, and it is a translation problem rather than a tax one. Someone has to sit with engineers or developers, understand what they were trying to achieve, and determine whether it involved genuine technological or scientific uncertainty rather than routine application of existing knowledge. Finance people frequently under-claim because they do not recognise qualifying work; technical people over-claim because everything feels novel.

Cost capture and apportionment. Staff time, subcontractors, consumables, software. This is management accounting work, and it is far easier if the time recording and project coding were designed with the claim in mind rather than reconstructed afterwards.

Technical narrative. Writing up the uncertainty and the advance in language that satisfies the requirements without overstating. This is where poorly-prepared claims fail on enquiry.

And Patent Box, which is different work entirely — tracking qualifying IP income by patent, applying the streaming calculation and the nexus fraction, and maintaining the records over years. It is more mechanical than R&D and more demanding of systems — HMRC’s Patent Box guidance sets out the election and the calculation —, which is why fewer eligible businesses claim it than should.

Who should own it

The realistic options, in ascending order of scale.

The Financial Controller, with an adviser. The most common arrangement and appropriate for most businesses — the FC will typically be qualified through ICAEW, ACCA or CIMA, with the adviser bringing CTA-level specialism from the Chartered Institute of Taxation. The FC owns cost capture and the relationship with the technical team; the adviser owns the technical narrative and the submission.

An in-house tax manager, with an adviser on the narrative. Sensible once a tax function exists. The internal person knows the business and can capture evidence through the year; the adviser provides specialist judgement on marginal activity.

A dedicated innovation-incentives role. Rare, and justified only where claims are large and recurring — typically a business claiming several hundred thousand pounds annually with an active patent portfolio.

Or a hybrid that works well: the management accountant owns cost capture and project coding as part of the monthly cycle, the FC owns the process, and the adviser is engaged for the technical narrative on a fixed fee rather than a percentage. That arrangement captures most of the saving without a hire.

When a hire is justified

Three tests, and all three should be true.

The claim is recurring and material — annual, and large enough that a percentage fee is a meaningful number.

The identification work is ongoing rather than annual. Businesses with continuous development activity benefit from someone capturing evidence as it happens; businesses with occasional projects do not.

And there is adjacent work to justify the rest of the role. Nobody is hired solely for R&D claims below a very large scale. The realistic version is a tax manager or senior management accountant whose remit includes innovation incentives — which is how most businesses acquire the capability.

When the adviser remains right

Where claims are occasional or the business is claiming for the first time — the learning curve is steep and the first claim sets the pattern.

Where the qualifying judgement is genuinely marginal. An opinion from a specialist firm carries weight on enquiry that an internal assessment does not.

Where Patent Box election is being considered, since the initial analysis is specialist and the decision is long-term.

And on any enquiry. Defending a challenged claim is disputes work rather than claims work — see our guide to the tax investigations role.

What is worth changing even where the adviser stays: move from a percentage fee to a fixed one where the claim is established and recurring. Percentage arrangements make sense when the adviser is doing the identification work and carrying the risk; they make less sense in year four when the business has done most of the preparation itself.

What to do in-house regardless

Four things that improve every claim and cost nothing to start. Code project time properly at source, so the cost apportionment is a report rather than a reconstruction. Capture the technical rationale contemporaneously — a short note when a project starts, describing what was uncertain, is worth more at enquiry than a reconstructed narrative eighteen months later. Keep the subcontractor and consumables records aligned to the projects. And review eligibility across the whole business annually, not just in the obvious department; qualifying activity in operations, manufacturing process or software integration is regularly missed.

Doing those four things well is the difference between a defensible claim and a hopeful one — and it is management accounting work rather than tax work, which is why it belongs in the monthly cycle rather than in a January scramble.