Every year, Canadian tech companies leave millions in SR&ED tax credits unclaimed. Not because they don’t qualify. Because they miss the filing deadline — or start preparing too late to file a complete claim.
The SR&ED filing deadline is absolute. CRA does not grant extensions. There is no grace period. If you miss it, the money is gone.
This post covers the exact deadlines for 2026, what happens if you miss them, and a practical preparation plan — whether you file with a consultant, with software, or on your own.
The SR&ED Filing Deadline: What You Need to Know
The SR&ED filing deadline isn’t a standalone date. It’s tied directly to your corporate tax return.
The rule: your T661 (the SR&ED claim form) must be filed no later than 18 months after the end of the fiscal year in which the R&D work was performed. And it must be filed with or before your T2 corporate income tax return for that fiscal year.
That 18-month window sounds generous. It isn’t.
Your T2 corporate tax return is due 6 months after your fiscal year-end. Most companies file their T661 alongside their T2. But even if you file the T2 on time, you technically have up to 18 months after year-end to submit the T661 — as long as you haven’t already filed your T2 without it.
This is where companies get tripped up. If your accountant files your T2 without the T661 attached, and you try to submit the SR&ED claim later, CRA will accept it only if you’re still within the 18-month window. But the claim must amend or accompany the T2. Filing a standalone T661 after the T2 has already been submitted requires an amended return, and timing gets tight.
The safest approach: file the T661 with the T2. That gives you one deadline to hit, not two.
How the Deadline Works for Different Fiscal Year-Ends
Your fiscal year-end determines your specific dates. Here are the three most common scenarios:
December 31 fiscal year-end:
- T2 due: June 30 (6 months after year-end)
- T661 absolute deadline: June 30 of the second year following (18 months after year-end)
- Example: For fiscal year ending December 31, 2024, the T661 deadline is June 30, 2026.
March 31 fiscal year-end:
- T2 due: September 30 (6 months after year-end)
- T661 absolute deadline: September 30 of the following year (18 months after year-end)
- Example: For fiscal year ending March 31, 2025, the T661 deadline is September 30, 2026.
June 30 fiscal year-end:
- T2 due: December 31 (6 months after year-end)
- T661 absolute deadline: December 31 of the following year (18 months after year-end)
- Example: For fiscal year ending June 30, 2025, the T661 deadline is December 31, 2026.
The pattern is simple: take your fiscal year-end, add 18 months. That’s your hard deadline for the T661.
Key Dates for 2026
Here’s a reference table for the SR&ED filing deadlines that fall in 2026. Find your fiscal year-end and mark the dates.
| Fiscal Year-End | T2 Corporate Tax Return Due | T661 SR&ED Claim Deadline (18 months) | Status as of Feb 2026 |
|---|---|---|---|
| December 31, 2024 | June 30, 2025 | June 30, 2026 | 4 months remaining |
| March 31, 2025 | September 30, 2025 | September 30, 2026 | 7 months remaining |
| June 30, 2025 | December 31, 2025 | December 31, 2026 | 10 months remaining |
| September 30, 2024 | March 31, 2025 | March 31, 2026 | 6 weeks remaining |
| December 31, 2025 | June 30, 2026 | June 30, 2027 | T2 due in 4 months |
If your fiscal year ended December 31, 2024: Your T2 was due June 30, 2025. If you filed the T2 without the T661, you have until June 30, 2026 to get the SR&ED claim in. That’s 4 months from today. If your documentation isn’t started, this is urgent.
If your fiscal year ended September 30, 2024: Your 18-month deadline is March 31, 2026 — just 6 weeks away. If you haven’t started, a full claim is very difficult to file in time.
If your fiscal year ended December 31, 2025: Your T2 is due June 30, 2026, and the T661 deadline is June 30, 2027. You have time. But the best time to start documentation is now — while the work is still fresh.
Important Nuances
- The T661 must be filed with or before the T2. If you plan to file them together (the standard approach), your effective deadline is 6 months after year-end — not 18 months.
- Amended returns are possible but add complexity. If you’ve already filed the T2, you can amend it to include the T661, but this must happen within the 18-month window.
- Provincial deadlines align with the federal deadline in most cases. Alberta, Ontario, Quebec, and other provinces with their own R&D credits typically follow the same filing timeline. Check your province’s specific requirements if you claim provincial credits separately.
What Happens If You Miss the Deadline
You lose the claim. That’s it.
CRA does not accept late-filed T661 forms. There is no appeals process for a missed SR&ED deadline. There is no “reasonable excuse” provision like there is for some other tax filings. The 18-month window is a hard statutory limit set by the Income Tax Act.
The Financial Impact Is Permanent
For a qualifying CCPC (Canadian-controlled private corporation) with $200K in eligible R&D expenditures, the refundable investment tax credit (ITC) alone can be worth $70K or more. Miss the deadline, and that $70K disappears. Not deferred — gone.
Over a 5-year period, a company that misses even one filing deadline on a $200K claim forfeits $70K-$130K in credits (depending on provincial top-ups). That’s a senior engineer’s salary. That’s 12 months of additional product development.
Refundable ITC vs. Deduction: Both Are at Risk
Two types of SR&ED benefits exist, and both are affected by a missed deadline:
Refundable investment tax credit (ITC): Available to qualifying CCPCs. This is actual cash back from CRA — a cheque or direct deposit. If you miss the filing deadline, you forfeit the refundable credit entirely.
Non-refundable ITC / deduction: Available to non-CCPCs and larger companies. These reduce your tax liability rather than generating a refund. A missed deadline means the deduction is lost for that fiscal year.
The refundable ITC is particularly painful to lose because it’s real cash flow. Many early-stage tech companies depend on SR&ED refunds as part of their operating budget. Missing the deadline doesn’t just mean “less tax savings” — it means tens of thousands of dollars that never arrive.
Late-Filed T2 with T661: Still No Credit
Some companies assume that if they file the T2 late but include the T661, the SR&ED claim will be processed. This is partially true — CRA will accept a late T2 with a T661 attached, as long as both are filed within the 18-month window. But there are penalties and interest on the late T2 itself, and the SR&ED review process may be flagged for additional scrutiny.
The worst scenario: filing the T2 on time without the T661, then discovering 19 months after year-end that the documentation is ready. At that point, the 18-month window has closed. The claim is dead regardless of how good the documentation is.
Why Most Companies Start Too Late
The most common reason companies miss the SR&ED deadline — or file a weaker claim than they should — isn’t negligence. It’s a documentation bottleneck that catches them off guard.
Here’s how it typically plays out:
Month 1 (3-4 months before deadline): The CFO or accountant flags that the SR&ED claim needs to get started. Someone emails the CTO.
Month 2 (2-3 months before deadline): The CTO reaches out to an SR&ED consultant. The consultant has a 3-4 week wait for onboarding because every other company is doing the same thing at the same time. SR&ED consulting is deeply seasonal — most consultants are fully booked from January through June.
Month 3 (1-2 months before deadline): The consultant starts scheduling retrospective interviews with engineers. Engineers are in the middle of sprint work. Scheduling takes 2-3 weeks. Each interview covers 2-3 projects and takes 60-90 minutes. For a team with 8-12 qualifying projects, that’s 4-6 interviews across 3-4 engineers.
Month 4 (at the deadline): The consultant is writing narratives based on interviews about work that happened 12-18 months ago. Engineers can’t remember details. Commit messages and ticket descriptions aren’t specific enough to fill the gaps. The narratives are generic. Some qualifying projects get dropped because there isn’t enough documentation to support them.
Result: The claim is filed, but it’s smaller than it should be. Or worse — the deadline passes and the claim isn’t filed at all.
The math simply doesn’t work. If you start 3 months before the deadline and the process takes 3-6 months, you’re already behind before you begin. The consultant bottleneck is real: the top SR&ED firms in Canada manage hundreds of clients, and peak filing season creates a queue you can’t skip.
The companies that file strong, complete claims aren’t smarter. They start earlier. Or they document continuously — which eliminates the bottleneck entirely.
How to Prepare Now (Whether or Not You Have a Consultant)
Regardless of how you plan to file your SR&ED claim — consultant, software, or in-house — the preparation work is the same. And you can start today.
Step 1: Identify Qualifying Projects
Go through your team’s work from the relevant fiscal year. For each major engineering effort, ask three questions:
- Was the outcome uncertain? Did the team face a problem where the solution wasn’t obvious? Where they had to experiment or try multiple approaches?
- Was the investigation systematic? Did they benchmark, prototype, test, and iterate — or was it ad hoc guessing?
- Was there a technological advancement? Did the team learn something new about the problem, the technology, or the approach — even if the project failed?
If the answer to all three is yes, the project likely qualifies. Most software teams have 5-15 qualifying projects per year.
Step 2: Gather Development Artifacts
CRA values evidence. The more specific and contemporaneous your evidence, the stronger your claim. Start collecting:
- Git commit histories for qualifying projects — these show what was attempted, when, and by whom
- Pull request descriptions and code review comments — these often contain the reasoning behind technical decisions
- Issue tracker tickets (Jira, Linear, GitHub Issues) — these document the problem statement, acceptance criteria, and approach
- Slack or Teams threads where technical decisions were discussed (export these before they’re lost to retention policies)
- Architecture decision records (ADRs) if your team writes them
- Benchmark results, performance test outputs, and experiment logs
This evidence is gold for SR&ED documentation. A commit history that shows three different approaches to solving a performance problem is direct evidence of systematic investigation and technological uncertainty.
Step 3: Document Technological Uncertainties While They’re Fresh
This is the single highest-impact action you can take right now. For each qualifying project, write 2-3 sentences answering:
- What was the technical challenge?
- Why couldn’t it be solved with known methods or existing tools?
- What did the team try first, and what happened?
Do this now — or better, within a week of completing the work. The details that CRA values most are exactly the details that fade fastest from memory. Six months from now, your lead developer won’t remember why they abandoned the first approach. Right now, they can explain it in 30 seconds.
Step 4: Track Time Allocation
SR&ED claims include labour costs as eligible expenditures. CRA needs to know how much time each qualifying employee spent on qualifying R&D work.
If you don’t have formal time tracking, estimate now while the work is recent. For each qualifying project, estimate the percentage of time each involved engineer spent on R&D activities. Even rough estimates documented now are better than fabricated numbers at filing time.
Step 5: Organize by Project
Create a folder (physical or digital) for each qualifying project. Include:
- Project description (1-2 paragraphs)
- Start and end dates
- Team members involved
- The uncertainties, investigation, and advancement notes from Step 3
- Links to relevant commits, PRs, and tickets from Step 2
- Time allocation estimates from Step 4
This project-level organization is exactly what a consultant or software tool needs to produce the T661 narratives. Having it ready cuts documentation time by 50-70%.
The Case for Continuous Documentation
Every step above is reactive. You’re gathering evidence and writing notes about work that’s already done. It works — but it’s inefficient, and you lose detail every day you wait.
The alternative: capture qualifying work as it happens.
CRA explicitly states that contemporaneous records — documentation created at the time the work was performed — carry more weight than retrospective accounts. This makes sense. A technical narrative written the week the work was done is more specific, more accurate, and more credible than one reconstructed from a 45-minute interview 14 months later.
Continuous documentation eliminates the annual fire drill. There’s no 3-month scramble before the deadline. No consultant scheduling bottleneck. No engineers trying to remember what they worked on last March. The documentation exists because it was captured in real time.
For software teams, continuous documentation is practical because the evidence already lives in your development workflow. Every commit, every PR, every ticket, every code review — these are contemporaneous records of R&D activity. The question isn’t whether the evidence exists. It’s whether anyone is capturing and organizing it for SR&ED purposes.
Bottom Line
The SR&ED filing deadline is not flexible. It’s 18 months after your fiscal year-end, and the T661 must be filed with or before your T2 corporate tax return. Miss it, and you forfeit the entire credit for that year.
Here are the key deadlines for 2026:
- September 30, 2024 fiscal year-end: Deadline is March 31, 2026 (6 weeks away)
- December 31, 2024 fiscal year-end: Deadline is June 30, 2026 (4 months away)
- March 31, 2025 fiscal year-end: Deadline is September 30, 2026
- June 30, 2025 fiscal year-end: Deadline is December 31, 2026
If your deadline is within 6 months, start now. If your deadline is further out, start now anyway — you’ll file a stronger claim with better documentation.
The companies that recover the most from SR&ED aren’t the ones with the best consultants. They’re the ones with the best documentation. And the best documentation is the kind that’s captured as the work happens, not reconstructed under deadline pressure.
Need help preparing your SR&ED claim? Our team can help you document qualifying R&D work and maximize your tax credits. Talk to us about your SR&ED filing →