Are Your Software Payments Actually Royalties?
For many businesses, software payments are treated as a routine operating cost - no different from paying for inventory or services. But under Australia’s evolving tax landscape, that assumption is becoming increasingly risky.
With the release of ATO Taxation Ruling TR 2026/2, the conversation has shifted. The issue is no longer whether software payments are deductible or commercially necessary. Instead, it is about how those payments are characterised - and whether they fall within the definition of a royalty.
That distinction carries direct tax consequences.
A Subtle Definition With Significant Impact
At its core, the ATO’s position is grounded in a long-standing principle: A payment is a royalty if it is made for the use of, or the right to use, copyright or similar intellectual property rights.
On the surface, this seems straightforward. In practice, however, modern software arrangements blur this line.
Unlike traditional software transactions where a business simply purchases a license and uses the product, today’s models often involve multiple layers of distribution, access, and control. SaaS platforms, cloud-based delivery, and regional distribution agreements have fundamentally changed how software is commercialised.
As a result, the same “software payment” can represent very different legal and economic realities.
Why Modern Software Models Create Tax Complexity
The ATO’s updated guidance focuses heavily on what it refers to as software intermediation arrangements. These are structures where an entity based in Australia sits between the software owner and the end user.
In these arrangements, the intermediary may do more than simply resell a product. It may:
facilitate access to software hosted elsewhere
distribute software to customers
customise or adapt the product
manage licensing or user rights
Individually, these activities may seem operational. But from a tax perspective, they raise a critical question:
Is the business merely selling a product - or exercising rights that belong to the copyright owner?
If the latter applies, the associated payments may be recharacterised as royalties.
The Reseller vs IP User Distinction
This is where the issue becomes both technical and commercially important.
A pure reseller model typically involves purchasing and on-selling software without any involvement in the underlying intellectual property. The reseller does not reproduce, modify, or control the software - it simply facilitates a transaction. In these cases, payments are generally not treated as royalties.
However, many real-world arrangements go beyond this.
Where a business has the ability directly or indirectly to:
reproduce or distribute software,
modify or adapt its functionality, or
grant access to end users under controlled terms,
it may be seen as exercising rights associated with copyright.
The ATO’s view is that these rights are not incidental. They are central to how the software is being exploited commercially - and therefore, payments connected to them may fall within the definition of royalties.
Why the ATO Is Paying Attention Now
The increased scrutiny is not occurring in isolation. It reflects a broader concern around cross-border profit allocation, particularly in the technology sector.
Many software businesses operate with:
intellectual property held offshore,
Australian entities acting as distributors or service providers,
and significant payments flowing out of Australia.
In some cases, these structures result in relatively low taxable profits being reported locally, despite substantial economic activity.
From the ATO’s perspective, this raises two issues:
Whether the character of payments (e.g. service fees vs royalties) has been correctly determined
Whether withholding tax obligations have been appropriately applied
The Oracle case illustrates how contentious this can become. At the centre of the dispute was whether payments made within a multinational group for software distribution rights should be treated as royalties. While the legal process is ongoing, the case highlights the scale of risk where classification is unclear.
Compliance Is No Longer Binary - It’s Risk-Based
Alongside the ruling, the ATO released draft PCG 2026/D4, which introduces a more practical, risk-based compliance framework.
Rather than treating all arrangements equally, the ATO is signalling where it is more or less likely to focus its attention.
At the lower end of the risk spectrum are arrangements that resemble straightforward resale. These typically involve:
no meaningful interaction with intellectual property,
commercially reasonable profit retained in Australia,
and transparent, consistent treatment of payments.
At the higher end are structures where:
significant payments are made offshore with limited local profit,
the nature of IP rights is unclear or understated,
or the arrangement appears designed to minimise Australian tax exposure.
This shift is important. It means businesses are not only being assessed on legal correctness, but also on how their structure is perceived in a broader economic context.
What This Means in Practice
For many businesses, the risk is not deliberate non-compliance - but misclassification.
Software payments are often structured based on commercial agreements, without fully considering how those agreements interact with tax law. Over time, this can lead to positions that are internally consistent but misaligned with the ATO’s interpretation.
The consequences can include:
unrecognised withholding tax liabilities
penalties and interest
disputes across jurisdictions, particularly where double taxation arises
A More Strategic Way to Think About It
The key takeaway is not that software payments are inherently problematic. It is that they can no longer be treated as generic expenses.
Instead, businesses need to ask:
What rights are actually being granted under this arrangement?
Who controls and exploits the intellectual property?
How are profits distributed across the group and does that reflect economic reality?
These are not purely tax questions. They sit at the intersection of legal structure, commercial model, and international tax policy.
Final Thought
The ATO’s latest guidance makes one thing clear:
The tax outcome of software payments depends on their character - not their label.
In an environment where software delivery models continue to evolve, that character is not always obvious.
For businesses operating in SaaS, distribution, or cross-border technology structures, this is less about reacting to a new rule - and more about reassessing whether existing structures still hold up under closer scrutiny.
Because increasingly, the risk is not in what you are doing - but in how it is being interpreted.
