Computer Software & SaaS · Arizona

Arizona Computer, Software, and SaaS Tax Guide

ByGerald J. Donnini II, Esq.·Tax Attorney

Table of Contents

  • Introduction
  • Nexus Considerations
  • General Rules and Compliance Considerations
  • Specific Exemptions
  • Sourcing Rules
  • Audit Considerations
  • Voluntary Disclosure Agreements (VDAs)
  • Conclusion
  • References & Resources

1. Introduction

For software companies, SaaS providers, and technology firms conducting business in Arizona, understanding the state's Transaction Privilege Tax (TPT) rules is essential. Unlike many states that use a traditional sales tax system, Arizona's TPT is a tax on the vendor for the privilege of doing business in the state. This distinction is important, as it means the vendor—not the customer—bears the legal responsibility for the tax, even though the tax may be passed on to customers.

Arizona has developed specific regulations regarding the taxation of software, digital goods, and technology services under Arizona Revised Statutes § 42-5001 and related provisions. The state makes important distinctions between prewritten (canned) software, custom software, and cloud- based services, with tax treatment varying based on delivery methods and customization levels. Most critically for technology companies, Arizona takes the position that electronically delivered software and SaaS offerings are taxable under the retail and personal property rental classifications, respectively—a significant contrast to states like Florida that exempt these digital products.

Purpose of This Guide

This guide helps businesses navigate Arizona's TPT rules related to software and technology services, focusing on:

  • Nexus Considerations: Understanding when businesses must register and collect Arizona TPT due to physical or economic presence.

> Important — TPR 24-1 (December 6, 2024): Per ADOR's ruling, Arizona's economic-nexus threshold counts retail-classified sales only. SaaS and other personal-property-rental revenue does not count toward the $100,000 threshold and, absent physical presence, does not by itself create a TPT collection duty. The ruling states that "economic nexus and the thresholds established by the State only apply to sales under the retail classification; thus, gross income and gross proceeds of sales derived by an out-of-state business under other classifications, such as personal property rentals, do not go toward establishing economic nexus." Note that physical presence (employees, inventory, servers, in-state agents) still triggers TPT across all classifications, including SaaS, from the first dollar. • Taxability of Software & Services: Clarifying the tax treatment of prewritten vs. custom software, cloud computing services, and related technology offerings. • Sourcing Rules: Determining how and where transactions are taxed based on customer location and method of software delivery. • Audit Considerations: Identifying common tax audit triggers and best practices for compliance. • Voluntary Disclosure Agreements (VDAs): Explaining the process for businesses to rectify past noncompliance while mitigating penalties.

Why This Matters for Technology Companies

Arizona's TPT laws impact software companies, SaaS providers, and technology firms in multiple ways:

  • TPT Obligations: Businesses selling software or related services to Arizona customers may have a duty to collect and remit Arizona TPT, depending on how the product is classified and whether the business has nexus. Importantly, because Arizona classifies SaaS as a personal property rental—not a retail sale—a remote vendor with no physical presence has subscription revenue that is rental-classified and therefore falls outside Arizona's economic-nexus thresholds. Physical presence in Arizona, however, makes all SaaS revenue taxable. Economic presence alone does not automatically obligate a remote SaaS seller to collect.
  • SaaS Complexity: Arizona treats SaaS as taxable under the personal property rental classification, despite no explicit statutory language addressing digital services.
  • Compliance Risks: Failure to correctly assess and collect TPT can result in significant penalties, interest, and extended audit exposure.

This guide walks through Arizona's specific TPT rules governing software, SaaS, and technology-related services while referencing applicable statutes, administrative rules, and Arizona Department of Revenue (ADOR) guidance.

2. Nexus Considerations

Understanding Nexus and Its Impact on TPT Obligations

Nexus determines whether a business has a sufficient connection to Arizona to require the collection and remittance of TPT. Businesses with nexus must comply with Arizona's TPT regulations, including registration, collection, and remittance. If a business fails to recognize or act upon its nexus obligations, it could face audits, back taxes, interest, and penalties—potentially extending back many years if the Arizona Department of Revenue determines non-compliance was intentional.

For software and technology companies, nexus determination is particularly important because Arizona's TPT applies to both physically delivered and electronically delivered software products. Unlike states that only impose tax collection requirements on tangible goods, Arizona's nexus rules affect businesses selling digital products and services, creating broader compliance obligations for technology companies.

Arizona establishes nexus through both physical presence and economic activity under [A.R.S. § 42-5044](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05044.htm). Businesses selling into Arizona must assess whether their activities create a taxable presence under existing statutes.

2.2 Physical Presence Nexus in Arizona

Physical presence nexus occurs when a business has a tangible footprint in Arizona. Under [A.R.S. § 42-5044](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05044.htm) and established case law, activities that create physical presence nexus include:

Business Facilities and Personnel

  • Property in Arizona:
  • Maintaining an office, store, warehouse, or storage facility
  • Owning or leasing real property
  • Installing or maintaining servers or data centers
  • Keeping inventory within Arizona borders
  • Personnel Activities:
  • Having employees who reside or regularly work in Arizona
  • Employing salespeople who solicit business in the state
  • Utilizing service technicians who perform installation or repairs
  • Remote employees working from home offices in Arizona
  • Representative Relationships:
  • Independent contractors who represent the company in Arizona
  • Affiliate relationships with in-state entities that create a substantial connection
  • Authorized installers or service providers acting on the company's behalf

Temporary or Limited Activities

  • Business Events:
  • Attending trade shows, conferences, or business exhibitions
  • Conducting training sessions or seminars
  • Participating in industry conventions
  • Delivery and Installation:
  • Using company-owned vehicles for deliveries in Arizona
  • Providing installation services for products sold
  • Performing on-site setup or configuration of software

Technology-Specific Physical Presence Indicators

  • Hardware and Infrastructure:
  • Servers or data centers located in Arizona
  • Network equipment installed at Arizona locations
  • Digital kiosks or terminals placed in the state
  • Support and Services:
  • On-site technical support personnel
  • Customer training staff who travel to Arizona
  • Contract developers or IT consultants working in Arizona

Example 1: A SaaS company headquartered in California maintains a small satellite office in Tempe, Arizona with three technical support specialists who serve clients across the Southwest region. Even though most of the company's development work occurs outside Arizona and its servers are hosted in Nevada, the presence of employees working from a physical location in Arizona establishes clear physical presence nexus, requiring the company to register for TPT and collect tax on all taxable sales to Arizona customers.

Example 2: A software development company based in Texas has no offices or employees in Arizona, but it sends representatives to attend a major technology conference in Phoenix for one week each year, where they demonstrate their products and collect leads. This temporary presence alone could potentially establish nexus requiring TPT registration, particularly if the company solicits sales during the conference and regularly generates significant business from these Arizona activities.

2.3 Economic Nexus in Arizona

Arizona enforces an economic nexus standard requiring remote sellers to collect and remit TPT if they have more than $100,000 in annual sales to customers in Arizona in the current or previous calendar year. This economic nexus standard, codified in [A.R.S. § 42-5044](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05044.htm), creates tax obligations even for businesses without physical presence in the state.

