The R&D Tax Incentive for software and SaaS companies

Introduction

Software and SaaS companies are often at the heart of genuine innovation. Yet many founders, CTOs, and product leads dismiss the R&D Tax Incentive as something only for lab coats or hard-tech manufacturers. That assumption leaves material funding on the table. The Australian Government’s Research and Development Tax Incentive is designed to reward precisely the kind of systematic experimentation and technical problem-solving that software teams do every quarter. If your business is building, optimising, or hardening a platform in a way that tackles technical uncertainty, you may be eligible for a sizeable offset against your company tax liability or a cash refund.

This guide walks through the practical steps a software or SaaS business should take to prepare a strong, substantiated claim. It is general information and does not constitute tax, financial, or legal advice. You must confirm your own position with a registered tax agent who can review and lodge the claim. The Australian Taxation Office (ATO) and AusIndustry jointly administer the program, and both publish detailed guidance that should be your primary reference.

If you want a plain-English overview of the entire program before diving into the software-specific detail, start with What is the R&D Tax Incentive? A plain-English guide for Australian businesses. Once you’re across the fundamentals, this article will help you map the rules to your engineering roadmap.

Pro tip, Do not self-assess in isolation. The demarcation between routine development and eligible R&D is subtle, and the ATO and AusIndustry increasingly scrutinise software claims. A registered tax agent who understands your codebase is critical.

Prerequisites for claiming the R&D Tax Incentive

Before you get into activity definitions and cost calculations, confirm that your business structure and activities tick the basic eligibility boxes.

Entity and residency requirements

You must be a company incorporated under Australian law or a foreign company that is an Australian tax resident. Sole traders, partnerships, and trusts cannot directly claim the R&D Tax Incentive; the activities must occur in a corporate vehicle. If you operate through a structure that does not qualify, talk to your accountant about restructuring before any claim is prepared.

Carrying on a business

The company must genuinely carry on a business. This is not a high bar for most trading entities, but the ATO looks for more than a passive shell. You need an ABN, ongoing trading activities, and commercial intent. Early-stage SaaS startups still in founder-funded mode can satisfy this test as long as there is evidence of business activity and a path to revenue.

Engaging in eligible R&D activities

This is the crux of the claim. Eligible activities fall into two categories: core R&D activities and supporting R&D activities. Your company must have conducted at least one core R&D activity during the income year. Supporting activities can only be claimed if they directly relate to a core activity. We define both in detail below.

A word on professional advice

The R&D Tax Incentive is jointly administered by the ATO and AusIndustry, and the rules change frequently. For example, announced reforms may lift the refundable-offset turnover threshold from $20 million to $50 million, but you must verify the current income year’s thresholds with your tax agent. For an overview of how changing thresholds can affect growing companies, see GrantsMAX for growing companies.

If you’ve never claimed before, the first lodgment can feel overwhelming. GrantsMAX for first-time claimants explains how the process works and what to expect.

Step 1: Understand what the ATO and AusIndustry mean by ‘R&D’ for software

The statutory definition of R&D centres on systematic, experimental activities undertaken for the purpose of generating new knowledge. The outcome must be uncertain, you cannot know or determine the result in advance through current knowledge, information, or experience. That requirement trips up a lot of software teams.

The core test: experimental activities

For a software activity to qualify as core R&D, you must be conducting experiments whose outcome cannot be predicted. You are testing a hypothesis. The experiment must be systematic, not ad hoc debugging or trial-and-error println checks. Examples often accepted by AusIndustry include:

• Designing and testing a novel algorithm where standard libraries are inadequate
• Experimenting with new cryptographic protocols to improve security beyond off-the-shelf implementations
• Developing a custom compression or indexing scheme to handle data volumes that break existing tools
• Prototyping a distributed consensus mechanism for a SaaS back-end under extreme latency constraints

The key is that the technical challenge should be both significant and unresolved before you begin. If a competent professional in the field could solve the problem by applying established practices, the activity is unlikely to be eligible.

How software and SaaS meet the test

