Capture 35% Refundable SR&ED for Canadian SaaS With a One Hour Audit

Most Canadian SaaS engineering work qualifies for SR&ED when it meets the Canada Revenue Agency’s three-part test: technological uncertainty, systematic investigation, and advancement of knowledge. If your team has wrestled with scaling problems, tuned algorithms, or run real experiments to solve a technical unknown, you likely have a claim. The first move: pull one engineer and one finance lead into a room for an hour and audit the last two fiscal quarters against that test.

TL;DR:

Genuine technical unknowns during scaling, algorithm tuning, or data experiments qualify, but routine code refactoring or API integration do not.

Accurate documentation must include hypotheses, test results, and technological advancements recorded contemporaneously in tickets, PR notes, or experiment logs.

The most common mistake is relying on vague retrospective narratives rather than detailed, ongoing evidence capturing within the engineering process.

Eligible costs are limited to salaries for work involving uncertainty, subcontractor fees, consumed materials, and capital expenditures, with rates depending on corporate structure.

A claim requires compliant forms, thorough internal review, and at least six years of organized records to withstand CRA audits and potential reviews.

What Is SR&ED for SaaS Companies, and What Does It Actually Pay For?
What Qualifies for SR&ED in SaaS? The Three-Part CRA Test Explained
How Much Can You Claim? Eligible Costs and Credit Calculations
How Do You Document SR&ED Work as You Go?
What Forms Do You Need to File an SR&ED Claim?
What Tools Help You Capture SR&ED Evidence Without Extra Process?
DIY, Software, or a Consultant: Which Path Fits Your Claim?
Can You Combine SR&ED With Other SaaS Funding Programs?
Does a Change in Ownership or Structure Affect Your SR&ED Claim?
What Do Real SR&ED Claims Look Like for Canadian SaaS Companies?
How Long Should You Keep SR&ED Records After Filing?
What Founders Consistently Get Wrong About SR&ED
Where This Guidance Comes From
Sources

What Is SR&ED for SaaS Companies, and What Does It Actually Pay For?

The CRA runs SR&ED tax incentives as Canada’s largest federal program for funding business research and development, and software companies are eligible claimants just like manufacturers or biotech firms. The program works through two mechanisms: an income tax deduction against eligible expenditures, and an investment tax credit (ITC) that can be refundable cash, a credit against tax owed, or both, depending on your corporate structure.

Here’s the mechanic that matters most for early-stage founders. A Canadian-controlled private corporation (CCPC) gets access to a refundable ITC, meaning the CRA can send you a check even if you owe no tax that year. That’s a meaningfully different outcome than a straight deduction, which only reduces taxable income you might not have yet as a pre-revenue or early-revenue startup.

Software development represents a significant share of approved SR&ED credits nationally, according to practitioner analysis of CRA claim data. That’s not a coincidence. SaaS companies constantly hit technical walls, scaling bottlenecks, data consistency problems, latency constraints, that force genuine experimentation rather than routine implementation.

Provincial credits stack on top of the federal ITC, and the combined rate varies meaningfully by province. Ontario, British Columbia, and Quebec each run their own R&D credit programs with different rates and eligibility rules, so your total refundable percentage depends on where your company is incorporated and operates, not just your CCPC status. An SR&ED guide for SaaS founders breaks down how these layers interact for a typical early-stage company.

What Qualifies for SR&ED in SaaS? The Three-Part CRA Test Explained

The CRA doesn’t care whether your code shipped. It cares whether you faced a genuine technical unknown and investigated it systematically. Three conditions have to be present together.

Technological uncertainty means you couldn’t have known the outcome in advance using standard engineering knowledge available in the field. Systematic investigation means you formed a hypothesis, tested it, measured results, and iterated, not just tried something once and moved on. Advancement of knowledge means the work generated new technical understanding for your team, even if the experiment failed or the feature never launched.

Work that typically clears this bar:

