What HMRC Accepts
Software costs form one of the eight categories of qualifying expenditure at CIRD83000. The test is whether the software is used directly in the qualifying R&D activity. Software used for routine administration, commercial operations, or support of the production environment is outside the rules.
Claimable software includes development tools and IDEs, compilers and build systems, specialist scientific packages (statistical, engineering, simulation, CAD, electronic design automation), testing frameworks and test automation tools, machine-learning platforms and libraries used in R&D training, modelling and analysis tools, and version control and code review systems used by the R&D team.
Apportionment
Apportionment is almost always required. A typical engineering organisation runs the same tool stack for R&D and for production support. The licence cost is split accordingly.
Two common methods:
- Headcount-based apportionment. The licence supports a team where the average R&D percentage is X%; the claimable share is X%.
- Time-based apportionment. The licence supports a specific system or workload where R&D use accounts for Y% of total hours; the claimable share is Y%.
For large tool estates, the method should be applied consistently across the licence portfolio and documented. Spot-fix percentages applied differently to different tools weaken the overall claim position.
What Is Included
- Annual or perpetual licence fees for tools used directly in R&D.
- SaaS subscriptions supporting R&D activity (with apportionment for mixed use).
- Support and maintenance contracts forming part of the licence arrangement.
- User-seat costs for R&D engineers and researchers.
- Specialist data-analysis or simulation software.
What Is NOT Included
- Licences for software used purely in non-R&D operations (CRM, HR, finance, marketing automation).
- Software bundled with hardware and treated as capital (usually follows the hardware treatment).
- Microsoft Office and similar office productivity software, except for the narrow R&D-attributable portion.
- Software licensed to customers as part of the product (this is cost of sales, not R&D input).
- Software whose cost is already captured under consumables or cloud categories.
Software vs Cloud Costs
Since April 2023, cloud computing costs have been a separate qualifying category in their own right. A cloud-native development tool accessed on a subscription basis sits between the two headings. The practical answer is usually to treat the subscription as software cost and the underlying compute usage as cloud cost. A specialist adviser will avoid double-counting and ensure each cost is captured once in the right category. See Data and Cloud Costs for the cloud treatment.
Common Enquiry Risks
- Claiming 100% of software licences without apportionment. Rarely defensible.
- Including general-purpose office suites. Usually too indirect to qualify.
- Double-counting across software and cloud categories. Watch the boundary.
- Claiming for software that supports the commercial product rather than its development. Support tools for a live product are not R&D input.
- Treating per-seat licences as uniformly R&D when some seats are held by non-R&D staff. Seat-by-seat evidence is cleaner.
Worked Example (Indicative)
A software company spends £48,000 in the year on IDE subscriptions, CI/CD tooling, test automation, and a specialist performance profiler used by its ten-engineer team. An analysis of engineer time shows that 72% of team hours are spent on qualifying R&D.
Claimable software cost: £48,000 x 72% = £34,560.
At the 20% merged scheme credit rate, this contributes £6,912 gross credit; net benefit approximately £5,184 after corporation tax at 25%. Modest on its own, but a meaningful addition to the overall claim when combined with staffing and other categories. Figures are indicative.
Licence Models and the Apportionment Impact
The commercial terms of a software licence affect the apportionment approach. Three common models:
Per-seat subscription. Each R&D engineer holds a seat; the cost is directly attributable to that individual and follows their R&D apportionment. Clean and easy to evidence.
Enterprise or floating licence. A licence pool shared across a larger team including non-R&D staff. Apportionment uses the share of R&D users within the pool, or the share of R&D time for the team as a whole.
Unlimited / site licence. A fixed fee covering unlimited use across the organisation. Apportionment is harder and typically uses either headcount proportion, activity analysis, or a defensible composite method agreed with the specialist adviser.
The apportionment choice should be consistent across similar licences, documented in writing, and reconciled to invoices for the claim period.
Sector Variations in Software Claims
Software and SaaS companies. Software licences for development tools, test automation, observability, and version control. Cloud-based CI/CD tools. Specialist platforms for performance testing or machine-learning experiment tracking. Typical share of the claim 3-8%.
Engineering. CAD licences, simulation software (finite element analysis, computational fluid dynamics), electronic design automation tools, specialist engineering databases. Typical share 4-10%.
Life sciences. Statistical packages, bioinformatics platforms, lab information management systems, sequencing analysis tools. Typical share 3-10%.
Construction. BIM (Building Information Modelling) software, structural analysis tools, project collaboration platforms. Typical share 2-7%.
Evidence Checklist
- Invoices for each software licence claimed, covering the relevant period.
- Proof of the licence holder (which users or teams).
- Apportionment schedule showing the R&D percentage applied and the methodology.
- Reconciliation to the general ledger subscription or licence cost accounts.
- A statement explaining why each tool is used directly in the R&D activity (to avoid misclassification of administrative software).
Building a Claim-Friendly Tooling Strategy
Companies that expect to claim R&D credits year after year benefit from organising their tooling in a way that simplifies apportionment. Three practical moves:
First, separate licences and subscriptions into an "R&D tools" cost centre within the accounting system. Monthly invoices then flow directly to the claim-ready ledger line without manual reclassification at year-end.
Second, where a tool is used by both R&D and non-R&D staff, consider per-seat licensing so the R&D headcount share is mechanically visible. A floating licence pool looks simple but produces apportionment complexity.
Third, maintain a short written note for each tool explaining its R&D role. Refresh the note at each year-end claim preparation. The narrative supports both the eligibility argument (direct use in qualifying activity) and the apportionment argument (share of R&D use).
Bundled and Capital-Embedded Software
Software bundled with hardware or embedded in a capital asset follows the hardware treatment. An embedded control system shipped with a piece of manufacturing equipment is part of the capital cost of the equipment, not a separate software cost for R&D purposes.
This distinction matters for companies that acquire R&D equipment with embedded software components. The whole capital outlay falls under Research and Development Allowances if the equipment qualifies, or under ordinary capital allowances otherwise. The embedded software is not separately claimable under the R&D tax credit rules.
Where software is licensed separately from hardware but only works with that hardware (a specialist measurement system's proprietary analysis software, licensed on annual renewal), the software cost sits in the software category and follows the apportionment for R&D use of the combined system.
Software the Company Has Built Itself
Software developed in-house is not itself a cost under the R&D rules. The cost of developing it appears under staffing, EPW, subcontractor, consumables (for any physical components), software, and cloud headings in the period of development.
Once developed, the software may itself be used as a tool in subsequent R&D activity. In that case, the ongoing cost of using it (staff time to maintain, cloud resources to run, licences for third-party dependencies) can still be claimed under the relevant categories in subsequent periods. The developed software itself has no separate cost line.
Where in-house software is capitalised as an intangible asset, the capitalised cost is outside the R&D tax credit rules. The underlying staff, EPW, and subcontractor costs are claimable in the period they were incurred, provided the R&D activity test is met.
Open Source and Freely Licensed Software
Open source software with no licence fee contributes nothing directly to the software cost category (there is nothing to claim). Support contracts for open source distributions (for example, a commercial Kubernetes support contract) are claimable with apportionment.
Contribution time to open source projects is not itself an R&D cost unless the contribution is directly part of resolving scientific or technological uncertainty in the claimant's own R&D programme. A contribution made to a public open source project purely for community engagement is outside the rules.
Accounting Treatment Interaction
The accounting treatment of software costs (opex versus capex versus intangible asset) does not determine the R&D tax treatment, but inconsistencies between the two can draw HMRC attention. A specialist adviser will align the R&D claim with the accounting presentation where possible, and document any divergences with a clear rationale.
SaaS Contract Types and Their R&D Treatment
Three common SaaS contract patterns and how they flow into the R&D claim:
Monthly rolling subscription. The cost is claimable in the month it is incurred, apportioned for R&D use. Simple and clean.
Annual subscription paid upfront. The cost is expensed across the subscription period and claimed accordingly. An annual licence paid in January for the 12 months ahead is claimed a twelfth at a time (or via prepayment accounting) across the period.
Multi-year enterprise deal. Costs are amortised over the contract term and claimed alongside the amortisation. A three-year deal paid upfront is claimed a third at a time, with the R&D apportionment applied each year based on that year's usage pattern.
Unused Licences and "Shelfware"
Licences paid for but not used ("shelfware") are generally claimable only to the extent of actual use in qualifying R&D activity. A company that over-purchased licences and never deployed them should not claim the unused portion.
This is rarely a major issue but is a common clean-up item in first-time claims. The licence register should be reconciled to actual deployment and use before the claim is finalised.
Specialist Simulation, Modelling, and Analysis Tools
Specialist scientific and engineering tools form a particular sub-category of software R&D cost. Examples include finite element analysis packages, computational fluid dynamics solvers, electronic design automation tools, chemistry modelling software, and statistical analysis platforms.
These tools are almost always used directly in qualifying R&D activity, and their cost is typically claimable in full or near-full after apportionment for R&D use. Licence fees can run to tens of thousands of pounds a year for top-tier engineering simulation tools, so the category deserves attention even in otherwise software-heavy claims.
Where a specialist tool is used on a per-project basis (for example, a simulation job executed for a specific R&D programme), project-level apportionment can be used: 100% for projects that are qualifying R&D, 0% for projects that are not.
API Subscriptions and Third-Party Services
Modern R&D programmes often depend on API-accessed services: cloud-based machine-learning APIs, geospatial data APIs, specialist analytics services. Where these services are used directly in qualifying R&D activity, their subscription cost is claimable on the same basis as licensed software.
The apportionment follows usage. A service used heavily in R&D experimentation and lightly in production operations has a high R&D apportionment; a service used primarily for customer-facing features has a low apportionment. API call logs or billing detail reports support the split.
Developer Productivity Tools
General developer productivity tools (issue trackers, wikis, documentation platforms, chat applications) support R&D activity indirectly. The apportionment follows the R&D-versus-non-R&D share of team use.
For an engineering-only team, apportionment tracks the team's R&D percentage. For a mixed team (engineering plus support, ops, product), apportionment follows the engineering share of seats or headcount, multiplied by the engineering team's R&D percentage.
Related Cost Categories
- Data and cloud costs — for hosted compute, storage, and data licences.
- Staffing costs — the largest category in most software claims.
- Eligible Expenses pillar guide.