Software companies often iterate rapidly, but iteration alone is not R&D. The work must involve genuine technical uncertainty. For example, building a standard CRUD (Create, Read, Update, Delete) dashboard for an admin panel, however elegant, is not R&D. But if you are trying to build a real-time, multi-tenant analytics engine that must handle 100 million events per hour with sub-second query latency on commodity cloud instances, you are probably confronting problems that existing architectures do not solve out of the box. Document that uncertainty.

Read the official software development sector guide

AusIndustry publishes a sector guide that every software founder and CFO should read: Software development sector guide for the R&D Tax Incentive. It provides concrete examples of activities that may and may not qualify. We cite it repeatedly in this article because it is the most prescriptive government resource available. Do not skip it.

Warning, The ATO and AusIndustry both review software claims closely. If your only evidence is a Jira ticket saying “build feature X,” you are unlikely to survive scrutiny. Step 3 below addresses substantiation in depth.

Step 2: Separate core R&D activities from supporting activities

Every eligible claim must have at least one core R&D activity. Supporting activities are those that directly relate to a core activity and are undertaken for the dominant purpose of supporting that R&D. If a core activity fails the experimental test, its supporting activities automatically fall away.

SaaS examples: cloud-native architecture vs standard deployment

Consider this common scenario: your team designs a new event-driven, serverless architecture to handle unpredictable burst workloads in a multi-tenanted SaaS product. The design involves experimenting with message-routing patterns, state management across ephemeral functions, and cold-start mitigation that has no established solution. That design and prototyping work may be core R&D. The supporting activities might include:

• Setting up temporary test environments in AWS or Azure
• Writing integration scripts to load test data
• Documenting experiment outcomes
• Conducting peer review sessions of the experimental design

By contrast, rolling out a standard Terraform module for a well-understood, three-tier web application is not R&D. You are applying known practices, not experimenting.

Supporting activities that may be eligible

Supporting activities can cover a wide swath of the development lifecycle as long as they are necessary for, and directly linked to, the core R&D. Common examples in software and SaaS include:

• Code reviews and technical discussions that directly shape the experimental path
• Writing test harnesses and scripts specifically to evaluate the experimental outcome
• Controlled production roll-outs to validate the novel solution under load (provided the roll-out is part of the experiment, not business-as-usual deployment)
• Security and performance testing of the novel module

Activities that are unrelated to the core experiment, routine sprint planning, stand-ups, general infrastructure maintenance, should be excluded.

Pro tip: document the hypothesis

Before starting any sprint you suspect may contain R&D, write a one-paragraph hypothesis. Something like: “We hypothesise that a bloom-filter-based duplicate detection layer can reduce deduplication latency by 80% compared with our current relational approach.” Then record the experiment, the results, and the decision made. This practice not only supports an R&D claim but also sharpens your engineering discipline.

Pro tip, The distinction between core and supporting activities is not always intuitive. For an interactive assessment of eligibility that reads your accounting data, explore Eligibility Assessment & Risk Flags. It flags areas a reviewer would scrutinise before your accountant lodges.

Step 3: Build a contemporaneous substantiation trail

Substantiation is the single greatest point of failure for software claims. Unlike laboratory notebooks or prototype photographs, software records are often scattered across GitHub, Slack, Confluence, Jira, email, and cloud logs. The ATO requires evidence that is contemporaneous, created at the time the activity was undertaken, and clearly linked to the R&D.

What strong records look like

A robust evidence pack for a software or SaaS R&D claim might include:

• Experiment design documents: One-pagers or internal wiki pages describing the technical hypothesis, the success criteria, and the planned method
• Version-controlled code: Git commits that reference the experiment (not generic features)
• Test results and logs: CI/CD outputs, load-test reports, profiling data
• Technical meeting notes: Detailed minutes from architecture review sessions where experimental design was debated
• Timesheet or story-point allocations: Contemporaneous records showing which staff spent time on the R&D activity and when
• Email and message threads: Discussions where technical uncertainty was explicitly acknowledged

Sworn statements or post-facto recollections are weak evidence. AusIndustry and the ATO want to see that a genuine experiment occurred, not a tidy narrative written 11 months later.

GrantsMAX and the audit-ready evidence trail

Gathering, indexing, and cross-referencing these records manually can consume weeks of engineering time. Audit-Ready Evidence Trail explains how GrantsMAX ties each activity and cost line to its source, emails, invoices, timesheets, and more, producing an evidence index your accountant can rely on. The system does not create evidence; it organises what already exists and flags gaps.

