Key takeaway: SR&ED contract expenditures (what you pay an arm's-length contractor to do SR&ED work on your behalf) are only 80% eligible for the tax credit, a rule that's been in place since 2012. Pay a dev shop $150,000 to build a specific, uncertain piece of your product under contract, and roughly $120,000 of that enters your qualified expenditure pool. Not the full amount. Whether a payment even counts as a "contract payment" in the first place turns on the substance of the deal, not what the invoice calls it, and getting that call wrong is an easy way to overstate a claim without realizing it.
Founders who outsource engineering tend to assume the SR&ED math works the same whether the work was done by an employee or a contractor. It doesn't. The moment you pay someone outside your company to do SR&ED for you, a different set of rules kicks in, and those rules shave a fifth off the eligible amount while hinging on questions most contracts never answer explicitly.
Here's what actually determines whether a payment is a SR&ED contract expenditure, how the 80% figure applies, and where the CRA draws the line between a contractor doing SR&ED "on your behalf" and one who's just supplying labour to your own project.
One thing this rule doesn't decide: whether the underlying work qualifies as SR&ED at all. That's a separate question, governed by the CRA's own two-part eligibility test for advancement and uncertainty. Contract-payment treatment only decides how much of an already-eligible spend counts toward your credit, not whether the work clears the bar in the first place. Get the eligibility call wrong and the 80% question never comes up.
What counts as a SR&ED contract expenditure
A SR&ED contract expenditure is a payment you make to an arm's-length party (the CRA calls them a "taxable supplier") to perform SR&ED for you or on your behalf. The Assistance and Contract Payments Policy defines a contract payment fairly narrowly: an amount paid to a claimant, by someone dealing at arm's length with them, specifically for SR&ED performed for or on behalf of that payer.
Two words are doing most of the work in that definition. "Arm's length" rules out paying your own subsidiary or a related party under this specific provision; those payments follow a different, more complicated set of rules covered elsewhere in the same policy. And "on behalf of" is the part that trips people up, because it's not about who signs the invoice. It's about whether the contractor was carrying out SR&ED because your contract required them to, as opposed to simply being labour you directed as part of your own project.
That distinction matters because of what happens next: contract SR&ED and third-party payments have been 80% eligible for Investment Tax Credits since 2012, per the CRA's own summary of the 2012 federal budget changes to the program. Run $150,000 through that math and roughly $120,000 lands in your qualified SR&ED expenditure pool, the base your investment tax credit is calculated against. The other $30,000 simply isn't part of the claim.
How the CRA decides if a payment is really a contract payment
The CRA doesn't take a contract's label at face value. A document that says "consulting services" or "contract payment" isn't conclusive either way, and the agency will look past the wording to what the arrangement actually does. There's no single test that settles it. Instead, the policy lays out four questions, and no one of them decides the case alone.
- Did the contract require specific SR&ED work? Language like "the contractor shall design, integrate, test, and verify performance" points toward a contract payment. The question isn't whether SR&ED happened. It's whether the contract is what made it happen.
- Who carried the cost risk? A ceiling price that caps what you'll pay, with the contractor on the hook for anything above it, suggests the contractor was working at their own risk rather than performing SR&ED on your behalf. If the contractor gets paid regardless of whether the work meets spec, that risk sits with you instead, and that cuts the other way.
- Who owns the resulting IP? If the contractor keeps the intellectual property from the work, that's a signal the SR&ED wasn't being done for you specifically. IP staying with your company points the other direction. (Crown contracts are a documented exception: federal policy generally leaves IP with the contractor regardless.)
- Is it a contract for services or a contract for goods? A services contract leans toward SR&ED performed on your behalf. A contract to simply buy a finished good doesn't rule it out, but it's a weaker signal.
None of these four questions is a checkbox. The CRA weighs them together against the actual facts of the arrangement. A contract clearly drafted with SR&ED credits in mind, but one that doesn't reflect how the work really happened, won't hold up on its own wording.
Why the label on the invoice isn't the last word
A contract written for scope and price, with no thought given to how the CRA reads it, can leave real SR&ED spend stranded in a grey zone. A vague statement of work, a fixed monthly retainer with no deliverable tied to specific research, or IP terms nobody thought through at signing can all leave the same dollar amount uncertain: maybe a contract payment at 80%, maybe something else entirely, maybe not eligible at all if the arrangement doesn't establish that SR&ED was performed on your behalf.
Founders who write their own contractor agreements, understandably, optimize for scope and price. The four factors above rarely make it into that conversation. By the time someone reviews the contract for SR&ED purposes, often at filing time over a year later, the paper trail either supports the claim or it doesn't. There's no going back to renegotiate wording retroactively.
A few patterns show up often enough to be worth naming directly.
- The fixed monthly retainer with no defined deliverable. Paying a dev shop $15,000 a month "for engineering support" doesn't say what SR&ED work the money bought, or that the contractor was required to do it. That's a weak fact pattern under the first factor above, even if genuinely uncertain work happened under the retainer.
- Time-and-materials billing detached from a research question. An hourly invoice that reads "development, 40 hours" tells you nothing about whether the hours went toward resolving a specific technical uncertainty or toward routine build work. The contract payment analysis needs the SOW and the invoice to point at the same uncertain problem.
- A contractor who's really embedded staff. Someone who works inside your team, on your tools, taking direction day to day like an employee would, looks less like "SR&ED performed on your behalf under contract" and more like labour supplied to your own project. That shifts the analysis back to the four factors rather than defaulting to contract-payment treatment.
None of these patterns is automatically disqualifying. They're just the shape of the arrangements that end up ambiguous, and ambiguous is exactly what you don't want sitting in a claim eighteen months after the work happened.
The anti-avoidance rule for routed payments
An arrangement designed to dodge the contract-payment label doesn't get to keep the workaround. Subsection 127(25) of the Income Tax Act deems a payment to still be a contract payment when a claimant and an arm's-length party set up a structure where the money flows through an intermediary (paid to one party, received by another who isn't itself a taxable supplier), and avoiding contract-payment treatment is one of the main purposes of the arrangement.
In plain terms: routing a payment through an extra entity to change its tax character doesn't work if that's what the structure is for. It's a narrow provision, but it matters if your corporate structure involves more than one entity paying for development work: a holding company and an operating company, say, or a services arm.
What happens on the other side, if you're the contractor
If your company is the one getting paid to do SR&ED for a client, the contract payment reduces your own pool of deductible SR&ED expenditures. The CRA is explicit that receiving a contract payment shrinks what you can separately claim, so the same work doesn't generate two ITC claims. That reduction happens project by project, and any amount that doesn't get applied in the year it's received carries forward to reduce the pool in a later year.
For SR&ED-heavy dev shops and agencies, that means a contract payment isn't a free pass to also file your own SR&ED claim on the identical work. Whoever the credit belongs to, payer or performer, depends on the same four-factor analysis above, and the answer isn't always obvious from either side of the table.
Where this sits next to the SR&ED grind rule
Contract expenditures and the SR&ED grind rule both live on the same CRA policy page, and both end with a smaller qualified expenditure pool than you started with, but for different reasons. The grind rule cuts your pool because a provincial credit counts as government assistance. The contract-payment rule cuts it because part of what you paid a contractor is treated as their profit margin rather than SR&ED spend, full stop, regardless of what any province is doing.
Run both in the same year: a company claiming an Ontario credit that also outsourced part of its build to a contractor sees the reductions stack. 80% of the contract payment enters the pool, then the provincial grind applies on top of what's left. Neither rule waives the other. Both are covered, alongside the rest of what changed under Budget 2025, in the full SR&ED guide.
A worked example, kept illustrative
Say a seed-stage startup pays an arm's-length firm $200,000 under a fixed-scope contract to build a specific piece of infrastructure involving genuine technical uncertainty, not routine integration work but something nobody on either team was sure would work. The statement of work spells out exactly what has to be delivered, there's a ceiling price the contractor can't exceed, and the resulting code and IP transfer to the startup on delivery.
That fact pattern reads like a contract payment: specific required work, cost risk on the contractor, IP flowing to the payer. At 80%, $160,000 of the $200,000 becomes a qualified SR&ED expenditure. The remaining $40,000 isn't eligible, no matter how the invoice was worded. This is illustrative math to show the mechanism. Your own contract's language and facts are what actually decide the treatment, not this example.
Now change one variable. Same $200,000, same startup, but the contractor bills hourly against an open-ended "product development support" agreement, gets paid regardless of outcome, and the startup's own engineers direct the work week to week. That fact pattern is weaker on every factor: no specific required SR&ED work named in the contract, no cost risk on the contractor, no clean signal that the work was performed "on behalf of" the payer rather than alongside them. The same $200,000 might still relate to genuine SR&ED, but whether it belongs in the claim as a contract expenditure, or needs a different treatment entirely, is exactly the kind of call that shouldn't be made by guessing.
What this means for how you write the contract
Write the contract like you'll need it to survive a CRA review in eighteen months, because you will. A statement of work that names the specific technical objective and its uncertainty, a price structure that puts real risk on the contractor, and IP terms that route the output to you are the same three things that make a contract payment easy to defend and a weak one easy to challenge. None of this is a reason to avoid contractors. It's a reason to have the SOW reflect the work as carefully as the invoice reflects the price.
This is also exactly the kind of judgment call worth a second set of eyes before you file. The line between "contractor doing SR&ED on your behalf" and "contractor supplying labour to your own project" isn't always obvious from the paperwork alone, and getting it wrong in either direction either understates a real claim or overstates one you can't defend.
That's the gap Glauq is built to close. The evidence (contracts, deliverables, the technical story behind the work) gets captured continuously as your team builds, instead of reconstructed from memory when the deadline is close. Then a qualified, independent SR&ED expert reviews the claim, including calls like this one, before anything goes to the CRA. Automation handles the capture; a named person takes accountability for the judgment. And the fee is flat, so a contractor-heavy year with more paperwork to sort through doesn't come with a bigger bill.
Frequently asked questions
Is a SR&ED contract payment the same as hiring a contractor? Not automatically. Hiring an individual contractor who works as part of your team, under your day-to-day direction, is generally treated differently from paying an arm's-length business to perform a defined piece of SR&ED on your behalf under contract. The CRA's Assistance and Contract Payments Policy applies its specific "contract payment" definition and the 80% treatment to the latter, based on the four factors above, not to every arrangement that involves an outside contractor.
Why is it 80% and not 100%? The CRA's summary of the 2012 federal budget changes states plainly that contract SR&ED and third-party payments are 80% eligible for Investment Tax Credits, a rule that's been in effect since 2012. The policy doesn't spell out a rationale in that summary. The effect is that a portion of a contract payment is treated as the contractor's margin rather than SR&ED expenditure, and only the remainder enters your qualified pool.
Does the 80% rule apply to payments to a related company? No, not under this provision. The contract-payment definition specifically requires the payment to be between parties dealing at arm's length. Payments to a non-arm's-length party, like your own subsidiary, are governed by a different set of allocation rules in the same policy, and they're complex enough that they're worth getting expert eyes on rather than assuming the 80% figure applies.
Can the CRA decide a payment isn't a contract payment even if the contract calls it one? Yes. The label in the contract isn't conclusive. The CRA looks at whether the substance of the arrangement matches the four factors (required SR&ED work, who bears cost risk, IP ownership, and services versus goods), and can reach a different conclusion than what the contract's wording states if the facts don't support it.
Does this rule apply on top of the SR&ED grind rule? Yes, and they stack. If you're outsourcing part of your SR&ED to an arm's-length contractor and also claiming a provincial credit, the 80% contract-payment reduction and the provincial grind both reduce your qualified expenditure base, at different points in the calculation. Neither one offsets the other.
Where do I find the exact worked-example math for my situation? This post covers the eligibility rule and the 80% treatment; the CRA maintains a separate, more detailed Contract Expenditures for SR&ED Performed on Behalf of a Claimant Policy for the fuller mechanics of specific fact patterns. If your arrangement involves mixed labour and contracted deliverables, non-arm's-length parties, or multi-year contracts, that's a good moment to bring in someone who reviews SR&ED claims for a living rather than working it out from a blog post.
The 80% figure is simple. Knowing whether your contract even qualifies as a contract payment in the first place is the part that takes judgment, and it's worth getting right before the deadline, not after.
See what your claim could be worth — estimate your refund or check your eligibility.