Tax Alert

High Court finds taxpayer liable for NSW payroll tax on payments to drivers

Woman ordering a rideshare
  • 13 minute read
  • 17 Nov 2026

The High Court has held Uber liable for NSW payroll tax on fares remitted to drivers. Explore the implications for platform and contractor arrangements.

In brief

On 4 November 2026, the High Court of Australia dismissed the taxpayer’s appeal in Uber Australia Pty Ltd v Chief Commissioner of State Revenue [2026] HCA 40, finding that Uber (the Taxpayer) was liable for New South Wales (NSW) payroll tax on the fares it collected from riders and remitted to the drivers. 

The majority found that the Taxpayer’s standard Driver Contract was a ‘relevant contract’ under the Contractor Provisions of the Payroll Tax Act 2007 (NSW). As observed by the Court, that is because, once a trip began, the Driver Contract obliged the driver to take the rider directly to their destination, and to do so to the standards the Taxpayer set. Having established that the gateway into the Contractor Provisions was satisfied, the Court found the exclusion for services ‘ancillary’ to the use of the driver’s own car did not apply. Lastly, with a ‘relevant contract’ identified, the fares the Taxpayer remitted to drivers were deemed to be ‘wages’, even though the contracts described the Taxpayer as the drivers’ ‘limited payment collection agent’.

The decision confirms that the Contractor Provisions, first introduced in the 1980s, can reach businesses not envisaged at the time of their introduction, including gig economy and platform business models. It also reiterates the approach taken by the courts that contractual labels are not determinative. 

This decision marks the first time the Contractor Provisions have been considered by the High Court, and it follows a series of earlier decisions in industries unrelated to the Taxpayer, such as financial services and health care. 

If your business has arrangements with independent service providers (e.g. digital platforms or introducer/facilitation arrangements) which you currently do not consider to fall within the scope of the Contractor Provisions, now is the time to consider whether or not the rules apply to you. 

In detail

Background

The business arrangements as explained by the Court were as follows. Uber operated a digital rideshare system that connected riders with drivers through its Rider App and Driver App. Uber entered into a standard form contract with each driver (the Driver Contract) and a separate standard form contract with each rider (the Rider Contract). When a driver accepted a trip request, the driver collected the rider and drove them to their destination. The rider paid the fare electronically to Uber. Uber then deducted its service fee, calculated as a percentage of Uber’s recommended fare, and other fees, and remitted the balance to the driver at least weekly.

The Chief Commissioner of State Revenue assessed the Taxpayer for payroll tax on the basis that he considered most of the amounts collected from riders and remitted to drivers were wages under the Contractor Provisions. The Taxpayer’s objections to the Chief Commissioner’s decision were disallowed and it sought review in the Supreme Court of NSW.

The case has had a mixed path through the courts. At first instance, Hammerschlag CJ in Eq found that the Driver Contracts were relevant contracts, but revoked the assessments because the amounts Uber remitted to drivers were not taken to be wages under section 35(1) (Uber Australia Pty Ltd v Chief Commissioner of State Revenue [2024] NSWSC 1124). The question was not whether the driver was paid for the work, but how the statute treated Uber’s remittance. His Honour accepted that the rider’s payment to the driver was for or in relation to the driver’s work. Uber’s later payment to the driver was different: under the contracts, Uber collected the fare as the driver’s limited payment collection agent and then had to account for it. His Honour read the words “in relation to” in section 35(1) in their context, alongside “for” and with the objects of Division 7 in mind. On that reading, “in relation to” required some reciprocity or calibration between the money paid and the work done. There was none between Uber and the driver, because the remittance was made under an obligation to account “and no more”. What Uber paid the driver was “in relation to the payment Uber has received, not in relation to the work itself”.

A five-judge bench of the NSW Court of Appeal allowed the Chief Commissioner’s appeal and dismissed Uber’s cross-appeal (Chief Commissioner of State Revenue v Uber Australia Pty Ltd (2025) 118 NSWLR 164), finding that the Driver Contracts were ‘relevant contracts’, and that payments to the drivers met the definition of ‘wages’ under the expansive relevant contract provisions. The Taxpayer sought, and was granted, special leave from the High Court to appeal this decision. 

The Contractor Provisions

Payroll tax is imposed on taxable wages paid or payable by an employer. In NSW, the Contractor Provisions in Division 7 of Part 3 of the Payroll Tax Act 2007 (NSW) extend the tax beyond employment relationships. Three provisions were central to the appeal:

  • Section 32(1)(b) defines a ‘relevant contract’ to include a contract under which a person, in the course of its business, has supplied to it the services of persons for or in relation to the performance of work

  • Section 32(2)(a) excludes a contract under which the services supplied are ancillary to the supply of goods, or to the use of goods which are the property of the person supplying the services

  • Section 35(1) deems amounts paid or payable by the deemed employer for or in relation to the performance of work relating to a relevant contract to be ‘wages’

Under sections 33 and 34, the person receiving the services is taken to be an ‘employer’, and the person performing the work is taken to be an ‘employee’. Where a payment includes amounts that are not attributable to the performance of work, section 35(2) provides for that part to be determined by the Chief Commissioner.

