An Australian business pays $80,000 a year to a US software provider for a cloud platform. Should the business be withholding 30% from each payment and remitting it to the ATO? The answer depends almost entirely on what the contract says — and most owners (and many of their accountants) get the answer wrong the first time.

This guide from Trinity Accounting Practice walks through when non-resident withholding tax applies to cross-border software, IP and service payments, the royalty-vs-service distinction the ATO looks for, and the PAYG reporting obligations that catch out Australian payers.

The basic rule — Division 12 withholding

Under Division 12 of the Income Tax Assessment Act 1936, Australian businesses must withhold tax on certain payments made to non-residents. Three categories of payment are caught: interest, unfranked dividends, and royalties. The Australian payer deducts the tax from the gross payment and remits it directly to the ATO. The non-resident recipient receives the net amount.

The default rate on royalties to non-residents is 30%. A tax treaty between Australia and the recipient’s country can reduce this — typically to between 5% and 15% — but only when the payer holds valid residency documentation from the foreign recipient. Without that documentation, the ATO requires withholding at the full domestic rate, regardless of any treaty entitlement.

Royalty vs service — the question that decides everything

For software and SaaS arrangements, the central question is whether the payment is a royalty or a service fee. The ATO has consistently published guidance on this through TR 93/12 and the more recent draft TR 2024/D1. The headline:

Royalty: payment for the right to use, copy, distribute, install, modify, or sublicense intellectual property. Includes payments for software you download to a device, source code access, perpetual licences, or territory rights. Royalties attract withholding.
Service fee: payment for access to a cloud-hosted platform where the user never controls the underlying IP. The provider retains all rights; the user simply consumes the service. Service fees performed offshore are generally not subject to royalty withholding.

The line in practice is whether the user gets rights to the software (royalty) or access to a hosted service (service). A subscription label does not automatically make it a service. A platform sitting in the cloud does not automatically make it a service either. The contract language — licence rights, download permissions, modification rights, sublicensing — is what the ATO looks at.

Worked scenarios

1. Cloud-hosted project management tool

An Australian SME pays a US provider for browser-based access to a project management platform. Nothing is downloaded. The user has no rights to copy, distribute or modify the software. The provider hosts and controls the application. → Service. No withholding applies.

2. Reporting software with download rights

A consulting firm enters a licence agreement for a reporting tool developed overseas. The agreement permits the firm to download installable components, integrate them into its workflow, and (in some clauses) sublicense functionality to its own clients. → Royalty. The payer must withhold tax before remitting payment.

3. Custom software exported by an Australian developer

An Australian software developer builds and delivers a custom application for a UK client. All development is performed in Australia. The Australian payer earns Australian-source income. → No Australian withholding applies (this is outbound income — the Australian developer simply reports the income in their own return).

4. Bundled SaaS plus on-premise components

A medical practice pays an overseas provider for clinical software bundled with browser-based access, downloadable installation modules, and local training. → Mixed. Each component must be analysed separately. The portion attributable to the on-premise software is likely a royalty; the portion attributable to cloud access is likely a service. The contract should be priced accordingly so the royalty component can be isolated.

What the ATO looks for in the contract

Where the wording could go either way, the ATO weighs a list of indicators. Several of these flip the answer toward royalty:

The recipient is granted rights to copy, adapt, or distribute the software.
The agreement uses licence terminology (even if the commercial label is “subscription”).
The provider supplies source code, object code, or escrow arrangements.
The contract mentions perpetual use, territory rights, or modification rights.
On-premise installation is permitted or required.

Service treatment is more likely where the access is purely cloud-based, the user has no interaction with the software backend, no rights to the IP are granted beyond usage, and the provider retains all control.

Using tax treaties to reduce the rate

Australia maintains tax treaties with more than 40 jurisdictions. Treaty rates for royalties typically range from 5% to 15%, replacing the 30% domestic rate. Under the Australia–US treaty, for example, royalties are taxed at 5%.

