What Documentation Does the CRA Expect to See?

The number one reason Scientific Research and Experimental Development (SR&ED) claims are reduced or denied by the Canada Revenue Agency (CRA) is not because the project lacks technical merit. It is because the company lacks the evidence to prove the work actually happened.

The CRA operates on a foundational legal principle: If it wasn’t documented, it didn’t happen. To pass a technical or financial review, you cannot rely on memory, storytelling, or retroactive summaries written months after the fact. The CRA expects contemporaneous documentation—evidence generated naturally in the ordinary course of business while the R&D was actively being performed.

Here is an explicit breakdown of the specific documentation the CRA expects to see to substantiate your claim.

1. Technical Evidence: Proving the “Systematic Investigation”

The CRA’s Research and Technology Advisors (RTAs) want to see a clear paper trail tracking your journey from initial problem statement to technical hypothesis, testing loops, and conclusions.

[Technical Problem] ──> [Hypothesis Formulated] ──> [Dated Test Logs / Iterations] ──> [Recorded Conclusions]
                   ▲
(CRA expects core proof at this stage)

Depending on your industry, your technical folder must contain:

For Software & SaaS Projects

• Source Code Repositories & Commit Logs: Version control timelines (Git, GitHub, GitLab, Azure DevOps) featuring timestamped commits, author names, and descriptions of what technical errors or constraints were being addressed.
• Architecture and System Design Diagrams: Whiteboard photos, Lucid chart files, or database schema maps showing the structural variations your team tested to overcome performance or scalability bottlenecks.
• Ticket Management Tracking: Historical archives from tools like Jira, Trello, or Click Up. The CRA looks closely at tickets detailing technical impediments, testing logs, experimental iterations, and bug spikes, rather than standard commercial
  feature tickets.

For Manufacturing, Engineering & Physical Prototyping

• Design Blueprints & CAD Files: Sequential revisions of 3D models or engineering schematics illustrating physical adjustments made to bypass a structural or mechanical limit.
• Daily Project Records & Laboratory Notebooks: Dated, signed notes from engineers detailing the parameters of specific test runs, materials used, and failure parameters.
• Photographs & Videos: Visual evidence of physical prototypes, custom assembly modifications, and components structural flaws or deformities captured during destructive testing.
• Scrap & Waste Tracking Matrices: Records indicating the exact volume and cost of raw materials ruined or consumed during trial manufacturing batches.

2. Labor Evidence: Proving “Who” and “When”

Labor is typically the largest expenditure bucket in any SR&ED claim. If you claim that a senior developer spent 60% of their annual hours on eligible R&D, you must provide clear evidence linking their paid time to specific experimental tasks.

• Timesheets & Activity Logs: Clean tracking sheets mapping daily or weekly employee hours to distinct SR&ED project codes, isolated clearly from routine tasks like maintenance, UI styling, or sales support.
• Meeting Minutes & Sprint Slack Logs: Digital chat logs (Slack, Microsoft Teams) or recorded minutes from technical standups showing engineers actively troubleshooting the core technical bottlenecks during the active claim window.
• Payroll Alignment Documents: Direct links between your project hour tracking systems and corporate payroll records (T4 slips) to prove the claimed hourly rates perfectly align with reality.

3. Third-Party Evidence: Proving Contractor Scopes

Because contractor fees are eligible for a 80% expenditure inclusion, the CRA audits external contracts meticulously to confirm who holds the economic risk and title to the intellectual property.

• Detailed Statements of Work (SOW): Contracts outlining the precise technological uncertainties the vendor was hired to solve, rather than generalized commercial milestone agreements.
• Itemized Invoicing: Vendor invoices breaking down the exact billing lines allocated to testing, analysis, and programming, completely separate from routine setup fees or administrative costs.

4. Financial Infrastructure: Proving the General Ledger

The CRA Financial Reviewer will expect your general ledger to perfectly mirror the numbers submitted on your Form T661.

• Dedicated Project Costing Accounts: Your corporate accounting software (Xero, QuickBooks) should ideally segregate R&D-specific material purchases, prototyping expenses, and contractor bills into distinct sub-accounts or tracking tags.
• Receipts & Proof of Payment: Clear vendor invoices paired with bank statements proving materials claimed were fully paid for and delivered within the applicable fiscal year.

The “Good, Better, Best” Rule for Documentation Compliance

You do not need to build a flawless, bureaucratic logging framework that paralyzes your engineering team. The CRA explicitly acknowledges that small startups may not have formal administrative setups. Instead, aim to structure your evidence according to this compliance hierarchy:

• POOR (Will Be Denied): A retrospective text narrative written at tax time supported only by a single invoice reading “For R&D services.”
• BETTER (Acceptable): Timesheets tracking general hours per month allocated to a project, backed by email chains discussing system errors and final project reports.
• BEST (Bulletproof): Automated timestamped Git logs, structured Jira tickets with explicit technical tags, daily/weekly timesheets linked to payroll, and dated photos of physical testing anomalies or code performance benchmarks.

The Action Plan for Founders

The easiest way to survive an SR&ED audit is to prepare for one from day one. Do not wait until your fiscal year wraps up to scramble for evidence. Implement automated project tagging inside your existing communication and task tracking networks today, ensuring your technical documentation compiles naturally while your team innovates.