Is SaaS Taxable in Tennessee? Yes, and the $1,600 Single-Article Rule Changes the Math for AI Agents

Key Takeaway: Tennessee taxes SaaS, and it says so in the statute rather than in a ruling. The same subsection also lists what it does not tax, and data processing and information services are at the top of that list. That split decides most AI agent transactions. The number that tools most often get wrong is the local tax. For a standalone prewritten application, Tennessee's single-article rule stops local tax at the first $1,600 and adds a separate 2.75% state tax on the next $1,600. A flat combined rate overstates a large subscription and understates a mid-sized one.

The Base: Software Use, Wherever the Software Sits

Tenn. Code Ann. § 67-6-231(a) taxes "the retail sale, lease, licensing or use of computer software in this state, including prewritten and custom computer software, ... regardless of whether the software is delivered electronically, delivered by use of tangible storage media, loaded or programmed into a computer, created on the premises of the consumer or otherwise provided." The rate is the tangible personal property rate: 7% state, plus local.

Subsection (b) is the SaaS provision. "Use of computer software" includes "the access and use of software that remains in the possession of the dealer who provides the software or in the possession of a third party on behalf of such dealer." If the customer accesses the software from a Tennessee location, "as indicated by the residential street address or the primary business address of the customer", that access "shall be deemed equivalent to the sale or licensing of the software and electronic delivery of the software for use in this state."

Two features stand out. First, custom software is taxed too, in the same sentence as prewritten. An agent that writes a bespoke application for a Tennessee client has not escaped the tax by making the deliverable one of a kind. Second, the trigger is the customer's address, not where the servers are. The Department of Revenue's notice RAS-3 applies the same address to the local rate.

What Tennessee Declines to Tax

The last sentence of § 67-6-231(b) is the one agent operators should read twice:

"Nothing in this subsection (b) shall be construed to impose a tax on any services that are not currently subject to tax under this chapter, such as, but not limited to, information or data processing services, including the capability of the customer to analyze such information or data provided by the dealer; payment or transaction processing services; payroll processing services; billing and collection services; internet access; the storage of data, digital codes, or computer software; or the service of converting, managing, and distributing digital products."

The Department's notice RAS-1 repeats the list and adds that these services "are not subject to tax even if the purchaser uses remote access to utilize or receive the service."

A second exclusion sits in the digital products statute. Section 67-6-233(a) taxes specified digital products at the tangible personal property rate. But § 67-6-233(d) excludes "subscriptions to data processing and information services that allow data to be generated, acquired, stored, processed or retrieved and delivered by electronic transmission to a purchaser, where the purchaser's primary purpose for the underlying transaction is the processed data or information."

The Agent Question: Software Use or Delivered Output?

Most AI agent work lands on one side of this line or the other:

• Taxable side. The customer, or the customer's own agent, operates the dealer's application: it runs the tool, configures it and works inside it. That is "access and use of software" under (b).

• Exempt side. The customer sends data or a question and receives processed data or information back. What it bought is the output, not a session with the software. A research agent that returns a report, a batch job over customer-supplied files and a storage bucket all fit the exclusion's terms.

The difficult case is the API. When one agent calls another agent's endpoint, it is technically running the dealer's code on the dealer's servers. It is also buying an answer. The statute gives no rule for machine callers. It asks what the customer's "primary purpose" was (in § 67-6-233(d)) and whether the service is "information or data processing" (in § 67-6-231(b)). Our reading: if the deliverable is the data or the analysis, the exclusion is available. If the deliverable is continuing access to a tool, even one driven by software rather than a person, it is not. Mixed facts lean taxable in Tennessee.

The Number: Tennessee's Single-Article Rule Reaches Software

Tenn. Code Ann. § 67-6-702(a)(1) authorizes local sales tax up to 2.75%, "provided, that the tax levied shall apply only to the first one thousand six hundred dollars ($1,600) on the sale or use of any single article of personal property." The Department's notice SUT-6 describes the matching state add-on: "an additional state tax of 2.75% applied to the amount in excess of $1,600 but less than or equal to $3,200."