Scaling a system past a threshold where standard architecture patterns break down and you have to engineer a novel solution
Tuning a matching, recommendation, or scoring algorithm where the “right” approach isn’t documented anywhere
Running machine learning experiments to test whether a model architecture can hit an accuracy or latency target
Designing a caching or data partitioning strategy for a workload that doesn’t fit off-the-shelf solutions
Evolving a database schema under real production constraints, like zero-downtime migrations at scale

Work that typically does not qualify: routine UI styling, wiring up a standard third-party API using its documented integration path, or refactoring code for readability without solving a technical unknown. Practitioner guidance on SaaS eligibility is consistent on this point: familiar engineering executed competently is not the same as research.

The framing trick that trips up most founders: don’t describe what you built. Describe what you didn’t know going in, and how you found out. A narrative that says “we built a caching layer” tells the CRA nothing. A narrative that says “we hypothesized that a write-through cache would reduce latency below 50ms under peak load, tested three eviction strategies, and found none met the target without a custom hybrid approach” is a claim.

Pro Tip: Audit work labeled “debugging,” “optimization,” or “performance tuning” first. Founders routinely miss SR&ED value hiding in tickets that never got tagged as R&D because nobody thought scaling work counted.

How Much Can You Claim? Eligible Costs and Credit Calculations

SR&ED reimburses specific cost categories, not your entire engineering budget. The core buckets are salaries and wages for employees doing eligible work, subcontractor costs (capped at 80% of the contract value when the subcontractor isn’t at arm’s length in certain structures), materials consumed or transformed during the R&D, and a limited allowance for capital-type expenditures.

Most SaaS startups use the proxy method because it’s simpler and their overhead (cloud hosting, office costs, tools) is hard to cleanly allocate per project.

Federal rates depend on corporate structure:

Corporate Structure	Federal ITC Rate	Refundable?
CCPC, expenditures up to $3 million	35%	Fully refundable
CCPC, expenditures above $3 million	15%	Non-refundable (credit only)
Non-CCPC (public or foreign-controlled)	15%	Non-refundable (credit only)

A quick example: a CCPC with $300,000 in eligible salaries applies the 55% proxy uplift, bringing the base to $465,000. At the 35% federal rate, that’s a $162,750 refundable federal credit before any provincial top-up. Add a provincial credit, and the combined recovery can run meaningfully higher depending on your province, since provincial rates and rules vary enough to change the total by tens of thousands of dollars on a claim this size.

The most common calculation error: claiming salary for time an engineer spent on eligible work when they also spent half their week on unrelated maintenance, without a defensible time allocation. The CRA expects a reasonable, documented split, not a guess made at filing time.

How Do You Document SR&ED Work as You Go?

Form T661’s Part 2 requires three narrative fields: the technological uncertainty you faced, the work you performed to overcome it, and the technological advancements achieved. The T4088 guide to Form T661 is explicit that concise, contemporaneous notes beat long retrospective essays written months later.

The problem is that most engineering teams don’t naturally produce evidence in this shape. Here’s a workflow that does, without adding real overhead:

Tag hypotheses at ticket creation. Require a one-line “what we think will happen and why we’re not sure” note on any ticket that involves genuine technical uncertainty.
Keep a README on prototype branches. When engineers spin up an experimental branch, a short README documenting the question being tested becomes direct evidence later.
Record outcomes in pull request notes. A PR template field for “what we measured and what it showed” turns routine code review into SR&ED documentation for free.
Log test and benchmark results. Screenshots or exported metrics from load tests, A/B experiments, or model evaluation runs are some of the strongest evidence in a CRA audit.
Map time to project codes monthly, not annually, so payroll allocation stays defensible instead of reconstructed from memory.

To run a quick audit of the last quarter, pull every closed ticket tagged “bug,” “performance,” or “investigation,” and ask whether each one involved a real technical unknown. Flag the ones that do, then match them to git commits, PRs, and time logs.