The Contractor Provisions were first introduced in Victoria in 1983 and followed in NSW in 1985 to capture contractual arrangements that disguised employment relationships. The current NSW provisions were based on, and are in comparable terms to, the Victorian provisions, and are largely harmonised across the states and territories with the exception of the ACT and WA.

The High Court’s decision at a glance

The Taxpayer raised three grounds of appeal. Gageler CJ and Gordon, Edelman, Gleeson, Jagot and Beech-Jones JJ rejected each of them, with Gageler CJ writing separate reasons. Steward J dissented. The table below summarises the outcome and reasoning on each issue, as explained in the judgment.

Issue  Majority finding  Steward J finding (dissenting) 
Was the Driver Contract a ‘relevant contract’ under section 32(1)(b)?  Yes. The driver was obliged to Uber to perform the driving services, to particular standards, so the services were supplied to Uber under the Driver Contract.  No. Drivers supplied transport services to riders, not to Uber. Uber benefited from those services but did not receive them. 
Were the driving services ‘ancillary’ to the use of the driver’s car under section 32(2)(a)?  No. The primary object of the Driver Contract was the supply of driving services, not the use of a car.  Unnecessary to decide (on the basis of no ‘relevant contract’). 
Were the remitted fares deemed to be ‘wages’ under section 35(1)?  Yes. The amounts remitted were paid for or in relation to the performance of work relating to the Driver Contract.  No. In remitting fares, Uber was fulfilling its promise to riders, acting as the drivers’ collection agent, not paying for work done for it. 

Based on the majority finding, the Taxpayer’s appeal was dismissed with costs. 

Issue 1: The Driver Contract was a ‘relevant contract’

The majority’s reasoning turned on terms within the Driver Contract under which the driver acknowledged and agreed with the Taxpayer that all riders “should be transported directly to their specified destination, as directed by the [rider], without unauthorised interruptions or stops”. The majority held that this was an obligation owed to the Taxpayer. While the Driver Contract did not oblige a driver to accept any particular trip, the majority did not consider this to be decisive. It likened the ability for a driver to choose whether or not to accept a trip to that of a casual employee, who is under no obligation to work on any particular occasion but, once work starts, is bound by obligations under the contract. The source of the driver’s obligation to transport the rider, once the rider was picked up, was found to be the Driver Contract. Whether or not there was also an implied contract between the driver and the rider did not change that conclusion. 

Further, the majority accepted that the same driving services could be supplied concurrently to the Taxpayer and riders without changing the outcome, referring to the High Court’s earlier decision in Accident Compensation Commission v Odco Pty Ltd (1990) 64 ALJR 606.

The majority also emphasised the other obligations and controls in the Driver Contract and the Taxpayer’s Community Guidelines. These included requirements to provide the services with due skill, care and diligence; vehicle and insurance requirements; and the Taxpayer’s right to deactivate drivers for reasons including low ratings, high cancellation rates and soliciting payment outside the Taxpayer’s system. In the majority’s view, these standards reinforced how central the driving services were to the Taxpayer’s rideshare business.

Importantly, the majority refined part of the Court of Appeal’s reasoning. It accepted that generating a financial benefit for the Taxpayer is not, of itself, enough for services to be ‘supplied to’ the Taxpayer. What was relevant in this case was the driver’s contractual obligation to the Taxpayer to supply particular driving services to a particular standard. 

Issue 2: The ‘ancillary to the use of goods’ exclusion did not apply

The next issue was whether driving services were ancillary to the use of the drivers’ own cars, which, if satisfied, would invoke the exclusion in section 32(2)(a) to the effect that a ‘relevant contract’ would not arise. The majority concluded this exclusion did not apply. Drawing on the legislative history, the majority explained that the exclusion targets contracts whose primary object is the use of goods, such as the hire of a crane where the owner also supplies the crane driver. Here, the Court took the view that the vehicle and the driver were similarly important to both the Taxpayer and the rider. 

Issue 3: The remitted fares were deemed ‘wages’

Section 35(1) is a deeming provision that creates its own concept of ‘wages’. As the majority observed, ordinary expectations of what constitutes wages are of limited relevance. 

The issue under consideration was whether the Taxpayer, by simply collecting money that belonged to the drivers and remitting that money, less its service fee, met the test for paying a ‘wage’. 

The majority cited a long line of judicial authority, including Construction, Forestry, Maritime, Mining and Energy Union v Personnel Contracting Pty Ltd (2022) 275 CLR 165, and cautioned against giving too much weight to the labels parties use to describe their relationship. It took the view that the Taxpayer was not a mere ‘limited payment collection agent’, given its involvement in setting the recommended fare (which the majority described as effectively the required fare) and calculating its service fee on that fare even if the driver agreed to charge less. 

On this basis, the majority was satisfied that the required connection between payments and the performance of work was present; the more driving services a driver performed, the more money was remitted to them. 

The dissent

