How to Write a Compliant R&D Tax Incentive Plan: A Step-by-Step Guide

Preparing a robust R&D tax incentive plan is crucial for securing your claim and withstanding potential ATO or AusIndustry reviews. A well-structured plan not only helps you receive your tax offset but also serves as valuable documentation for managing your innovation activities throughout the year.

This guide will walk you through the essential components of a compliant R&D plan and show you how to use Avanzu to streamline the entire process.

Why Your R&D Plan Matters

Your R&D plan serves multiple critical purposes:

1. Compliance Documentation: Demonstrates to AusIndustry that your activities meet the legislative requirements
2. Internal Roadmap: Guides your team through planned R&D activities and budget allocation
3. Audit Protection: Provides contemporaneous evidence if your claim is reviewed
4. Budget Management: Helps track spending against projected costs throughout the year
5. Knowledge Management: Documents your technical approach, hypothesis, and learnings

With increasing scrutiny from the ATO and AusIndustry, having a well-prepared plan is no longer optional—it’s essential.

Understanding Core vs. Supporting Activities

Before writing your plan, you must clearly understand the distinction between core and supporting R&D activities, as this fundamentally shapes how you structure your documentation.

Core R&D Activities

Core R&D activities must satisfy all four of these criteria:

1. Unknown Outcome: The outcome cannot be known or determined in advance based on current knowledge, information, or experience
2. Systematic Progression: The activity follows a systematic progression of work based on principles of established science
3. Experimental Process: It proceeds from hypothesis to experiment, observation, evaluation, and logical conclusions
4. New Knowledge: The purpose is to generate new knowledge (including new products, processes, or services)

Example of Core R&D: Developing a new machine learning algorithm to predict crop yields based on soil conditions, where the accuracy of the model and optimal feature selection cannot be known without experimentation.

Supporting R&D Activities

Supporting activities are those that:

• Are directly related to core R&D activities
• Are undertaken for the dominant purpose of supporting the core R&D work

Example of Supporting R&D: Setting up test environments, collecting soil sample data, or creating infrastructure specifically to support the core ML algorithm development.

Important: Routine business activities, even if they support innovation generally, don’t qualify as supporting R&D unless directly tied to a specific core R&D activity.

Step-by-Step: Writing Your R&D Plan

Step 1: Define Your R&D Project

Start with a clear project overview:

Project Title: Be specific and technical

• ❌ “Improving our software”
• ✅ “Development of Predictive Maintenance Algorithm Using IoT Sensor Data and Neural Networks”

Project Description: Explain in 2-3 paragraphs:

• What you’re trying to achieve
• Why current approaches are insufficient
• What makes this R&D (not just development)

Duration: Specify the financial year(s) the project covers

Budget: Provide total estimated R&D expenditure

Step 2: Articulate Your Hypothesis

This is critical and often overlooked. Recent tribunal cases emphasize that your hypothesis must be formed before experiments commence.

Your hypothesis should clearly state:

• What technical uncertainty you’re trying to resolve
• What you believe the outcome might be (but cannot know for certain)
• Why existing knowledge doesn’t provide the answer

Example: “We hypothesize that a convolutional neural network architecture with attention mechanisms will achieve >90% accuracy in detecting crop disease from drone imagery, but we cannot know the optimal network depth, attention mechanism configuration, or training approach without systematic experimentation.”

Step 3: Describe Core R&D Activities

For each core activity, document:

Activity Name: Descriptive and specific

Technical Challenge: What can’t be known in advance?

Current State of Knowledge: What do existing approaches do, and why are they insufficient?

Experimental Approach: How will you systematically test your hypothesis?

• What experiments will you conduct?
• What variables will you test?
• How will you measure success?

Expected Timeline: When will this activity occur?

Allocated Budget: Estimated expenditure for this specific activity

Evidence Collection: How will you document experiments and results?

Step 4: Detail Supporting Activities

For each supporting activity:

Activity Name: Clear description

Purpose: Explicitly state how this directly supports a specific core activity

Relationship to Core R&D: Reference the core activity by name

Allocated Budget: Estimated costs

Important: Only include activities whose dominant purpose is supporting core R&D. General business activities don’t qualify.

Step 5: Document Your Technical Approach

Provide enough technical detail to demonstrate genuine experimentation:

• Methodologies you’ll employ
• Technologies and tools to be used
• Key technical decisions that need experimental validation
• Alternative approaches you’ll test
• Success criteria and metrics

Don’t oversimplify or make it sound routine. The plan should clearly show why the outcome is genuinely uncertain.

Step 6: Identify Team Members and Roles

List key personnel involved in R&D activities:

• Names and roles
• Relevant qualifications
• Specific contributions to R&D work

This helps substantiate salary costs allocated to R&D and demonstrates appropriate expertise.

Step 7: Budget and Expenditure Planning

Break down anticipated costs by category:

Employee Costs:

