Is SaaS taxable in Arkansas? A developer's guide to the exemption

If you're building a product that needs to calculate SaaS sales tax for your customers, this guide is for you. It covers Arkansas's SaaS tax rules and rates, what to account for when you build sales tax calculation into your product, and how Ziptax returns accurate Arkansas rates through an API without you building and maintaining a rate engine.

Arkansas SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Arkansas tax?

Arkansas taxes software based on how it's delivered, not on what the product is called. Prewritten software is taxable as tangible personal property under Ark. Code Ann. § 26-52-304, but the statute excludes anything delivered electronically or by load and leave—delivery that puts no tangible storage media in play—from that taxable definition.

Bundles are where implementations break. Apply taxability per line item, not per order: a SaaS subscription that ships a physical onboarding kit or a required local component stays exempt on the pure-access portion, but the tangible media is taxable. An undifferentiated lump sum drags the whole invoice into taxable territory.

How do you charge the correct sales tax rate for SaaS in Arkansas?

Under current rules, you don't. Because remotely accessed SaaS with no download is exempt, the sales tax on a subscription sold to an Arkansas customer is $0. That holds for every component short of a downloaded client on physical media, a bundled tangible good, or a specified digital product. Arkansas has no 2027-style transition to plan around, so this is the steady state, not a temporary one.

Where this gets more interesting than a flat answer is what else you might be selling alongside the subscription. If any part of your catalog crosses into tangible personal property, a specified digital product, or a taxable service delivered into Arkansas, you need an address-level rate for that portion. Arkansas's membership in the Streamlined Sales Tax Governing Board changes how you'd register and file across multiple states if you also sell elsewhere; it doesn't change what you owe in Arkansas itself.

Engineering teams have two options for calculating the correct rate on whatever portion of a sale is taxable: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Use the Ziptax Sales Tax API

You send the buyer's address at the point of checkout, and the API resolves the exact city and county rates that apply.

To calculate a live rate against an Arkansas address, use the v60 endpoint:

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=500 Woodlane St, Little Rock, AR, 72201"

To verify complete payload structures, explore the REST API documentation.

Three things to do with that response. Multiply by the combined rate rather than assembling it from the components. Store the jurisdiction on the transaction, because rebuilding it later from an address is lossy. Store the effective date too, because it is what lets you answer a question about a past period, and Arkansas republishes its city and county rate table every quarter.

If your product catalog handles complex items like SaaS, downloaded software, or bundles, you can also pass a product taxability code to dynamically check product rules.Search for the correct product code and review Taxability Information Codes (TICs) to see how the response returns product-specific tax flags and exemptions.

What an API will not tell you: whether your company has crossed a nexus threshold in Arkansas, whether facilitated marketplace sales count toward that threshold, and whether a specific line item qualifies for the custom-programming carve-out. All three stay on your side of the integration.

To automate threshold tracking, tax filings, and remittance, including Streamlined Sales Tax registration and filing if you sell into multiple SST member states, you can set up merchant management to connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.

Option 2: Build and maintain it yourself

A real choice if you already hold jurisdiction data for other reasons. If you take this route, Arkansas needs four things handled:

1. A product taxability decision separate from the rate lookup. Pure SaaS is exempt, so the rate isn't the operative question for it. Downloaded software on physical media, specified digital products, and bundled tangible goods still need one.
2. Address-level rate resolution for city and county. Arkansas layers a city rate and a county rate on top of the 6.50% state rate, and combined rates range from 6.50% to 12.625% depending on the address.
3. Threshold accumulation on the right basis: tangible personal property, taxable services, digital codes, and specified digital products delivered into Arkansas, over the current or previous year, not pure SaaS revenue.
4. An effective date on every rule. Arkansas DFA republishes its city and county rate table quarterly, so a stored rate is only good until the next cycle.

Four things to watch out for:

1. ZIP-based shortcuts. City and county boundaries don't follow ZIP code lines, so two customers who share a ZIP code can sit in different combined-rate jurisdictions. Resolve the rate from the full street address instead.
2. Treating the whole account as exempt. A customer who is pure SaaS today and adds a downloaded component, bundled hardware, or a specified digital product tomorrow introduces a taxable line your system needs to catch, not wave through on the old assumption.
3. Rate changes landing mid-quarter. Arkansas DFA updates its city and county tax table every quarter, and nothing tells you when a given jurisdiction changed unless you're tracking effective dates.
4. Assuming a local tax cap applies. Some states cap local tax on a single transaction. Arkansas repealed that general cap for most merchandise and services back in 2008; it now applies only to motor vehicles, aircraft, watercraft, manufactured housing, and travel trailers. Don't build a software or specified-digital-product calculation that assumes local tax stops accruing after some dollar amount.