Notice SUT-57 applies this to software. "A separate prewritten computer software application or module that is sold by itself, without any other computer software application or module bundled with it, and sold for one price, will qualify as a single article." That "applies regardless of how the software is delivered, whether downloaded or remotely accessed." So "only the first $1,600 of the sales price of prewritten computer software is subject to the applicable local sales tax," the 2.75% state add-on applies between $1,600.01 and $3,200, and "beyond $3,200, no local tax or additional state single article tax is due." For subscriptions: "If prewritten computer software is sold pursuant to a software service agreement that requires multiple payments during the agreement period, the single article treatment described above will apply to the total of the service agreement payments."

Using SUT-6's own illustrative 2.25% local rate, the correct tax on a standalone prewritten SaaS application works out as follows:

• $1,000 agreement: $70.00 state + $22.50 local = $92.50 (9.25%).

• $2,500 agreement: $175.00 state + $36.00 local + $24.75 add-on = $235.75 (9.43%).

• $12,000 agreement: $840.00 state + $36.00 local + $44.00 add-on = $920.00 (7.67%).

A flat 9.25% gives $92.50, $231.25 and $1,110.00. It is right on the first, $4.50 short on the second and $190 over on the third. The rule cuts both ways.

Three limits. Custom software does not get single-article treatment; SUT-57 says it "is subject to the full local and state sales tax rates." A bundle of applications sold for one price does not qualify under SUT-57's own terms, and the notice does not say how the bundle is then taxed locally. And no notice we read addresses per-call metered billing with no fixed agreement. Until the Department says otherwise, the conservative approach is to treat the contract as the article and total its payments.

Specified digital products follow a separate local rule. Section 67-6-702(f)(4) sets local tax on them at a flat 2.5%, whatever the local rate is.

Users, Addresses and Machines

Section 67-6-231(b) allows apportionment: when the price "relates to users located both in this state and outside this state as indicated by a residential street or business address, the dealer or customer may allocate to this state a percentage of the sales price or purchase price that equals the percentage of users in this state."

The denominator is people with addresses. An autonomous agent has neither. For a buyer whose seats are human, the apportionment works as written. For a buyer whose "users" are a fleet of agents running in a cloud region, the statute gives no counting rule. Compare Maryland, whose primary-use-location definition names "equipment that makes use of" the service. Tennessee's does not. A buyer relying on apportionment should document a method it can explain, and it should expect the address of the business itself to be the default.

How AgentTax Handles Tennessee

Verified against the engine today (buyer, B2B, $1,000 unless noted):

• SaaS (digital_service): taxable. Nashville 37201 computes 9.25% ($92.50) and Memphis 38103 computes 9.75%.

• Data processing and information services (work_type: compute or research, and storage): $0, with the TN_TRUE_OBJECT_BOUNDARY advisory quoting the (b) exclusion and warning that software-use facts stay taxable.

• Conservative results, disclosed: consulting computes 9.25%, although advice delivered as output sits closer to the excluded side of the line. data_purchase computes 9.25% on a hold that covers one-off dataset purchases, which the exclusion arguably reaches.

Three gaps, stated plainly:

• The single-article rule is not modeled. The engine applies the full combined rate to the whole amount. As the worked numbers show, that over-collects on standalone prewritten software above about $3,556 in Nashville. With a 2.25% local rate it slightly under-collects between $1,600 and that point. At Memphis's 2.75% local rate the two methods agree up to $3,200 and diverge above it. Until this ships, compute the single-article figure yourself for any standalone application over $1,600.

• Local coverage is four ZIPs. Nashville, Memphis, Chattanooga and Knoxville. A suburban ZIP such as 37027 returns the 7% state rate with a ZIP_UNKNOWN advisory and no local tax, which is an under-collection. Reserve at the local rate for the buyer's address.

• No user apportionment and no flat 2.5% local rate on specified digital products. Both need facts the API does not collect yet.

Tennessee also appears in our earlier SAP America analysis, but that case concerned the business tax, not sales tax. For the threshold question, see economic nexus for AI agents. To run the numbers, use the playground or the AI agent sales tax API.

What to Watch

Two things. First, whether the Department extends SUT-57 to usage-metered software, which is how most agent APIs are billed. Second, whether any Tennessee ruling tests the (b) exclusion against a machine caller. The statute separates buying output from using a tool; it does not yet say which one an API call is.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.