T661 Form Guide: Complete Every Section (2026)

T661 Form Guide: How to Complete Every Section for Your SR&ED Claim

Form T661, the SR&ED Expenditures Claim, is the Canada Revenue Agency form every corporation must file (with its T2 return, within 18 months of fiscal year-end) to claim Scientific Research and Experimental Development tax credits. It combines project technical narratives (Part 2) with the expenditure calculation (Part 3) that drives your investment tax credit; the official form and its guide are published by the CRA as Form T661 and Guide T4088.

CRA Form T661 is the single most important document in your SR&ED tax credit claim. Every company claiming the Scientific Research and Experimental Development incentive must file it. The technical narratives you write on this form determine whether your claim is accepted without issue or flagged for a detailed CRA review.

Yet most claimants treat the T661 as an afterthought, rushing through it at tax time, writing vague descriptions, and hoping for the best. That approach costs Canadian businesses millions in denied or reduced claims every year.

This guide walks through every section of Form T661 line by line, with specific advice on what CRA reviewers look for and how to write narratives that satisfy their requirements.

---

What Is Form T661 and Why It Matters

Form T661, titled "Scientific Research and Experimental Development (SR&ED) Expenditures Claim," is the mandatory form for all SR&ED tax credit claims in Canada. It is filed alongside your T2 corporate income tax return and serves two purposes:

1. Technical justification -- It describes each SR&ED project, the technological uncertainties you faced, the systematic work you performed, and the advancements you achieved.
2. Financial calculation -- It details the qualifying expenditures (salaries, materials, contractors, overhead) that form the basis of your investment tax credit.

The CRA uses your T661 as the primary basis for evaluating your claim. If the form is incomplete, vague, or inconsistent, your claim will be delayed, reduced, or denied. If the form is well-prepared with specific technical detail and clear documentation, your claim is far more likely to be processed without intervention.

For background on the SR&ED program itself, see our complete SR&ED guide. Download the current form from the CRA at canada.ca: Form T661 and read the line-by-line instructions in T4088, Guide to Form T661.

T661 vs Schedule 31 (T2SCH31)

---

When to File Form T661

Form T661 must be filed within 18 months after the end of the fiscal year in which the SR&ED work was performed. It is submitted with your T2 corporate income tax return.

Missing this deadline means forfeiting your entire claim for that fiscal year, there are no extensions. For specific deadline calculations based on your fiscal year, see our SR&ED claim deadline guide.

Important: While you have 18 months, filing early is strongly recommended. Earlier filing means earlier refunds and more time to respond to any CRA inquiries.

---

Overview of the T661 Form: All 10 Parts

Form T661 has ten parts (CRA, Guide T4088). Here is what each covers and how much attention it needs:

Part 2 is by far the most important. The CRA's Research Technology Advisors (RTAs) focus their reviews on your Part 2 narratives. Get Part 2 right and everything else follows. Get it wrong and nothing else matters.

---

Deep Dive: Part 2 -- Project Information

Part 2 requires you to describe each SR&ED project in three mandatory sections. These correspond to the CRA's three-criteria eligibility test: technological uncertainty, systematic investigation, and technological advancement.

Line 242: Scientific or Technological Uncertainty

What the CRA wants to know: What specific technical problem could not be solved using standard practice or publicly available knowledge?

This is where most claims go wrong. The CRA is not asking what business problem you were solving. They want to know what technological barrier you could not overcome with existing knowledge.

Weak example (will likely be rejected):
"We needed to build a faster data processing system for our customers."

Strong example (demonstrates genuine uncertainty):
"The existing event-streaming architecture processed a maximum of 2.4 million events per second under production load. Our application required sustained throughput of 10 million events per second with sub-50ms end-to-end latency. No documented approach for our message schema and ordering guarantees could achieve both requirements simultaneously. The uncertainty was whether a partitioning strategy could be designed that maintained strict ordering semantics while distributing load across consumer groups without introducing latency from rebalancing operations."

Writing tips for Line 242:

• State what was unknown or unachievable at the start of the project
• Reference specific technical metrics, constraints, or thresholds
• Explain why existing approaches, tools, or documented methods were insufficient
• Avoid business language, focus on technology, not markets or revenue
• Be specific about the gap between what was known and what needed to be discovered

