AgentTax
This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.
Practical Guide

Is SaaS Taxable in Arizona? Yes, as a Rental, and Arizona's Economic Nexus Threshold Does Not Count It

Beardsley Rumble|2026-09-25|7 min read

Key Takeaway: Arizona taxes SaaS, but not as a service and not under its retail classification. The courts treat software a user can see as tangible personal property, and a subscription to it as a rental. That classification has two consequences agent operators rarely hear about. The Department of Revenue says rental income does not count toward Arizona's economic nexus threshold. And the rental test depends on the customer controlling the software, which is exactly what an autonomous agent takes away.

The Base: A Tax on the Seller, Measured by Rentals

Arizona's transaction privilege tax (TPT) is levied on the seller's privilege of doing business, measured by gross income under business classifications. Software subscriptions fall under the personal property rental classification. A.R.S. § 42-5071(A) defines it as "the business of leasing or renting tangible personal property for a consideration."

Software fits that definition because of how broadly Arizona defines tangible personal property. A.R.S. § 42-5001(21) defines it as "personal property that may be seen, weighed, measured, felt or touched or that is in any other manner perceptible to the senses."

The state rate is 5.6%. Counties and cities add their own layers. The Department's September 2026 rate table puts the Maricopa County personal property rental rate at 6.30% (state plus county) and Phoenix's city rate for "Rental, Leasing, & Licensing for Use of TPP" at 2.80%. That makes 9.10% combined in Phoenix, 8.10% in Tempe (1.80% city) and 8.70% in Tucson (2.60% city, 0.50% Pima County).

The Case That Settled It: ADP v. Arizona Department of Revenue

In ADP, LLC v. Arizona Department of Revenue, No. 1 CA-TX 21-0009 (Ariz. Ct. App. Jan. 31, 2023), ADP argued its hosted timekeeping software was a human-resources service. The Court of Appeals affirmed the tax on two grounds.

Perceptibility. The court followed a 1943 Arizona Supreme Court decision holding that a jukebox record played for a patron was tangible because it was audible. It concluded that ADP's software "is likewise perceptible because it can be viewed by the County's users while accessing and using the program" (¶ 10).

Control. Under the Supreme Court's laundromat case, a rental exists where customers have exclusive use and "perform all the manual activities necessary" to run the machine. The court found the County's employees did exactly that by entering their own hours and data (¶ 17). It measured exclusivity "at the level of the customer's interface" rather than the server (¶ 19), so ADP gained nothing from pointing out that every customer ran on the same code.

Two further holdings matter to anyone selling automation. The court said "paying to use technology that performs that same function by automation subjects the transaction to TPT" (¶ 28), rejecting the argument that automated services are still services. And it held that TPT reached the County's use of the software in Arizona even though ADP hosted it on servers in other states (¶ 26).

The City of Phoenix won on a simpler ground: its code expressly taxes "leasing, licensing for use, or renting" tangible personal property and deems non-custom software tangible (¶¶ 29-32). City tax does not depend on perceptibility at all.

Where an Autonomous Agent Departs From ADP

ADP's facts are a person at a screen, logging in and typing. Much agent commerce looks nothing like that.

In Taxpayer Information Ruling LR 16-011 (Sept. 23, 2016), the Department considered an out-of-state subscription-billing provider. Its clients uploaded customer payment data through an API. After that, "payment requests are made continuously and automatically based on the information on [the provider's] servers without any further input from clients." Clients could view results in a portal, and fees were a percentage of successful payments rather than a charge for software use.

The Department agreed the API and portal were software, and therefore tangible personal property. It still ruled there was no rental: "Both and its clients use the software... Thus, there does not appear to be the type of exclusive control required by Peck to constitute the rental of tangible personal property (software)." It held the income was not taxable under any classification.

A customer who logs in and drives a tool is renting it (ADP). A customer who hands over data and lets the vendor's system do the work, paying on outcomes, arguably is not (LR 16-011). An agent that runs a task end to end and bills per result sits closer to the second.