Pro tip, If you use Xero, MYOB, or QuickBooks, the accounting data often contains the payroll and invoice records that map staff time and cloud costs to R&D activities. See how GrantsMAX for SMBs on cloud accounting reads that data, read-only, to surface eligible expenditure.

Step 4: Tally eligible R&D expenditure

Once you have identified the core and supporting activities, you can calculate the notional R&D deduction that flows into the tax offset calculation. This is where your registered tax agent’s involvement becomes essential, because the ATO has detailed rules about what can and cannot be included.

Labour, overhead, consumables, cloud

Common expenditure items for software and SaaS R&D include:

• Salary and wages paid to employees for the time they spent on eligible R&D activities. You must be able to show a reasonable allocation of time, typically via timesheets or work logs.
• On-costs such as superannuation, workers’ compensation, and payroll tax that relate directly to R&D labour.
• Consumables, cloud credits, SaaS subscriptions used exclusively or proportionally for the R&D, and other materials consumed during testing.
• Overhead expenses such as rent for office space used for R&D, or electricity to run test equipment, can be included under prescribed rules.
• Contract expenditure for external contractors who performed eligible R&D activities under your direction.

The cost of developing a product feature that later generates revenue is not R&D expenditure unless that development involved eligible R&D activities. Similarly, post-release maintenance, bug fixes, and customer support are generally excluded.

Warning, Do not double-count expenditure that has already been claimed as a different tax deduction. The R&D Tax Incentive interacts with other deductions, and getting the crossover wrong can trigger an ATO review. Always have your accountant validate the calculation.

For an overview of how GrantsMAX pulls a cost structure directly from Xero and links it to activity narratives, see AI Application Pack Drafting.

Step 5: Register with AusIndustry

You cannot claim the R&D Tax Incentive in your tax return unless you have registered eligible R&D activities with AusIndustry. Registration is an online process via the Department of Industry, Science and Resources portal and must be completed before you lodge your company tax return, and within 10 months after the end of your income year.

Timing and key requirements

The registration asks for:

• A description of each core R&D activity
• The expected total R&D expenditure for the income year
• An indication of the category (core or supporting) for each activity

The descriptions should be plain yet precise. They must capture the technical uncertainty, the experimental approach, and the new knowledge you sought. The AusIndustry registration number must be carried into your company tax return schedule.

Pro tip, Do not view registration as a rubber stamp. If your description is vague or boilerplate, AusIndustry may later question whether the work was genuinely R&D. Align the wording with the contemporaneous evidence you collected in Step 3.

Step 6: Prepare a complete, evidence-backed application pack

The claim ultimately turns on the quality of the pack your accountant lodges. A strong pack typically contains:

• Project narratives: A plain-English explanation of each core R&D project, including the technical challenge, the hypothesis, the experiments conducted, the outcomes, and why the work was uncertain
• Activity schedules: Lists of core and supporting activities mapped to staff, time periods, and expenditure
• Cost worksheets: A detailed breakdown of labour, consumables, overhead, and contract expenditure with clear allocation methodologies
• Supporting evidence index: A schedule that links each line item to the contemporaneous records described in Step 3

The narrative must connect the expenditure to the experimental activities. It should be technical enough to convince a peer but clear enough for a non-engineer reviewer.

How GrantsMAX drafts the pack

AI Application Pack Drafting turns your business data into a complete, evidence-backed pack. From the R&D activity and project narratives to the cost structure pulled from Xero, the system produces a draft in hours, not weeks. Your registered tax agent then reviews, refines, and lodges.

Pro tip, Many claims fail because the narrative treats the software itself as a product rather than describing the underlying experimental effort. Focus on the technical uncertainty resolved, not the feature shipped.

Step 7: Engage a registered tax agent for review and lodgment

The R&D Tax Incentive is a tax measure administered by the ATO. Only a registered tax agent can lawfully charge a fee for preparing and lodging a tax return that includes an R&D claim. Moreover, the Tax Practitioners Board holds agents to professional standards that include verifying the claim’s reasonableness.

Why the accountant’s role matters

