Transaction Privilege Tax (TPT), a seller-side gross-receipts tax
Start with the high-impact answers, then use the complete rule explorer for product-specific and long-tail research.
Transaction Privilege Tax (TPT), a seller-side gross-receipts tax Arizona TPT is not a conventional buyer-imposed sales tax. State, county, and city components are reported by business classification and location code, and some non-program cities retain distinctive rules.
The applicable rate depends on the TPT business class, the seller or customer location rules for that class, and the city code. Retail, contracting, lodging, utilities, and other classes should never share a generic rate shortcut.
The principal repository-tracked return is TPT-2. Paper eligibility is taxpayer-specific; electronic filing or a waiver may control.
Facilitated sales generally enter gross receipts and are removed through the state's designated deduction or exclusion workflow.
The repository tracks Arizona Transaction Privilege Tax Exemption Certificate and supports generation from reviewed fields. Certificate validity still depends on the purchaser, seller, claimed use, dates, signatures, and any state-specific acceptance conditions.
The current Atlas research does not publish an active holiday rule for this state. Confirm the current revenue-department calendar before changing tax.
No separately verified special-rate category is published in the current member-state register for this jurisdiction. Product-specific research observations remain available below.
The corpus contains one prepared food observation under these researched conditions: sale context: restaurant or bar. The research observation says the observed treatment is included in base; with special rate required; a 5.6% state rate; local interaction: product specific local; sourcing: special; effective from 2026-07-01. Restaurant and bar activity uses its own TPT business classification with the 5.6 percent state component and location-specific county and city rates. Status: Research observation — independent review required. Confirm the cited authority and transaction facts before use.
The corpus contains one telecommunications observation. The research observation says the observed treatment is included in base; with special rate required; a 5.6% state rate; local interaction: product specific local; sourcing: special; effective from 2026-07-01. Communications may require the base classification plus a 1.1 percent device code, a 20-cent monthly 911 charge per activated service, or a 0.8 percent prepaid-wireless E911 component. Status: Research observation — independent review required. Confirm the cited authority and transaction facts before use.
The corpus contains one construction service observation under these researched conditions: sale context: prime contracting. The research observation says the observed treatment is included in base; with special rate required; a 5.6% state rate; local interaction: product specific local; sourcing: special; effective from 2026-07-01. Prime contracting and MRRA materials use specific TPT business codes and location-dependent rates. Status: Research observation — independent review required. Confirm the cited authority and transaction facts before use.
Choose the calculation engine or the compliance workflow. Inspect the public examples, then bring five cases from your business.
Evaluate addresses, product identity, certificate dates, refunds and retries with the same inputs your integration will use.
Inspect calculation examples →Disclosed reference inputs and executed results. Confirm coverage and configuration for your own transactions.
Evaluate the calculation engine →Trace a generated sample return to its source rows. See how seller sales, marketplace activity and unresolved responsibility are separated.
Trace the sample return →Synthetic Virginia package demonstration. Review, authorization and state acceptance remain separate steps.
Evaluate sales tax compliance →See task rates and subscription prices. Public evidence is open to inspect; we confirm scope and commercial terms before a private evaluation.
Arizona TPT is not a conventional buyer-imposed sales tax. State, county, and city components are reported by business classification and location code, and some non-program cities retain distinctive rules.
The applicable rate depends on the TPT business class, the seller or customer location rules for that class, and the city code. Retail, contracting, lodging, utilities, and other classes should never share a generic rate shortcut.
Tax situs is a legal determination. Mailing city, ZIP code, county proximity, and geocoding are useful evidence, but none should silently substitute for the jurisdiction rule that controls the transaction.
Product identity should be established before a rate is selected. In Arizona, examples that deserve their own rule path include:
These are examples, not an exhaustive taxability matrix. Bundles, customer use, delivery method, exemptions, and effective dates can change the result.
The underlying research inventory contains 17 Arizona treatment records across 11 product families. The inventory includes effective-date, evidence, rate-class, local-interaction, and sourcing fields. Its breadth is not a claim that every observed treatment is active in production: unresolved or independently unreviewed records remain non-operative.
17 of 17 records shown
Research observation — independent review required
Before operational use: ingest all city classification and tier windows; preserve vendor-liability accounting and pass-through presentation; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: sale context: restaurant or bar
Before operational use: ingest restaurant city and county windows; encode prepared-food business boundary; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: subtype: amusement
Before operational use: ingest amusement city and county windows; encode activity boundary; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: rented product: tangible personal property
Before operational use: ingest rental city and county windows; encode rental subtypes and sourcing; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: sale context: prime contracting
Before operational use: encode prime speculative owner-builder and MRRA boundaries; ingest local windows; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: subtype: utility service
Before operational use: ingest utility city and county windows; encode utility subtype and sourcing; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Before operational use: encode telecommunications subtype and component applicability; ingest local windows; route fixed 911 amount; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: lodging type: operator furnished transient lodging
Before operational use: ingest all city hotel and additional-tax windows; encode stay duration and Pima unincorporated addition; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: lodging type: online lodging marketplace
Before operational use: ingest marketplace city windows; encode marketplace role and Pima unincorporated addition; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: sale context: use tax purchase
Before operational use: ingest city use-tax windows; encode prior-tax credit and use location; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: sale context: food for home consumption
Before operational use: ingest every city food classification and threshold window; encode food boundary; independent review
Research observation — independent review required
Identity or conditions: rented product: commercial real property
Before operational use: ingest exact county and city commercial-lease windows; encode commercial-use boundary; independent review
Research observation — independent review required
Identity or conditions: rented product: residential real property; sale context: thirty or more consecutive days
Before operational use: encode residential-use and duration transition; independent review
Research observation — independent review required
Identity or conditions: subtype: municipal water
Before operational use: encode water volume and applicable district; route fixed amount calculation; independent review
Research observation — independent review required
Identity or conditions: rented product: short term motor vehicle
Before operational use: encode greater-of and county applicability; ingest city vehicle-rental codes; independent review
Research observation — independent review required
Before operational use: build complete business-classification matrix; ingest local windows; independent review
State authority research source 1State authority research source 2
Research observation — independent review required
Identity or conditions: subtype: adult use
Before operational use: semantically extract all current marijuana state county city and excise components; independent review
The principal repository-tracked return is TPT-2. Paper eligibility is taxpayer-specific; electronic filing or a waiver may control.
How to file Arizona sales tax: 2026 due dates, frequencies, and forms →
Facilitated sales generally enter gross receipts and are removed through the state's designated deduction or exclusion workflow.
Seller registration, nexus thresholds, zero-return obligations, facilitator certifications, and direct sales must be evaluated separately. Prophit keeps those facts attached to the return treatment instead of dropping marketplace transactions from the record.
The repository tracks Arizona Transaction Privilege Tax Exemption Certificate and supports generation from reviewed fields. Certificate validity still depends on the purchaser, seller, claimed use, dates, signatures, and any state-specific acceptance conditions.
A certificate should be tied to the correct customer, seller, state, reason, product use, effective period, and transaction population, then monitored for expiration or changed facts.
Prophit currently structures Arizona transaction data for worksheet for portal entry. Availability is kept separate from customer credentials, state acceptance, and direct transmission authority.
See how Prophit.ai compares to other options in the sales tax software buyer's guide.
Product availability varies by jurisdiction and customer configuration. Workflow support does not by itself establish registration, filing authority, credentials, agency acceptance, or tax advice.
This guide is grounded in the repository's reviewed filing, marketplace, certificate, and tax-authority records. Rules change; confirm the current source and effective period before acting.
Reviewed and current as of October 26, 2026
