R&D Tax Incentive for Software Companies in Australia
Does your software development qualify for a 43.5% refundable tax offset? This guide explains what activities are eligible, how much you can claim and the common mistakes that trigger AusIndustry reviews.
Australia’s R&D Tax Incentive is one of the most valuable tax offsets available to software companies – yet most founders either do not know they qualify or leave significant money on the table by claiming too little. Worse, some claim too much and face costly compliance reviews from AusIndustry.
The program offers eligible companies a tax offset of up to 43.5% on qualifying R&D expenditure. For a software company spending $300,000 on eligible research and development, that can mean $130,500 returned as a cash refund – not a deduction, a refund.
But software R&D is one of the most scrutinised categories in the program. AusIndustry and the ATO know that the line between genuine research and routine development is blurry in software. Getting your claim right – with proper documentation and a clear understanding of what qualifies – is essential.
This guide explains how the R&D Tax Incentive applies specifically to software companies, what activities qualify, what does not, and how to build a claim that withstands review.
Does Software Development Qualify for the R&D Tax Incentive?
Yes – but not all software development qualifies, and this is where most companies get it wrong.
The R&D Tax Incentive is governed by the Industry Research and Development Act 1986 and administered jointly by AusIndustry (which assesses eligibility) and the ATO (which processes the tax offset). To qualify, your activities must meet the definition of core R&D activities or supporting R&D activities under the legislation.
The critical requirement is technical uncertainty. Your work must involve generating new knowledge where the outcome cannot be known in advance by a competent professional in the field. If a skilled software engineer could reasonably predict the result before starting the work, it is not R&D under the program.
Software development qualifies when it involves experimentation to resolve genuine technical challenges. It does not qualify when it involves applying known techniques to build products – even if those products are innovative from a commercial perspective.
This distinction is the single most important concept for software companies to understand. Commercial innovation and technical R&D are not the same thing.
Core R&D Activities in Software – What Qualifies
The legislation defines core R&D activities as experimental activities whose outcome cannot be known or determined in advance on the basis of current knowledge, information or experience. They must be conducted for the purpose of generating new knowledge.
For software companies, the following categories of work commonly qualify.
Algorithm Development
Developing new algorithms or computational methods where performance, accuracy or feasibility cannot be determined in advance. This includes novel search algorithms, custom compression methods and matching algorithms where known approaches produce unacceptable results.
Novel Architecture or System Design
Designing system architectures that address technical challenges beyond current approaches. This includes distributed database designs, real-time event processing pipelines and novel microservices orchestration for failure modes that existing patterns cannot handle.
Performance Optimisation Beyond Known Methods
Optimising performance beyond what established techniques can achieve. Common in high-frequency trading, real-time analytics and large-scale data processing where standard database optimisation, caching or memory management techniques are insufficient.
AI and Machine Learning Development
AI and ML development frequently qualifies because it inherently involves experimentation with uncertain outcomes. This includes custom neural network architectures, novel feature engineering, reinforcement learning systems and techniques to reduce model bias beyond existing methods.
Cybersecurity Research
Developing new security mechanisms, encryption approaches or threat detection methods involving genuine technical uncertainty. This includes novel intrusion detection systems, new cryptographic protocols and privacy-preserving computation methods.
Supporting R&D Activities
Work directly related to core R&D that would not have been done otherwise. This includes R&D-specific testing and QA, data collection and preparation, technical documentation, prototyping and specialised cloud environments for experiments.
What Does NOT Qualify as Software R&D
Understanding what falls outside the program is just as important as knowing what qualifies. AusIndustry specifically scrutinises software claims, and the following activities are consistently excluded.
- Routine coding and bug fixes – Writing code to implement a design that is already understood, fixing defects or maintaining existing systems
- UI/UX design without technical uncertainty – Designing interfaces and conducting usability testing (unless novel interaction methods require experimentation)
- System administration and DevOps – Server setup, CI/CD pipelines, cloud infrastructure management and monitoring
- Deploying existing frameworks – Using React, Django, TensorFlow or integrating third-party APIs is not R&D, even in a novel commercial context
- Commercial software customisation – Configuring Salesforce, SAP or Xero integrations, regardless of complexity
- Market research and commercial experimentation – A/B testing, market validation and business model experimentation
The key test: If a competent software engineer could predict the outcome before starting the work, it is not R&D – no matter how complex or commercially valuable the work may be.
The Technical Uncertainty Test – Explained for Developers
The concept of “technical uncertainty” is the foundation of every R&D Tax Incentive claim. AusIndustry applies this test rigorously.
The Competent Professional Test
The legislation asks: could a competent professional in the relevant field determine the outcome in advance, based on current knowledge, information and experience?
A “competent professional” is not a graduate developer. It is someone with current, relevant expertise in the specific technical domain. If such a person would say “I know how to solve this” before the work begins, there is no technical uncertainty. If they would say “I am not sure this approach will work – we need to experiment” then technical uncertainty exists.
Uncertainty vs Routine Work – Examples
| Uncertain (Likely Qualifies) | Routine (Does Not Qualify) |
|---|---|
| “We need to process 10M events/sec with sub-ms latency. Three approaches have failed. We are experimenting with a custom in-memory data structure.” | “We need to build a REST API for our mobile app.” |
| “Our ML model plateaus at 80% accuracy. The business requires 95%. We are experimenting with novel architectures.” | “We are migrating from a monolith to microservices.” |
| “We need distributed consistency guarantees that existing consensus protocols cannot provide for our use case.” | “We need to improve page load time by implementing caching.” |
The Hypothesis-Experiment-Evaluation Cycle
Genuine R&D follows a structured process. AusIndustry expects evidence of:
- Hypothesis – A clear statement of the technical question you are trying to answer
- Experiment – A systematic approach to testing the hypothesis
- Evaluation – An assessment of results, including failed experiments
- Iteration – Refinement based on what you learned
If your development process does not include this cycle – if you simply build features to a specification – it is unlikely to qualify as R&D.
How Much Can You Claim?
Companies With Turnover Under $20 Million
You receive a 43.5% refundable tax offset on eligible R&D expenditure. This is the company tax rate (25%) plus an 18.5% premium.
Because this offset is refundable, you receive the benefit even if your company is in a tax loss position. This makes the program particularly valuable for startups and growth-stage software companies that are not yet profitable.
Companies With Turnover of $20 Million or More
You receive a non-refundable tax offset equal to your company tax rate plus a premium based on R&D intensity:
| R&D Intensity | Premium Above Company Tax Rate |
|---|---|
| Up to 2% | 8.5% |
| Over 2% | 16.5% |
There is a $150 million annual cap on eligible R&D expenditure per entity.
Worked Example – Software Startup
Consider a Sydney-based SaaS company with 8 developers and annual turnover of $4 million.
| Item | Amount |
|---|---|
| Total developer salaries | $500,000 |
| Eligible R&D salaries (60% of team time) | $300,000 |
| Cloud computing costs for R&D | $30,000 |
| Contractor costs for specialist R&D | $20,000 |
| Total eligible R&D expenditure | $350,000 |
| R&D Tax Offset (43.5%) | $152,250 |
If the company is in a tax loss position (common for startups), the full $152,250 is received as a cash refund from the ATO. This is the refundable offset in action – and it is why the R&D Tax Incentive is one of the most important non-dilutive funding sources for early-stage software companies.
For a profitable company already deducting the R&D expenditure at the 25% company tax rate, the net additional benefit is $64,750 – the difference between the 43.5% offset and the 25% standard deduction.
How to Document Your Software R&D
Documentation is where software R&D claims succeed or fail. AusIndustry has increasingly focused on contemporaneous records, and software companies have a significant advantage – your development tools already capture much of what is needed.
The Contemporaneous Records Requirement
Records must be created at the time the R&D is conducted, not retrospectively when preparing a claim. AusIndustry checks metadata, timestamps and document histories to verify records are genuinely contemporaneous.
What AusIndustry Looks For
- Technical uncertainty – What was unknown? Why could a competent professional not determine the outcome in advance?
- Systematic progression – How did you approach the problem? What experiments did you conduct?
- Evaluation of outcomes – What did you learn? How did results inform the next experiment?
- New knowledge generated – What did you discover that was not previously known?
Using Your Existing Development Tools as Evidence
Software companies produce extensive records through their normal workflow:
- Git commits and pull requests – Commit messages referencing experimental approaches, branches indicating R&D work, PR discussions analysing results, code reviews discussing failures and successes
- Jira, Linear or project management tickets – Tickets tagged as R&D, descriptions articulating technical challenges, comments documenting hypotheses and results, time logs
- Technical specs and design documents – Architecture decision records (ADRs), technical RFCs, performance benchmarks, research notes
- Communication records – Slack threads discussing technical challenges, meeting notes from R&D planning sessions
Hypothesis Documentation Template
For each core R&D activity, maintain a record of:
| Element | What to Record |
|---|---|
| Technical question | What are you trying to determine? |
| Why it is uncertain | What existing knowledge or approaches fall short? |
| Experimental approach | How will you test your hypothesis? |
| Results and analysis | What happened? Did it work? Why or why not? |
| New knowledge | What did you learn that was not previously known? |
This does not need to be a formal lab notebook. A well-structured Confluence page, a detailed Jira epic or a series of well-documented pull requests can serve the purpose – as long as the information is captured contemporaneously.
Common Mistakes Software Companies Make
After advising software companies on R&D claims for years, we see the same mistakes repeatedly. Avoiding these will strengthen your claim and reduce the risk of an adverse finding.
1. Claiming All Developer Salaries
Not all development is R&D. Most companies find 30-70% qualifies. Claims for 100% attract scrutiny and likely adverse findings. Implement time tracking that separates R&D from BAU development.
2. No R&D/BAU Separation
When R&D and production work share the same Jira board and codebase, it becomes difficult to demonstrate which activities involved genuine uncertainty. Use distinct labels, epics or boards for R&D.
3. Poor Documentation
“We did the R&D but we did not write it down” is not viable. Without contemporaneous records, AusIndustry will reject your claim regardless of the quality of your actual R&D work.
4. Missing the Registration Deadline
You must register with AusIndustry within 10 months of the financial year end. For FY2025-26, the deadline is 30 April 2027. Missing it means losing the entire claim for that year.
5. Not Tracking Time Properly
“We estimate about 50% was R&D” is weak. Use time-tracking tools or weekly R&D time allocations. Even a simple weekly breakdown of hours between R&D and non-R&D work is sufficient.
6. Confusing Commercial and Technical Innovation
Your product may be commercially innovative, but the test is whether the technical outcome was uncertain – not whether the commercial outcome was uncertain. Focus claims on technical challenges, not business value.
The Claim Process Step by Step
Filing an R&D Tax Incentive claim involves two agencies and several deadlines.
Step 1 – Conduct and Document Your R&D (Ongoing)
Throughout the financial year, conduct your R&D activities and maintain contemporaneous documentation. Track time, record hypotheses and experiments, and keep technical records.
Step 2 – Register With AusIndustry
Register your R&D activities with AusIndustry within 10 months of the end of the financial year. For FY2025-26, the deadline is 30 April 2027.
The registration requires you to describe each core R&D activity (including technical uncertainty and experimental approach), supporting activities, the knowledge gap and outcomes (including failures).
Step 3 – Calculate Eligible Expenditure
Calculate eligible R&D expenditure including staff costs (salaries, super and on-costs for R&D time), contractor costs, materials and consumables (cloud computing, hardware, specialised licences) and a reasonable apportionment of overheads.
Step 4 – Lodge Your Company Tax Return
Include the R&D Tax Incentive schedule in your company tax return. If your company has turnover under $20 million and is in a tax loss, the refundable offset is typically paid within a few weeks of assessment.
Step 5 – Maintain Records for Audit
Keep all R&D documentation for at least five years after the claim. The ATO can review claims within this period, and AusIndustry can issue findings at any time.
Frequently Asked Questions – Software R&D Tax Incentive
Does building a SaaS product qualify for the R&D Tax Incentive?
Building a SaaS product can partially qualify. The portions of development that involve genuine technical uncertainty – novel algorithms, experimental architectures, performance challenges beyond known solutions – are eligible. Standard product development work such as building CRUD interfaces, integrating payment gateways or implementing user authentication using known methods does not qualify. Most SaaS companies find that 30-60% of their development work involves qualifying R&D.
Can startups claim the R&D Tax Incentive?
Yes, and startups benefit the most. Companies with aggregated turnover under $20 million receive a 43.5% refundable tax offset. Because it is refundable, pre-revenue and loss-making startups receive a cash payment from the ATO rather than just a tax reduction. This makes the R&D Tax Incentive one of the most important non-dilutive funding sources for Australian tech startups. If you are also raising capital, learn about ESIC tax concessions for your investors and ESOP startup concessions for employee equity.
What is the difference between an R&D tax offset and a tax deduction?
A tax deduction reduces your taxable income, saving you tax at your company tax rate (25% for base rate entities). A tax offset directly reduces the tax you owe – or, if refundable, is paid to you as cash. The R&D Tax Incentive provides an offset at 43.5% for small companies, which is 18.5 percentage points more generous than a standard deduction. For a $100,000 R&D claim, a deduction saves $25,000 in tax, while the refundable offset returns $43,500.
Can I claim cloud computing costs (AWS, Azure, GCP) as R&D expenditure?
Yes, but only the portion used for R&D activities. If you use AWS for both production workloads and R&D experiments, you must apportion the costs. Best practice is to use separate cloud accounts or resource tags for R&D workloads so you can clearly identify and substantiate the R&D portion. General production hosting costs do not qualify.
How far back can I claim the R&D Tax Incentive?
You can amend prior-year tax returns to include R&D claims, subject to the ATO’s standard amendment periods (generally two to four years). However, you must have registered the R&D activities with AusIndustry within 10 months of the end of the relevant financial year. If you missed the AusIndustry registration deadline, the claim for that year is lost.
What happens if AusIndustry audits my claim?
AusIndustry conducts “findings” rather than audits. They review your registered activities to assess whether they meet the legislative definition of R&D. If they issue an adverse finding, the claimed activities are deemed not to be R&D, and the ATO will reassess your tax return to remove the offset. This can result in a tax debt plus interest. Having strong contemporaneous documentation is your best defence.
Can I claim R&D for work done by overseas contractors?
R&D conducted overseas can only be claimed if approved in advance through AusIndustry’s Overseas Finding process. The activities must be unable to be conducted in Australia for specified reasons (e.g. access to specific facilities or expertise not available locally). Work done by offshore teams for cost reasons does not qualify. Domestic R&D by Australian-based contractors is claimable without additional approvals.
Do I need to succeed for the R&D to qualify?
No. Failed experiments are valid R&D – in fact, they are expected. The purpose of R&D is to generate new knowledge, and learning that an approach does not work is genuine new knowledge. What matters is that there was genuine technical uncertainty at the outset and that you conducted a systematic investigation. If every experiment succeeds, AusIndustry may question whether genuine uncertainty existed.
How does the R&D Tax Incentive interact with ESIC and ESOP concessions?
The R&D Tax Incentive, Early Stage Innovation Company (ESIC) tax concessions and Employee Share Option Plan (ESOP) concessions are separate programs that work together. ESIC provides tax incentives for investors in qualifying early-stage companies. ESOP provides tax concessions for employees receiving equity. A company can benefit from all three simultaneously – the R&D offset reduces the company’s tax burden, ESIC incentivises investment, and ESOP helps attract talent. Learn more about ESIC tax concessions and ESOP startup concessions.
When should I engage an R&D tax adviser?
Ideally, engage an adviser before you start claiming – or at minimum, before your first AusIndustry registration. An R&D tax specialist can help identify eligible activities you may have overlooked, structure documentation processes, calculate expenditure correctly and prepare registrations that withstand scrutiny. The cost of specialist advice typically pays for itself many times over through larger, more defensible claims.
Related R&D Tax Insights
Talk to an R&D Tax Specialist
Prime Partners has a dedicated R&D Tax Incentive advisory practice that works with technology and innovation-driven companies. We combine deep tax expertise with genuine understanding of software development – so we can identify every eligible activity while building claims that are robust under review.
Whether you are a startup making your first R&D claim or an established software company looking to optimise an existing program, we can help you maximise the benefit while managing compliance risk.
If you are raising capital, ask about ESIC tax concessions for your investors. Using equity to attract developers? Our ESOP startup concessions advisory can help.
This guide is current as at March 2026 and is based on the Industry Research and Development Act 1986 and current AusIndustry guidance. It is general information only and does not constitute tax or legal advice. Contact your adviser for guidance specific to your circumstances.
Further reading: R&D Tax Incentive – business.gov.au | R&D tax incentive – ATO