Pre-summer is the ideal window to get your R&D tax claim into shape before autumn filings. For UK SaaS and AI teams, the difference between a smooth HMRC process and a prolonged enquiry generally comes down to one thing; evidence. This guide sets out what qualifies, what doesn’t, how the new mechanics work, and how to bake compliance into sprints and month-end so you are not paper-chasing at year-end.

We focus on practical steps, with a simple timeline and checklist you can drop workflow. We also show how integrating R&D with monthly management accounts improves claim quality and cash flow forecasting.

Who can claim and what “R&D” means for software and AI

In the UK, R&D for tax purposes applies when a project seeks an advance in science or technology and faces technical uncertainty that a competent professional could not readily resolve. For SaaS and AI teams, this usually means pushing beyond standard implementation patterns or well-documented approaches.

 

Examples that can qualify:

  • New ML model architectures or training strategies to achieve a step-change in accuracy, latency or robustness where known methods failed.
  • Systems-level breakthroughs such as new compilers, distributed schedulers, or privacy-preserving compute with provable guarantees.
  • Data engineering techniques where data quality, scale or noise characteristics require original solutions not available off the shelf.

 

Work that typically does not qualify:

  • Routine integration of known APIs or frameworks used as intended.
  • Cosmetic UI refreshes, standard refactors, and business-as-usual bug fixing.
  • Commercial data warehousing and hosting without a technical advance.
  • Feature toggles, A/B tests and configuration work using established patterns.

 

Your claim should be built around projects, each with a clear technical hypothesis, uncertainty, experiments and outcomes.

 

How the R&D tax credit works under the merged framework

From April 2024, HMRC operates a merged R&D framework for most companies, with separate rules retained for an “R&D intensive” SME category. In practice:

 

  • Most companies claim under the merged scheme with a taxable credit similar in spirit to the former RDEC but available to a broader base.
  • Loss-making SMEs that are R&D intensive can access a higher payable credit rate. “Intensive” usually means qualifying R&D expenditure is at least 30% of total spend in the period, but check the current HMRC definition at the time you file.

 

Relief is delivered as either a reduction in Corporation Tax, a taxable credit, or a payable amount for certain loss-making companies. The net cash impact depends on your profit or loss position, the applicable rate, any caps and PAYE/NIC limits. Do not promise a fixed percentage internally without modelling your specific numbers.

 

What expenses can qualify vs what to exclude

Qualifying costs often include:

  • Staff costs for employees directly and actively engaged in R&D, plus a sensible proportion for supervising and supporting roles. Include gross pay, employer NIC and employer pension contributions.
  • Externally provided workers and certain subcontractors, subject to scheme-specific limits and contractual control. For software, subcontracting treatment can be nuanced depending on who bears technical risk.
  • Consumables, cloud compute, and software used directly for R&D activities. Track ML training runs, datasets, and environment costs separately from production.

 

Common non-qualifying items:

  • Pure production hosting and routine operations.
  • General analytics and BI platforms used for commercial reporting.
  • Sales, marketing, customer support and product management unrelated to eligible technical work.
  • Capital expenditure unless specific criteria for software or prototypes are met.

 

Keep timesheets or sprint allocation estimates that tie people and costs to specific R&D tasks. Vague apportionments are a red flag.

 

Subcontracting and contractual nuance

Claimability often turns on who sets the technical direction, accepts technical risk, and owns the results. Points to pin down in writing:

 

  • Statement of work describing the uncertain technical objectives, not just deliverables.
  • Who designs the solution path and who can change scope in response to failed experiments.
  • IP ownership and whether the subcontractor is delivering routine services or contributing original R&D.

 

Under the merged rules, subcontracting restrictions exist and differ from the old SME/RDEC split. If in doubt, obtain advice early and keep versions of contracts and change notes.

 

Evidence standards HMRC expects

Think like a research notebook, not a marketing brochure. For each project:

 

  • Hypothesis: the technical question and what would count as an advance.
  • Uncertainty: why a competent professional could not readily solve it.
  • Experiments: sprint tickets, branches, model versions, datasets, and environment details.
  • Metrics: target thresholds for accuracy, latency, throughput, or privacy guarantees, and how you measured them.
  • Outcomes: what worked, what failed, and the knowledge gained.

 

Keep experiment logs, model training summaries, benchmark scripts, error analyses, and post-mortems. Embed evidence capture into your tools rather than assembling it later.

 

 

What are the new rules and scheme changes to note

Recent changes you should plan for:

 

  • Merged scheme mechanics, with R&D intensive SME uplift carved out separately.
  • Additional information forms and pre-notification for new claimants in certain cases.
  • Overseas expenditure restrictions with limited exceptions where talent, geography or regulations make UK performance impracticable.
  • PAYE/NIC cap mechanics, limiting payable credits by reference to your payroll footprint, with some leeway for subcontracting and EPWs.
  • Data, cloud and pure mathematics are in scope, but you must tie them to an R&D project and evidence uncertainty and advance.

 