Retain everything for at least six years past the relevant tax year, and keep it indexed by project rather than buried in a general engineering wiki, so you can respond to a CRA review request within days, not weeks.

Pro Tip: Set a recurring calendar reminder each sprint to tag SR&ED evidence while it’s fresh. Founders who reconstruct narratives at filing time consistently under-claim, because nobody remembers the failed approach that got dropped three months earlier.

What Forms Do You Need to File an SR&ED Claim?

Three forms work together. Form T661 carries your technical narratives and expenditure calculations. Form T2 is your corporate income tax return, which the SR&ED claim attaches to. Schedule T2SCH31 calculates your federal investment tax credit based on the figures from T661.

The filing deadline is strict: claims must be filed within a set period after your fiscal year-end as specified by the CRA deadline details. Miss it, and the claim is gone permanently, no extensions, no exceptions. Most practitioners recommend filing SR&ED alongside your regular tax return rather than waiting until the deadline approaches.

Before you submit, run this checklist:

Have an engineer and a finance person independently review the technical narratives for accuracy and consistency
Build an evidence index that maps each claimed project to specific tickets, commits, and test results
Sanity-check your salary allocation percentages against actual time logs, not estimates
Confirm your proxy or traditional overhead calculation matches the method declared on the form
Verify subcontractor costs are capped correctly if the 80% rule applies

What Tools Help You Capture SR&ED Evidence Without Extra Process?

You don’t need a dedicated SR&ED platform to build a strong claim, but you do need your existing tools working for you. Issue trackers, version control systems, CI pipelines, and time-tracking software already generate most of the raw evidence; the trick is capturing it consistently rather than reconstructing it later.

Tag SR&ED-relevant tickets at creation with a one-line hypothesis field
Attach experiment results directly to pull requests instead of a separate document
Export CI test and benchmark logs into a dated folder per project, not just console output
Use time-tracking categories that map directly to SR&ED project codes

Dedicated SR&ED software or a consultant earns its cost once claim complexity or audit risk rises past what a DIY spreadsheet can handle.

DIY, Software, or a Consultant: Which Path Fits Your Claim?

Your decision hinges on four factors: how complex your technical narratives are, how often you file, how much audit exposure you’re carrying, and how much internal bandwidth your team actually has.

DIY works for simple, single-project claims with a founder who has time to learn the T661 format.
SR&ED software fits teams that want structured evidence capture but don’t need hands-on tax strategy.
A consultant or fractional CFO fits companies with multiple concurrent projects, prior audit history, or a founder who’d rather spend that time building product.

When evaluating outside help, check for direct SaaS claim experience, a track record supporting clients through CRA reviews, and documented outcomes, not just promises. AidVenture’s fractional CFO services are built around exactly this kind of hands-on support, pairing SR&ED claim preparation with the broader financial planning founders need once the credit lands.

Can You Combine SR&ED With Other SaaS Funding Programs?

SR&ED isn’t exclusive. Most Canadian SaaS founders stack it with other funding sources, and doing so correctly requires understanding how each program treats government assistance.

If you receive a grant, a repayable contribution, or funding from a program like the Industrial Research Assistance Program (IRAP), that assistance typically reduces your SR&ED-eligible expenditure base dollar for dollar. The CRA treats government assistance as an offset against the costs you’re claiming, so you can’t claim the full salary cost through SR&ED and also claim it as fully grant-funded. Your accountant needs to know about every grant, loan, or credit your company receives before the SR&ED calculation is finalized, not after.

That said, combining is usually still worth it. A company might use IRAP funding to cover a portion of a project’s cost, then claim SR&ED on the remaining eligible expenditure, netting more total support than either program alone. Venture capital and angel investment don’t reduce your SR&ED base the same way, since equity investment isn’t government assistance.

The practical takeaway: map every funding source your company touches against your SR&ED expenditures before filing, and factor expected recoveries into near-term financial planning rather than treating the credit as a surprise windfall.