Key Economic Nexus Provisions for Software and Technology Companies

  • Sales Threshold:
  • $100,000 in annual gross proceeds of sales or gross income in the current or previous calendar year
  • No transaction threshold requirement (unlike some states that also have a minimum number of transactions)
  • Threshold applies to retail sales, remote sales, and marketplace facilitated sales combined
  • Included Transactions:
  • Both tangible personal property and digital products/services count toward the threshold
  • Prewritten software (regardless of delivery method) counts toward the threshold
  • SaaS and other cloud services count toward the threshold
  • Both exempt and taxable sales are included when calculating the threshold amount
  • Measurement Period:
  • Previous calendar year (January 1 - December 31)
  • Current calendar year (ongoing measurement)
  • Once the threshold is exceeded, registration is required within 30 days
  • Registration Timeline:
  • Within 30 days of meeting the threshold
  • Registration is required through [AZTaxes.gov](https://aztaxes.gov/) or [Arizona Business One Stop](https://onestop.az.gov/)
  • Companies must begin collecting TPT on the first day of the month following registration

Specific Implications for Digital Products and Services

What's particularly important for software and SaaS companies is that Arizona includes electronically delivered software and SaaS in the economic nexus threshold calculation. Unlike some states that only include tangible property sales in their economic nexus threshold (such as Florida), Arizona's threshold includes both tangible and digital products.

This means that:

  • Companies selling only digital products (like downloadable software or SaaS) can establish economic nexus if their Arizona sales exceed $100,000
  • The taxability of the product or service does not matter for threshold purposes—even exempt sales count toward the threshold
  • Companies must track all Arizona sales, regardless of delivery method or product type

Example: A cloud-based project management software company headquartered in Colorado has no physical presence in Arizona. The company tracks its Arizona sales and determines it had $112,000 in subscription revenues from Arizona customers in the previous calendar year. Despite having no office, employees, or servers in Arizona, the company has established economic nexus under Arizona law and must register for TPT within 30 days of exceeding the threshold. Going forward, the company must collect and remit TPT on its SaaS subscriptions sold to Arizona customers at the rate applicable to its principal business location (in this case, the Colorado headquarters location would determine which Arizona tax rate to apply).

2.4 Marketplace Facilitator Rules in Arizona

Arizona has specific marketplace facilitator rules codified in [A.R.S. § 42-5076](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05076.htm) that require platforms such as Amazon, eBay, and Shopify to collect and remit TPT on behalf of third-party sellers. These rules have significant implications for software and digital product providers who sell through these channels.

Definition and Scope:

Under Arizona law, a marketplace facilitator is defined as a person or entity that:

  • Facilitates a retail sale by a marketplace seller by listing or advertising the seller's products
  • Directly or indirectly collects payment from the purchaser and transmits payment to the marketplace seller

Both conditions must be met to qualify as a marketplace facilitator. Common examples include:

  • App stores (Apple App Store, Google Play)
  • E-commerce platforms (Amazon, eBay)
  • Software marketplaces (Salesforce AppExchange)
  • Digital content platforms (Steam, Adobe Exchange)

Key Requirements and Thresholds:

  • Economic Nexus Threshold: Marketplace facilitators must collect and remit TPT if they exceed $100,000 in sales to Arizona customers in the current or previous calendar year.
  • Scope of Collection Responsibility: Once the threshold is met, the facilitator must collect TPT on ALL sales facilitated through their platform, regardless of whether individual sellers would have a collection obligation.
  • Tax Classification: Sales by marketplace facilitators are typically classified under the retail or personal property rental classification depending on the nature of the transaction.
  • Local Tax Rates: Marketplace facilitators generally collect tax at the rate applicable to the Arizona business location where they receive orders.

Impact on Software and Technology Sellers:

For software developers, SaaS providers, and other technology companies using marketplace platforms:

  • Collection Responsibilities Shift: The marketplace facilitator—not the individual seller—becomes responsible for collecting and remitting TPT.
  • Documentation Requirements: Sellers should maintain records of marketplace sales with TPT collected by the facilitator separate from direct sales.
  • Verification Responsibilities: Software sellers should verify that facilitators are properly collecting TPT, as the ultimate liability for uncollected tax may remain with the seller if the facilitator fails to comply.
  • Mixed Sales Channels: If a business sells both through marketplaces and directly to customers, they must still register and collect TPT on their direct sales if they establish nexus in Arizona.

Compliance Best Practices:

  • Marketplace Agreements: Review marketplace terms and conditions to understand tax collection responsibilities
  • Tax Settings: Ensure marketplace seller tax settings correctly identify taxable products
  • Record-keeping: Maintain separate records of marketplace vs. direct sales
  • Exemption Certificates: Understand how marketplace facilitators handle exempt transactions

Example: A software development company creates specialized accounting applications and sells them through both its own website and the Salesforce AppExchange marketplace. For sales made through AppExchange to Arizona customers, Salesforce (as the marketplace facilitator) is responsible for collecting and remitting the applicable TPT. However, for sales made directly through the developer's website, the developer must determine its own nexus status and TPT collection obligations. If the developer exceeds the $100,000 economic nexus threshold through combined marketplace and direct sales, it must register and collect TPT on its direct sales, while Salesforce continues handling tax collection for marketplace transactions.

Compliance Obligations and Registration

Businesses that establish nexus through physical presence or economic thresholds must register for TPT collection with the Arizona Department of Revenue. Once registered, businesses are required to collect the applicable state and local TPT on taxable transactions and remit these amounts to the state.

Registration can be completed online through [AZTaxes.gov](https://aztaxes.gov/) or [Arizona Business One Stop](https://onestop.az.gov/). The cost for each TPT license is $12 per location. Businesses with multiple locations can opt for a consolidated license, allowing them to file a single return.

Conclusion: Proactive Nexus Management

Understanding and managing nexus is essential for TPT compliance in Arizona. With Arizona's economic nexus threshold of $100,000 in annual sales, businesses must track their revenue carefully.

To ensure compliance, businesses should:

  • Regularly assess their business activities in Arizona
  • Monitor sales volumes to determine when they cross the economic nexus threshold
  • Register for TPT collection when necessary
  • Track regulatory changes that could impact nexus requirements
  • Maintain accurate sales records and consult tax professionals to ensure compliance

3. General Rules and Compliance Considerations

Introduction

Determining the taxability of software, cloud computing, and related technology services in Arizona requires careful analysis of how products and services are structured, delivered, and classified under state law. Arizona's TPT laws provide distinct rules for prewritten and custom software, maintenance agreements, information services, and bundled transactions.

3.1 Prewritten (Canned) Software

Prewritten or "canned" software refers to standardized software developed for sale to multiple customers without significant modification. In Arizona, the taxability of prewritten software is governed by [A.R.S. § 42-5061](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05061.htm) for retail sales and [A.R.S. § 42-5071](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05071.htm) for rental/subscription arrangements:

  • Taxable Regardless of Delivery Method: Unlike states like Florida that exempt electronically delivered software, Arizona considers prewritten software to be tangible personal property (TPP) subject to Arizona TPT regardless of how it's delivered. This includes:
  • Software delivered on physical media (CDs, USB drives, etc.)
  • Software downloaded directly to the customer's device
  • Software delivered via email or file transfer
  • Access codes or license keys that activate downloaded software
  • Classification Determines Tax Rate:
  • Retail Classification (A.R.S. § 42-5061): One-time sales of prewritten software are taxed at the combined state (5.6%), county, and city rates applicable to the seller's location
  • Personal Property Rental Classification (A.R.S. § 42-5071): Leased or subscription-based prewritten software is taxed under this classification, which may have different local tax rates
  • Taxability Does Not Depend on Use: Whether the software will be used for business or personal purposes does not affect its taxability – all prewritten software is taxable unless a specific exemption applies.

Example: An Arizona business with offices in Tempe purchases accounting software through download for $5,000 from a software vendor based in Phoenix. Since Arizona considers prewritten software as tangible personal property regardless of delivery method, this transaction is subject to TPT at the Phoenix rate (currently 8.6% combined state, county, and city tax). The Phoenix-based vendor would need to collect approximately $430 in TPT on this sale, even though nothing physical was transferred to the customer and the customer is located in a different city.

3.2 Custom Software

Custom software is software that is specifically developed and tailored for a single customer's needs. In Arizona, custom software is generally treated differently from prewritten software under Arizona Transaction Privilege Tax Ruling TPR 93-48 and [A.R.S. § 42-5061](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05061.htm):

  • Professional Service Exemption: Custom software development is considered a professional service rather than a sale of tangible personal property, making it exempt from Arizona TPT. This exemption applies regardless of:
  • Delivery method (electronic or physical)
  • Billing structure (hourly, project-based, or milestone-based)
  • Who retains intellectual property rights
  • Detailed Definition: Arizona defines custom software as "any computer software which is written or prepared for a single customer, including those services represented by separately stated charges for the modification of existing prewritten programs when the modifications are written or prepared exclusively for a particular customer."
  • Documentation Requirements: To support custom software exemption claims, businesses should maintain:
  • Detailed contracts specifying the unique nature of the software
  • Scope documents outlining custom features and functionality
  • Documentation of requirements gathering specific to the customer
  • Evidence that the software is not marketed or sold to other customers
  • Modification of Prewritten Software: Charges for significantly customizing prewritten software may qualify for exemption if:
  • The modifications are substantial (not minor configuration changes)
  • The charges for customization are separately stated on invoices
  • The modifications are made exclusively for one customer

Example: A manufacturing company in Chandler, Arizona contracts with a Phoenix-based software development firm to create a custom inventory management system specifically designed for their unique production processes, materials tracking requirements, and integration with their proprietary machinery. The developer charges $175,000 for this project, with detailed specifications documenting the customer-specific nature of the solution. Since this is genuinely custom software developed exclusively for a single customer's needs, the entire $175,000 is exempt from TPT as a professional service. The developer should maintain detailed documentation of the custom nature of the project in case of audit.

3.3 Software as a Service (SaaS)

Arizona treats Software as a Service (SaaS) as taxable based on several key rulings from the Arizona Department of Revenue (ADOR) and court decisions:

  • Taxable: Arizona considers SaaS to be a lease of tangible personal property, subject to TPT under the personal property rental classification at a rate of 5.6% state tax plus applicable county and city taxes.
  • Judicial Precedent: In ADP, LLC v. Arizona Department of Revenue, the Arizona Court of Appeals affirmed that SaaS constitutes a lease of tangible personal property subject to TPT, even when hosted on servers outside Arizona. The court determined that customers' use of the provider's software through remote access constituted a taxable lease transaction.
  • Rental Classification: Under [Arizona Revised Statutes § 42-5071](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05071.htm), the leasing or renting of tangible personal property is subject to TPT, which the ADOR applies to SaaS offerings.

Example: A Phoenix-based business subscribes to a cloud-based customer relationship management (CRM) platform for $12,000 annually. Since Arizona treats SaaS as a taxable lease of tangible personal property, this subscription is subject to TPT under the personal property rental classification. The total tax would include the state rate of 5.6% plus applicable local taxes (which can vary significantly). If the SaaS provider operates out of state but has economic nexus in Arizona, they must collect and remit this tax.

3.4 Information Services vs. Professional Services

Arizona differentiates between taxable information services and non-taxable professional services, a distinction that significantly impacts technology companies offering data-related services:

  • Taxable Information Services:
  • Services involving the collection, compilation, or analysis of general data sold to multiple customers
  • Database access with standardized reports and analysis
  • Information aggregation services that don't involve substantial professional judgment
  • Standardized market research reports sold to multiple clients
  • Online reference libraries or databases with standard content
  • Syndicated data feeds with minimal customization
  • Non-Taxable Professional Services:
  • Consulting that involves application of professional expertise and judgment
  • IT support services provided by qualified professionals
  • Software customization services based on client requirements
  • Tailored data analysis requiring specialized knowledge or judgment
  • Training and implementation services
  • Systems architecture and design work
  • Key Differentiating Factors according to Arizona DOR rulings:
  • Level of Customization: More customized services tend to be considered professional services
  • Professional Judgment: Services requiring significant professional expertise or judgment are generally exempt
  • Uniqueness: Services provided uniquely to a specific client are more likely to be exempt
  • Educational Qualifications: Services provided by individuals with specialized education or credentials tend to qualify as professional services

Example 1: A marketing agency subscribes to a data provider's standardized consumer behavior database that delivers identical reports to all subscribers. The data provider makes no customizations for individual clients. This is likely taxable as an information service since the same information is provided to multiple customers without significant customization.

Example 2: A consulting firm provides a detailed financial analysis report for a technology company considering expansion into Arizona. The analysis involves consultants with financial expertise examining the client's specific situation, applying professional judgment, and creating a custom report with recommendations unique to that business. This service would be exempt from TPT as a professional service because it involves specialized expertise applied to a specific client's circumstances.

3.5 Maintenance and Support Agreements

The taxability of software maintenance agreements in Arizona depends on the structure of the contract and the nature of the services provided:

  • Taxable: If a maintenance contract includes new versions of prewritten software or updates to prewritten software components, the entire contract may be taxable.
  • Non-Taxable: If the contract only covers technical support and consultation services separately from software updates, these services may be non-taxable.

Example: A company purchases a software maintenance plan that includes both phone support and software updates. If the charges for consultation services are not separately stated from the charges for software updates, the entire contract is likely taxable.

3.6 Bundled Transactions

When taxable and non-taxable items are sold together as a single transaction in Arizona, the taxability of the entire transaction is determined by specific rules outlined in [Arizona Administrative Code R15-5-2016](https://apps.azsos.gov/public_services/Title_15/15-05.pdf) and various ADOR rulings. These rules are particularly important for technology companies that often combine software, hardware, and services:

Bundling Rules for Software and Technology

  • Default "All or Nothing" Rule: If a business sells a package that includes both taxable items (like prewritten software) and non-taxable components (like professional services) without separately stating the charges, the entire amount is generally subject to TPT.
  • Itemization Requirements:
  • Charges must be separately stated on the same invoice or billing document
  • Each component must be reasonably priced (not artificially allocated to minimize tax)
  • Customers must have the option to purchase components separately
  • Documentation must support the business purpose of the separate components
  • Separately Stated Charges: When properly itemized, only the taxable portion (such as prewritten software or hardware) is subject to TPT, while exempt services remain untaxed.
  • Documentation Best Practices:
  • Maintain separate SKUs or product codes for taxable vs. non-taxable items
  • Include clear descriptions of each component on invoices
  • Retain contracts showing the distinct nature of bundled components
  • Document pricing methodologies used for bundled vs. unbundled sales

How to Structure Compliant Bundled Transactions

  • Clearly define each component in contracts and proposals
  • Separately state prices for each component on invoices
  • Establish stand-alone pricing for each component
  • Maintain records showing that customers can purchase components separately
  • Apply TPT only to the taxable components

Example: A Phoenix-based technology firm sells an enterprise software implementation package for $100,000, which includes:

Scenario 1 - Improper Bundling: The company provides a single invoice for "Enterprise Software Solution" - $100,000 Result: The entire $100,000 is subject to TPT, even though a significant portion represents exempt professional services.

Scenario 2 - Proper Unbundling: The company itemizes the invoice as:

  • Prewritten Enterprise Software License - $65,000 (taxable)
  • Custom Interface Development - $15,000 (exempt professional service)
  • Implementation Services - $12,000 (exempt professional service)
  • Training - $8,000 (exempt professional service) Result: Only the $65,000 software license is subject to TPT, saving the client approximately $3,010 in tax (at an 8.6% combined rate) on the $35,000 of exempt services.

This structuring makes the transaction more attractive to clients while ensuring proper TPT compliance.

4. Specific Exemptions

Introduction

Arizona provides various exemptions from TPT for specific types of software, technology services, and related activities. Understanding these exemptions is crucial for businesses to properly structure transactions and avoid unnecessary tax liabilities.

4.1 Exemption for Custom Software

Custom software developed exclusively for a single customer is exempt from Arizona TPT. Since the transaction is considered a professional service rather than a sale of tangible personal property, no tax is imposed on the charges associated with custom software development.

  • Definition: Arizona defines custom software as any computer software that is written or prepared exclusively for a single customer, including separately stated charges for the modification of existing prewritten programs when the modifications are written or prepared exclusively for a particular customer.
  • Scope of Exemption: This exemption applies regardless of delivery method (electronic or physical).

Example: A business hires a software firm to create a tailored accounting program for its internal use. Since the software is uniquely designed and not resold to multiple customers, the transaction is exempt.

4.2 Exemption for Software Maintenance Services

When software maintenance contracts are structured properly, certain components may be exempt from TPT according to [A.R.S. § 42-5061](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05061.htm) and ADOR interpretations:

  • Non-Taxable Components:
  • Consultation services that are separately stated on invoices
  • Telephone or email technical support provided by qualified staff
  • Training services related to software use
  • Troubleshooting and problem diagnosis
  • Remote access technical assistance
  • Required Criteria for Exemption:
  • The maintenance contract must separately state charges for consultation services on invoices and contracts
  • The customer must have the option to purchase these services separately from software updates
  • The service components must genuinely represent professional services rather than disguised software updates
  • Taxable Components:
  • Software updates, patches, and bug fixes for prewritten software
  • New versions or modules of the software
  • Any maintenance services bundled with software updates without separate itemization
  • Access to knowledge bases or documentation when bundled with updates

Example: An Arizona-based software company offers an annual maintenance plan with the following structure:

  • Technical support package: $1,800/year (phone support, remote troubleshooting, email assistance)
  • Software updates package: $3,200/year (quarterly updates, patches, new features)

Customers can purchase either package independently or both together. On invoices, these charges appear as separate line items with distinct descriptions. Under Arizona's TPT rules, the $1,800 technical support package qualifies as an exempt professional service, while the $3,200 software updates package remains taxable. By structuring their offering this way, the company ensures that customers who only need support services can purchase them tax-free, while maintaining proper TPT compliance on the taxable software components.

4.3 Exemption for Resale

Software purchased for resale may be exempt from TPT if the purchaser provides a valid resale certificate to the vendor and subsequently resells the software in the regular course of business. This exemption, based on [A.R.S. § 42-5061(A)(1)](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05061.htm) and described in [Arizona Publication 623](https://azdor.gov/sites/default/files/media/PUBLICATION_623.pdf), is particularly relevant for software retailers, value-added resellers (VARs), and marketplace facilitators:

Requirements for the Resale Exemption:

  • Documentation Required:
  • The purchaser must provide a properly completed Arizona Form 5000A (Arizona Resale Certificate) to the vendor at the time of purchase
  • The certificate must include the purchaser's TPT license number and required information about the nature of their business
  • Digital copies of resale certificates are acceptable if they contain all required information
  • Qualified Purchases:
  • Software must be purchased exclusively for resale in the ordinary course of business
  • The purchaser cannot use the software for any purpose other than demonstration or display while holding it for sale
  • Software must be in the same form when resold (though minimal installation or configuration is permitted)
  • Limitations and Restrictions:
  • Software purchased for internal use, even partially, does not qualify
  • Software that will be substantially modified before resale does not qualify under this exemption (though it might qualify as a custom software service)
  • Resale certificates cannot be used retroactively after a purchase has been completed

Taxable Event Upon Resale:

  • The subsequent sale of the software to the final customer is subject to TPT
  • The reseller must collect and remit TPT on the full selling price
  • Different TPT rates may apply to the resale transaction depending on the location where the reseller receives the order

TPT License Requirements:

  • To issue a valid resale certificate, the purchaser must hold an active Arizona TPT license
  • Out-of-state resellers without Arizona locations may be able to use their home state resale certificates if they meet certain requirements
  • Marketplace facilitators reselling software must ensure they are properly registered for TPT collection

Example: A software solutions provider in Scottsdale purchases accounting software licenses from a publisher for $40,000 with the intent to resell them as part of technology packages to its Arizona clients. The provider presents a properly completed Form 5000A to the publisher, certifying that these licenses are exclusively for resale.

The provider's purchase is exempt from TPT based on the resale certificate. When the provider later sells these software licenses to an end-user client for $60,000 as part of a $100,000 technology solution package (with the remaining $40,000 being exempt professional services that are separately stated), the provider must collect and remit TPT on the $60,000 software component at the applicable Scottsdale rate.

4.4 Other Technology-Related Exemptions

Arizona offers certain additional exemptions that may apply to technology businesses:

  • Research and Development Equipment: Machinery and equipment used directly in research and development activities may be exempt from TPT under certain conditions.
  • Manufacturing Equipment: Computer equipment used directly in manufacturing operations may qualify for exemption under Arizona's manufacturing equipment exemption.
  • Sales to Qualifying Healthcare Organizations: Software and technology products sold to qualifying healthcare organizations may be exempt when certain conditions are met.

5. Sourcing Rules

Introduction

Sourcing rules determine which sales are subject to Arizona TPT based on the location where a taxable transaction is deemed to occur. These rules are particularly important for businesses that sell software, cloud services, and digital goods, as different rules may apply depending on whether the product is physically delivered, downloaded, or accessed remotely.

5.1 Arizona's Origin-Based Sourcing

Arizona is primarily an origin-based sourcing state for TPT purposes, meaning that:

  • Origin-Based: For most transactions, TPT is based on the location of the seller rather than the location of the customer.
  • Seller's Business Location: If the seller receives an order at an Arizona business location, the sale is sourced to that business location, and the TPT rate for that location applies.

This origin-based approach differs from many states that use destination-based sourcing (where tax is based on the delivery location).

5.2 Sourcing Rules for Software Sales

For software transactions, the sourcing rules depend on how the software is delivered, as established in [A.R.S. § 42-5040](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05040.htm):

  • Tangible Media: When software is delivered on physical media (CD, USB drive), the transaction is sourced to the business location of the seller where the order is received. This means the applicable state, county, and city tax rates are determined by the seller's business location, not the customer's location.
  • Electronic Delivery: For electronically delivered software, including downloads and SaaS, the transaction is still sourced to the business location of the seller where the order is received. This origin-based approach applies consistently regardless of delivery method.
  • Multiple Business Locations: If a software company maintains multiple business locations in Arizona, the applicable tax rate is determined by which location received the order, processed the sale, or arranged for delivery—not necessarily where the software was developed or where company headquarters are located.

Example: A software company with an office in Phoenix sells prewritten software to customers throughout Arizona, including customers in Tucson, Flagstaff, and rural areas. The company's Phoenix office processes all orders. For TPT purposes, all these sales are sourced to Phoenix regardless of the customer's location. Therefore, the company would apply:

  • The state rate of 5.6%
  • Maricopa County rate of 0.7%
  • Phoenix city rate of 2.3%

This results in a combined TPT rate of 8.6% on all sales, even for customers located in cities with different local tax rates. If the company later opens a second office in Tucson that begins processing orders for southern Arizona customers, those specific sales would then be sourced to Tucson and subject to Tucson's combined TPT rate instead.

5.3 Sourcing Rules for SaaS and Cloud-Based Services

For SaaS and cloud-based services, which Arizona treats as leases of tangible personal property:

  • Seller's Location: The transaction is sourced to the seller's business location in Arizona where the order is received.
  • Remote Sellers: For remote sellers with no physical location in Arizona, but who have economic nexus, the applicable TPT rate is determined by the seller's principally conducted business activity.

Example: A SaaS provider based outside Arizona with economic nexus sells subscriptions to Arizona customers. The provider must collect and remit Arizona TPT based on the applicable state and local rates for its principally conducted business activity.

5.4 Multi-State Transactions and Use Tax Considerations

When software and digital products are sold to businesses with multi-state operations, determining the appropriate tax jurisdiction becomes complex. Arizona's use tax complements the TPT system and applies when taxable items are purchased from out-of-state vendors that don't collect Arizona TPT. Understanding these rules is critical for technology companies with customers or operations that span multiple states.

Arizona Use Tax Framework

Arizona's use tax is governed by [A.R.S. § 42-5155](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05155.htm) and applies to the storage, use, or consumption of tangible personal property in Arizona upon which TPT was not paid:

  • Tax Rate: Arizona's use tax rate is 5.6% at the state level, matching the state TPT rate. Local use taxes may also apply depending on the jurisdiction.
  • Application to Software and Digital Products:
  • Prewritten software installed or used in Arizona but purchased from out-of-state vendors
  • Downloaded software used in Arizona from vendors that don't collect TPT
  • Subscriptions to SaaS platforms accessed in Arizona from non-collecting vendors
  • Responsibility: The purchaser is responsible for self-assessing and remitting use tax directly to the Arizona Department of Revenue if the seller does not collect it.

Multi-State Software Allocation Rules

For software licenses or subscriptions used across multiple states, Arizona provides guidance on allocating the taxable portion:

  • Software License Allocation:
  • Based on the percentage of users physically located in Arizona
  • Alternatively, based on formal license terms that specify user allocation by state
  • Documentation of the allocation methodology is essential for audit defense
  • SaaS and Cloud Services Allocation:
  • Generally based on the location of users accessing the service
  • Should be consistently applied and documented
  • May require coordination with the vendor's collection practices
  • Master License Agreements:
  • Enterprise-wide agreements covering multiple states require careful allocation
  • Documentation should include user counts or access logs by location
  • Corporate contracts should consider tax implications in their structure

Documentation Requirements

To support multi-state allocations and use tax compliance, businesses should maintain:

  • User Location Records: Documentation of employee or user locations by state
  • Access Logs: Records showing where services are accessed geographically
  • License Agreements: Contracts specifying how licenses are allocated by location
  • Exemption Certificates: Valid certificates for any exempt portion of multi-state purchases
  • Use Tax Payment Records: Evidence of tax paid to other states to avoid double taxation

Practical Examples

Example 1 - Multi-State Enterprise Software License: A national retail company with headquarters in Phoenix purchases enterprise resource planning (ERP) software from a California vendor for $500,000. The software will be used by employees across 10 states, with 30% of users located in Arizona. The California vendor is not registered to collect Arizona TPT.

Calculation:

  • Taxable amount allocated to Arizona: $500,000 × 30% = $150,000
  • Arizona state use tax: $150,000 × 5.6% = $8,400
  • Additional local use tax may apply depending on the specific Arizona jurisdiction

The company must self-report and remit this use tax to the Arizona Department of Revenue on its regular use tax return.

Example 2 - SaaS with Multi-State Operations: An Arizona-based manufacturing company subscribes to a cloud-based analytics platform from a Tennessee provider for $200,000 annually. The company has operations in Arizona (60%), Nevada (25%), and Utah (15%), with users accessing the platform from all three states. The Tennessee provider has nexus in Nevada and Utah but not in Arizona.

Compliance Requirements:

  • The Arizona company must self-assess use tax on the Arizona portion: $200,000 × 60% = $120,000 taxable in Arizona
  • Arizona state use tax due: $120,000 × 5.6% = $6,720
  • The SaaS provider will collect sales tax on the Nevada and Utah portions based on those states' rules
  • The company should maintain documentation of this allocation methodology

This approach ensures proper compliance while avoiding taxation of the same subscription in multiple states.

6. Audit Considerations

Introduction

TPT audits are a critical aspect of compliance for businesses operating in Arizona, particularly in the software, SaaS, and technology industries. The Arizona Department of Revenue (ADOR) routinely conducts audits to ensure businesses are correctly collecting and remitting TPT. Given Arizona's stance that SaaS and electronically delivered software are taxable, businesses operating in this space may be subject to audit for failing to collect TPT on their transactions.

6.1 Common Audit Triggers for Software and Technology Businesses

Although Arizona taxes electronically delivered software and SaaS, many technology businesses still misunderstand their TPT obligations or face compliance challenges due to the complex nature of digital products and services. The Arizona Department of Revenue (ADOR) has identified several common issues that may trigger audits for software and technology companies:

1. Nexus and Registration Issues

  • Economic Nexus Threshold Errors:
  • Failing to monitor when sales exceed the $100,000 threshold
  • Incorrectly excluding digital product sales from threshold calculations
  • Not registering within 30 days of exceeding the threshold as required by [A.R.S. § 42-5044](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/05044.htm)
  • Physical Presence Misinterpretation:
  • Unrecognized nexus through remote employees working in Arizona
  • Failing to register after temporary business activities like trade shows
  • Not accounting for in-state servers or data centers that create nexus
  • Marketplace Facilitator Confusion:
  • Assuming marketplace facilitators handle all tax obligations when selling through multiple channels
  • Failure to verify proper tax collection by marketplace facilitators
  • Not registering for direct sales when also selling through marketplaces

2. Product and Service Classification Errors

  • Misclassification of Software:
  • Incorrectly treating prewritten software as custom software to avoid TPT
  • Mischaracterizing taxable SaaS as non-taxable services
  • Applying classifications inconsistently across similar products
  • Delivery Method Misinterpretation:
  • Erroneously believing electronically delivered software is exempt (as it is in some other states)
  • Inconsistently classifying the same software delivered through different methods
  • Failing to document delivery methods for audit defense purposes
  • Inconsistent Treatment of Similar Transactions:
  • Taxing certain SaaS offerings but not others without clear distinction
  • Varying treatment of substantially similar services based on contract language rather than actual service provided
  • Treating identical products differently based on customer type without statutory basis

3. Bundling and Invoice Issues

  • Bundled Transactions Without Separation of Charges:
  • Selling both taxable components (software) and non-taxable services (consulting) without separately stating charges
  • Inadequate documentation to support allocation between taxable and non-taxable items
  • Artificially shifting value between taxable and non-taxable components to minimize tax
  • Inconsistent Invoicing Practices:
  • Using different invoice formats that treat similar transactions inconsistently
  • Vague product or service descriptions that make taxability determinations difficult
  • Missing or inadequate information on delivery methods, locations, or service types
  • Improper Discount Allocation:
  • Applying discounts disproportionately to taxable components to reduce the tax base
  • Not clearly documenting how discounts are allocated in bundled transactions
  • Inconsistent discount policies that vary based on tax consequences rather than business practices

4. Documentation and Procedural Deficiencies

  • Exemption Certificate Management:
  • Accepting incomplete or expired exemption certificates
  • Failing to collect certificates at the time of sale
  • Not maintaining proper exemption certificate files for the required retention period
  • Inadequate Record Retention:
  • Not maintaining records for the statutory four-year period as required by [A.R.S. § 42-1104](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/01104.htm)
  • Inability to produce supporting documentation during an audit
  • Missing transaction details needed to verify proper tax treatment
  • Filing and Reporting Errors:
  • Inconsistencies between federal income tax returns and TPT returns
  • Unusual patterns in reported sales or deductions compared to industry norms
  • Failing to file returns for specific business locations or activities

Real-World Example:

A Scottsdale-based software company offers both standard accounting software (taxable) and custom implementation services (exempt). During an ADOR audit, the company faces scrutiny because:

  • Their invoices use vague descriptions like "Software Solution Package" without distinguishing between taxable software and exempt services
  • They used inconsistent tax treatments for similar transactions—collecting TPT on some bundled sales but not others
  • They improperly documented delivery methods, making it difficult to verify their claim that certain transactions were exempt custom software
  • They failed to maintain complete exemption certificates for sales claimed as exempt

The audit results in a significant assessment of back taxes, interest, and penalties that could have been avoided with proper classification, documentation, and invoicing practices.

6.2 The Arizona TPT Audit Process

The ADOR follows a structured audit process. Understanding what to expect can help businesses prepare and minimize risks:

  • Initial Contact & Notice of Audit
  • Businesses receive an official Audit Notification Letter specifying the audit period and required documentation.
  • The typical audit period is three years but can extend further if substantial underreporting is suspected.
  • Information Gathering & Records Request
  • Auditors request TPT returns, invoices, exemption certificates, customer contracts, and supporting documentation.
  • Software and SaaS providers should prepare detailed records of transactions, including delivery methods and contract terms.
  • Fieldwork & Review of Transactions
  • The auditor examines sample transactions to verify tax compliance.
  • If discrepancies are found in a sample period, auditors may extrapolate errors across the entire audit period.
  • Preliminary Findings & Business Response
  • The auditor issues preliminary findings, giving the business a chance to provide additional documentation or contest any errors.
  • This is a crucial time to correct any misunderstandings or misinterpretations.
  • Final Audit Assessment & Appeal Rights
  • After considering any disputes, ADOR issues a final assessment, which may include back taxes, interest, and penalties.
  • Businesses have the right to challenge the findings through Arizona's administrative appeals process.

6.3 Best Practices for Handling an Audit

Being proactive in compliance and documentation is the best way to minimize audit risk. Businesses should implement the following best practices:

Documentation and Record Retention

  • Maintain Clear Records: Keep detailed sales invoices, exemption certificates, contracts, and tax filings for at least four years as required by [A.R.S. § 42-1104](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/01104.htm).
  • Organize Digital Evidence: Document delivery methods for software (electronic vs. physical) with screenshots, email confirmations, or digital receipts.
  • Maintain Exemption Certificates: Keep valid resale or exempt organization certificates (Form 5000A) properly completed and accessible for all exempt sales.

Compliance Procedures

  • Properly Classify Transactions: Create clear internal guidelines for how different software products and services are categorized for tax purposes under Arizona's TPT classifications.
  • Separate Bundled Transactions: Clearly distinguish taxable software sales from exempt services on invoices, with separate line items and pricing for each component.
  • Implement Regular Tax Reviews: Schedule quarterly internal reviews of tax collection practices, especially after introducing new products or services.
  • Track Nexus Thresholds: Implement systems to automatically alert when sales approach Arizona's $100,000 economic nexus threshold.

During the Audit

  • Designate a Point Person: Assign a single knowledgeable contact to interact with auditors to maintain consistency.
  • Respond Promptly: Provide requested documentation within required timeframes to demonstrate good faith compliance.
  • Consider Professional Representation: Engage tax professionals with experience in Arizona TPT for complex technology businesses.
  • Review Preliminary Findings Carefully: Take time to thoroughly examine and address any discrepancies in the auditor's preliminary determinations.

Example: A Phoenix-based software company sells both SaaS products (taxable under the rental classification) and custom software development services (exempt as professional services). The company maintains a meticulous audit-ready system where each invoice clearly separates these components—for instance, a $50,000 project shows $30,000 for SaaS subscriptions and $20,000 for custom implementation services on separate line items. The company also keeps a digital record of all customer contracts that explicitly outline the nature of each service provided. When audited, the company can immediately produce these records, along with a consistent history of proper TPT collection on the taxable portions, significantly streamlining the audit process and reducing potential liability.

7. Voluntary Disclosure Agreements (VDAs)

Introduction

A Voluntary Disclosure Agreement (VDA) allows businesses with past-due tax liabilities to come forward voluntarily and resolve unpaid taxes while potentially reducing penalties and limiting the lookback period. For software and technology businesses in Arizona, a VDA can be particularly useful when a company has established nexus but failed to collect and remit TPT on taxable transactions, such as sales of software or SaaS offerings.

7.1 When Should a Software Business Consider a VDA?

Arizona's Voluntary Disclosure Agreement (VDA) program, administered under the authority of [A.R.S. § 42-2051](https://www.azleg.gov/viewdocument/?docName=https://www.azleg.gov/ars/42/02051.htm), is designed to encourage businesses to voluntarily comply with tax laws before being contacted by the Arizona Department of Revenue (ADOR) for an audit. The program provides significant benefits for companies seeking to resolve past noncompliance issues.

Software and technology companies should consider a VDA if they find themselves in any of the following situations:

1. Nexus Issues

  • Unregistered Economic Nexus: Businesses that exceeded Arizona's $100,000 sales threshold but failed to register for TPT
  • Unrecognized Physical Presence: Companies that unknowingly created physical nexus through employees, servers, or other in-state activities
  • Marketplace Relationships: Businesses selling through marketplace facilitators that didn't properly collect tax on their behalf

2. Product Classification and Taxability Errors

  • Software Misclassification: Incorrectly treating taxable prewritten software as exempt
  • SaaS Mischaracterization: Failing to collect TPT on SaaS or cloud computing services due to misunderstanding Arizona's position that these are taxable
  • Bundling Issues: Not properly separating taxable and non-taxable components in bundled transactions
  • Delivery Method Confusion: Erroneously believing electronically delivered software is exempt (as it is in some other states)

3. Procedural and Administrative Oversights

  • License Lapse: Operating with an expired TPT license or registration
  • Local Tax Errors: Applying incorrect local tax rates or failing to include applicable county and city taxes
  • Filing Failures: Missed filings or inconsistent reporting of taxable sales
  • Use Tax Obligations: Companies that purchased taxable software or IT equipment from out-of-state vendors without paying Arizona use tax

4. Timing Considerations

  • Recent Acquisition Discovery: Post-acquisition diligence revealing tax compliance issues from previous ownership
  • Tax Department Review: Internal tax audits identifying historical compliance gaps
  • Software Implementation: New tax software implementation revealing past calculation errors
  • Notification of Similar Audit: Learning of an ADOR audit of a similar business in your industry

Eligibility Requirements

To qualify for Arizona's VDA program, businesses must meet these conditions:

  • Not currently under audit by the ADOR
  • Not previously contacted by ADOR about the tax type and periods in question
  • Not registered for the specific tax type being disclosed (for the periods under disclosure)
  • Not filed returns for the tax type during the lookback period
  • Not collected but failed to remit the tax in question

Example Scenario: A technology company based in Washington state sells software through both downloads and SaaS subscriptions. The company has tracked $750,000 in Arizona sales over the past three years but never registered for TPT because they mistakenly believed their products were exempt from Arizona tax since they had no physical presence in the state. After consulting with a tax advisor, the company discovers that:

  • They established economic nexus in Arizona more than two years ago
  • Their SaaS and downloaded software are both taxable in Arizona
  • They potentially face significant penalties and interest on approximately $60,000 of unpaid TPT

By pursuing a VDA, the company can voluntarily disclose this noncompliance, register for TPT, pay the past-due tax plus interest (but typically without penalties), and implement proper compliance procedures going forward. This approach minimizes their financial exposure while establishing a clean slate with Arizona tax authorities.

  • Established Nexus Without Registering: Businesses that met physical or economic nexus thresholds but failed to register and collect TPT.
  • Misclassified Software or SaaS: If taxable software or SaaS was sold but mistakenly classified as exempt, a VDA can help correct the error before an audit occurs.
  • Missed Use Tax Payments: Companies that purchased taxable software or IT equipment from out-of-state vendors without paying Arizona TPT or use tax.
  • Need to Resolve Historical Noncompliance: If a company recently discovered it had TPT obligations in Arizona for past periods, a VDA can help mitigate penalties and limit exposure.

7.2 Benefits of Arizona's VDA Program

By entering into a Voluntary Disclosure Agreement with the Arizona Department of Revenue, businesses can secure significant advantages compared to waiting for an audit. These benefits are particularly valuable for software and technology companies that may have complex TPT issues related to digital products and services.

Financial Benefits

  • Penalty Abatement:
  • Most penalties are typically waived under a VDA, which can represent substantial savings
  • Failure-to-file penalties (5% per month up to 25% of tax due)
  • Failure-to-pay penalties (0.5% per month up to 10% of tax due)
  • Negligence penalties (10% of additional tax due)
  • These penalties could otherwise total up to 45% of the unpaid tax
  • Audit Risk Reduction:
  • Significantly reduces the likelihood of a comprehensive audit
  • Avoids the time and expense of managing a full-scale audit process
  • Limits the scope of review to self-disclosed issues rather than all potential tax matters
  • Manageable Payment Terms:
  • Structured payment plans may be available for larger liabilities
  • More flexible terms than those typically offered in post-audit situations
  • Opportunity to budget and plan for tax payments

Administrative and Compliance Benefits

  • Controlled Disclosure Process:
  • Company maintains greater control over the information disclosed
  • Process is generally more collaborative than adversarial
  • Company can present facts in the most favorable light permitted by law
  • Limited Lookback Period:
  • Generally limited to three years plus current period
  • Compared to potential four-year lookback under standard audit procedures
  • Protection from assessment for periods prior to the lookback period
  • Streamlined Registration:
  • Expedited TPT registration process
  • Coordinated approach to compliance going forward
  • Clear guidance on filing requirements
  • Compliance Assistance:
  • Arizona DOR provides guidance to help businesses understand their tax obligations
  • Education on proper tax collection and reporting procedures
  • Clarity on application of TPT to specific business models

Strategic and Reputational Benefits

  • Clean Slate Effect:
  • Brings company into compliance without the stigma of enforcement action
  • Demonstrates good faith effort to comply with tax laws
  • Establishes positive relationship with tax authorities
  • Risk Management:
  • Addresses potential liabilities before they grow larger
  • Eliminates uncertainty regarding tax exposure
  • Prevents compounding interest and penalties
  • Confidentiality:
  • Process offers greater confidentiality than a public audit
  • Initial discussions can often be conducted anonymously through representatives
  • Helps protect company reputation and privacy

Quantifying the VDA Benefit - Example Calculation:

A software company discovers it had $400,000 in taxable, but unreported, SaaS sales in Arizona over the past three years, resulting in approximately $32,000 in unpaid TPT (applying an 8% average combined state and local rate).

Without VDA (Audit Scenario):

  • Unpaid Tax: $32,000
  • Interest (assume 10% average over period): $4,800
  • Failure to File Penalty (25%): $8,000
  • Failure to Pay Penalty (10%): $3,200
  • Possible Negligence Penalty (10%): $3,200
  • Total Potential Liability: $51,200

With VDA:

  • Unpaid Tax: $32,000
  • Interest: $4,800
  • Penalties: $0 (typically waived)
  • Total Liability: $36,800

Potential Savings: $14,400 (28% reduction in total liability)

Beyond these direct financial savings, the company also avoids the significant administrative burden and business disruption of a full audit, which can require hundreds of hours of staff time and potentially extend to other tax types or periods outside the VDA scope.

7.3 The Arizona VDA Process

The process for participating in Arizona's Voluntary Disclosure Program involves several key steps designed to facilitate tax compliance while minimizing penalties. The Arizona Department of Revenue has established specific procedures outlined in [Publication 52](https://azdor.gov/forms/voluntary-disclosure-program) and on their [VDA program webpage](https://azdor.gov/business/voluntary-disclosure-and-compliance-program):

1. Application Submission and Initial Consultation

  • Anonymous Initial Contact: Taxpayers or their representatives may make initial contact anonymously to discuss eligibility without revealing the company's identity.
  • Formal Application: Upon determining eligibility, businesses submit the Arizona Voluntary Disclosure Application (Form 10873).
  • Required Information:
  • Business description and activities in Arizona
  • Tax types for disclosure (TPT, corporate income, etc.)
  • Time period of noncompliance
  • Estimated liability amount
  • Explanation of how the tax issue was discovered

2. Application Review and Agreement Preparation

  • Review Process: An ADOR disclosure officer reviews the application, typically within 30 days.
  • Agreement Drafting: If approved, ADOR prepares a disclosure agreement outlining:
  • Lookback period (typically limited to three years)
  • Payment terms and deadlines
  • Waiver of penalties (if applicable)
  • Future compliance requirements

3. Documentation and Registration Requirements

  • Business Registration: Applicants must:
  • Register for an Arizona TPT License
  • Complete all necessary business registration forms
  • Make these filings within 30 days of acceptance into the program
  • Required Documentation:
  • Complete transaction records for the lookback period
  • TPT Schedule in lieu of filing returns for past periods
  • Supporting documentation for calculated tax liability
  • Proof of nexus-creating activities and their timing

4. Tax Calculation, Filing, and Payment

  • Liability Calculation: The ADOR provides:
  • An audit summary of findings
  • Detailed tax calculation worksheets
  • Final billing notice with tax and interest amounts
  • Payment Timeline: Businesses typically have 15 days to:
  • Make full payment of the agreed tax liability plus interest
  • Submit any final documentation requirements

5. Agreement Finalization and Ongoing Compliance

  • Executed Agreement: Once payment is received, ADOR sends the fully executed agreement to the business.
  • Ongoing Requirements:
  • Maintain active registration and licensing
  • File timely returns going forward
  • Comply with all Arizona tax laws
  • Subject to normal audit procedures for future periods

Example Scenario: A SaaS provider based in California discovers it established economic nexus in Arizona two years ago by exceeding the $100,000 sales threshold but never registered or collected TPT. The company's tax advisor initiates anonymous contact with the ADOR to confirm eligibility for the VDA program. After confirming eligibility, the company submits a formal application detailing $250,000 in taxable sales to Arizona customers over the two-year period.

Upon acceptance into the program, the company:

  • Registers for an Arizona TPT license
  • Provides detailed records of all Arizona sales
  • Calculates TPT liability of approximately $21,500 (at state rate plus average local rates)
  • Pays the tax plus interest (penalties are waived)
  • Implements systems to collect and remit TPT on future Arizona sales

Through this process, the company resolves its past liability without penalties, eliminates the risk of a more extensive audit, and establishes proper compliance procedures for the future.

7.4 VDA Considerations for Software and SaaS Companies

While participating in a VDA can provide significant benefits, software and SaaS companies should consider:

  • One-Time Opportunity: Taxpayers may only participate in the program once for each tax type, so proper preparation is essential.
  • Limited Refund Rights: Participants may not amend returns or request refunds for tax periods that fall within the agreement lookback period.
  • Ongoing Compliance Requirements: The ADOR monitors compliance after the VDA is completed, and failure to uphold the terms may result in further investigation or audit.

7.5 Best Practices for a Successful VDA Submission

To maximize the benefits of Arizona's Voluntary Disclosure Agreement program and ensure a smooth process, software and technology companies should implement the following best practices based on guidance from the [Arizona Department of Revenue](https://azdor.gov/business/voluntary-disclosure-and-compliance-program) and industry experience:

1. Pre-Submission Preparation

  • Conduct a Comprehensive Internal Review
  • Perform a detailed historical analysis of all Arizona sales transactions
  • Review all product and service offerings for proper tax classification
  • Identify all activities that may have created nexus in Arizona
  • Determine when nexus thresholds were first exceeded
  • Calculate potential tax liability for the lookback period
  • Gather and Organize Supporting Documentation
  • Sales records by product/service type and delivery method
  • Customer location data and revenue allocation methods
  • Contracts and invoices demonstrating tax treatment
  • Evidence of delivery methods (electronic vs. physical)
  • Documentation supporting exempt transactions
  • Develop Clear Tax Position Narratives
  • Prepare written explanations of tax treatment decisions
  • Document the basis for classifying products and services
  • Explain methodologies used to calculate tax liability
  • Address potential areas of uncertainty or controversy

2. Professional Representation Considerations

  • Engage Qualified Tax Professionals
  • Consider using representatives with Arizona TPT experience
  • Tax attorneys may provide attorney-client privilege protection
  • Representatives can make initial anonymous inquiries
  • Professionals familiar with ADOR procedures can expedite the process
  • Anonymous Initial Discussions
  • Use professional representatives for preliminary discussions
  • Explore eligibility without revealing company identity
  • Discuss specific fact patterns hypothetically
  • Gauge ADOR receptiveness to proposed treatment
  • Representative Authorization
  • Provide proper power of attorney documentation
  • Clearly define the scope of representative authority
  • Maintain regular communication with representatives
  • Review all submissions before authorization

3. Application and Disclosure Strategy

  • Apply Consistent Methodology
  • Use consistent tax treatment across similar transactions
  • Apply uniform classification principles
  • Maintain conceptual integrity in tax positions
  • Avoid contradictory treatment of similar items
  • Properly Structure Disclosure Document
  • Provide a clear executive summary
  • Include detailed explanations for each product/service type
  • Document calculation methodologies
  • Present information in a logical, easy-to-follow format
  • Be Comprehensive but Concise
  • Include all relevant information
  • Organize information systematically
  • Avoid unnecessary detail that might create confusion
  • Anticipate and address potential questions or concerns

4. Implementation and Follow-Through

  • Respond Promptly to ADOR Requests
  • Adhere to all deadlines
  • Provide requested information completely
  • Maintain ongoing communication
  • Address clarification requests thoroughly
  • Prepare for Registration and Compliance
  • Prepare TPT license application simultaneously
  • Set up accounting systems for ongoing compliance
  • Develop tax collection procedures for future sales
  • Create documentation standards for future transactions
  • Plan for Payment
  • Arrange for payment of agreed liability
  • Consider timing and cash flow implications
  • Explore payment plan options if needed
  • Budget for both tax and interest obligations

5. Post-VDA Compliance Planning

  • Implement Forward-Looking Procedures
  • Develop clear internal guidelines for tax classification
  • Create consistent invoicing practices
  • Establish procedures for collecting and maintaining exemption certificates
  • Set up regular compliance reviews
  • Training and Education
  • Train sales and accounting staff on TPT requirements
  • Educate customer service teams on tax-related inquiries
  • Ensure IT teams properly code tax collection systems
  • Establish ongoing education for tax department personnel
  • Documentation Standards
  • Create standardized documentation practices
  • Implement systems to maintain proper records
  • Establish protocols for document retention
  • Develop audit-ready filing systems

Comprehensive Example:

A software developer with $1.5 million in historical Arizona sales realizes it should have been collecting TPT but wasn't registered. The company takes these steps for a successful VDA:

  • Engages a tax professional with Arizona TPT expertise who makes an anonymous inquiry to ADOR
  • Conducts detailed analysis of all transactions, categorizing them as:
  • Standard software downloads (taxable)
  • SaaS subscriptions (taxable)
  • Custom development projects (exempt)
  • Support and maintenance (partially taxable)
  • Prepares a disclosure document that:
  • Explains when and how nexus was established
  • Details the company's product offerings with clear descriptions
  • Provides calculation methodologies and supporting schedules
  • Addresses special situations and exemption claims
  • Simultaneously prepares:
  • Arizona TPT license application
  • Systems to collect TPT going forward
  • Staff training on Arizona tax requirements
  • Implementation of proper documentation procedures
  • After receiving VDA approval:
  • Promptly pays agreed-upon tax and interest
  • Submits all required registration documents
  • Implements comprehensive compliance procedures
  • Schedules quarterly internal reviews to ensure ongoing compliance

By following these best practices, the company minimizes penalties, establishes a clean compliance record, and creates systems to maintain proper TPT collection going forward.

8. Conclusion

Navigating Arizona's TPT for Software and Technology

Navigating Arizona's Transaction Privilege Tax laws for software, SaaS, and technology services requires a deep understanding of transaction classification, sourcing rules, and compliance obligations. Unlike states such as Florida that exempt electronically delivered software and SaaS, Arizona treats these digital products as taxable, considering them tangible personal property or leases subject to TPT. This stance has been reinforced by court decisions, most notably in the ADP, LLC v. Arizona Department of Revenue case (247 Ariz. 265, 448 P.3d 888), which confirmed that SaaS is subject to TPT under the personal property rental classification.

Key Takeaways

The complexity of Arizona's tax rules means that technology businesses must take a proactive approach to compliance:

  • Nexus Awareness: Companies with $100,000+ in annual sales to Arizona customers have economic nexus and must register for TPT, even for digital products and services. This threshold applies to the current or previous calendar year and requires registration within 30 days of meeting the threshold.
  • Proper Classification: Understanding what is taxable and what is exempt is essential:
  • Prewritten software is taxable regardless of delivery method (including downloads)
  • Custom software is generally exempt as a professional service when properly documented
  • SaaS is taxable as a lease of tangible personal property under A.R.S. § 42-5071
  • Professional services should be separately stated from taxable components on all invoices
  • Software maintenance agreements require careful structuring to preserve exemptions
  • Origin-Based Sourcing: Arizona follows origin-based sourcing for TPT under A.R.S. § 42-5040, meaning tax is based on the seller's location rather than the customer's location—a significant difference from destination-based states. For technology companies with multiple locations, understanding which location "receives the order" is critical.
  • Documentation Requirements:
  • Maintain thorough records for at least four years (the statute of limitations period)
  • Separate taxable and non-taxable elements in invoices with clear descriptions
  • Retain exemption certificates (Form 5000A) for all exempt transactions
  • Document delivery methods and transaction details for all software sales
  • Compliance Strategies:
  • Register for TPT through AZTaxes.gov or Arizona Business One Stop
  • File returns monthly, quarterly, or annually based on tax liability thresholds
  • Consider consolidated returns for multiple business locations
  • Utilize the VDA program for historical non-compliance issues

Implementation Action Plan

Technology companies selling into Arizona should:

  • Immediate Actions (0-30 days):
  • Assess current and previous year sales to determine economic nexus status
  • Review product and service offerings to identify taxable components
  • Update invoice templates to properly separate taxable and non-taxable items
  • Short-Term Actions (30-90 days):
  • Register for TPT if threshold is met or expected to be met
  • Implement systems to track origin-based tax rates applicable to business locations
  • Review and update customer contracts to clarify tax treatment
  • Long-Term Compliance (Ongoing):
  • Monitor ADOR updates and technical rulings related to digital products
  • Conduct quarterly internal tax reviews, particularly when introducing new offerings
  • Maintain documentation of tax decisions and classification rationales
  • Consider periodic nexus studies as business activities evolve

By implementing these practices, software and technology companies can navigate Arizona's complex TPT system effectively, minimize audit exposure, and create a solid foundation for tax compliance in an evolving digital landscape.

9. References & Resources

Arizona Department of Revenue Resources

  • TPT Home: Main portal for forms, instructions, publications, and bulletins -- [Arizona Transaction Privilege Tax](https://azdor.gov/business/transaction-privilege-tax)
  • Nexus Information: Guidance on economic and physical nexus thresholds -- [Nexus Program](https://azdor.gov/taxpayer-education/nexus-program/nexus-program-tpt)
  • Economic Threshold Information: Details on Arizona's economic nexus standards -- [Economic Threshold](https://azdor.gov/business/transaction-privilege-tax/retail-sales-subject-tpt/out-state-sellers/economic-threshold)
  • Voluntary Disclosure Program: Information on Arizona's VDA process -- [Voluntary Disclosure and Compliance Program](https://azdor.gov/business/voluntary-disclosure-and-compliance-program)

Key Arizona Statutory & Regulatory References

  • [Arizona Revised Statutes § 42-5001: Definitions related to TPT, including tangible personal property](https://www.azleg.gov/arsDetail/?title=42)
  • [Arizona Revised Statutes § 42-5071: Personal property rental classification, which applies to SaaS](https://www.azleg.gov/arsDetail/?title=42)
  • [Model City Tax Code § 115: Definitions of computer software and custom computer programming](https://azdor.gov/business/transaction-privilege-tax/model-city-tax-code/index-articles-and-regulations)
  • [Model City Tax Code § 450: Municipal taxation of leasing and rental activities](https://azdor.gov/business/transaction-privilege-tax/model-city-tax-code/index-articles-and-regulations)
  • [Model City Tax Code § 460: Municipal taxation of retail activities](https://azdor.gov/business/transaction-privilege-tax/model-city-tax-code/index-articles-and-regulations)

Notable Court Decisions and Rulings

  • ADP, LLC v. Arizona Department of Revenue: Arizona Court of Appeals decision affirming that SaaS is subject to TPT as a lease of tangible personal property
  • ADOR Private Letter Ruling LR10-007: Defines SaaS and establishes that leased and subscription-based software are subject to TPT

Additional Compliance Support

Armed with these Arizona-specific tools and resources, businesses can:

  • Mitigate Risk: Understand which transactions are taxable, which might be exempt, and how to structure invoices to minimize compliance pitfalls.
  • Maintain Documentation: Keep thorough records of contracts, itemized invoices, and exemption certificates to defend tax positions in the event of an audit.
  • Ensure Compliance: Stay current on private letter rulings and administrative rules, especially as technology evolves and new rulings are issued.

If you ever need personalized assistance, whether for setting up a Voluntary Disclosure Agreement, responding to a TPT audit, or clarifying complex software tax classifications, our team at Sales Tax Helper is here to help you save time and protect your bottom line.

Disclaimer: This guide is intended as an overview and does not constitute legal or tax advice. Always consult a qualified tax professional or attorney for advice specific to your business situation.

Get answers for your Arizona software and SaaS questions

Create a free Sales Tax Helper account to check your nexus exposure and keep your Arizona compliance on track. Need a hand? Our attorneys, CPAs, and former state auditors are ready to help.

Need Expert Help?

Our team of attorneys, CPAs, and former state auditors handles exactly these situations. Free consultation — no obligation.

Get Started FreeContact Us