An R and D tax credit guide is worth reading even if you think you do not qualify, because the definition is considerably broader than most founders assume.
The credit does not require laboratories or patents. It requires technical uncertainty and a systematic process of resolving it, which describes most software development.
This guide covers who qualifies, how the payroll offset lets pre-revenue companies benefit, what documentation is needed, and the nine things that matter most.
A federal credit against tax liability for qualified research expenses. Most states offer their own credit on top, with separate rules and separate claims.
Qualifying activity must meet a four-part test: a permitted purpose, technological in nature, elimination of uncertainty, and a process of experimentation. Software development frequently meets all four.
| Expense type | Qualifies? | Notes |
|---|---|---|
| US-based engineering salaries | Yes | Usually the largest component |
| Contractor development work | Partially | Typically 65% of cost |
| Cloud compute for development | Yes | If used in the research process |
| Supplies used in research | Yes | Must be consumed |
| Work performed outside the US | No | Excluded entirely |
| Routine maintenance and bug fixes | No | No technical uncertainty |
A credit against income tax is useless to a company with no taxable income. The payroll tax offset solves this, allowing qualifying small businesses to apply the credit against employer payroll taxes instead.
That turns the credit into cash for a pre-revenue company, which is why it matters disproportionately to early-stage startups.
Eligibility has conditions around gross receipts and company age. The IRS research credit guidance sets out the qualification tests in detail.
Contemporaneous records beat reconstruction every time, and the standard is higher than for ordinary startup tax deductions. The credit is examined regularly and claims supported by project documentation created at the time hold up far better than those assembled afterwards.
Startup tax deductions generally need receipts. This needs something more: evidence of what technical uncertainty existed and how it was systematically addressed.
Items one to three determine whether you qualify. The rest affect how much you get.
No laboratory required. Building software that solves a problem with no obvious solution, where you tried several approaches, typically meets the test. Most product engineering qualifies.
Bug fixes, routine updates, cosmetic changes and implementing a known solution all fail the uncertainty test. The distinction is whether the outcome was in doubt at the start.
Qualifying small businesses can apply the credit against employer payroll taxes rather than income tax, which turns it into cash rather than a carried-forward asset.
Development performed outside the United States is excluded entirely. For companies with distributed engineering teams this materially affects the qualifying wage base.
Qualifying contractor costs are typically included at 65% rather than in full, and the contract terms matter. Work where the contractor retains rights may not qualify at all.
Section 174 capitalization requires research expenses to be amortised rather than deducted immediately. This affects taxable income separately from the credit and caught many companies unprepared.
Many states offer their own credit and some are refundable, meaning cash regardless of liability. These are claimed separately and the qualification rules frequently differ from federal.
Project-level time records and technical documentation created during the work. An R and D tax credit guide that does not emphasise this is understating the examination risk.
The payroll offset election is made on a timely filed return. Missing the deadline can forfeit the ability to use the credit against payroll tax for that year entirely.
Series a funding accounting often surfaces unclaimed credits during diligence, which is a late and avoidable moment to discover them.
A Portland developer tools company had never considered the R and D credit, assuming it applied to hardware and pharmaceutical research rather than software.
A review of three years found qualifying engineering wages throughout, none of which had been treated as anything other than ordinary startup tax deductions. Two prior years were amended and the current year claimed with the payroll offset elected.
| Year | Qualifying wages | Federal credit | Form |
|---|---|---|---|
| Year 1, amended | $612,000 | $38,400 | Income tax credit |
| Year 2, amended | $847,000 | $52,100 | Income tax credit |
| Year 3, current | $1,140,000 | $71,300 | Payroll offset |
| Oregon state credit | – | $19,600 | State claim |
| Total identified | – | $181,400 | – |
| Cash received within 12 months | – | $90,900 | – |
Series a funding accounting picked the credit up at the next raise. The current year payroll offset produced $71,300 in cash across four quarters, which funded two engineering hires. The amended years created carried-forward credits usable once the company became profitable.
A federal credit against tax liability for qualified research expenses, with most states offering their own credit alongside. Qualifying activity must involve technical uncertainty resolved through a systematic process of experimentation.
Frequently yes. Building software where the technical approach was uncertain at the outset and several approaches were tested typically meets the four-part test. Routine maintenance and bug fixes do not.
Yes, through the payroll tax offset. Qualifying small businesses can apply the credit against employer payroll taxes rather than income tax, which turns it into cash rather than a carried-forward asset.
Section 174 capitalization requires research and experimental expenditure to be amortised over several years rather than deducted immediately. It affects taxable income separately from the credit and increased tax bills for many loss-making companies.
Project-level time tracking, technical documentation describing the uncertainty being resolved, design and test records showing experimentation, payroll records, and contractor agreements confirming US-based work.
Generally yes, by amending returns within the statute of limitations. The payroll offset election cannot be made retrospectively though, so amended years produce income tax credits rather than cash.
Most software companies qualify and many never claim. The barrier is almost always the assumption that the credit is for something else, which costs US startups a substantial amount every year.
Explore our fractional CFO services, read how to track expenses properly, or our diligence checklist. SaaS companies should see our SaaS accounting services.
Ask us whether your work qualifies.
Animesh Shah | Accounting Lead, Finkeepers
Chartered Accountant with 15+ years leading accounting delivery for US businesses across QuickBooks, NetSuite, Odoo and Sage. Research credit guidance referenced here is published by the IRS.
This article provides general guidance for educational purposes only. Credit eligibility, thresholds and state rules vary and change. Always consult a qualified CPA before claiming research credits. Last updated October 2026.
Built by experienced professionals, Finkeepers delivers reliable accounting services for startups and SMBs, powered by proven processes and modern software.