If you’re running a Canadian software startup with five or more developers, there’s a government program that has almost certainly been paying you back a portion of your engineering payroll. And you haven’t claimed it.
SR&ED (Scientific Research and Experimental Development) is Canada’s largest federal business tax incentive. In fiscal 2024-25, 22,758 companies filed claims and received $4.5 billion in approved investment tax credits. Software development represented 40.8% of all allowed credits. The largest single field. That’s roughly $1.8 billion going back to companies doing the kind of work most startups do every day.
64% of SR&ED claims come from companies with under $4M in revenue. This isn’t a program for mature enterprises with dedicated R&D labs. It’s designed for exactly the kind of exploratory, uncertain, sometimes-it-works-sometimes-it-doesn’t engineering that defines early-stage software development.
Here’s what you need to know to start capturing it.
What SR&ED Is (Without the Government Jargon)
SR&ED is a tax credit for work involving genuine technological uncertainty, systematic investigation, and the pursuit of technological advancement. For Canadian-controlled private corporations (CCPCs) under a certain revenue threshold, a large portion of the credit is refundable. You get a check even if you have no taxable income.
Think of it as the government sharing the cost of your R&D risk. When your team spends months figuring out a distributed systems problem that no documented solution could solve, or builds a novel ML architecture because existing approaches failed for your use case, that’s the kind of work SR&ED was designed to support.
It’s not a grant, a loan, or a subsidy. It’s a return of a percentage of what you already spent on qualifying work. You don’t apply in advance. You claim it when you file your corporate tax return, covering work your team did in the prior fiscal year.
The primary filing document is the T661 form, which requires written technical narratives for each qualifying project plus a detailed expenditure calculation. That’s the part most startups find difficult.
Does Your Startup Qualify? Five Questions
SR&ED eligibility isn’t binary. You don’t qualify as a company. Specific projects or activities qualify based on whether they meet CRA’s three-part test: technological uncertainty, systematic investigation, and pursuit of technological advancement.
These five questions help identify whether qualifying work is happening.
1. Has your team faced problems where no known solution existed?
Not “we didn’t know how to do it.” The test is whether a skilled practitioner applying existing public knowledge could have determined the answer. If your engineers were working at the edge of what’s documented, and the outcome wasn’t predictable from existing techniques, that’s technological uncertainty. Novel algorithms, new data architectures, ML approaches addressing limitations in existing methods, system-level interaction effects requiring original investigation. You’ve probably had qualifying work.
2. Did your team test hypotheses and document the results?
SR&ED requires systematic investigation: formulate an approach, test it, observe results, draw conclusions, adjust. Formal lab notebooks aren’t necessary. But the work must be structured. Git commit histories, pull request descriptions, design documents, sprint notes that capture the investigative process are all legitimate evidence. Teams that ship fast and clean up documentation later risk losing this record.
3. Did you generate new technical knowledge, even from failed attempts?
You don’t need to have succeeded. Learning that an approach won’t work under specific conditions is technological advancement in CRA’s definition. Months spent on an architecture you ultimately scrapped may still qualify if the investigation was systematic and the result advanced your team’s understanding beyond what was publicly known.
4. Is your company a Canadian-controlled private corporation (CCPC)?
The most favorable SR&ED rates apply to CCPCs under specific revenue and taxable capital thresholds. If your startup is incorporated in Canada, majority-owned by Canadian residents, and not publicly listed, you almost certainly qualify as a CCPC. Foreign-controlled companies and public corporations can still claim SR&ED, but at lower rates and without the refundable portion.
5. Did you spend money on the work?
SR&ED credits are calculated on qualifying expenditures: wages paid to employees doing eligible work, materials consumed in the investigation, and third-party contracts for SR&ED performed on your behalf. The credit is a percentage of those expenditures. If no one got paid to do the work, there’s no expenditure base to claim against.
If you answered yes to most of these, you have qualifying work in your history.
How Much Could You Get?
The federal investment tax credit (ITC) rate for CCPCs with prior-year taxable income under $800,000 and taxable capital under $10 million is 35% on the first $3 million of eligible expenditures. That portion is fully refundable. You receive it as a check regardless of your tax position.
For eligible expenditures above $3 million, or for CCPCs exceeding the taxable capital limit, the federal rate drops to 15%, non-refundable. It offsets taxes owed but isn’t paid out directly.
Most provinces add their own layer. Ontario provides a 3.5% refundable Ontario Innovation Tax Credit (OITC) and an 8% Ontario Research and Development Tax Credit (ORDTC). Quebec’s rates are among the highest in the country. The combined federal-provincial benefit for an early-stage CCPC in Ontario typically lands between 40-50 cents recovered per dollar of eligible expenditure.
What does that look like in practice? A startup with $800,000 in SR&ED-eligible wages (roughly five to eight developers with meaningful qualifying time):
- Federal ITC (35% refundable): $280,000
- Ontario OITC (3.5% refundable): $28,000
- Ontario ORDTC (8% non-refundable): $64,000
That’s roughly $308,000 in cash returned, plus $64,000 in non-refundable credits against future tax. The exact calculation depends on your overhead method, subcontractor inclusion, and provincial rules.
When to Start
Immediately. Not because of a deadline trick. Because of how the program works.
SR&ED documentation is most defensible when it’s created as work happens. CRA views contemporaneous records as the strongest evidence of qualifying work. Git logs, pull requests, sprint notes, test results, design documents created during the investigation. Documentation assembled at filing time from memory is weaker and more vulnerable in an audit.
More practically, qualifying work that wasn’t flagged as it happened is often simply lost. Engineers don’t remember the failed approach they abandoned in April when you’re reconstructing the claim in November. The architecture discussion documenting the uncertain problem in March is buried in an archived Slack thread. The time your senior engineer spent investigating a race condition requiring novel analysis? Gone, unless someone captured it at the time.
Every month you wait is a month of qualifying work that probably won’t make it into your claim. Over a full fiscal year, that gap typically amounts to tens of thousands of dollars in uncaptured credits.
There’s also a hard deadline. The SR&ED filing deadline is 12 months after your corporate tax return due date for the year in which eligible expenditures were incurred. For most Canadian corporations, that’s 18 months from fiscal year-end. Miss it and CRA cannot extend it by law. The entire year’s claim is disallowed with no appeal mechanism.
The Startup-Specific Mistake: Waiting Until You’re “Bigger”
This is the most expensive decision startup founders make about SR&ED. The thinking goes: we’ll figure out R&D credits once we’re more organized, once we have a proper accounting team, once we have a VP Finance.
The problem: SR&ED credits accrue to past fiscal years. Every year you delay is a year of qualifying expenditures that can’t be recovered retroactively once the deadline passes. If your startup has been building technically uncertain software for three years and hasn’t filed, the first two years are probably gone.
The other dimension: the refundable credit matters most when you’re pre-revenue or pre-profit. Once your company reaches meaningful profitability, the non-refundable portion grows as a share of your total credit. The years when SR&ED cash has the highest impact are the early years, when every dollar returned extends runway.
Companies that start claiming SR&ED in year one or two often recover enough to fund an additional hire, extend runway by several months, or hit the next milestone before needing to raise again. That has a compounding effect on dilution and valuation that’s hard to quantify but very real.
How to Claim Without Disrupting Your Engineering Team
The standard process requires your engineers to write technical narratives for each qualifying project. Those narratives must describe the technological uncertainty, document the systematic investigation, and explain the advancement achieved. CRA has word limits and specific language requirements. Most engineers aren’t trained to write this way, don’t want to, and shouldn’t be pulled off product work to do it.
The traditional approach: at year-end, a consultant interviews your engineers, reconstructs the qualifying work from memory and whatever documentation exists, writes the narratives, and charges a percentage of the claim (typically 15-25%). A $300,000 claim generates a $45,000-$75,000 consulting fee. The quality of the narratives is limited by how much your team remembers.
There’s an alternative. If you capture qualifying work continuously using your existing development tools, the narratives can be built from the actual record of the investigation rather than reconstructed from memory. Engineering time cost is near zero because the evidence is already being created in the normal course of work. You just need a system that captures it in a CRA-ready format.
For the mechanics of what you’ll actually file, the T661 form guide covers every section, including how to write the technical narratives that determine whether your claim survives review.
Starting Your First Claim: The Practical Checklist
If you’re claiming SR&ED for the first time, here’s what you need.
Identify qualifying projects. Review your engineering work for the fiscal year and identify projects involving genuine technological uncertainty and systematic investigation. What problems did your team face where the solution wasn’t known? What did you have to figure out through original investigation?
Quantify eligible expenditures. Pull payroll data for engineers who worked on qualifying projects. Estimate the percentage of their time on qualifying work. That’s your wage expenditure base. Add materials consumed in the research (rare for software companies), subcontractor costs for SR&ED work, and apply overhead (proxy method: 55% of wage base; traditional method: itemized allocation).
Write the technical narratives. For each qualifying project, you need three descriptions matching CRA’s T661 Part 2 format: the technological uncertainty at the project’s start, the systematic investigation performed, and the advancement achieved. These require technical precision and CRA-specific framing. The T661 guide covers what each section must contain.
File with your corporate tax return. The T661 and T2SCH31 must both be filed by the SR&ED deadline for the relevant fiscal year. Both forms are required. Filing only one forfeits part of the benefit.
Start capturing for next year immediately. The most valuable thing you can do after filing your first claim is put a system in place so the second claim is easier and more complete.
The Number Worth Knowing
Software development represents 40.8% of all SR&ED credits approved by CRA. The program exists to fund exactly the kind of technically uncertain, systematically investigated work that defines how good software companies build product. If your team is shipping non-trivial software, the question isn’t whether SR&ED applies. The question is how much of your qualifying work you’re actually capturing.
Ready to stop leaving money on the table? Talk to our team about automating your SR&ED documentation.