Does a Change in Ownership or Structure Affect Your SR&ED Claim?

Yes, and this catches founders off guard during fundraising or acquisition talks. Your CCPC status is the single biggest lever in your SR&ED rate, since it determines whether you get the enhanced 35% refundable rate or the reduced 15% non-refundable rate.

A CCPC is, broadly, a private corporation controlled by Canadian residents. Bring in enough foreign investment, and control can shift enough to jeopardize CCPC status, even without a majority stake changing hands, depending on shareholder agreements and voting rights. Taxable capital also matters. As your CCPC’s taxable capital grows past certain thresholds, your $3 million expenditure limit for the enhanced rate starts phasing out.

Mid-year ownership changes complicate the fiscal year calculation too, since the CRA may require you to prorate your expenditure limit across the periods before and after the change. If your company is restructuring, merging, or closing a funding round that brings in significant non-Canadian ownership, loop in whoever is preparing your SR&ED claim before the deal closes, not after.

What Do Real SR&ED Claims Look Like for Canadian SaaS Companies?

Claim sizes vary enormously depending on team size, salary levels, and how much genuinely uncertain engineering work happened in a given fiscal year, but the pattern is consistent: companies that document as they go end up with claims meaningfully larger than companies that reconstruct everything at filing time.

Larger, more established SaaS companies with dedicated R&D teams working through genuine architecture and algorithm challenges regularly file claims in the seven-figure range once multiple projects and several years of eligible salary are combined.

The through-line across successful claims isn’t company size. It’s specificity. Claims that name the exact technical uncertainty, the exact experiments run, and the exact metrics measured survive review far more often than claims built on vague descriptions of “improving the platform.” Founders who treat SR&ED evidence capture as an ongoing engineering habit, tagging hypotheses on tickets, keeping experiment notes on PRs, rather than an annual scramble, consistently produce the stronger claims.

How Long Should You Keep SR&ED Records After Filing?

The CRA can review a filed SR&ED claim for years after acceptance, so retention isn’t optional paperwork, it’s active risk management. Keep all supporting documentation, technical narratives, time logs, financial records, and evidence files for at least six years from the end of the tax year the claim covers. That’s the general retention standard for business records in Canada, and SR&ED claims carry the same exposure to review as any other tax filing.

Store records in a format you can actually retrieve under pressure. A CRA review notice typically gives you a limited window to respond, and scrambling to find a two-year-old ticket history or a former employee’s time logs is how strong claims turn into weak audit responses. Index your evidence by project and fiscal year from the start, not after a review letter arrives.

Filing accepted doesn’t mean the file is closed. If your company later amends a prior return, changes accounting methods, or gets flagged for a broader tax review, your SR&ED documentation from that same period can resurface as part of the process. Treat post-filing retention as a standing part of your finance operations, not a one-time archiving task, and revisit your indexing system whenever your accounting stack or team changes.

What Founders Consistently Get Wrong About SR&ED

The biggest mistake isn’t ineligible work, it’s late reconstruction. Founders wait until filing season, then try to remember what was uncertain about a feature built eight months earlier. That memory gap is exactly where claim value disappears, because vague retrospective narratives read weaker to CRA reviewers than sharp contemporaneous notes.

The second mistake: under-claiming developer time by assuming only “R&D-labeled” work counts, when scaling fixes and algorithm tuning often qualify too.

Three quick wins: run a one-hour audit of last quarter’s tickets today, add a one-line hypothesis field to your ticket template this week, and capture evidence for one full sprint before your next filing.

— Sergio

Where This Guidance Comes From

This playbook draws on the CRA’s own SR&ED program overview and T4088 guide to Form T661, along with practitioner documentation guidance from SD Tax Law and Axscope’s SaaS-specific eligibility breakdown. These sources anchor the eligibility criteria, filing mechanics, and documentation standards described throughout.