Your engineer or founder cannot simply sign off the R&D schedule on a trust basis. The tax agent must be satisfied that the expenditure claimed relates to eligible activities and is substantiated. The agent signs the return and takes professional responsibility. This layer of independent review is a protection for your business, not a formality.

The GrantsMAX accountant review workflow

Accountant Review & Lodge Workflow explains how the platform prepares the pack and hands it to your registered accountant in a shared workspace. The accountant can review, adjust, and comment before final lodgment. The business owns the claim at all times. GrantsMAX does not lodge, file, or guarantee any outcome.

Pro tip, Choose an accountant who understands software. A generic tax agent may not recognise the distinction between routine feature development and an eligible experiment. Many R&D-active startups work with firms listed on the GrantsMAX for R&D-active startups page.

Step 8: Maintain records and prepare for potential review

Your obligations do not end when the return is lodged. The ATO and AusIndustry may review claims for up to four years (or longer if fraud or evasion is suspected). You must retain all records that support the claim, contemporaneous evidence, registration number, the tax agent’s working papers, and the final pack, for at least five years.

Document retention and ATO reviews

The ATO publishes its review and audit approach on its website. Reviews can be triggered by data-matching, revenue-correctness checks, or a spike in claimed expenditure. If you receive a review notice, your registered tax agent will manage the engagement, but the records must come from you. A disorganised or incomplete trail is the quickest way to see legitimate expenditure disallowed.

Internationally, the importance of documentation is underscored by court cases such as Siemer Milling Co. v. United States, where a U.S. federal court closely examined contemporaneous records to determine the validity of a research credit claim. While the legal framework differs, the principle is universal: weak records lead to weak outcomes.

Pro tip, Schedule a quarterly “evidence sweep” with your engineering leads. Spend 30 minutes pulling the key documents from that quarter into a dated folder. This small habit can save enormous stress if a review arrives.

Summary and key takeaways

Claiming the R&D Tax Incentive for a software or SaaS company is not about writing code in isolation; it is about running systematic experiments to solve genuine technical uncertainty. Here are the core points to remember:

• Core vs supporting: Only experimental activities where the outcome could not be known or determined in advance qualify as core R&D. Supporting activities must relate directly to those core experiments.
• Software specifics: The Software development sector guide for the R&D Tax Incentive published by AusIndustry is your primary compliance roadmap. Read it before you write a single word of a claim.
• Substantiation is everything: Contemporaneous records, experiment logs, code commits, meeting notes, timesheets, are not optional. They are the foundation of a defensible claim. For an audit-ready index, see Audit-Ready Evidence Trail.
• Get the right numbers: Labour, cloud costs, and on-costs can all be included if properly allocated. Your accounting system (Xero, MYOB, QuickBooks) often holds the raw data. GrantsMAX for SMBs on cloud accounting explains how that data feeds the claim.
• Register on time: AusIndustry registration must be completed before you lodge the tax return and within 10 months of year-end. Late registration is generally not accepted.
• Accountant involvement is mandatory: Only a registered tax agent can prepare and lodge the claim. Accountants who white-label the workflow can manage multiple client claims efficiently through Annual Refresh & Accountant Channel.
• Audits happen: The ATO and AusIndustry review software claims. Keep your records for at least five years. For a complete view of the accountant-led lodgment process, see Accountant Review & Lodge Workflow.

We have not set out every nuance. The rules are detailed and the consequences of a poorly prepared claim can be severe. Before you proceed, engage a registered tax agent who routinely handles software R&D claims. If you are a founder or CFO evaluating whether your development pipeline is worth pursuing, start by exploring how GrantsMAX for founders and CFOs surfaces eligibility and prepares an evidence-backed pack.

Join the GrantsMAX waitlist

GrantsMAX is building the AI agent that reads your accounting data, discovers the government grants and R&D tax incentives your software or SaaS business may be eligible for, and prepares a complete, evidence-backed claim pack for your registered tax agent to review and lodge. We never lodge, file, or guarantee an outcome, we prepare the pack. You own the claim. The accountant lodges.

If you would like early access, join the waitlist at www.grantsmax.com. We publish accurate, practical guidance on the R&D Tax Incentive, EMDG, and Australian government grants regularly. Stay informed and be ready when the next income year opens.