SR&ED Documentation Requirements: Complete Checklist
Proper documentation is the foundation of a successful SR&ED claim. The Canada Revenue Agency (CRA) requires evidence that your work meets SR&ED criteria and that your expenditure calculations are accurate. Without adequate documentation, even legitimate R&D can be denied.
This comprehensive checklist covers all documentation required to support your SR&ED tax credit claim.
Why Documentation Matters
The Stakes
Poor documentation leads to:
- Reduced or denied claims
- CRA audits and reviews
- Lost tax credits (potentially hundreds of thousands)
- Challenges claiming in future years
- Stress and wasted time
Good documentation enables:
- Maximum eligible claim amounts
- Faster CRA processing
- Successful audit defense
- Foundation for future claims
- Peace of mind
CRA's Perspective
CRA reviewers need to verify:
- Work meets SR&ED definition (technological uncertainty, systematic investigation, advancement)
- Expenditures are eligible and accurately calculated
- Claimed amounts are reasonable
Without documentation, you're asking them to take your word for it—they won't.
Technical Documentation Requirements
Project-Level Documentation
For each SR&ED project, maintain:
1. Project Description
- Clear statement of objectives
- Technical challenges/uncertainties faced
- Why standard practice couldn't solve the problem
- Approach taken to address uncertainty
2. Hypothesis Documentation
- What you believed would work
- Scientific/technical basis for hypothesis
- Alternative approaches considered
- Why chosen approach was selected
3. Experimentation Records
- Tests conducted
- Variables tested
- Methodologies used
- Iterations and refinements
- Failed attempts (valuable evidence!)
4. Results and Analysis
- Test results and data
- Analysis of outcomes
- What was learned
- How results informed next steps
- Conclusions reached
5. Advancement Achieved
- New knowledge gained
- Technological progress made
- How uncertainty was resolved
- Application of advancement
Contemporaneous Documentation
"Contemporaneous" means created at or near the time the work was performed—not reconstructed later.
Examples of good contemporaneous evidence:
- Lab notebooks with dated entries
- Design documents with version history
- Meeting notes with technical discussions
- Email threads discussing technical challenges
- Code commit logs with meaningful messages
- Test reports with dates
- Project management records
- Prototype photos with timestamps
Why timing matters:
- CRA values real-time records over after-the-fact summaries
- Demonstrates systematic approach
- More credible during audits
- Difficult to fabricate retroactively
Industry-Specific Documentation
Software Development:
- Code repositories with commit history
- Technical architecture documents
- Algorithm design notes
- Performance benchmarking results
- Bug/issue tracking with technical detail
- Sprint planning with technical stories
- Code review notes
Manufacturing:
- Process flow diagrams (before/after)
- Machine settings and parameters tested
- Quality control test results
- Production trial data
- Material testing records
- Equipment modification records
- CAD/CAM files with iterations
Life Sciences:
- Lab notebooks (GLP where applicable)
- Experimental protocols
- Assay results and analysis
- Formulation records
- Stability testing data
- Regulatory submission documents
- Literature review notes
Engineering:
- Design calculations
- Simulation results
- Prototype test data
- Material specifications
- Failure analysis records
- Standards compliance testing
- CAD files with revision history
Financial Documentation Requirements
Salary and Wage Records
Required for each employee claimed:
- Name and position
- Annual salary/wages
- T4 slips
- Pay stubs or payroll records
- Time allocation to SR&ED (percentage or hours)
- Basis for allocation (time sheets, estimates, methodology)
- Job description showing SR&ED relevance
Time Tracking Options:
1. Time Sheets (Best)
- Daily or weekly time records
- Allocation by project
- Signed by employee and supervisor
2. Project Management Systems
- Software-based time tracking
- Hours by task/project
- Less precise but acceptable
3. Informed Estimates
- Reasonable allocation percentages
- Supported by project plans
- Consistent methodology
- CRA accepts if reasonable
Common Issues:
- No allocation methodology (claiming 100% without basis)
- Retroactive estimates without support
- Including non-SR&ED time (admin, sales, routine)
Materials Documentation
Required records:
- Invoices for materials purchased
- Inventory records showing consumption
- Allocation to specific SR&ED projects
- Explanation of how materials were consumed/transformed
- Exclusion of materials in final products sold
Key Principle: Only materials consumed or transformed in SR&ED qualify—not materials incorporated into products you sell.
Contractor Documentation
Required for third-party SR&ED payments:
- Contracts or agreements clearly defining SR&ED work
- Invoices with detailed descriptions
- Proof of payment
- Evidence contractor performed SR&ED (not routine services)
- Arm's-length relationship verification
Remember: Only 80% of arm's-length contractor payments are eligible.
Common Issues:
- Vague contracts ("consulting services")
- No detail on work performed
- Non-SR&ED services included (IT support, routine engineering)
Overhead Documentation
Proxy Method (65% of salaries):
- No additional documentation required
- Automatic calculation
Traditional Method (actual overhead):
- Detailed overhead cost records
- Allocation methodology to SR&ED
- Rent, utilities, equipment depreciation
- Reasonable allocation basis
- Consistent year-over-year approach
Recommendation: Use proxy method unless actual overhead significantly exceeds 65% of salaries.
Capital Equipment Records
If claiming SR&ED capital equipment:
- Purchase invoices
- Equipment specifications
- Documentation showing >90% SR&ED use
- Usage logs or records
- Depreciation schedules
Documentation Best Practices
1. Document in Real Time
Do:
- Create records as work progresses
- Date all entries
- Keep working files, not just final versions
- Save iterations and drafts
Don't:
- Reconstruct documentation at year-end
- Create records specifically for CRA
- Discard "failed" work evidence
- Rely on memory
2. Be Specific and Technical
Good: "Tested 8 different CNN architectures with varying layer depths (4-12) and filter sizes (3x3, 5x5, 7x7) on training dataset of 50,000 images. VGG-16 variant with 3x3 filters achieved 87% accuracy vs. baseline 72%."
Bad: "We developed an AI model and tested different approaches until one worked."
3. Show the "Why"
Document not just what you did, but why:
- Why was there technological uncertainty?
- Why did you try approach A before B?
- Why did test X fail and what did you learn?
- Why is the result an advancement?
4. Keep Everything
Retain:
- Design documents and iterations
- Email threads with technical discussion
- Meeting notes
- Test data and results (positive and negative)
- Prototypes, samples, models
- Failed approaches (crucial evidence!)
Don't discard:
- Preliminary versions
- Abandoned approaches
- Failed experiments
- Rough notes
5. Organize Systematically
Create structure:
- Folder per project
- Chronological organization
- Clear file naming conventions
- Index or summary document
- Backup copies
Example structure:
/ProjectAlpha/
/01-Planning/
/02-Design/
/03-Experimentation/
/04-Results/
/05-Documentation/
README.md (project summary)
Documentation Checklist by Phase
During the Project
- Technical objectives documented
- Uncertainties identified and recorded
- Hypotheses documented
- Experimental approach planned
- Time being tracked to project
- Test results recorded as generated
- Iterations documented
- Team meetings noted
At Project Completion
- Summary of advancement achieved
- All results compiled
- Lessons learned documented
- Final technical documentation complete
- Time allocations finalized
- Materials consumed tallied
At Claim Preparation
- Project descriptions drafted
- Technical narratives written (Form T661)
- Financial calculations completed
- All supporting documents organized
- Backup documentation accessible
- Internal review completed
For CRA Review/Audit
- All documents easily retrievable
- Index of available evidence
- Key personnel available for interviews
- Technical explanations prepared
- Financial reconciliations ready
Common Documentation Failures
1. No Contemporaneous Records
Problem: Reconstructing documentation months later Impact: CRA skepticism, reduced credibility Solution: Document as you go, even briefly
2. Too Generic
Problem: "We did R&D on the project" Impact: Doesn't prove SR&ED criteria met Solution: Specific technical details, uncertainties, experiments
3. Missing Time Allocation
Problem: "The team worked on it" Impact: Can't calculate eligible salaries Solution: Track time by project, even roughly
4. No Failure Documentation
Problem: Only showing successful outcomes Impact: Doesn't demonstrate experimentation Solution: Failed attempts are valuable evidence—keep them!
5. Contractor Work Undocumented
Problem: Invoice says "consulting services" Impact: Can't prove SR&ED work performed Solution: Detailed contracts and work descriptions
Building a Documentation System
Simple Approach (Small Companies)
- Project folders for each SR&ED initiative
- Weekly notes documenting technical work
- Time tracking spreadsheet by project
- Email archive of technical discussions
- Test results folder with dated files
Time investment: 1-2 hours/week
Intermediate Approach (Medium Companies)
- Project management software with SR&ED tags
- Time tracking system integrated with payroll
- Document management with version control
- Quarterly SR&ED reviews to ensure capture
- Templates for consistent documentation
Time investment: 2-4 hours/week across team
Enterprise Approach (Large Companies)
- Dedicated SR&ED coordinator or team
- Integrated systems (PLM, ERP, time tracking)
- Formal SR&ED processes with training
- Automated reporting and dashboards
- Regular audits of documentation completeness
Time investment: Embedded in operations
Working with SR&ED Consultants
Professional Services to Help with Documentation
Documentation and Compliance:
- Technical Documentation Services - Transform your records into compelling technical narratives
- Compliance Review Services - Ensure your documentation is CRA-defensible
Building Your System:
- Documentation Consultation - See our guide on finding experts
What Consultants Need from You
- Access to technical personnel for interviews
- Existing documentation (whatever you have)
- Financial records (payroll, invoices, etc.)
- Time allocation information
- Project background and context
What Consultants Provide
- Technical narrative writing
- Documentation organization
- Gap identification
- Best practices guidance
- CRA-compliant formatting
Documentation Handoff
Organize before handing off:
- List of potential SR&ED projects
- Key personnel by project
- Available documentation by type
- Financial records by category
- Prior year claims (if any)
Frequently Asked Questions
How long should I keep SR&ED documentation?
Minimum 7 years from claim filing date (CRA reassessment period). For recurring claims, keep documentation for each year.
What if I didn't document well this year?
Document what you can now, even if after-the-fact. Some documentation is better than none. Implement better practices for next year.
Can I use email as documentation?
Yes! Email threads with technical discussions are valuable contemporaneous evidence. Archive relevant threads by project.
Do I need a formal lab notebook?
Not required unless your field demands it (e.g., pharmaceutical). Any consistent record-keeping system works.
What if my documentation is in another language?
CRA accepts English or French. Other languages may require translation if requested during review.
How detailed do time records need to be?
Detailed enough to support your allocation. Daily time sheets are ideal; weekly summaries are acceptable; annual estimates are risky.
Next Steps
Strong documentation is the foundation of successful SR&ED claims. To build your documentation system:
- Assess current practices against this checklist
- Identify gaps in technical and financial records
- Implement simple improvements (weekly notes, time tracking)
- Train your team on SR&ED documentation importance
- Review quarterly to ensure consistent capture
Get Expert Help with Documentation
If you need professional guidance:
- Technical Documentation Services - Build compelling technical narratives
- Compliance Review Services - Ensure defensible documentation
- Claim Preparation Services - End-to-end claim support
Related Resources
- Complete Guide to SR&ED Tax Credits
- SR&ED Claims Process Step-by-Step
- Common SR&ED Mistakes to Avoid
- Preparing for an SR&ED Audit
Last updated: November 2024. Documentation requirements may vary based on your specific situation. Consult with a qualified SR&ED professional for guidance.