To apply the treaty rate, the Australian payer must hold a valid tax residency certificate (or equivalent treaty documentation) from the foreign recipient, dated for the relevant income year. Without this documentation, the ATO requires withholding at the full 30%, even where the recipient is treaty-eligible.

A second, often-better option: structure the contract so the payment falls outside the royalty article entirely (i.e. as a service). Where a payment is purely a service fee performed offshore by a non-resident, no Australian withholding applies. The treaty becomes irrelevant because the payment is not Australian-source royalty income to begin with.

PAYG reporting obligations — easy to miss

When an Australian business withholds tax on a non-resident payment, the obligation does not end with remitting the withheld amount. The payer must also complete and lodge a PAYG Annual Report for Non-Residents after the financial year-end. The report includes the payee’s name and residency, total payment amount, withholding amount, and date and nature of each payment.

The ATO uses this data to match against treaty claims, foreign tax credits, and compliance risk reviews. Common errors we see at Trinity:

Applying a treaty rate without holding valid residency evidence — defaults to 30% on review.
Misclassifying a royalty payment as a service fee (or vice versa).
Withholding correctly but omitting the PAYG annual lodgement.
Failing to document the classification decision in writing — the ATO expects the reasoning to be on file.

Where the ATO has been more aggressive recently

Recent ATO guidance has tightened the position on software arrangements. Where a contract is structured as a service but the underlying substance involves licence-style rights — particularly on-premise installation or source code access — the ATO has signalled it will override the contractual classification. Several Taxpayer Alerts highlight the substance-over-form approach the ATO applies to international software arrangements.

For Australian businesses with material overseas software spend, this means contract reviews are no longer a luxury. They are an audit risk-management item.

A Trinity insight from 22 years in practice

The single most common pattern we see is the Sydney SME paying a major US software provider for what everyone in the business calls a “subscription,” with the assumption that no withholding applies. We pull the contract. Buried in clause 14 is a software licence grant — perpetual rights, installation rights, the lot. The arrangement is structurally a royalty, the payer should have been withholding, and three years of payments are now exposed. The fix is rarely complicated — it is usually a contract amendment with the vendor — but it has to happen before the ATO knocks.

A pre-payment checklist for cross-border software and service payments

Classify the payment correctly — royalty vs service.
Pull the contract and read the actual rights granted, not the marketing.
Confirm the recipient’s country of residency.
Check treaty availability for that country.
Obtain a valid residency certificate for the relevant income year.
Calculate the withholding rate (domestic 30% or treaty rate).
Apply PAYG withholding correctly on each payment.
Remit to the ATO with the correct payment code.
Document the classification and treaty position in writing.
Lodge the PAYG Annual Report for Non-Residents after year-end.

What this means for you

If you pay an overseas SaaS provider material amounts: book a contract review. Subscription labels do not protect you from a royalty classification.
If you have ever withheld at the treaty rate: confirm you hold the residency certificate on file for each year.
If you export Australian-developed software or services: the rules are different — you are the recipient, not the payer. Different planning required.
If you have bundled SaaS arrangements: price each component separately so royalty and service portions can be isolated.
If you have not been filing the PAYG Annual Report for Non-Residents: remediate before the ATO asks.

How Trinity can help

Trinity Accounting Practice reviews cross-border software and service contracts to classify payments correctly, manages treaty documentation, calculates withholding and lodges the annual reports. For Sydney SMEs with material overseas software spend — and for Australian businesses exporting digital services — this is one of the highest-risk-relative-to-effort areas of compliance we work in.

Book a cross-border tax review with the Trinity team →

General advice only. This article contains general information current as at May 2026 and does not constitute tax, financial or legal advice. It does not take into account your personal circumstances, objectives or needs. Before acting on any information in this article, you should consider its appropriateness to your situation and seek professional advice from Trinity Accounting Practice or another qualified adviser. Liability limited by a scheme approved under Professional Standards Legislation.