The R&D tax incentive portal is really two connected systems: AusIndustry's portal for registering your R&D activities, and the ATO's process for lodging the financial part of the claim. In 2023-24, 13,901 companies used the AusIndustry customer portal, covering $17.7 billion in estimated R&D expenditure, so if you're sorting this out near EOFY, you're not alone.
A familiar startup scenario goes like this. The founders know the product team has done real technical work. The finance lead knows there may be an R&D claim. Then someone opens the portal and realises it isn't just a form. It asks for core activities, supporting activities, dates, costs, and technical detail that can stand up later if the claim is reviewed.
That's where many first-time claims go sideways. The portal helps you submit, but it doesn't build the evidence trail for you. For software companies especially, the critical work is tying code, tickets, experiments, and spend back to technical uncertainty and new knowledge in a way that's defensible. If you're trying to understand the process and avoid avoidable mistakes, start with ClaimKit's overview of the process.
Table of Contents
- Your Guide to the Australian R&D Tax Incentive Portals
- What Are the R&D Tax Incentive Portals
- How Do I Access and Prepare for the Portals
- What Are the Critical Deadlines and Timelines
- How Do I Build an Evidence-Backed Claim
- What Are My Options for Preparing and Lodging a Claim
- Frequently Asked Questions About the R&D Portals
Your Guide to the Australian R&D Tax Incentive Portals
If you're a founder or finance lead trying to work out the R&D tax incentive portal, the key point is simple. You're dealing with one system to register activities and another to complete the tax side of the claim. Confusing those steps creates delays, and weak preparation creates risk.
For startup teams, the hardest part usually isn't opening the portal. It's knowing what the government is asking you to prove. A software team may have strong engineering work in GitHub, Jira, Linear, Notion, and Xero, but that still needs to be translated into a compliant registration and a supportable financial claim.
Practical rule: treat the portal as a submission gateway, not as your documentation system.
A good claim usually comes together in this order:
- Confirm eligibility early: Work out whether the project involved technical uncertainty, experimentation, and a genuine attempt to generate new knowledge.
- Gather records before drafting: Pull engineering logs, issue histories, meeting notes, invoices, payroll data, and contractor records before anyone starts writing.
- Separate technical and financial work: Your technical narrative should explain the R&D activities. Your financial records should show which costs were incurred and why they relate to those activities.
- Work backwards from the deadline: EOFY comes quickly. Portal access, internal approvals, and adviser reviews often take longer than founders expect.
The founders who handle this best don't wait for tax return time. They start building a record while the work is still happening, especially when product and engineering teams are moving fast.
What Are the R&D Tax Incentive Portals
Many founders talk about “the portal” as if it's one screen and one submission. It isn't. Think of it more like a permit plus an expense claim. First, you register the R&D activities with AusIndustry. Then you complete the financial claim through the tax process with the ATO.
Two portals, two jobs
The AusIndustry portal is where you describe the activities themselves. This is the part that asks what you were trying to solve, what technical uncertainty existed, what experiments you ran, and which activities were core versus supporting. That's the registration step.
The ATO side is where the financial part is reflected through your company tax process. In practice, founders often think the tax schedule is the whole claim, but it can't stand on its own. The activity registration drives everything that follows.
A simple way to view it:
| Portal | Main purpose | What you prepare |
|---|---|---|
| AusIndustry | Register eligible R&D activities | Technical narrative, activity descriptions, project framing |
| ATO | Lodge the financial side of the claim | Eligible expenditure, tax schedules, company tax return inputs |
That distinction matters because good finance data can't rescue a weak technical registration, and a strong technical story can't rescue poor cost substantiation.
Why the digital shift matters
The current setup isn't optional. The AusIndustry customer portal launched on 5 July 2021, replacing the old Smart Form PDF process and making digital submission mandatory, with more detailed descriptions required for core R&D activities and supporting R&D activities as explained in this overview of the 2021 portal changes.
That change pushed founders to provide more depth up front. For startups, that's mostly a good thing. It forces clearer thinking about what actually qualifies, but it also exposes vague claims very quickly.
If you want a plain-English background on who's involved and how claims are prepared, ClaimKit's about page gives a useful snapshot of the newer software-assisted model alongside expert review. For the official government program page, use the Australian Government's R&D Tax Incentive information.
How Do I Access and Prepare for the Portals
The first hurdle is rarely technical eligibility. It's access. Many teams leave login setup too late, then discover a director needs to authenticate properly before anyone can draft or submit.
Start with access before you need it
The portal requires secure authentication through an AUSkey legacy pathway or a RAM-linked MyGovID arrangement, depending on your setup. In practice, startups should make sure a director's identity is linked correctly to the company and that any nominated tax agent relationship is sorted well before the submission window gets tight.
This isn't glamorous work, but it prevents the classic late-April scramble where the finance lead has the documents but not the permissions.
Before anyone logs in to draft the registration, check these basics:
- Director access is active: The director who needs to approve or authorise the process should be linked properly to the entity.
- Agent authority is current: If an accountant or adviser is helping, make sure the relationship is established in the system rather than assumed.
- Entity details match records: Company name, ABN, year end, and contact details should line up across your corporate and tax records.
Prepare the technical substance first
Once access is sorted, substantive preparation begins. Eligible activities must be experimental, have outcomes that can't be known in advance based on current knowledge, generate new knowledge, and be supported by good contemporaneous project documentation, as outlined in Bentleys' explanation of R&D Tax Incentive eligibility.
That means you should be able to answer questions like:
- What technical problem were we trying to solve?
- Why couldn't the answer be known in advance?
- What hypotheses or approaches did the team test?
- What did we learn from failed or partial attempts?
- Which records were created while the work was happening?
For software startups, the portal is much easier to complete when engineering leads prepare short internal summaries for each project. Not marketing summaries. Technical ones. A sentence or two on the uncertainty, the proposed method, the iterations, and the result is often enough to create a strong drafting base.
A founder's best evidence usually already exists. It's just scattered across product, engineering, and finance tools.
A useful explainer on the process is below if your team wants a quick walkthrough before drafting.
What founders can do this week
If you want momentum without turning this into a month-long side project, start with a tight working session.
- List candidate projects: Pull the software, platform, infrastructure, or product initiatives where the team faced genuine technical uncertainty.
- Nominate one technical owner: Usually an engineering manager, CTO, or senior developer who can explain what was attempted and why.
- Collect live records: Export Jira or Linear tickets, GitHub pull requests, architecture notes from Notion, and spend records from Xero.
- Mark non-R&D work early: Feature polish, routine bug fixes, and standard implementations should be separated out now, not argued over later.
- Create a draft evidence folder: Organise by project, then by technical records and financial records.
This early pass saves a lot of time later because it forces the business to distinguish between product progress and eligible R&D work.
What Are the Critical Deadlines and Timelines
The most unforgiving rule in the process is the registration deadline. It doesn't matter whether the work was brilliant, expensive, or clearly groundbreaking if the registration misses the legal window.
The date that matters most
Eligible R&D activities must be registered with AusIndustry within 10 months of the company's income year end. For a company with a 30 June year end, that creates a hard deadline of 30 April. If you miss it, the expenditure is legally disqualified from the tax offset, as explained in Azure Group's summary of the application timing rules.
That's the part many first-time claimants underestimate. They assume the tax return deadline is the main deadline. For R&D, the activity registration date comes first, and it controls whether the claim can proceed at all.
How the timing works in practice
A practical startup timeline often looks like this:
- Soon after year end: Identify the projects and pull records while the engineering context is still fresh.
- During the preparation window: Draft the technical descriptions, align them with payroll and accounting records, and review any grey areas.
- Before the registration cut-off: Submit the AusIndustry registration through the portal.
- After registration: Complete the financial side through the company's tax process.
If your team starts drafting in April for a 30 June year end, you may already be late in practical terms even if you're not late legally.
The portal itself enforces the timing logic. That's why deadline management is not just an admin issue. It's a claim preservation issue. Startups that treat R&D as a post-EOFY tidy-up often create avoidable pressure for founders, finance teams, and engineering leads all at once.
How Do I Build an Evidence-Backed Claim
A lot of startup teams think the hard part is writing the narrative for the portal. It isn't. The hard part is proving that the narrative matches what occurred.
Narrative without evidence is where claims weaken
The biggest gap I see in software claims is the space between a polished explanation and contemporaneous records. The ATO expects records created at the time of the activity, not estimates rebuilt later. The ATO checklist for getting R&D claims right is particularly relevant here, and the verified data notes that 43.5% of refundable claims are scrutinised for lack of contemporaneous evidence.
For software startups, that usually means the evidence is spread across systems the tax team doesn't control. GitHub may show technical experimentation. Jira or Linear may show iteration and problem framing. Notion may hold architecture decisions. Xero may show contractor invoices or software spend. None of those tools, on their own, tells the whole R&D story.
What good evidence looks like for software teams
Good evidence is specific, dated, and connected.
It often includes:
- Engineering activity records: Pull requests, commit history, issue threads, deployment notes, and linked tickets that show what the team tried.
- Decision records: Technical notes, architecture discussions, stand-up summaries, and retrospective comments that show uncertainty and reasoning.
- Financial substantiation: Payroll mapping, contractor agreements, invoices, and bookkeeping entries that tie costs to the underlying activities.
- Project chronology: A sequence that shows the work unfolded through testing, failure, revision, and learning.
A common weakness is rebuilding everything from memory once the portal opens. That usually creates broad statements like “the team developed a scalable API layer” or “we improved machine learning performance”. Those phrases may be true, but they don't show the experimental path.
Strong claims don't just say what was built. They show what couldn't be known in advance and how the team worked through that uncertainty.
If your finance team is extracting support from old reports, contracts, and archived attachments, a tool for AI-powered PDF data extraction can help turn buried documentation into usable inputs for review. That's especially helpful when historic evidence sits in board packs, consultant reports, or scanned invoices.
A practical way to organise the paper trail
For founders, the best workflow is usually simple:
| Evidence area | Example startup tools | What you're trying to prove |
|---|---|---|
| Technical work | GitHub, Jira, Linear | Experiments, iterations, unresolved uncertainty |
| Knowledge creation | Notion, design docs, meeting notes | What the team learned and why it was new to the company |
| Costs incurred | Xero, payroll reports, invoices | Actual expenditure connected to the registered activities |
Then pressure-test each project with one hard question: if someone independent reviewed this in a year, could they trace the claim from technical problem to experiment to evidence to cost?
If the answer is “mostly, but not cleanly”, fix that before lodgement. For a deeper read on project eligibility and how software work is assessed, ClaimKit's blog and its R&D tax incentive eligibility guide are useful starting points.
What Are My Options for Preparing and Lodging a Claim
There isn't one right way to prepare an R&D claim. The best option depends on your team's technical complexity, internal bandwidth, and tolerance for manual documentation work.
The scale of the program shows why founders spend time getting this right. In 2023-24, 13,901 companies registered through the AusIndustry customer portal, representing $17.7 billion in estimated R&D expenditure, up from $12.7 billion in 2019-20 according to these Australian R&D Tax Incentive statistics.
The three common approaches
Most startups choose between three paths.
The first is DIY. This can work if the claim is straightforward, your records are already organised, and someone internally can own both the technical and financial coordination. The trade-off is founder or finance time, plus the risk of weak framing or incomplete substantiation.
The second is a traditional R&D advisor. Firms such as Treadstone, Prime Partners, Link R&D Advisory, and Bulletpoint can be a good fit for companies that want a guided process and direct adviser involvement. The trade-off is often a more manual workflow, especially for software teams whose evidence lives in engineering tools rather than neat project files.
The third is a software-assisted model with expert review. This approach tends to suit tech startups because it can pull evidence from systems the team already uses, generate first-pass drafts, and then have specialists review before lodgement. For founders, the main benefit is usually speed and transparency rather than replacing expert judgement.
Comparison of R&D Claim Preparation Methods
| Method | Typical Cost | Founder Time | Evidence Automation | Expert Review |
|---|---|---|---|---|
| DIY | Lower direct spend, higher internal effort | High | Limited | Optional through your accountant or adviser |
| Traditional advisor | Professional fees, often with a managed process | Moderate | Usually manual or document-driven | Yes |
| Software-assisted platform | Platform fee plus review-based support | Lower to moderate | Strong for connected tools | Yes |
What matters most is fit.
- Choose DIY if your projects are simple and your records are already tidy.
- Choose a traditional advisor if you want hands-on external support and your business prefers a conventional consulting model.
- Choose a platform model if your evidence is spread across engineering and finance tools and you want a faster drafting workflow with review before submission.
If you're comparing adviser models or need a starting point for who helps with claims, ClaimKit's consultants page gives a useful reference point for the expert-review approach.
Frequently Asked Questions About the R&D Portals
Can startups claim if some engineering work happened overseas?
Potentially, but this is an area where founders make expensive mistakes. The program has a 50% cost-in-Australia requirement across total project costs, and overseas expenditure may require a finding lodged before the income year ends. The portal can accept information, but it doesn't replace the legal requirements around overseas work. If you've used offshore engineers, get this checked early.
What happens after the AusIndustry registration is lodged?
Registration is only one part of the process. After that, the financial side still needs to be reflected through your tax lodgement with the ATO. In practical terms, founders should expect follow-up work on expenditure mapping, schedules, and record quality rather than treating the AusIndustry submission as the finish line.
Do I need an advisor to use the portal?
No. An advisor isn't legally required. But plenty of startups still choose help because the challenge isn't logging in. It's framing the technical work correctly, separating eligible from non-eligible costs, and keeping contemporaneous records organised.
What's the minimum startup profile for a refundable offset?
Eligible companies may access the refundable 43.5% tax offset if combined revenue is less than AUD 20 million across the Australian entity and connected groups, and the company incurs more than AUD 20,000 in eligible R&D expenditure during the year, as outlined in Acclime's guide to Australia's R&D tax incentives. Whether a specific company qualifies still depends on the facts of the projects and the expenditure claimed.
Where can I get help with practical claim admin and document handling?
If you're dealing with privacy, records, and document preparation, it helps to use providers that explain how data is handled and how draft claims are reviewed. ClaimKit's privacy information is worth reading if you're assessing software-assisted options and want to understand how startup data may be managed in the claim process.
If you want a faster way to turn engineering and finance records into a structured R&D claim, ClaimKit is built for Australian tech companies. It connects with tools like GitHub, Jira, Linear, Notion, and Xero, drafts claim materials with AI, and pairs that draft with expert review and ATO lodgement support so your team can prepare a more organised, evidence-backed submission.
Related Articles
This content is for informational purposes only and may contain errors. Please contact us to verify important details.