Line 244: Work Performed (Systematic Investigation)

What the CRA wants to know: What systematic approach did you follow to address the uncertainty? What hypotheses did you test? What experiments did you conduct?

This section must demonstrate that your approach was methodical, not random trial-and-error. The CRA wants to see a structured investigation with defined hypotheses, controlled experiments, and analysis of results.

Weak example:
"Our developers tried different approaches until they found one that worked."

Strong example:
"We formulated three hypotheses for achieving the target throughput: (H1) hash-based partitioning with consumer-side ordering, (H2) log-structured merge with batched acknowledgments, and (H3) a hybrid approach using tiered partitioning with deterministic routing. We built isolated benchmarking environments for each approach using production-representative data. H1 achieved 7.2M events/sec but introduced unacceptable reordering under consumer group rebalancing. H2 reached 9.8M events/sec but latency spiked to 120ms during compaction cycles. We then developed H3 by combining deterministic routing from H1 with the batched acknowledgment model from H2, systematically tuning partition counts, batch sizes, and compaction thresholds across 47 benchmark iterations."

Writing tips for Line 244:

• Describe your methodology, not just the outcome
• Reference hypotheses, prototypes, experiments, or systematic testing
• Show iteration, what you tried, what you learned, what you changed
• Include specific technical details (configurations tested, metrics measured)
• Demonstrate that work was planned and analyzed, not ad hoc

Line 246: Technological Advancement

What the CRA wants to know: What new knowledge, understanding, or capability resulted from the work?

This does not need to be a groundbreaking invention. Incremental advances count. The CRA wants to see that your systematic investigation produced knowledge that did not previously exist, even if it is specific to your technical context.

Weak example:
"We successfully built a faster system."

Strong example:
"The investigation established that deterministic partition routing combined with batched acknowledgments and tuned compaction intervals can sustain 10.3 million events per second with p99 latency of 42ms under production conditions. Specifically, we determined that partition counts must exceed consumer group size by a factor of at least 8x to prevent rebalancing-induced latency spikes, and that compaction intervals below 200ms negate the throughput gains from batching. These findings were not documented in existing literature for our ordering-guarantee requirements and represent a novel configuration methodology for high-throughput event-streaming systems with strict ordering semantics."

Writing tips for Line 246:

• State what you now know that you did not know before
• Be specific about the technical knowledge gained
• Include quantitative results where possible
• Mention if findings were novel relative to publicly available knowledge
• Connect the advancement back to the uncertainty described in Line 242

---

Part 3: Expenditures -- Calculating Your Qualifying Costs

Part 3 is where you calculate the dollar value of your claim. The main expenditure categories are:

Salaries and Wages

The largest component for most claims. Include the portion of employee salaries allocated to SR&ED activities. You must reasonably estimate the percentage of each employee's time spent on eligible work.

Key rules:

• Include salary, wages, and taxable benefits
• Prorate based on time spent on SR&ED vs. other activities
• Bonuses and stock options are generally excluded
• Keep time-tracking records to support your allocation

Materials Consumed or Transformed

Materials that were consumed or transformed during SR&ED work (not materials incorporated into products sold). This includes raw materials used in prototyping, testing materials destroyed during experiments, and consumables used in the R&D process.

Contractor Payments (80% Rule)

If you hired arm's-length contractors for SR&ED work, you can claim 80% of the amount paid. The 20% reduction is the CRA's proxy for the contractor's profit margin.

Key rules:

• The 80% rate applies to arm's-length contractors only
• Non-arm's-length contractor payments follow different rules
• You must have documentation showing the contractor performed SR&ED-eligible work
• Subcontractor agreements should reference the R&D nature of the work

Overhead -- The Proxy Method

Most claimants use the proxy method to calculate overhead, which adds 55% of eligible salary expenditures to your claim. This is simpler than the traditional method (which requires tracking actual overhead costs) and often yields a comparable or better result.

Proxy method calculation:

• Eligible salaries: $500,000
• Proxy overhead (55%): $275,000
• Total qualifying expenditures (salaries + proxy): $775,000

