SR&ED Claims for Software Companies
Your engineering team is already doing the R&D. Platform re-architecture, performance engineering at scale, legacy system migration, complex integration development, data pipeline optimization and multi-tenant infrastructure challenges. We identify the qualifying work across your entire engineering organization, prepare the technical narratives and file the claim with CRA. 35% refundable for CCPCs.
Why Established Software Companies Leave SR&ED Credits Unclaimed
Most software companies with existing products and revenue assume SR&ED is only for early-stage startups building something from scratch. That assumption costs them six figures every year. CRA does not limit SR&ED to greenfield development. Any work that involves technological uncertainty and systematic investigation qualifies, including improvements to existing products, platform migrations, scaling challenges and integration engineering on mature systems.
In a 15-person engineering team, it is common for 40% to 60% of total engineering hours to involve qualifying SR&ED work buried inside product roadmap items, technical debt reduction, infrastructure projects and platform evolution. The challenge is identifying which engineering work crosses the line from routine development to technological advancement. That is what we do.
| SR&ED Element | For Established Software Companies |
|---|---|
| Federal ITC rate (CCPC) | 35% refundable on the first $3,000,000 of qualifying expenditures. Refundable means CRA sends a cheque regardless of tax liability. |
| Federal ITC rate (non-CCPC or above $3M) | 15% non-refundable on expenditures above $3,000,000 or for non-CCPCs. Applied against federal tax owing. |
| Ontario Innovation Tax Credit (OITC) | 8% non-refundable on eligible Ontario SR&ED expenditures. Applied against Ontario tax owing. |
| CCPC expenditure limit for 35% rate | $3,000,000 per year. Phased out when prior-year taxable income exceeds $500,000 or prior-year taxable capital exceeds $10,000,000. |
| Filing deadline | 18 months after fiscal year-end. No extensions. Missed deadlines forfeit the claim permanently. |
The $3M Expenditure Limit and the Phase-Out: CCPCs lose access to the enhanced 35% rate when prior-year taxable income exceeds $500,000 or taxable capital exceeds $10,000,000. The rate phases down to the 15% non-refundable rate for non-CCPCs. Software companies approaching these thresholds should plan their SR&ED claims strategically. We model the phase-out impact for every software company client and advise on the optimal claim structure to maximize the refundable portion.
For a complete overview of our SR&ED service, visit our SR&ED Tax Credit Claims page. For ongoing software company accounting and tax advisory, see our accounting services for software companies.
SR&ED in Product Evolution: Where the Credits Hide in Your Roadmap
Software companies with existing products perform SR&ED every sprint without recognizing it. The qualifying work is embedded inside feature development, platform improvements, infrastructure projects and technical debt initiatives. Here are the categories we extract from your engineering backlog.
| Engineering Category | When It Qualifies for SR&ED | When It Does NOT Qualify |
|---|---|---|
| Platform re-architecture | Migrating from monolith to microservices where the decomposition strategy, service boundaries, data consistency patterns or inter-service communication require experimental approaches that existing frameworks do not solve | Refactoring code within the same architecture using established design patterns and documented best practices |
| Performance engineering at scale | Optimizing query execution, caching strategies, data partitioning or concurrency models to achieve performance targets that cannot be met through standard tuning (e.g., sub-100ms response at 50,000 concurrent users with complex joins) | Adding indexes, upgrading hardware, implementing standard Redis caching or adjusting connection pool sizes |
| Legacy system migration | Migrating a legacy system to a new technology stack where data fidelity, business logic translation, state management or real-time cutover strategies require systematic experimentation to validate | Rewriting an application in a new language using equivalent logic with no technical uncertainty about the approach |
| Complex integration development | Building integrations with third-party systems where API limitations, data format incompatibilities, rate limiting constraints or undocumented behaviours require iterative experimentation to resolve | Connecting to a well-documented API using standard SDKs with published integration guides |
| Data pipeline and ETL engineering | Designing data pipelines where volume, velocity, schema evolution, exactly-once semantics or cross-system consistency introduce technical challenges beyond the capabilities of standard tools | Building a standard ETL pipeline using Airflow, dbt or Fivetran with documented connectors and transformations |
| Multi-tenant architecture evolution | Evolving tenant isolation, resource allocation, configuration management or data partitioning strategies where existing multi-tenancy patterns fail at the required scale or customization depth | Implementing a standard schema-per-tenant or row-level security approach with documented best practices |
| Security and compliance engineering | Developing novel authentication, authorization, encryption or audit logging systems where regulatory requirements (SOC 2, PIPEDA, HIPAA) demand capabilities beyond standard library implementations | Implementing OWASP best practices, standard OAuth2 flows or off-the-shelf WAF configurations |
| Observability and reliability engineering | Building custom observability tools, anomaly detection for system health, auto-remediation engines or chaos engineering frameworks where existing tools (Datadog, New Relic, PagerDuty) do not meet the technical requirements | Configuring standard monitoring dashboards, setting alert thresholds or implementing basic health checks |
Every Sprint Contains Potential SR&ED: In a mature software company, SR&ED-eligible work does not live in a separate R&D department. It is distributed across product teams, platform teams, infrastructure teams and even customer success engineering. A product team building a new collaboration engine is doing SR&ED if the real-time sync architecture requires experimental approaches. A platform team migrating the authentication layer is doing SR&ED if the session management across microservices introduces unresolved technical challenges. We audit your entire engineering organization, not just the projects labelled "R&D."
How We Identify and Claim SR&ED Across Your Engineering Org
Four phases. We embed into your engineering process. No disruption to your team.
Engineering Audit
We review your product roadmap, sprint boards, architecture decision records, post-mortems and technical design docs to identify all qualifying projects across every team.
Developer Interviews
We interview lead engineers, architects and team leads to capture the technical challenges, experimental approaches and outcomes for each qualifying project.
Narrative and Calculation
We prepare the Form T661 technical narrative for each project, allocate developer time across qualifying and non-qualifying work and calculate total eligible expenditures.
File and Defend
We file the claim with CRA, respond to any Research Technology Advisor review and defend every project through to refund deposit or credit application.
Free SR&ED Engineering Audit for Software Companies
We review your engineering backlog and estimate the total credit across all teams. No obligation. No disruption.
Eligible Expenditures for Software Company SR&ED Claims
| Expenditure | What Qualifies for Software Companies | How We Calculate It |
|---|---|---|
| Engineering salaries (in-house developers) | Gross salary of software engineers, architects, DevOps/SRE engineers, data engineers and QA engineers performing qualifying SR&ED work. Includes salary, bonuses and vacation pay. | Time allocation per developer per project per sprint. We use Jira/Linear ticket data, commit history and sprint velocity reports to build defensible allocations. A senior engineer spending 45% of their time on qualifying projects: 45% of their $140,000 salary ($63,000) is eligible. |
| Engineering management (partial) | Engineering managers, directors and VPs who directly contribute to the technical approach (architectural decisions, design reviews, technical problem-solving). Supervisory-only time does not qualify. | Time allocated based on meeting logs, design review participation, ADR contributions and sprint planning involvement in qualifying projects. Typically 15% to 30% of an engineering manager's time qualifies. |
| Contractor and outsourced development | Payments to contract developers, offshore development teams or outsourced engineering firms performing qualifying SR&ED work. Only 80% of the contractor cost is eligible. | Contractor invoices reviewed by project and deliverable. Only the R&D portion qualifies. Feature implementation on an existing architecture without technical uncertainty is excluded. 80% of qualifying invoices claimed. |
| Cloud infrastructure for R&D | AWS, GCP, Azure and other cloud costs allocated to R&D environments: staging, testing, experimentation, performance benchmarking, load testing and CI/CD for qualifying projects. Production workloads do not qualify. | Cloud bills segmented by environment tags (dev, staging, perf-test vs. production). R&D-tagged resources included. We help your DevOps team configure tagging for SR&ED at onboarding. |
| Third-party tools and services consumed in R&D | API costs, data licensing fees, testing tool subscriptions and SaaS platform charges used exclusively for R&D experimentation. Must be consumed during the SR&ED work, not ongoing production costs. | Invoices and usage reports reviewed. R&D-only usage separated from production. Only the R&D portion claimed. |
| Proxy overhead (55% of qualifying salaries) | Automatically added to qualifying salary and wage expenditures. Covers office rent, utilities, benefits, administrative support and indirect costs. No individual tracking required. | Calculated automatically. $800,000 in qualifying salaries x 55% = $440,000 proxy overhead. Total eligible: $1,240,000. |
Worked Example: B2B SaaS Company with 12-Person Engineering Team
| Item | Total Cost | SR&ED Eligible |
|---|---|---|
| 8 software engineers at $130,000 average | $1,040,000 | $468,000 (45% average time on qualifying projects) |
| 2 senior/staff engineers at $160,000 average | $320,000 | $192,000 (60% time on qualifying architectural work) |
| 1 engineering manager (partial technical contribution) | $165,000 | $41,250 (25% time on qualifying design reviews and ADRs) |
| 1 DevOps/SRE engineer | $135,000 | $47,250 (35% time on qualifying infrastructure R&D) |
| Offshore contractor team (3 developers, 6 months) | $180,000 | $86,400 (60% qualifying x 80% rule) |
| Cloud infrastructure (R&D environments) | $96,000 | $38,400 (40% R&D-tagged environments) |
| Subtotal eligible expenditures | $873,300 | |
| Proxy overhead (55% of salaries: $748,500 x 55%) | $411,675 | |
| Total qualified expenditures | $1,284,975 | |
| Federal ITC (35% refundable) | $449,741 | |
| Ontario OITC (8% non-refundable) | $102,798 | |
| Total SR&ED benefit | $552,539 |
$552,539 from a 12-Person Engineering Team: This B2B SaaS company with $1.9M in total engineering costs receives $449,741 in refundable federal credits (cash deposit) plus $102,798 in Ontario credits. The federal refund alone covers 3.5 developer salaries for a full year. This is not a hypothetical scenario. It is a typical outcome for a mid-size Ontario software company with a 12-person engineering team that has never filed SR&ED before. The credit has been available every year they were operating. Every unfiled year is six figures permanently lost.
Multi-Project SR&ED Claims: How We Structure Claims for Larger Engineering Teams
Software companies with 10+ engineers typically have 5 to 15 qualifying SR&ED projects running in parallel across product teams, platform teams and infrastructure teams. Each project requires its own technical narrative, time allocation and expenditure calculation. The claim is the sum of all qualifying projects filed on a single Form T661.
| Claim Component | Single-Project Claim (Small Company) | Multi-Project Claim (Larger Software Company) |
|---|---|---|
| Number of projects | 1 to 3 | 5 to 15 (sometimes 20+) |
| Technical narratives | 1 to 3 narratives, each describing a single technological advancement | 5 to 15+ narratives. Each project has its own uncertainty, investigation and advancement. Cross-project dependencies documented. |
| Time allocation complexity | Each developer allocated to 1 to 2 projects. Simple time split. | Developers contribute to multiple qualifying and non-qualifying projects. Sprint-level allocation required. Jira/Linear data cross-referenced with payroll records. |
| Developer interview depth | 30-minute interviews with 2 to 3 developers | 60 to 90-minute interviews with each team lead. Architecture review session with VP Engineering or CTO. Sprint board walkthrough for each team. |
| CRA review complexity | Lower review risk. Single-project claims are straightforward for RTAs. | Higher scrutiny. Multi-project claims require consistent methodology across all narratives. CRA may select 3 to 5 projects for deep review and extrapolate. |
| Typical annual claim value | $30,000 to $150,000 | $200,000 to $600,000+ (35% rate). Larger teams with $3M+ in qualifying expenditures access the 15% non-refundable tier. |
Consistency Across Narratives Is Critical: When CRA reviews a multi-project claim, the RTA evaluates whether the methodology is consistent across all projects. If one narrative describes rigorous systematic experimentation and another describes vague "iterative development," the entire claim loses credibility. We use a standardized narrative framework for every project: identical structure, consistent language, uniform level of technical detail. This consistency is what separates a defensible $500,000 claim from one that gets reduced to $150,000.
Time Allocation: The Make-or-Break Factor for Software SR&ED
CRA's most common reason for reducing software company SR&ED claims is disagreement on time allocation. How much of each developer's time was genuinely spent on qualifying SR&ED work? The answer must be defensible, documented and consistent with your engineering records.
| Allocation Method | How It Works | CRA Defence Strength |
|---|---|---|
| Jira/Linear ticket analysis | Each ticket tagged as SR&ED-eligible or not. Story points or hours tracked per ticket. Developer time allocated based on ticket assignment and sprint velocity. | Strong. Provides granular, contemporaneous, per-developer allocation that CRA can verify independently. |
| Git commit and pull request analysis | Commit history reviewed to identify contributions to qualifying code branches, repos or features. Lines of code, commit frequency and PR reviews correlated to project timelines. | Strong supporting evidence. Best used alongside ticket analysis, not as the sole allocation method. |
| Sprint retrospective and planning records | Sprint planning documents showing which team members were assigned to qualifying projects. Retrospective notes documenting technical challenges encountered and resolved. | Moderate. Useful context but lacks per-developer hour-level granularity that CRA prefers. |
| Developer interviews and self-assessment | Each developer estimates the percentage of their time spent on qualifying projects. Validated against ticket data and commit history. | Moderate. Accepted by CRA when supported by corroborating evidence. Self-assessment alone is weak. |
| Blanket percentage applied to all developers | A single percentage (e.g., "all developers spent 50% on R&D") applied uniformly across the team. | Weak. CRA frequently rejects blanket allocations. Individual developer allocations are expected. |
We Build Per-Developer, Per-Project, Per-Sprint Allocations: Blanket percentages are the number one reason CRA reduces software SR&ED claims. We build individual time allocations for each developer on each qualifying project using a combination of Jira/Linear ticket data, git commit history, sprint records and developer interviews. The result is a defensible allocation matrix that CRA can audit line by line without finding inconsistencies. This level of detail takes more preparation but protects six-figure claims from arbitrary reduction.
Software Company Types We File SR&ED Claims For
| Company Type | Common Qualifying Projects | Typical Annual Claim |
|---|---|---|
| B2B SaaS platforms | Multi-tenant scaling, workflow engine development, role-based access control beyond standard RBAC, real-time collaboration, API versioning and backward compatibility under complex constraints | $150,000 to $600,000 |
| Enterprise software and ERP | Complex integration engines, data transformation pipelines for legacy format compatibility, custom reporting engines with dynamic schema, multi-entity transaction processing | $200,000 to $700,000 |
| Data and analytics platforms | Real-time analytics on streaming data, custom query optimizers, data lake governance with schema evolution, ML-powered anomaly detection in operational data | $100,000 to $400,000 |
| Vertical SaaS (industry-specific) | Domain-specific workflow automation, regulatory compliance engines (healthcare, finance, construction), industry-specific data models requiring novel approaches | $80,000 to $350,000 |
| API-first and developer tools | Custom language parsers, SDK generation engines, rate limiting and quota management at scale, developer experience tooling with novel UI/UX engineering challenges | $100,000 to $400,000 |
| E-commerce and marketplace platforms | Search and recommendation engines, dynamic pricing algorithms, inventory management optimization, fraud detection, payment orchestration across multiple processors | $80,000 to $300,000 |
| Infrastructure and DevOps software | Custom container orchestration, CI/CD pipeline optimization for specialized workloads, infrastructure-as-code engines, automated security scanning with novel detection approaches | $100,000 to $400,000 |
| Communication and collaboration platforms | Real-time messaging at scale (WebSocket management, presence systems), video processing pipelines, document collaboration with conflict resolution, notification delivery optimization | $100,000 to $500,000 |
For ongoing software company accounting, bookkeeping, revenue recognition and tax advisory, visit our software company accounting services.
Not Sure How Much Your Engineering Team Qualifies For?
We review your roadmap, interview your leads and estimate the total credit across all teams. Free. No obligation.
The 10 SR&ED Mistakes Software Companies Make
| # | Mistake | What It Costs | How We Prevent It |
|---|---|---|---|
| 1 | Assuming SR&ED is only for startups or greenfield development | $100,000 to $600,000+ per year unclaimed. Product evolution, platform work and infrastructure R&D all qualify. | Engineering audit across all teams. Every qualifying project identified, including platform, infrastructure and technical debt initiatives. |
| 2 | Only claiming projects explicitly labelled "R&D" | 50% to 70% of qualifying work missed. SR&ED hides inside product roadmap items, infrastructure tickets and tech debt sprints. | We audit your full Jira/Linear backlog, not just the "R&D" label. Every ticket screened for technological uncertainty. |
| 3 | Applying a blanket time allocation percentage across all developers | CRA reduces the claim by 30% to 60%. Blanket allocations lack the per-developer granularity CRA expects. | Per-developer, per-project, per-sprint allocation using ticket data, commit history and developer interviews. |
| 4 | Not including engineering management time | $20,000 to $60,000 in credits missed. EMs who contribute to architectural decisions and design reviews qualify partially. | Engineering manager time allocated based on documented participation in qualifying design reviews, ADRs and technical planning. |
| 5 | Not tagging cloud infrastructure for R&D vs. production | $15,000 to $40,000 in eligible cloud costs unclaimed because R&D environments cannot be separated from production billing. | We help your DevOps team configure environment tags (dev, staging, perf-test) at onboarding. R&D-tagged resources included in the claim. |
| 6 | Inconsistent narrative quality across multi-project claims | CRA reduces the entire claim based on the weakest narrative. One poorly written project undermines 14 well-documented ones. | Standardized narrative framework applied to every project. Same structure, same language, same level of technical detail. |
| 7 | Not including offshore or contractor development costs at 80% | $30,000 to $80,000+ in credits missed on contractor fees that qualify at the 80% rate. | Every contractor invoice reviewed. Qualifying R&D work identified. 80% rule applied to eligible contractor costs. |
| 8 | Missing the 18-month filing deadline | Entire year's claim forfeited permanently. Software companies with fiscal year-ends in Q1 are most at risk. | Filing deadline tracked from year-end. Data collection starts during the fiscal year, not after. |
| 9 | Not considering the $3M expenditure limit phase-out | Companies approaching $500K taxable income lose the 35% refundable rate without strategic planning. | Phase-out impact modelled annually. Claim structure optimized to maximize the refundable portion. |
| 10 | Filing without SR&ED expertise | Claims prepared by general accountants are reduced at 3x the rate of claims prepared by SR&ED specialists. Multi-project software claims require both technical and CRA-specific expertise. | Every claim prepared by our SR&ED team. Technical narratives written with your engineering leads. Multi-project coordination managed end to end. |
SR&ED Pricing for Software Companies
Contingency-based. You pay only when CRA approves your credit.
| Service | Fee | Includes |
|---|---|---|
| SR&ED claim preparation and filing | 15% to 20% of the approved credit (contingency) | Full engineering audit, multi-project identification, per-developer time allocation, technical narrative preparation (all projects), expenditure calculation, Form T661 filing, CRA correspondence |
| Retainer (for large multi-project claims) | $1,000 upfront + contingency on approval | Same as above, plus dedicated SR&ED specialist, quarterly engineering reviews, ADR integration support, multi-year claim coordination |
| Free engineering audit | $0 | We review your roadmap, sprint boards and architecture records. We estimate the total qualifying credit across all engineering teams. No obligation. |
| CRA review and audit defence | Included | RTA meeting preparation, engineer coaching for interviews, financial documentation package, multi-project narrative consistency review, objection filing if claim is reduced |
| Ongoing SR&ED documentation setup | Included for bookkeeping clients | We configure Jira/Linear tagging for SR&ED, set up ADR templates, establish sprint-level documentation protocols so evidence is captured during development, not reconstructed at year-end |
| Annual T2 corporate tax return | FREE | Included for every SR&ED and bookkeeping client. Claim filed alongside the T2. |
For ongoing software company bookkeeping, revenue recognition, HST filing and investor-ready financials, explore our software company accounting services. For our SR&ED process across all industries, visit our SR&ED tax credit claims page.
No Upfront Cost. We Get Paid When You Get Paid.
Contingency-based SR&ED for software companies. 15% to 20% of the approved credit. Free engineering audit. CRA defence included.
SR&ED Claims for Software Companies: Cities We Serve
We file SR&ED claims for software companies across every Ontario city and Canada. No distance limits, no extra fees.
Frequently Asked Questions: SR&ED for Software Companies
Your Engineering Team Is Already Doing the R&D. Get Paid for It.
Gondaliya CPA files multi-project SR&ED claims for software companies across Canada. 35% refundable credit. Per-developer time allocation. Contingency pricing. CRA defence included. 900+ five-star reviews.