Canada's Scientific Research and Experimental Development program is one of the most generous research-and-development incentives in the world, and one of the most misunderstood, particularly where outsourced or contracted development is involved. Companies routinely leave money on the table by assuming outsourced work cannot qualify, and others put a claim at risk by assuming all of it does. The truth sits in between, and it is worth getting right.
This is general information for technology and finance leaders, not tax advice. SR&ED claims turn on specific facts and any company making one should work with a qualified adviser and the Canada Revenue Agency's own guidance.
What SR&ED actually rewards
SR&ED is a federal tax incentive administered by the Canada Revenue Agency. It offers a general non-refundable investment tax credit of fifteen per cent on qualifying expenditures, and an enhanced, fully refundable credit of thirty-five per cent for Canadian-controlled private corporations on qualifying spend up to an annual expenditure limit, per the Canada Revenue Agency. That expenditure limit was raised substantially in recent federal changes, increasing the amount of R&D spend eligible for the enhanced refundable rate for CCPCs. Provincial credits stack on top of the federal ones.
The refundable part is what makes the program powerful for a private company. A qualifying CCPC can receive cash back on eligible R&D even before it is profitable, which for a growing technology company is a materially different thing from a credit it can only use against future tax.
The test that decides eligibility
The eligibility question is not whether the work was hard, novel to the company, or expensive. It is whether the work sought to resolve a technological uncertainty through a systematic investigation, where the outcome was not knowable in advance by a competent professional applying standard practice.
In software terms, routine development does not qualify no matter how much effort it took. Configuring known technology, integrating documented APIs, and building features whose implementation path is clear are excluded. What can qualify is work where the team faced a genuine technological obstacle, could not solve it with established methods, and worked through it experimentally: novel algorithm development, performance or scalability problems with no known solution, and engineering under constraints where standard approaches demonstrably failed. The claim rests on the uncertainty and the systematic effort to resolve it, documented as it happened.
How outsourced and contractor work is treated
This is where outsourced development is misunderstood in both directions. Work performed by a contractor can qualify for SR&ED, but the rules for contract expenditures are specific and they differ from the treatment of employee salaries. Amounts paid to a Canadian contractor for eligible SR&ED work performed in Canada can be claimable, subject to the program's rules on arm's-length payments and the applicable proportions, and the underlying work still has to meet the same uncertainty test.
Two conditions do most of the work in practice. The eligible activity generally has to be performed in Canada to count toward the credit, which means where the development physically happens matters to the claim. And the arrangement has to be documented well enough to show what was done, by whom, and against which technological uncertainty, because a contract line that says software development proves nothing to a reviewer.
Structuring an engagement so the claim survives
The failures that sink SR&ED claims on outsourced work are almost always documentation failures, not eligibility failures. The work qualified; the company just could not prove it after the fact. A few structural choices prevent that.
Contract in Canada, deliver in Canada. For the outsourced portion to feed the credit, the eligible work generally needs to be performed in Canada. A Canadian delivery arm gives the claim a clean footing that offshore development does not.
Capture the uncertainty in real time. The provider should record what technological obstacle was being addressed, what approaches were tried, and what was learned, as the work happens. A reviewer wants a contemporaneous trail, not a reconstruction built at claim time.
Separate experimental work from routine work. Not everything a development team does qualifies. An engagement that tracks eligible investigation distinctly from routine build makes the claim defensible and stops the routine work from contaminating it.
Keep the paperwork a reviewer expects. Time records against activities, technical documentation, and a clear statement of the uncertainty and the systematic approach are what turn a plausible claim into a supportable one.
Provincial credits stack on the federal one
The federal credit is only part of the picture. Most provinces offer their own research-and-development tax incentives that stack on top of the federal SR&ED credit, which raises the effective rate of support well above the federal figure alone for work performed in that province. The combined federal-provincial rate, and the rules for how the two interact, vary by province, so the total value of an eligible dollar of R&D depends on where in Canada the work is done.
For a buyer structuring outsourced development, this reinforces the same conclusion the eligibility rules point to. Keeping the work in Canada is not only what preserves the federal credit, it is what unlocks the provincial one, and the two together are what make the after-credit cost of Canadian development competitive with locations that look cheaper on the rate card but leave the incentives on the table. A qualified adviser can model the combined rate for the specific province and corporate structure involved.
Where a Canadian delivery partner helps
An outsourced development arrangement delivered in Canada, by a provider that understands what SR&ED review requires and documents the work accordingly, can preserve eligibility that offshore delivery would forfeit, while still capturing the cost advantage of outsourcing. Corpshore Canada delivers IT outsourcing and software engineering from Canadian operations under Toronto governance, with reported IT cost reductions of thirty-five to fifty-five per cent, and the point relevant here is narrower than the cost: Canadian delivery keeps the R&D on Canadian soil, where the credit can reach it, and disciplined documentation keeps the claim standing when a reviewer asks. The generosity of SR&ED is real. Capturing it on outsourced work is a structuring problem, and it is a solvable one.