Three cautions keep that from being a conclusion:

  • LR 16-011 binds the Department only as to the taxpayer that asked. The ruling says it "may not be relied upon, cited, or introduced into evidence in any proceeding by a taxpayer other than the taxpayer who has received" it. It shows the Department's reasoning, not your answer.

  • ADP post-dates it and cuts the other way on automation. The court rejected the premise that "automated functions constitute the provision of services" (¶ 21). Where the customer still operates the tool, automation inside it does not help.

  • The facts carry the whole weight. A dashboard the customer configures and drives, flat seat pricing, and a license clause all point toward ADP.

The Finding Most Guides Miss: Rentals Do Not Create Economic Nexus

Arizona's economic nexus statute, A.R.S. § 42-5044(A), applies to a person that "conducts business in an activity classified under section 42-5061" (the retail classification) and exceeds $100,000 in gross proceeds from Arizona customers. The rental classification is § 42-5071, and § 42-5044 does not mention it.

The Department spells out the consequence in Transaction Privilege Tax Ruling TPR 24-1 (final Dec. 6, 2024). Economic nexus is "applicable to the retail classification only," and "income derived from other classifications, such as the personal property rental classification, does not go toward such thresholds." Its Example 1 is a SaaS company almost word for word: an out-of-state company with no physical presence derived $250,000 from monthly subscriptions to cloud software sold to Arizona customers, and "would not have economic nexus with Arizona from its personal property rentals."

For an out-of-state agent platform with no Arizona employees, contractors, inventory or property, subscription revenue creates no Arizona TPT obligation however large its Arizona customer base grows. Two limits:

  • Physical presence changes everything. TPR 24-1 says a business with substantial nexus by physical presence is taxable "under all TPT classifications" from the first dollar, and it treats activity by agents, contractors and affiliated persons as the business's own. An Arizona-based sales rep or implementation contractor is enough.

  • The tax does not disappear. It moves to the buyer. Without seller nexus, TPR 24-1 points to Arizona use tax, for which "the consumer is liable." An Arizona business buying agent services from a non-collecting vendor should expect to self-assess.

How AgentTax Computes Arizona

Verified against the engine this morning, $1,000 into Arizona across all fifteen transaction types:

  • Buyers pay the full combined rate on every type: $91.00 in Phoenix (ZIP 85001), $81.00 in Tempe, $87.00 in Tucson, each matching the Department's September table. Every Arizona call carries a STATE_DEFAULT_NO_CATEGORY_RULE advisory. The engine has no category-specific Arizona rule for digital services and falls back to the state's taxable default. That includes consulting, which we price as taxable because an agent doing advisory work is closer to ADP's software than to a human professional. It may over-reserve where your facts look like LR 16-011, which is the conservative side to be wrong on.

  • Some Phoenix ZIPs are under-rated. ZIP 85001 is correct at 9.10%, but three other Phoenix ZIPs we carry (85008, 85016, 85339) compute 7.90%, and downtown ZIPs we do not carry fall back to the 5.60% state rate. We have flagged the table for correction. Until it ships, a Phoenix buyer outside 85001 should reserve at 9.10%.

  • Sellers are gated on the nexus you configure. Our nexus monitor carries Arizona at a $100,000 revenue threshold and does not separate retail income from rental income. A remote SaaS or agent seller with no physical presence may not need to register at all under TPR 24-1. Weigh that before setting AZ to hasNexus: true, and check it against your own facts. See our economic nexus guide for agents.

  • Origin rules apply to Arizona sellers selling within Arizona. For those transactions, the engine sources the local rate to the seller's location.

Try it on your own numbers. Run an Arizona transaction without an account, or get a free API key. Compare against the 50-state SaaS taxability guide and the AI agent sales tax hub.

What to Watch

Whether the Legislature extends § 42-5044 to the rental classification, which as written leaves remote SaaS in use tax, where compliance is weakest. And whether a court applies the control test to a headless agent: no interface anyone views, no human operating it, billed per outcome. ADP turned on a person at a screen. The next case may not have one.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.*