Because details evolve, build a habit of checking guidance when you close each period, not just at year-end.

 

 

Bake compliance into sprints and month-end

Make compliance part of how you work, not a year-end scramble:

 

  • Sprint planning: tag R&D tickets and note the hypothesis and metric targets. Flag expected data or compute needs.
  • During the sprint: capture experiment artefacts in your repo or MLOps tool. Require short experiment logs as part of “definition of done.”
  • Sprint review: record outcomes, metrics and reasons for continuing, pivoting or stopping.
  • Month-end with finance: roll up R&D-tagged time, payroll, EPW invoices, cloud training runs and dataset costs. Reconcile to the general ledger and store a monthly R&D pack.

 

Integrating R&D with monthly management accounts creates an audit-friendly trail and supports cash runway modelling. If you want management reporting that aligns KPIs with R&D evidence and costs, see how our management accountants build monthly packs that stand up to investor and HMRC scrutiny.

You can learn more about our monthly management accounts approach on our site.

 

Timeline: pre-summer to autumn filing

  • Now: confirm eligible projects and align definitions with engineering leads. Map staffing, subcontractors and cloud lines to project codes. Set up ticket tags and timesheet categories.
  • July: implement a monthly R&D pack within your management accounts. Backfill evidence for earlier periods while details are fresh. Review subcontract terms.
  • August: draft the technical narratives with hypotheses, uncertainties and experiment summaries. Validate metrics and thresholds with tech leads. Model claim scenarios, including PAYE/NIC caps.
  • September: finalise numbers, perform a peer review on eligibility and exclusions, and prepare the additional information form. Sanity-check the cash flow impact in your forecasts.
  • October or your filing month: submit with clean narratives and reconciled schedules. Keep your evidence indexed.

 

Quick compliance checklist for SaaS and AI teams

Define eligible projects with a concise hypothesis and explicit uncertainties.
Tag R&D tickets and record experiment logs with metrics and versions.
Separate production hosting from R&D compute and dataset costs.
Track time by project, including EPWs and subcontractors, with contracts on file.
Prepare monthly R&D cost reconciliations tied to your general ledger.
Draft technical narratives early and update after each sprint review.
Model caps and scheme mechanics before promising any cash impact.

 

How much is the R&D tax credit worth?

It depends on your profit or loss position, whether you qualify as R&D intensive, and cap mechanics. Under the merged rules, most profitable companies see a Corporation Tax reduction or taxable credit at the published rate for the period. Loss-making intensive SMEs can access a higher payable credit rate, subject to the PAYE/NIC cap. Always model your own numbers rather than relying on headline percentages.

 

Why integrate R&D with management accounts

A joined-up approach improves both compliance and cash planning:

 

  • Better evidence: sprint artefacts flow straight into monthly packs.
  • Cleaner numbers: costs are reconciled monthly, reducing HMRC queries.
  • Clear runway: forecasts reflect the timing and magnitude of credits, not just rough estimates.

 

Venn combines R&D claim preparation with monthly management accounts and KPI reporting so that claims are robust and cash flow projections are realistic. If you want to strengthen your monthly management accounts and connect R&D tracking to board-ready reporting, explore our service overview for management accountants. For end-to-end claim support, see our page on R&D tax credits.

 

FAQs

  • Who can claim the R&D tax credit? UK companies subject to Corporation Tax that carry out qualifying R&D projects aimed at a scientific or technological advance and facing genuine technical uncertainty.
  • How does the R&D tax credit work? Relief is provided as a reduction in tax, a taxable credit, or a payable amount for certain loss-making companies, under the merged framework with a separate uplift for R&D intensive SMEs.
  • What expenses can qualify? Staff directly engaged in R&D plus related employer costs, qualifying subcontractors and EPWs, consumables, cloud compute and software used directly for R&D. Exclude routine production, commercial analytics, and non-technical activities.
  • What are the new rules? A merged scheme with additional disclosures, restrictions on some overseas costs, and PAYE/NIC cap mechanics. An intensive SME category can access a higher payable credit.
  • How much is it worth? The benefit varies based on profitability, intensity status and caps. Model your numbers using current rates for your accounting period.

 

Next steps

If you want a compliance-first claim without derailing delivery, integrate R&D tracking into your monthly close and let finance carry the weight. Venn can help stitch together sprint evidence, cost tracking and forecasting so your autumn filing is calm and query-ready. Explore how our management accountants can support your monthly management accounts, and read more about our R&D tax credits service to get started.

 

Learn more about our monthly management accounts approach: https://vennaccounts.com/management-accounts/

See our R&D tax credits support: https://vennaccounts.com/rd-tax-credits/

Explore KPI-led reporting and forecasting: https://vennaccounts.com/financial-planning-analysis-reporting