• Salaries for time spent on R&D
• Include estimates of percentage allocation

Contractor Costs:

• External specialists or consultants
• R&D-specific contract work

Materials and Consumables:

• Items used or transformed during R&D

Depreciation:

• Equipment used predominantly for R&D

Other Eligible Costs:

• Cloud computing for R&D
• Specialized software licenses
• Testing and prototyping materials

Step 8: Risk and Mitigation

Acknowledge technical risks and how you’ll manage them:

• What could prevent you achieving the hypothesis?
• What alternative approaches will you try?
• How will you pivot if initial experiments fail?

This demonstrates genuine experimental uncertainty.

Documentation Best Practices

Contemporaneous Records

Your plan is just the starting point. Throughout the year, maintain:

1. Lab Books or Research Journals: Document experiments as they happen
2. Technical Meeting Minutes: Record discussions about technical challenges and decisions
3. Test Results: Capture experimental outcomes, successes, and failures
4. Progress Reports: Regular updates on R&D progress
5. Email Correspondence: Technical discussions with team members or experts
6. Code Repositories: Version control showing experimental development
7. Design Documents: Technical specifications and architecture decisions

What AusIndustry Looks For

When reviewing your claim, AusIndustry evaluates:

✅ Before Experiments: Was your hypothesis documented before work began?

✅ Genuine Experimentation: Is there evidence of systematic testing and evaluation?

✅ Technical Uncertainty: Is the outcome genuinely uncertain, or is this routine development?

✅ New Knowledge: Are you attempting to create something genuinely new?

✅ Contemporaneous Evidence: Do your records align with what you claimed?

Common Mistakes to Avoid

1. Vague Hypotheses

❌ “We want to make our product better” ✅ “We hypothesize that implementing a GraphQL federation architecture will reduce API latency to <100ms for 95th percentile requests, but the optimal schema design and caching strategy cannot be known without experimental validation”

2. Including Routine Work

Don’t claim activities where the outcome is known or can be achieved using standard approaches. Debugging, UI refinements, and incremental improvements rarely qualify.

3. Retroactive Documentation

Your plan and hypothesis must be documented before or at the start of the R&D work, not months later when preparing your claim.

4. Insufficient Technical Detail

Generic descriptions make claims vulnerable. Provide enough technical depth to demonstrate why the work qualifies as R&D.

5. Poorly Connected Supporting Activities

Supporting activities must be directly tied to specific core activities and undertaken for the dominant purpose of supporting R&D.

Using Avanzu to Manage Your R&D Plan

Avanzu streamlines the entire R&D planning and tracking process:

Create Structured Projects and Activities

• Define your R&D projects with all required details
• Create separate core and supporting activities
• Document hypotheses, technical approaches, and budgets in one place
• Track project timelines and milestones

Allocate Expenditure Throughout the Year

• Automatically import transactions from Xero
• Allocate costs to specific R&D activities as they occur
• Track actual spending against budgeted amounts
• See real-time summaries of R&D expenditure by activity

Real-Time Budget Monitoring

• Monitor spending against your planned budgets
• Identify over/under-allocation before year-end
• Adjust plans based on actual R&D progress
• Ensure you stay within compliance requirements

Generate Comprehensive Reports

• Export detailed R&D plans in Excel format
• Include all activities, budgets, and allocations
• Provide compliant documentation for AusIndustry
• Share with accountants or R&D advisors

Maintain Audit Trail

• Every allocation is time-stamped and tracked
• Activity logs provide contemporaneous evidence
• Transparent transaction history
• Export everything needed for ATO reviews

Timeline for R&D Planning

July-August (Start of Financial Year):

• Draft initial R&D plan for the year
• Document hypotheses for planned projects
• Set up projects and activities in Avanzu
• Brief your team on documentation requirements

Throughout the Year:

• Allocate transactions as they occur
• Update activity descriptions based on actual work
• Document experimental results and technical decisions
• Monitor spending against budgets

April-May (Before Lodgment):

• Finalize all transaction allocations
• Review activity descriptions for accuracy
• Generate comprehensive R&D reports
• Prepare supporting documentation
• Engage R&D advisor for final review

Within 10 Months of Year-End:

• Register with AusIndustry
• Lodge claim with ATO

Conclusion

A well-prepared R&D tax incentive plan is your foundation for a successful claim. It demonstrates compliance, guides your team, protects against audits, and ensures you capture all eligible expenditure throughout the year.

The key is to:

1. Clearly articulate genuine technical uncertainty
2. Document your hypothesis before experimentation begins
3. Distinguish core from supporting activities
4. Maintain contemporaneous records as work progresses
5. Use tools like Avanzu to track everything systematically

Don’t wait until tax time to think about your R&D plan. Start now, document as you go, and maximize your chances of a smooth, successful claim.

---

Ready to create and manage your R&D plan more effectively? Start your free trial with Avanzu and experience streamlined R&D tax incentive management.