Fintech grants and R&D tax credits UK: how to separate funded vs self-funded work

Fintech grants and R&D tax credits UK can be combined, but only if you separate scope and costs cleanly. The most common failure mode is not ‘double claiming’ on purpose, but messy project governance: work packages that drift, timesheets that do not map to funding sources, and narratives that contradict each other across grant and HMRC reporting. 

Start with a simple definition 

‘Funded work’ means activity where a grant or contract is explicitly paying for defined tasks or deliverables. ‘Self-funded work’ is the residual R&D you pay for yourself, even if it runs alongside the funded project. Your goal is to prove, with records, which costs were covered by which source, and to keep technical narratives consistent. 

Know which R&D tax regime you are in 

For accounting periods beginning on or after 1 April 2024, claims sit within the merged R&D expenditure credit scheme, with Enhanced R&D Intensive Support (ERIS) for certain loss-making R&D-intensive SMEs.  

Eligibility tests still hinge on whether the work meets the definition of R&D for tax purposes, and you must follow the scheme’s rules on qualifying expenditure. Grant funding changes the fact pattern and can affect how expenditure is treated, so do not assume yesterday’s interpretation applies. 

What HMRC means by ‘subsidised’ expenditure 

HMRC’s internal manual discusses when expenditure is considered subsidised, including examples where payments cover all contract costs or where R&D costs are incidentally incurred.  

The practical implication is governance: you should be able to point to the grant agreement (or contract), the funded work packages, and the accounting trail that shows which costs were reimbursed, and which were not. 

A practical 7-step separation method that finance teams can live with 

1. Write work packages as accounting objects. Give each work package a unique code, owner, and definition of done. 

2. Tag each work package as funded, co-funded, or self-funded. If co-funded, record the funding percentage and the rule that drives it (from the grant agreement). 

3. Set up cost centres or project codes in the ledger that mirror the work packages. Do not rely on narrative explanations later. 

4. Use time recording that maps to work packages, not generic ‘R&D’ buckets. If time recording is light-touch, at least record sprint-level allocation with approvers. 

5. Keep a single evidence pack. Store architecture changes, experiment logs, test results, and release notes in one place, then reference the same artefacts in both grant reports and HMRC narratives. 

6. Reconcile monthly. Compare ledger, timesheets, and grant claims while memory is fresh, and correct miscodings before the period closes. 

7. At year end, produce two outputs: (a) a grant reconciliation that shows funded cost coverage, and (b) an R&D technical narrative that aligns to the same work package structure. 

Reporting alignment: avoid contradictions 

• Use the same baseline and objectives in grant reporting and R&D narratives. Differences trigger questions. 

• Keep deliverables realistic. Grant reports often reward certainty, while R&D narratives require uncertainty resolution. Reconcile this by describing uncertainty at the start and measurable learning milestones. 

• Be precise about subcontractors. Grant rules and R&D tax rules can treat subcontracting differently, so document who did what, where, and under which contract. 

How grant rules create hidden constraints 

Innovate UK funding rules reference the UK Subsidy Control Act 2022 framework when describing eligibility and the status of different organisation types.  

In practice, this means you should treat grant agreements as compliance documents: they define eligible costs, reporting frequency, audit rights, and exploitation commitments. Build your project controls to satisfy both the grant and the tax claim, rather than bolting one on later. 

Common CFO headaches and mitigations 

• Cash flow timing mismatch: grant payments are milestone-based while tax relief is periodic. Mitigation: build a combined cash model and buffer delays. 

• Evidence scattered across tools: engineering artefacts live in Git, Jira, cloud logs; finance has the ledger. Mitigation: create a simple evidence index tied to work packages. 

• Audit fatigue: multiple assurance points (grant audit, HMRC review). Mitigation: standardise governance once, reuse the pack. 

• Team churn: knowledge leaves mid-year. Mitigation: capture uncertainty statements and outcomes continuously, not at claim time. 

Where specialist support fits 

Combining incentives is mainly an operating model problem. FI Group by EPSA supports companies with innovation incentives by helping design work-package governance that spans grants and R&D tax relief, aligning evidence capture, and supporting scheme interpretation so finance and engineering stay consistent. Sector context is available here: Fintech innovation grants and R&D tax credits UK. 

FAQs 

Can I claim R&D tax relief on a project that received a grant? 

Often yes, but treatment depends on the facts and the applicable scheme rules. The key is to document which expenditure was funded and how. 

Is it safer to split funded and self-funded work into separate projects? 

Not always. Separate projects can help clarity, but they can also create artificial boundaries. Work-package level separation is usually more practical. 

What documents should I keep? 

Grant agreement, work package definitions, ledger exports, timesheets or sprint allocations, subcontractor agreements, and a technical evidence pack (tests, logs, design changes). 

What if the funded scope changes mid-project? 

Record a formal change control: updated work packages, updated budgets, and a narrative explaining why the change was necessary and how it affects funding coverage. 

Who should own this internally? 

A joint owner model works best: finance owns cost integrity, engineering owns the evidence pack, and a programme lead owns work-package governance.