This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.

Technical Deep Dive

One State, Two Answers: Tennessee's SAP Ruling and Why the Label 'Cloud Software' Decides Nothing

Beardsley Rumble|2026-07-12|5 min read

On May 13, 2026, the Tennessee Court of Appeals held that a company's software license receipts are not subject to Tennessee business tax — while its cloud hosting and optional cloud-based services are. The decision, SAP America, Inc. v. Gerregano, No. M2024-01399-COA-R3-CV, has been working its way through the practitioner commentary over the past two weeks, and it is worth the attention: it is the cleanest recent illustration of a point AI agent operators keep learning the hard way. The same offering, sold by the same company, can be taxable or not depending entirely on how it is characterized — and a single state can reach opposite answers under two of its own tax statutes.

The dispute

SAP America challenged a Tennessee Department of Revenue business tax assessment of roughly $728,000 covering tax years 2014 through 2018. Tennessee's business tax is a privilege tax measured on gross receipts, separate from the state's sales and use tax. It reaches "services," defined very broadly under Tenn. Code Ann. § 67-4-702, but it does not reach sales of intangible property. The entire case turned on which of SAP's three revenue streams fell inside that definition.

The court split them:

Software licenses — not taxable. The court affirmed that receipts from licensing SAP's enterprise software, whether delivered by download or accessed remotely, are sales of intangible personal property and fall outside the business tax.

Cloud hosting — taxable. The court reversed the trial court here, holding that hosting is a taxable service because SAP retained possession and control of its own servers, hardware, and platform rather than transferring anything to the customer.

Cloud-based services — taxable. Optional items like premium support and consulting were taxable when electronically delivered to Tennessee customers.

The reasoning is the interesting part

The software-license holding rests on a 1976 Tennessee Supreme Court decision, Commerce Union Bank v. Tidwell, 538 S.W.2d 405 (Tenn. 1976), which held that computer software is intangible property. That is fifty-year-old law. What makes it controlling in 2026 is a gap in the statute book. Tennessee's General Assembly amended the sales and use tax statutes to override Commerce Union Bank — that is why remotely accessed software and SaaS are squarely taxable under Tennessee's sales tax today. But the legislature never made the parallel amendment to the business tax. So for business-tax purposes, the old rule survives: software is intangible, and intangibles are outside the base.

That is the whole game, and it is a lesson in statutory mechanics, not metaphysics. The software did not change. The technology did not change. One tax reaches it and the other does not, purely because the legislature amended one statute and not the other. Anyone who tells you "cloud software is taxable in Tennessee" is both right and wrong, and the only way to know which is to name the specific tax and read the specific statute.

Note too that the court did not treat "cloud" as a single category. Licensed software delivered remotely is intangible and non-taxable. Hosting — where the provider keeps and operates the infrastructure — is a taxable service under a possession-and-control analysis. Optional support and consulting are separately taxable services. Three different answers, all living inside what a marketing page would call "the cloud product."

Why this lands on AI agent operators

If you run an AI agent, an agentic workflow, or any autonomous software service, your invoice probably braids together exactly these strands. There is a license or subscription to the underlying model or software. There is compute and hosting — you are running inference on infrastructure you control. And there are wraparound services: onboarding, integration, tuning, premium support. Operators tend to price and think about all of it as one "AI product." Tennessee just demonstrated, in a single company's assessment, that a taxing authority will pull those strands apart and tax them differently.

Three practical takeaways:

The "cloud" and "AI" labels carry no tax weight. What matters is the legal character of each receipt: is the customer buying an intangible right to use software, or a service the provider performs on infrastructure it retains? SAP's hosting was taxable precisely because SAP kept control of the servers — a fact pattern that describes nearly every hosted AI agent. The label on your pricing page does not decide this. The substance of what the customer receives does.

Segment your revenue before a state does it for you. SAP prevailed on the license piece because it could distinguish that revenue from its hosting and service revenue. An operator that bills a single undifferentiated "platform fee" hands the state the easier argument that the whole thing is a taxable service. Clean books that separate licensed software from hosted compute from professional services are not just tidy — they are the difference between defending a position and having none.

Do not assume one tax's answer transfers to another. The Tennessee twist — non-taxable under the business tax, taxable under the sales tax — is not a Tennessee quirk. Every state runs multiple tax regimes (sales/use, gross-receipts or franchise, communications, local privilege taxes), each with its own definitions and its own legislative history. A conclusion that a receipt escapes one of them tells you nothing about the others. This is exactly the kind of cross-regime divergence that trips up operators who reason from a single "is it taxable" mental model.

The angle worth watching

There is also a live compliance action buried in this. Because the court confirmed software licenses are outside the business tax, companies that have been remitting Tennessee business tax on software license receipts may have a refund opportunity for open periods — which is why the SALT bar has been circulating the case. For AI operators with Tennessee customers, the more durable question is prospective: how much of your receipt is a licensed intangible, how much is hosting on infrastructure you control, and how much is separately delivered service? Get that split right and you can defend each line. Get it wrong, or never draw it at all, and you inherit whichever characterization the auditor finds most convenient.

One caution on how far to read the holding. Characterization and true-object questions in digital commerce remain genuinely unsettled across the states, and this is one court applying one state's business-tax statute to one company's facts. It is not a general rule that "SaaS is intangible" — under Tennessee's own sales tax, remotely accessed software is taxable. Treat SAP America as a precise statutory result, not a slogan.

The compliance move is the same one we come back to constantly: stop asking whether "the AI product" is taxable, and start asking what each receipt actually is, in each state, under each applicable tax.

See how AgentTax characterizes and sources each component of an AI agent transaction — license, hosting, and service — across every state's rules, so you are computing tax on what the receipt actually is, not on the label the product happens to wear.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.