Arizona TPT Ruling: TPR 24-1 Clarifies SaaS is Not Taxable Without Physical Presence

On December 6, 2024, the Arizona Department of Revenue issued Transaction Privilege Tax Ruling 24-1 (TPR 24-1), outlining how to determine whether an out-of-state business — including those offering Software as a Service (SaaS) — has substantial nexus for the purpose of imposing Arizona Transaction Privilege Tax (TPT).

The ruling clarifies two distinct paths for establishing nexus:

• Substantial nexus by physical presence
• Economic nexus (retail classification only)

Importantly, the ruling confirms that when a business has only economic nexus, TPT applies solely to sales under the retail classification. Because SaaS is typically classified as personal property rental, not retail, many SaaS providers may fall outside Arizona TPT obligations absent physical presence.

Arizona TPR 24‑1 provides important clarity for SaaS and other remote sellers by confirming when Transaction Privilege Tax applies — and when it does not. Businesses should reassess nexus and revenue classification to avoid unnecessary tax exposure. Here’s what to know.

Substantial Nexus by Physical Presence

Substantial nexus by physical presence applies broadly and creates immediate TPT obligations across all classifications.

TPR 24-1 explains that businesses establish substantial nexus in Arizona by performing non-transitory activities within the state that are significantly associated with the business’ ability to establish and maintain a market in Arizona. Businesses with physical presence in Arizona are treated the same as in-state businesses and are subject to TPT beginning with the first dollar derived from taxable business activity once physical presence is established.

The ruling further clarifies that physical presence applies across all TPT classifications. As a result, a business with physical presence in Arizona is responsible for reporting and remitting TPT for all applicable classifications for as long as that presence exists.

Economic Nexus (Retail Classification Only)

Economic nexus applies more narrowly and is measured solely by retail activity.

TPR 24-1 addresses remote sellers and clarifies that economic nexus is measured by gross proceeds derived under the retail TPT classification only. Gross proceeds from other classifications, such as personal property rental, do not count toward establishing economic nexus.

If a business has economic nexus but no physical presence in Arizona, TPT applies only to retail-classified sales. The ruling provides examples illustrating that SaaS revenue, when properly classified as personal property rental, does not trigger TPT solely due to exceeding the economic nexus threshold.

Key Implications to Consider

TPR 24-1 highlights the importance of clearly distinguishing revenue streams and the respective tax classifications.

Key considerations include:

• Misclassifying SaaS revenue as retail may unnecessarily trigger TPT obligations.
• Businesses offering multiple products or services should separately track revenue by classification.
• In-state activities, such as marketing, customer support, or partnerships, may unintentionally create a physical presence.

For businesses operating across state lines, proper classification and monitoring of activities are essential for managing Arizona TPT exposure.

Next Steps

Businesses affected by this ruling can consider the following steps:

• Review in-state business activities to determine if there is a physical presence or economic nexus in Arizona.
• Ensure that revenue is being classified appropriately – particularly distinguishing SaaS from taxable retail sales – to ensure there is no overreporting or incorrect tax collection.
• Confirm proper revenue classification, particularly distinguishing SaaS from retail sales.
• Document these findings and maintain clear records to support tax positions in the event of a review or audit.

Need help understanding your Arizona TPT exposure? Our State and Local Tax team can help you evaluate nexus, confirm revenue classification, and manage compliance with confidence.