If you're building a product that needs to calculate SaaS sales tax for your customers, this guide is for you. It covers Arizona's SaaS tax rules and rates, what to account for when you build sales tax calculation into your product, and how Ziptax returns accurate Arizona rates through an API without you building and maintaining a rate engine.
Arizona SaaS sales tax at a glance
Product Taxability Rules
| Does Arizona tax SaaS? | Yes. Remotely accessed SaaS is taxed as a rental of tangible personal property under Arizona's Transaction Privilege Tax (TPT). |
|---|---|
| Is this changing in 2027? | No. Arizona's SaaS taxability is stable, with no pending legislation changing this position. |
| Base State Tax Rate | 5.6% |
| Local Combined Rate Range | 5.6% to approximately 11.2%, determined by the TPT rate tied to the seller's business location (in-state sellers) or the customer's delivery address (remote sellers). Not resolvable from ZIP code alone. |
State Registration & Collection Triggers
| What triggers a tax collection requirement? | Meeting either of these conditions (whichever happens first):• Economic nexus: more than $100,000 in Arizona gross sales in the current or previous calendar year. No transaction-count component. Sales by commonly owned entities (more than 5% common ownership) are combined.• Physical nexus: an office, inventory, an employee, or other property in Arizona. |
|---|---|
| What revenue counts toward the $100k threshold? | Arizona gross sales, before deductions. |
| Does SaaS revenue count toward the $100k limit? | Yes. Because SaaS is taxable rental revenue in Arizona, it counts toward the threshold the same as any other taxable sale, with no carve-out. |
| Lookback Calculation Window | Current or previous calendar year (fixed calendar year, not a rolling 12-month window). |
| Are marketplace sales included? | Not toward the remote seller's own threshold, when a marketplace facilitator properly collects and remits TPT on those sales and you manage exemption certificates to document it. The facilitator has its own $100,000 threshold. |
| SST State (Streamlined Sales Tax)? | No. Arizona is not an SST member state, so you register and file directly with the Arizona Department of Revenue. |
| Primary Data Sources | Arizona Department of Revenue, Streamlined Sales Tax Governing Board |
Which types of software does Arizona tax?
Arizona taxes software based on what the transaction is, not on what the product is called or how polished the delivery looks.
| What you sell | Taxable in Arizona |
|---|---|
| SaaS, accessed remotely, no download | Yes. Taxed as a rental of tangible personal property under the personal property rental classification (TPT). |
| Prewritten software, downloaded | Yes. Treated as a retail sale of tangible personal property under A.A.C. R15-5-154. |
| Prewritten software on physical media | Yes. Same retail classification. |
| Custom software written for a single customer | Generally no. Treated as an exempt professional service, provided the customization isn't merely a modification to pre-written (canned) software (A.A.C. R15-5-154). |
| Digital products (e-books, audio, video, streaming) | Yes. Taxable under Arizona TPT (retail classification) as tangible personal property, which the state defines broadly to include digital items that are "perceptible to the senses" (A.R.S. § 42-5001(21)). |
| SaaS bundled with tangible goods | Split the bundle. Keep the SaaS charge on its own invoice line; the tangible line items are taxable on their own terms. |
Remember: keep line items separate. The Arizona Court of Appeals case that confirmed SaaS taxability turned partly on this: the court noted that the SaaS charge was broken out as its own invoice line rather than folded into a bundled service fee, which defeated the argument that it was merely incidental. A single lump-sum invoice risks exposing the whole charge to tax, not just the software line.
How do you charge the correct sales tax rate for SaaS in Arizona?
Because Arizona already taxes SaaS today, with no 2027 cutover to track, the calculation problem here is getting the right combined rate on every transaction, not watching for a future law change.
Arizona's TPT sources differently depending on where your business is. If you have a physical location in Arizona, tax is generally sourced to that business location (origin-based). If you're a remote seller with no Arizona physical presence, Arizona instead sources tax to the customer's delivery address (destination-based), using the Department of Revenue's published Remote Seller and Marketplace Facilitator rate tables. Most SaaS companies selling into Arizona from outside the state fall into the second case.
Option 1: Use the Ziptax Sales Tax API
You send the buyer's address at the point of checkout, and the API evaluates the exact state, county, and city rate that applies. The platform tracks jurisdiction boundaries and rate changes automatically, including Arizona's quarterly rate table updates.
To calculate a live rate against an Arizona address, use the v60 endpoint:
Bash
curl -G https://api.zip-tax.com/request/v60 \
-H "X-API-KEY: <apiKey>" \
-d key=your-api-key \
--data-urlencode "address=100 N Central Ave, Phoenix, AZ, 85004"To verify complete payload structures, review our official Get Tax Rates API Reference Doc, or explore the REST API documentation directly.
Three things to do with that response. Multiply by the combined rate rather than assembling it from the components. Store the jurisdiction on the transaction, because rebuilding it later from an address is lossy. Store the effective date too, since Arizona's rate tables are republished quarterly and a rate can change mid-year.
If your product catalog handles complex items like SaaS, digital goods, or bundles, you can also pass a product taxability code to dynamically check product rules. Use the ZipTax product code search tool and review Taxability Information Codes (TICs) to see how the response returns product-specific tax flags and exemptions.
What an API will not tell you: your company's physical presence or economic registration status in Arizona. Tracking whether you have crossed the nexus threshold and must legally register remains on your side of the integration.
To automate threshold tracking, tax filings, and remittance, you can set up merchant management through Ziptax Merchant Tools to connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.
Option 2: Build and maintain it yourself
A real choice if you already hold jurisdiction data for other reasons. Arizona needs four things handled:
- Address-level rate resolution across state, county, and city layers, refreshed on the Department of Revenue's quarterly update cadence rather than assumed static.
- Sourcing logic that switches between origin-based (your own Arizona business location) and destination-based (the customer's address, for remote sellers), rather than applying one rule everywhere.
- Threshold accumulation on a fixed calendar-year, non-rolling basis, including SaaS revenue from the first dollar, since Arizona doesn't carve SaaS out of the gross-sales calculation the way some states do.
- An effective date on every rate, since a quarterly-updated table means last quarter's stored rate can silently go stale.
Five things to watch out for:
- TPT is a vendor privilege tax, not a conventional sales tax. Legally, Arizona taxes the seller for the privilege of doing business, and the seller passes that cost to the buyer by convention, not statute. It behaves like a sales tax for calculation purposes, but the legal framing matters if a dispute ever turns on exemption language written for TPT rather than a sales-and-use tax.
- Rate tables update quarterly, not annually. A city or county can change its TPT rate between the Department of Revenue's scheduled table publications, and your stored rate is right only until the next update lands.
- Filing is centralized, but audit authority is not entirely. Arizona licenses, collects, and files state, county, and city TPT through a single Department of Revenue system rather than requiring separate filings with individual cities. However, cities can still independently audit TPT: under Ariz. Rev. Stat. § 42-6001, as amended in 2024, the Department can deny a city or town's request to audit a taxpayer that does business in more than one Arizona city, which blocks that city from auditing it. Don't assume centralized filing means zero local audit exposure.
- SaaS counts toward your nexus threshold here, unlike states that exclude it. If you're tracking the $100,000 Arizona threshold, include SaaS revenue in that count from the start rather than assuming it's carved out the way it would be in a state where SaaS isn't yet taxable.
- The legal ground is completely settled. The Court of Appeals decision confirming SaaS taxability is the operative law, and the Arizona Supreme Court officially denied review of the ADP case on September 12, 2023. You can safely build your compliance position treating the question of SaaS taxability as permanently closed.
When does a SaaS business have to collect sales tax in Arizona?
Registration and collection are two separate obligations with different triggers. Conflating them is where most engineering implementations go wrong.
Rule 1: Monitor your registration triggers (nexus)
You must obtain a TPT license and register with the Arizona Department of Revenue the moment either of these conditions is met:
- Physical presence: an employee working in Arizona, an office, inventory held in the state, or other property.
- Economic threshold: your Arizona gross sales exceed $100,000 in the current or previous calendar year. Because SaaS is taxable in Arizona, SaaS revenue counts toward this figure from the first dollar.
Rule 2: Apply the correct sourcing and rate
- If you have a physical location in Arizona: source tax to that business location (origin-based), and register for the city and county rates tied to it alongside the state rate.
- If you're a remote seller with no Arizona physical presence: source tax to the customer's delivery address (destination-based), using the Department of Revenue's published Remote Seller and Marketplace Facilitator rate tables.
- Once you cross the $100,000 threshold, Arizona requires you to begin collecting in the month following 30 days after you met it. Plan your billing cutover date around that window, not just your registration date.
Where Ziptax helps
If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.
Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.
- Rooftop precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, eliminating the accuracy liabilities of ZIP-based shortcuts.
- Engineered for platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
- Frictionless pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
- The TaxCloud runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.
Get Arizona SaaS tax rates from an API
Address-level rates for every Arizona jurisdiction, plus the rest of the US, Canada, and select other markets, through the Ziptax Sales Tax API.
Frequently asked questions
Do you have to register in Arizona if you sell SaaS? Yes, if you cross Arizona's $100,000 threshold or have physical presence in the state. Unlike states where SaaS is currently exempt, there's no separate carve-out to track here: because SaaS is taxable TPP rental revenue in Arizona, it counts toward the $100,000 threshold the same as any other sale, from your first dollar of Arizona revenue.
Does Arizona tax SaaS differently depending on how it's delivered? No, not in the way some states split it. Remotely accessed SaaS, downloaded prewritten software, and software on physical media are all treated as taxable in Arizona, whether classified as a rental of tangible personal property (SaaS) or a retail sale of tangible personal property (downloads and physical media). The distinction that matters more in Arizona is whether software is genuinely custom-built for one customer, which is an exempt professional service.
Can you use a ZIP code to get the Arizona TPT rate? Not reliably. Arizona's county and city TPT boundaries don't align with ZIP code boundaries, and the applicable rate also depends on whether you're sourcing to your own business location or to the customer's address. Two customers in the same ZIP code can fall under different city tax rates, and a seller resolving rates by ZIP alone risks both under- and over-collecting. Resolve rates using the full street-level address.
Is Arizona's SaaS tax position final, or could it change? The current operative rule is fully settled. SaaS is taxable, as confirmed by the Arizona Court of Appeals in ADP, LLC v. Arizona Department of Revenue (2023). The Arizona Supreme Court explicitly denied further review of the case in September 2023, firmly closing the matter. There are no pending statutory shifts, so engineering teams should build their tax logic around SaaS being fully taxable in the state.
Sources
- SaaS Taxability (Personal Property Rental Classification): Arizona Revised Statutes § 42-5071 &Arizona Department of Revenue Taxpayer Information Ruling LR11-011.
- Court Confirmation: ADP, LLC v. Arizona Department of Revenue, Arizona Court of Appeals, Division One, No. 1 CA-TX 21-0009 (Jan. 31, 2023); Review Denied by Arizona Supreme Court, Case No. CV-23-0056-PR (Sept. 12, 2023).Snell & Wilmer Case Analysis.
- Custom & Prewritten Software Classifications: Arizona Administrative Code § R15-5-154 (Computer Hardware, Software, and Data Services).
- Definition of Tangible Personal Property: Arizona Revised Statutes § 42-5001(21).
- Economic Nexus and the $100k Threshold: Arizona Department of Revenue, Economic Threshold (Out-of-State Sellers).
- Out-of-State Seller Licensing & Registration: Arizona Department of Revenue, Out-of-State Sellers.
- Marketplace Facilitator & Remote Seller Sourcing Rules: Arizona Department of Revenue, Filing Requirements for Remote Sellers and Marketplace Facilitators.
- Quarterly Rate Tables: Arizona Department of Revenue, TPT Rate Tables & Remote Seller Location Tables.
- Local Audit Authority & Multi-City Unified Audits: Arizona Revised Statutes § 42-6001 and§ 42-6005, as amended by House Bill 2380 (Laws 2024, Chapter 33).
- Streamlined Sales Tax (SST) Status: Streamlined Sales Tax Governing Board, Member State Directory.