Tennessee court ruling on SAP exposes gaps in state tax law as AI blurs the line between software and cloud services

Tennessee Court Signals Tax Fight Over AI-Powered Software

A Tennessee appeals court decision on cloud-based software taxation may preview the next major state tax dispute: whether artificial intelligence processing buried inside software changes what customers are actually buying.

The court in SAP America, Inc. v. Gerregano split the difference between SAP and the state. Software licenses remained nontaxable, but cloud hosting and cloud-based services qualified as taxable services delivered electronically into Tennessee. The ruling applied traditional tax categories cleanly because SAP's offerings came with separate invoices for each component.

That separation won't last. Modern software increasingly depends on remote functions for authentication, updates, syncing, analytics, payment processing, storage, and customer support. Adding AI to that mix makes the problem urgent.

When Remote Processing Becomes the Product

The court used the "true-object" test to decide what was taxable. When a transaction contains multiple elements, courts ask what the customer was really buying and use that answer to determine tax treatment.

This test works when pieces are visible and separately priced. It breaks down when remote functionality is buried inside what feels like software to the customer.

Consider a tax-preparation product that runs calculations locally but sends ambiguous entries to a remote AI model for classification. That's probably still software. But if the same product uses a hosted model to generate return positions, risk analyses, and tax planning recommendations-and customers pay by usage and store data in the vendor's cloud-the answer gets murkier. At that point, calling it a software license starts to strain credibility.

States Need a Clearer Standard

Rather than abandon the true-object test, states should clarify it with a safe harbor for software. Remote functionality should not recharacterize a transaction as a taxable service unless the state can show the remote component does more than help the product operate.

States could create a presumption that software transactions remain nontaxable licenses when remote functions are limited to a set list: authentication, updates, syncing, security, or modest product enhancements. States could rebut that presumption when customers are actually buying hosted processing, managed infrastructure, access to models, or AI inference.

Without such a threshold, states will face pressure to declare any AI processing a taxable service. That approach would be administrable but arbitrary-like declaring all soup beverages because some soup is liquid.

The better rule asks a single question: Is the remote function helping software operate, or is it the thing the customer is really buying? The answer matters less for SAP's neatly separated offerings and more for the hybrid products already arriving.

Learn more about how generative AI and LLM systems are reshaping business operations, or explore AI for finance professionals managing these emerging tax questions.