The alternative is the traditional method, where you track actual overhead costs (rent, utilities, equipment depreciation) allocated to SR&ED. Most small and mid-size companies find the proxy method both simpler and sufficient.

---

Common T661 Mistakes That Trigger CRA Audits

Based on patterns from thousands of SR&ED claims, these are the most frequent errors that lead to CRA reviews, reductions, or denials:

1. Writing Business Objectives Instead of Technical Uncertainties

The number one mistake. Line 242 asks about technological uncertainty, not business challenges. "We needed to increase sales" or "customers wanted faster delivery" are not technological uncertainties.

2. Describing Results Instead of Systematic Investigation

Line 244 asks about your process, not your product. "We built a machine learning model" tells the CRA nothing about whether the work was systematic. Describe the hypotheses, experiments, and iterative analysis.

3. Claiming Routine Development as SR&ED

Implementing well-documented features using established frameworks is not SR&ED. Using React to build a dashboard, integrating a standard API, or deploying with Docker are routine activities. The work must involve genuine technical uncertainty. Review our SR&ED eligible project examples to see what qualifies across different industries.

4. Insufficient Time Allocation Records

The CRA frequently challenges salary claims because companies cannot demonstrate how employee time was split between SR&ED and non-SR&ED activities. Even approximate weekly logs are better than nothing.

5. Inconsistent Narratives Across Projects

If your T661 describes five projects but your financial records show costs for three, the CRA will question the discrepancy. Ensure technical and financial sections are consistent.

6. Missing Contractor Documentation

Claiming contractor costs at 80% without documentation that the contractor performed SR&ED-eligible work is a red flag. Maintain statements of work and deliverable records.

7. Overclaiming Support Activities

Support activities (testing, data collection, engineering) are eligible only when they directly support an SR&ED project. Claiming all QA work or all data analysis as SR&ED without linking it to specific projects invites scrutiny.

8. Filing at the Last Minute

Claims filed close to the 18-month deadline receive more scrutiny and leave no time to address CRA questions. Early filing signals preparedness.

For detailed guidance on handling a CRA review, see our SR&ED audit preparation guide.

---

T661 for Software Companies

Software companies represent the largest group of SR&ED claimants, and they also face unique challenges with Form T661. CRA reviewers are increasingly sophisticated about software development and can distinguish genuine R&D from routine coding.

What Qualifies in Software

• Developing algorithms where the solution approach was uncertain
• Achieving performance targets that exceeded known architectural capabilities
• Building systems that required novel approaches to concurrency, scale, or reliability
• Creating machine learning models where the feasibility of achieving target accuracy was uncertain
• Developing integration architectures where no documented approach existed for the specific combination of constraints

What Does Not Qualify in Software

• Implementing features using established frameworks and documented patterns
• Building CRUD applications, dashboards, or standard web interfaces
• Integrating third-party APIs following their documentation
• Standard DevOps, deployment, and infrastructure work
• UI/UX design and front-end styling

Software-Specific Writing Tips

• Reference specific technical metrics (latency, throughput, accuracy, memory usage)
• Name the technologies, architectures, and approaches you evaluated
• Describe why documented approaches (Stack Overflow, vendor docs, academic papers) were insufficient
• Show experimental methodology, benchmarks, A/B tests, controlled comparisons
• Quantify the gap between what was achievable with known methods and what you needed

For industry-specific guidance, see our SR&ED for software companies page.

---

How GrantOps Automates T661 Preparation

Writing T661 technical narratives is the most time-consuming part of SR&ED claims. Most companies spend weeks gathering information from developers, reconstructing project timelines, and drafting descriptions that satisfy CRA requirements.

GrantOps automates this process by connecting directly to your development tools:

• Automatic project identification -- GrantOps scans your Git repositories, project management tools, and technical documentation to identify potentially eligible SR&ED projects
• Narrative generation -- AI generates draft T661 narratives (Lines 242, 244, 246) based on actual commit history, pull requests, and technical discussions
• Time allocation -- Developer activity data provides evidence-based time allocation across SR&ED and non-SR&ED work
• Expenditure calculation -- Salary and overhead calculations are automated using your HR and financial data
• Audit-ready documentation -- All supporting evidence is organized and linked to specific T661 claims

