The Sales Tax Treatment of Software: Your Roadmap to Multistate Success

Once upon a time, a long time ago, buying software meant going to a store, selecting a box off a shelf, and uploading the content of a disk to a computer. That computer was probably plugged into a wall and maybe even connected to a phone line. This seems like a distant memory, so far removed from how we interact with technology today. Software now can be downloaded with the simple click of a button, accessed remotely through the cloud, licensed through subscriptions, or even bundled with other digital services such as consulting, data analytics, or artificial intelligence.

As technology has evolved, state sales tax laws have struggled to keep pace. Sales tax legislation tends to shift slowly, while the ethos of the technology industry is more akin to “move fast and break things.” The result is a patchwork of rules that creates enormous compliance challenges for software developers, software as a service (“SaaS”) providers, and businesses purchasing technology solutions. Understanding how states classify software transactions has become one of the most important issues in modern state and local taxation.

The Threshold Question: Product or Service?

When assessing the taxability of software, the first consideration is the delivery model. All 45 states that impose a state level sales tax will impose tax on sales of software delivered through a tangible medium such as a disk, unless a specific exemption applies. However, for electronically delivered, remotely hosted, or other delivery models of SaaS, it is important to look at the state law to understand how the state defines SaaS. This goes beyond a simple “taxable” “not taxable” review. The question pivots on whether the state taxes SaaS as tangible personal property, or a service. Some states define software products as tangible personal property. By way of example, Colorado will define SaaS as tangible personal property, subject to state sales tax, effective January 1, 2027. By contrast, Iowa taxes Saas as a digital product, and Florida treats Saas as a digital product excluded from tax. This distinction is important for reasons beyond just determining taxability. State economic nexus laws generally apply to sales of tangible personal property. There is some question as to whether states can impose economic nexus on sellers of digital services.

Canned vs. Custom

The secondary question for determining if a SaaS product is taxable is to understand whether the product is "canned,” versus a custom product. “Canned” refers to software developed for general commercial use and sold or licensed to multiple customers. Most software, like your Microsoft Office Suite or an Adobe subscription, are canned. States that tax SaaS all tax canned software. Custom software, by contrast, is developed specifically for a particular customer and generally cannot be marketed to others without significant modification. Many states exempt custom software because it is viewed as a professional service or the creation of intellectual property rather than the sale of tangible personal property.

The distinction becomes increasingly difficult when vendors modify standardized software for individual customers. At what point does customization transform canned software into custom software? States answer this question differently, creating significant uncertainty for taxpayers.

Sourcing the "Use" of Software

For consumers and sellers of SaaS, the considerations extend beyond the taxability of the product. It is important to understand and drill down on where the tax attaches. Suppose a company headquartered in Florida licenses cloud-based accounting software used by employees located throughout the country. Where does taxable use occur? At corporate headquarters? At the server location? At each employee's location? Many states source software receipts based upon the customer's billing address, while others consider the location where the software is actually used. Enterprise software providers frequently struggle with apportioning receipts among multiple jurisdictions, particularly when users move between states. These sourcing questions have become even more significant as remote work arrangements have become commonplace.

Additional Considerations: Bundled Transactions

Modern software contracts rarely involve software alone. A single agreement may include a software license, cloud hosting, technical support, consulting, artificial intelligence tools, and warranties. Whether these components are separately stated or bundled into a single taxable charge varies significantly among jurisdictions. In many states, if taxable software is bundled with otherwise exempt services for one non-itemized price, the entire transaction may become taxable. Other states permit reasonable allocation between taxable and nontaxable components if properly documented. Careful contract drafting often becomes just as important as understanding the underlying tax law.

Florida's Approach

Florida generally treats canned computer software as taxable tangible personal property when delivered via tangible medium. Electronically delivered, remotely hosted, and other electronic delivery models are outside the taxing statutes and therefore not subject to Florida sales tax. Florida’s approach is straightforward at the time of the initial purchase of a SaaS product, but this gets complicated in context of upgrades and updates. When SaaS was purchased on tangible medium, and therefore taxable, and updates to that software are taxable regardless of delivery method. Conversely, upgrades to a SaaS product are not taxable if delivered electronically, regardless of the initial delivery method. The reasoning, in TAA 15A-015, is that upgrades are not a renewal of the product initially provided.

The Bottom Line

Software taxation illustrates the broader challenge facing state tax systems in the digital economy. Statutes written for tangible products now govern cloud computing, artificial intelligence platforms, subscription services, and technologies that legislators could scarcely have imagined decades ago.

Until greater uniformity emerges, software companies and purchasers must navigate a complex web of state-specific rules governing downloads, SaaS subscriptions, licenses, customization, and digital services. For many businesses, understanding these distinctions is no longer simply a compliance issue, it has become a competitive advantage.

When considering the taxability of your software product, it is important to contact a provider with experience in multistate taxation who understands the industry. At Ribeiro Law, we have worked with software providers of all sizes, across multiple states. Contact us today for a free consultation!