What documentation is required to claim a resale exemption on purchases made for resale in Arizona?

For remittance businesses operating in Arizona, understanding resale exemptions is essential when purchasing goods or services intended for resale—such as branded prepaid cards, kiosks, or software platforms used to facilitate cross-border transfers. To claim a resale exemption, you must provide your supplier with a properly completed Arizona Transaction Privilege Tax (TPT) Resale Exemption Certificate (Form 5000A). This form must include your Arizona TPT license number, business name, address, and a detailed description of the items being purchased for resale.

It’s critical that the certificate is signed, dated, and retained by both parties for at least four years—per Arizona Department of Revenue requirements. Remittance providers often overlook this step when procuring technology or hardware, inadvertently triggering unintended tax liabilities. Unlike some states, Arizona does not accept multi-state resale certificates; only Form 5000A is valid.

Additionally, ensure your Arizona TPT license is active and covers the appropriate classification (e.g., “Retailer” or “Software-as-a-Service”). Failure to maintain compliance may jeopardize exemption claims during audits. Partnering with a tax-savvy remittance compliance advisor can help streamline documentation and reduce risk—keeping your operational costs low and your filings audit-ready.

Does Arizona require remote sellers to collect TPT on marketplace-facilitated sales?

Arizona requires remote sellers to collect Transaction Privilege Tax (TPT) on marketplace-facilitated sales—effective since October 1, 2019. Under Arizona law, marketplace facilitators (e.g., Amazon, Etsy, or Walmart Marketplace) must register with the Arizona Department of Revenue and collect, remit, and report TPT on behalf of third-party sellers using their platform—even if those sellers lack physical presence in the state.

This rule significantly impacts remittance businesses supporting cross-border or multi-state e-commerce clients. If your remittance service processes payments for Arizona-based marketplace sellers—or facilitates payouts to sellers operating through Arizona-registered platforms—you must ensure TPT compliance is embedded in your reporting and reconciliation workflows.

Remote sellers not using a registered facilitator may still be liable for TPT if they meet economic nexus thresholds ($100,000 in annual gross revenue from Arizona sales). However, facilitators assume primary collection responsibility, reducing direct liability for individual sellers—provided the facilitator is compliant.

For remittance providers, staying updated on Arizona’s TPT rules helps avoid client penalties, supports accurate tax-inclusive disbursements, and strengthens trust with U.S.-focused fintech and e-commerce partners. Partnering with certified tax automation tools or Arizona-licensed tax advisors ensures seamless integration of TPT obligations into your payout infrastructure.

How does Arizona treat bundled software (SaaS + hosted support) for TPT purposes?

Azure-based remittance businesses operating in Arizona must understand how the state treats bundled software—such as SaaS platforms paired with hosted support—for Transaction Privilege Tax (TPT) purposes. Unlike many states, Arizona generally excludes true SaaS from TPT because it’s considered a non-taxable service, not tangible personal property.

However, when SaaS is bundled with taxable elements—like on-premise installation, customization, or hardware—it may trigger TPT liability. Crucially, Arizona’s Department of Revenue clarifies that *hosted support alone* (e.g., helpdesk, uptime monitoring, bug fixes) remains non-taxable when inseparable from the SaaS subscription. This is favorable for remittance firms relying on cloud-based compliance and FX tools.

That said, remittance providers must carefully document contracts to demonstrate that support is truly incidental and integrated—not sold separately. If support is itemized or priced independently, Arizona may treat it as a taxable “maintenance agreement,” especially if it extends beyond standard SaaS scope.

For cross-border remittance operations, proper nexus assessment and TPT registration remain essential—even with favorable SaaS treatment. Consulting an Arizona tax specialist ensures your bundled offering stays compliant while optimizing tax efficiency across your digital financial infrastructure.

Are groceries (food for home consumption) exempt from TPT in Arizona—and if so, at all jurisdictional levels?

Arizona’s Transaction Privilege Tax (TPT) treats groceries differently than other retail goods—making it vital for remittance businesses serving immigrant families to understand. Food intended for home consumption is fully exempt from state-level TPT, per Arizona Revised Statutes § 42-5075. This exemption applies broadly to staples like fruits, vegetables, meat, dairy, bread, and non-alcoholic beverages purchased for home preparation.

However, the exemption does *not* automatically extend to all local jurisdictions. While most cities and counties align with the state’s grocery exemption, a small number—including Phoenix, Tucson, and Mesa—have adopted their own TPT ordinances that *may* impose local taxes on groceries. Remittance providers must therefore verify not just state rules, but also the specific taxing authority where funds are being sent or used.

This nuance matters: when customers send money to family in Arizona, understanding local tax treatment helps recipients budget accurately—especially low-income households relying on remittances for essential food purchases. Misunderstanding could lead to unexpected costs or compliance missteps for small retailers accepting remittance-funded payments.

For remittance businesses, highlighting Arizona’s grocery tax exemption—and cautioning about local variations—builds trust and supports financial literacy. Embedding this insight into customer FAQs or localized guides strengthens your value proposition while improving transparency and user confidence.

What is the TPT treatment of repair parts sold separately versus included in a repair service?

For remittance businesses handling cross-border payments to suppliers of repair parts, understanding the Transaction Price Treatment (TPT) under ASC 606 is critical—especially regarding how repair parts are classified. When repair parts are sold separately (e.g., via e-commerce or direct invoicing), they constitute distinct performance obligations and must be priced, recognized, and remitted as standalone goods subject to standard revenue recognition timing.

In contrast, when repair parts are bundled *within* a broader repair service agreement (e.g., “labor + parts” flat-fee contracts), TPT requires allocating the transaction price based on relative standalone selling prices. This impacts remittance scheduling: funds for the parts portion may be held or released differently than labor fees, affecting cash flow and FX settlement timing.

Remittance providers must integrate TPT-aware invoicing data—distinguishing line-item treatment—to ensure accurate, compliant fund disbursement. Misclassifying bundled parts as separate items risks revenue misallocation, audit exposure, and delayed supplier payouts.

Partnering with remittance platforms that support ASC 606-compliant segmentation—tagging parts vs. service lines—enhances transparency, reduces reconciliation effort, and strengthens financial controls across global repair supply chains.

 

 

About Panda Remit

Panda Remit is committed to providing global users with more convenient, safe, reliable, and affordable online cross-border remittance services。
International remittance services from more than 30 countries/regions around the world are now available: including Japan, Hong Kong, Europe, the United States, Australia, and other markets, and are recognized and trusted by millions of users around the world.
Visit Panda Remit Official Website or Download PandaRemit App, to learn more about remittance info.