The result: T661 forms that are more accurate, more detailed, and completed in days instead of weeks, without pulling developers away from their work.

---

Frequently Asked Questions

What is CRA Form T661?

Form T661 is the mandatory form for claiming the SR&ED tax credit. It includes technical descriptions of your R&D projects and a detailed breakdown of qualifying expenditures. Every SR&ED claim requires a completed T661 filed with your T2 corporate income tax return.

How many projects should I include on my T661?

Include every project that meets the CRA's three-criteria test (technological uncertainty, systematic investigation, technological advancement). There is no limit. Most companies claim between 2 and 15 projects per fiscal year. Each project gets its own set of Line 242/244/246 narratives.

How long should T661 narratives be?

There is no official length requirement, but effective narratives for each project typically range from 300 to 800 words per section (Lines 242, 244, 246). Brevity with specificity is better than length with vagueness. Focus on technical detail, not word count.

Can I amend a T661 after filing?

Yes. If you discover errors or additional eligible projects, you can file an amended T661 within the 18-month deadline. Amendments filed after the deadline are generally not accepted for new projects but may be accepted for corrections to existing claims.

Do I need to attach supporting documents to the T661?

No documents are attached when filing. However, you must retain supporting documentation (time logs, technical records, financial records) in case of a CRA review. The CRA can request documentation for up to six years after filing.

What is the difference between the proxy method and traditional method for overhead?

The proxy method adds 55% of eligible salaries as overhead, no need to track actual costs. The traditional method requires you to calculate actual overhead (rent, utilities, depreciation) allocated to SR&ED. Most small and mid-size companies use the proxy method for simplicity. You choose one method per claim year and cannot switch mid-year.

What is a CCPC and why does it matter for T661 claims?

A Canadian-Controlled Private Corporation (CCPC) receives the enhanced 35% refundable SR&ED credit rate on the first $6 million of qualifying expenditures. Eligible Canadian public corporations (ECPCs) now also qualify for the 35% refundable rate. Non-CCPCs that are not ECPCs receive only 15%, and it is non-refundable. Corporate status significantly affects the financial value of your T661 claim.

Should I hire a consultant to prepare my T661?

Traditional SR&ED consultants charge 15-25% of the credit value and handle the entire process. This makes sense for companies with limited internal expertise but is expensive. AI-powered tools like GrantOps can automate T661 preparation at a fraction of the cost while producing more detailed narratives backed by actual development data.

---

Sources

• Form T661, SR&ED Expenditures Claim — Canada Revenue Agency
• T4088 Guide to Form T661 — Canada Revenue Agency
• How to claim SR&ED tax incentives — Canada Revenue Agency
• Guidelines on the eligibility of work for SR&ED tax incentives — Canada Revenue Agency

Sources

• Form T661, SR&ED Expenditures Claim — Canada Revenue Agency
• T4088 Guide to Form T661 — Canada Revenue Agency
• How to claim SR&ED tax incentives — Canada Revenue Agency
• Guidelines on the eligibility of work for SR&ED tax incentives — Canada Revenue Agency

Start Preparing Your T661 Today

Form T661 is the gateway to Canada's largest R&D incentive. A well-prepared T661 means a smoother CRA review, faster refunds, and maximum credit recovery. A poorly prepared one means delays, reductions, and missed opportunities.

GrantOps automates the hardest parts of T661 preparation, identifying eligible projects, generating CRA-compliant technical narratives, calculating expenditures, and assembling audit-ready documentation. Published pricing plus an 8% success fee instead of consultant contingency fees. No weeks of manual work.

Start free — connect GitHub and get a T661 draft in days, not months

Related resources:

• What is SR&ED? Complete guide -- Full program overview
• SR&ED eligible project examples -- Real examples across industries
• SR&ED claim deadlines -- Filing windows by fiscal year end
• SR&ED audit preparation guide -- How to handle a CRA review
• What is a CCPC? -- Why corporate status affects your credit rate
• Automate SR&ED claims -- How GrantOps streamlines the process