Business & Brand

California Is Now Treating Software as Taxable "Tangible Personal Property"

July 8, 2026

Starting January 1, 2027, SaaS and AI subscriptions sold into California will carry the same sales tax as furniture and appliances.

California Is Now Treating Software as Taxable "Tangible Personal Property"
Credit:
powered by

For decades, California declined to tax software delivered over the internet. The reasoning was rooted in the structure of the tax itself: sales tax applies to tangible personal property, and a cloud subscription involves no physical object changing hands. Nothing ships. Nothing gets handed over. The state's own regulations reflected that, exempting downloaded and remotely accessed software while taxing the same product if it arrived on a disk.

That distinction is gone. With Governor Gavin Newsom's signing of Senate Bill 122 on June 29 as part of the 2026-27 budget, California amended the statutory definition of "tangible personal property" to include "digital products," defined as prewritten software whether it is shipped on physical media, downloaded, or accessed remotely through a browser. The state did not create a separate digital services tax. It reclassified software as a physical good.

What actually changes

Beginning January 1, 2027, retail sales of prewritten software into California will be subject to the state's full sales and use tax: the 7.25% statewide base rate plus local district taxes, which push combined rates above 10% in some jurisdictions. This is the standard rate applied to physical goods. There is no reduced digital rate.

Delivery method no longer matters. Boxed software, downloads, and cloud access all receive identical treatment. Transactions are sourced to the buyer's California address using a statutory hierarchy that begins with the billing address, so out-of-state vendors with nexus in California will need to collect based on where their customers are located.

Custom software, meaning code written to the specifications of a single customer, remains exempt. Modifications to prewritten software count as custom only to the extent of the modification, and only if those charges are separately stated on the invoice. The line between custom and prewritten software has been contested in California tax law for decades, and this law raises the stakes on that classification considerably.

AI tools are in scope

Standardized AI products, including assistants, copilots, and generation tools sold as subscriptions to many customers, are expected to be treated as taxable prewritten software, consistent with how other states that tax software have handled them. A company paying for seats on an AI coding assistant, a chatbot platform, or an enterprise LLM subscription should expect roughly 8 to 10 percent or more added to the invoice, depending on where in California it is billed.

The same applies to the rest of the modern software stack. Team communication platforms, design suites, tax preparation software, CRMs, and developer tools all fall under the new definition if the same product is sold to many customers.

Several categories are explicitly carved out: digital books, music, movies, video games, cryptocurrency and other digital assets, and infrastructure-as-a-service platforms. Raw cloud compute appears to stay exempt while the software running on top of it gets taxed, a distinction likely to generate disputes.

The money, and who pays

The state projects roughly $2 billion a year in combined revenue once the tax is fully phased in, with about $900 million going to the general fund and $1.1 billion to local governments annually. Fiscal 2026-27 will see a partial-year haul since the tax takes effect midway through.

Most of the revenue will come from business-to-business transactions, since companies are the largest software buyers. The state's nonpartisan Legislative Analyst's Office has cautioned that taxing business inputs can end up costing consumers more than a direct consumption tax, because businesses pass the cost through and the tax creates inefficiencies that compound on top of the pass-through. When every layer of a company's software stack gets 8 to 10 percent more expensive, prices eventually reflect it.

Six months to prepare

For software companies selling into California, the timeline is short. Between now and January 1, 2027, vendors need to classify every product against the prewritten-versus-custom line, configure billing systems to calculate combined state and local rates based on customer location, and collect exemption and resale certificates from business customers. Without a valid certificate on file, sellers must charge the tax regardless of the buyer's status. Multi-year contracts signed before the effective date but running past it are a gray area the statute does not resolve.

The California Department of Tax and Fee Administration is expected to issue guidance on the open questions, including bundled transactions, heavily configured enterprise platforms, freemium and usage-based pricing, and how technology transfer agreement principles apply now that software is no longer classified as intangible. Legal and administrative challenges are also plausible given the scale of the change.

The bigger picture

California was one of the last major states to exempt SaaS from sales tax, and its holdout status mattered because it is the largest software market in the country and the place where much of this software is built. With SB 122, the state joins the majority of jurisdictions that tax cloud software. It got there not by writing a digital tax but by declaring in statute that software accessed through a browser counts as a tangible object. As of January 1, 2027, in California, it does, and it will be taxed accordingly.

If this caught your attention, that’s not accidental.


The best editorial systems don’t happen by accident. Outlever builds them.

Get the latest AI insights first.

Sign up for updates, interviews, and fresh analysis on how AI is reshaping business, brands, and technology.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.