Steward J would have allowed the appeal. His Honour characterised the Contractor Provisions as an anti-avoidance regime directed at arrangements that disguise what are, in substance, emoluments of employment, and considered that their general words should be read in that light. 

His Honour noted there was no suggestion that the Driver Contract was a form of disguised employment. On his Honour’s view, drivers were independent businesspeople who acquired lead generation services from the Taxpayer, and the only contract of carriage was the one implied between driver and rider. The requirement in clause 3 of the Driver Contract to take riders directly to their destination was a promise about the manner in which transport services were delivered, not a supply of services to the Taxpayer. His Honour also considered that section 35(1) requires a relationship of exchange between the deemed employer and deemed employee, and that the Taxpayer’s remittance of fares was a fulfilment of its role as collection agent rather than a payment for work. 

What this means in practice

While the decision turns on the Taxpayer’s particular contracts and tripartite arrangement, the majority’s reasoning has implications for any business that engages workers through a platform or intermediary model, or which enters into contracts with independent service providers (on terms however described) which it in turn pays money to. Several features of the reasoning are likely to be relevant when testing other arrangements.

Substance over labels. Describing parties as independent service providers, stating that a contract creates no employment or contractor relationship, or describing the business as a ‘payment collection agent’ will not, on its own, take an arrangement outside the Contractor Provisions. The courts will examine the rights and obligations the contract actually creates.

Obligations and standards imposed by the platform. Workers’ freedom to choose when and whether to work did not prevent a ‘relevant contract’ from arising. What mattered was the obligations owed to the platform once work started, supported by quality standards, ratings and the platform’s right to deactivate workers. Businesses should review the obligations, service standards and controls in their contracts and policies, including community guidelines and similar documents that have contractual force.

Payment flows and control over funds. Where payments are channeled through the business, and the business can set prices, deduct fees, or adjust or cancel amounts before remitting them, the remitted amounts are more likely to be treated as paid by the business. Arrangements where workers are paid directly by customers, or where workers are paid for the relevant services by a third party, may need separate analysis. 

Historical exposure. Businesses with similar arrangements should consider their potential payroll tax exposure for current and prior years, and the options for engaging with the relevant revenue office under a voluntary disclosure to mitigate the imposition of penalties or interest. A private ruling can also be considered.

Other exclusions. The Court considered only the exclusion in section 32(2)(a). Whether other exclusions from the definition of ‘relevant contract’ might apply to different platform arrangements was not in issue. However, it is worthwhile considering the extent to which other exclusions can apply. This will depend on the facts and circumstances, and should be assessed carefully.

The wider context

The decision is significant for how long-standing payroll tax laws apply to new ways of working. Gageler CJ observed that the Contractor Provisions continue ‘always speaking in the present’ to participants in the gig economy that has emerged this century. The majority acknowledged that when the provisions were drafted, Parliament was unlikely to have foreseen the gig economy but found that the legislative history supported its conclusion. In particular, the definition of ‘relevant contract’ was intentionally wide, with exclusions to exempt transactions not intended to be caught. Steward J’s dissent took a different view from the majority. In his Honour’s view, where the language of the law is indeterminate, the task of a judge is not always to give the broadest possible meaning. The split reflects a genuine tension between a broad reading that protects the payroll tax base as working practices change, and a narrower reading focused on disguised employment. 

The takeaway

The High Court’s decision marks the first occasion of the Contractor Provisions – and their reach in the modern environment - being considered at this level. The key message for business is that the payroll tax Contractor Provisions are very broad, and the assessment of whether they apply will not be limited to how the relationship is labelled.

If your business engages parties through a platform or intermediary model, if it enters into contracts with independent service providers for the benefit of its business, or if it collects and remits payments for those who perform work, you should review your contracts, policies and payment flows against the Court’s reasoning. Given the dissent and the reliance on the specific terms of the Taxpayer’s contracts, outcomes for other businesses will depend on their own facts, so specialist advice is recommended.

We now await the findings of the NSW Parliamentary Inquiry into the “Application of the contractor and employment agent provisions in the Payroll Tax Act 2007”, which is considering the application of the Contractor Provisions, including legislation, judicial decisions and public regulatory guidance on these rules. Many submissions from a range of businesses, associations and advisers were made to the Inquiry. It is anticipated that the Committee will take the High Court’s decision into account in its findings and recommendations.


Contact us

Adam Nicholas

Partner, Workforce, PwC Australia

Contact form

Caleb Khoo

Partner, Tax Controversy Leader, PwC Australia

Contact form

Shane Pinto

Partner, Employment Taxes, PwC Australia

Contact form

Jake Roche

Director, PwC Australia

Contact form

Greg Kent

Partner, Workforce, PwC Australia

Contact form

Anne Bailey

Partner, Workforce, PwC Australia

Contact form

Paula Shannon

Partner, Workforce, PwC Australia

Contact form

Follow PwC Australia

Required fields are marked with an asterisk(*)

By submitting your email address, you acknowledge that you have read the Privacy Policy and that you consent to our processing data in accordance with the Privacy Policy (including international transfers). If you change your mind at any time about wishing to receive the information from us, you can send us an email message using the Contact Us page.

Hide