California starts taxing SaaS on January 1, and how you invoice decides the size of the bill

California will charge sales tax on SaaS from January 1, 2027, and for most software vendors the first customer conversation about it will happen on a renewal call rather than on a pricing page. SB 122 was signed on June 29 and chaptered as Chapter 23, Statutes of 2026, rewriting the state's definition of taxable property so that it covers software delivered in any form. The detailed rules deciding how much of a given contract is taxable are still being drafted.

What the statute actually does

SB 122 amends California's Revenue and Taxation Code so that "tangible personal property" now includes a digital product, which new section 6016.1 defines as "prewritten computer software transferred on tangible storage media, transferred electronically, or accessed remotely". California did not invent a software tax; it moved software inside the sales tax it already had, which is why local district rates ride along automatically.

The exclusion list is short. Digital books, audio, video, video games and crypto assets are out. So is "digital infrastructure", which the bill describes as a cloud service that lets a user create, deploy, scale or run the user's own software on the provider's platform. Compute sits outside the tax base. A seat licence does not.

Two carve-outs bear on how software gets packaged. Custom software prepared to the special order of a single customer stays untaxed, but the bill states plainly that software held for general or repeated sale is prewritten even when it began as a custom build. Separately, section 6372.1 exempts a service delivered electronically where the provider's effort primarily drives it and begins only after the customer asks. That exemption is then switched off for "the right to use the provider's computer software running on a cloud infrastructure". Human work delivered through a screen is exempt; the platform it arrives on is not.

Where the state thinks your customer is

Location follows use, not paperwork. Section 6010.5.1 fixes the place of use wherever the right or power over the product is exercised, and says remote access occurs where the person accessing it is located. A further presumption treats anything bought outside California and used inside it within 90 days as bought for California use. Restructuring a billing address does not relocate the seats.

Above a threshold, the collection duty flips. Once one purchaser buys more than $5m of digital products from one retailer in a calendar year, section 6201.55 relieves that retailer of collecting use tax and makes the buyer self-assess, remit directly, and hold a use tax direct payment permit. A vendor's biggest accounts stop being a billing-system problem and become a procurement negotiation.

Why this is a marketing problem, not only a finance one

SaaStr founder Jason Lemkin, whose firm also runs a venture fund and so has its own stake in software margins, puts the practical increase at 8 to 10% once the 7.25% state rate and local district taxes combine, and reports that the state expects roughly $2bn a year from the change. It is not a price rise anyone at your company decided on, but on a January invoice it looks exactly like one.

That is the part marketers own. The number on your pricing page stops being the number a Californian buyer pays, and nobody on the growth team usually sits within reach of the tax line. If your standard annual uplift is 7% and the state adds 9%, the renewal reads as a 16% increase, and only half of it is negotiable.

The second lever is stranger. Because the exemptions turn on what is being sold rather than who sells it, how a contract is written down starts to change what it costs. Lemkin's summary of the bundling risk is the line to internalise:

A bundle billed as one line item is taxable in full.

Separating implementation, training, support and managed services from the subscription itself is billing work with a real number attached for the customer, and it costs the vendor nothing but process. Expect the infrastructure exclusion to become a positioning claim too: a platform that can honestly describe itself as somewhere customers run their own code lands on the cheaper side of a 10% gap from a rival that cannot. That classification will be contested, and a marketing team leaning on it before the tax department has written its position down is manufacturing a liability, not a differentiator.

There is a legitimate fourth-quarter campaign here, and it carries a trap. Early renewals invoiced and paid in December can genuinely sit before the operative date. But transition rules for contracts straddling that date are, on SaaStr's account of the department's July workshop, exactly what remains unwritten, so an offer promising tax-free treatment rests on a regulation nobody has read. Sell the timing, not the guarantee.

• Classify every SKU as taxable, exempt or genuinely unclear, and get the unclear ones a written position.
• Rework quote and invoice templates so services are separately stated from subscription access.
• Give sales and CS one paragraph of explanation and the affected-account list, before anyone improvises tax policy on a January call.
• Decide in advance whether you will absorb your own annual uplift on California accounts, and on which ones.