When does a SaaS business have to collect sales tax in Arkansas?

Registration and collection are two separate obligations. Conflating them is where most engineering implementations go wrong.

Rule 1: Monitor your registration triggers (nexus)

You must legally register to file with the state the moment either of these conditions is met:

• Physical presence: An employee working in Arkansas, an office, inventory held in the state, or leased server capacity.
• Economic threshold: Your sales of tangible personal property, taxable services, digital codes, or specified digital products delivered into Arkansas cross $100,000, or 200 separate transactions, in the current or previous calendar year. Pure SaaS revenue isn't counted in any of those categories.

Rule 2: Apply the correct collection logic

A seller whose only Arkansas revenue is pure remotely accessed SaaS (no download, no bundled tangible good, no specified digital product) most likely never crosses this threshold at all, because none of that revenue falls into a category the threshold measures.

Registration becomes a live question the moment some Arkansas revenue is tangible personal property, a taxable service, a digital code, or a specified digital product: a downloaded client on media, bundled hardware, or a digital audio or video add-on.

Where Ziptax helps

If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.

Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.

• Rooftop precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, eliminating the accuracy liabilities of ZIP-based shortcuts.
• Engineered for platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
• Frictionless pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
• The TaxCloud runway: When your transaction volume scales, or you sell into other Streamlined Sales Tax member states alongside Arkansas, you can pair Ziptax with TaxCloud for the rest of compliance. As a CSP in the SST program, TaxCloud delivers free filing and registration for eligible remote sellers across Arkansas and its other 23 member states. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.

Get Arkansas SaaS tax rates from an API

Address-level rates for every Arkansas jurisdiction, plus the rest of the US, Canada, and select other markets.

Frequently asked questions

Do you have to register in Arkansas if your SaaS product is exempt there? Not necessarily. Arkansas's $100,000 / 200-transaction economic nexus threshold is measured on tangible personal property, taxable services, digital codes, and specified digital products delivered into Arkansas, not gross revenue. Pure SaaS doesn't count toward the threshold.

Does Arkansas tax software differently depending on how it is delivered? Yes. Prewritten software delivered on physical media is taxable tangible personal property. Software delivered electronically or by load and leave falls outside that definition and is exempt. Custom software built for a single customer is treated as a nontaxable service regardless of delivery method.

Can you use a ZIP code to get the Arkansas sales tax rate? Not reliably. Arkansas's combined rate is built from the state rate plus separate city and county rates, and those boundaries don't follow ZIP lines. Two customers who share a ZIP code can sit in different cities or counties and owe different amounts.

Is Arkansas's SaaS exemption written into a dedicated statute? It's an interpretation of a more general rule. Neither Ark. Code Ann. § 26-52-304 nor Gross Receipts Tax Rule GR-25 mentions software as a service by name. Both exclude software "delivered electronically" from the definition of taxable computer software. Arkansas's Streamlined Sales Tax taxability matrix applies the exemption to SaaS on that basis.

Does being a Streamlined Sales Tax member state change anything for a SaaS seller in Arkansas? It doesn't change what's taxable in Arkansas. It changes how you'd register and file if you have exposure in other Streamlined member states too, allowing you to register once through the SST Registration System rather than state by state.

Sources

1. SaaS and software exemption (electronic delivery exclusion):
2. Ark. Code Ann. § 26-52-304 
3. Arkansas Gross Receipts Tax Rule GR-25
4. Arkansas's Streamlined taxability matrix classification: Arkansas Department of Finance and Administration, Arkansas Taxability Matrix (rows 30040 to 30060, citing Ark. Code Ann. §§ 26-52-304 and 26-53-109) and the Streamlined Sales Tax Project Overview.
5. Specified digital products: Ark. Code Ann. § 26-52-301(1)(B)-(C), (3)(C)(iii) (taxation of specified digital products and digital codes).
6. Economic nexus and the $100,000 / 200-transaction threshold: Arkansas Department of Finance and Administration, Remote Sellers Guidance, implementing Act 822 of 2019 (Ark. Code Ann. § 26-52-111).
7. State and local tax rates: Arkansas Department of Finance and Administration, State Sales and Use Tax Rates and the quarterly City and County Tax Table (October to December 2026).
8. Local tax single-transaction cap (repealed for general merchandise in 2008): Arkansas Department of Finance and Administration, Sales and Use Tax FAQs.
9. Streamlined Sales Tax (SST) status: Streamlined Sales Tax Governing Board, Arkansas State Detail.