California SB 122: Every SaaS Tool Your Team Uses Is About to Cost 8–10% More
EntrepreneurshipCalifornia was the last major holdout. For three decades, the state treated remotely accessed software as a service, not a product — meaning SaaS subscriptions escaped sales tax entirely. That ends January 1, 2027.
What Happened
Governor Gavin Newsom signed SB 122 on June 29, 2026. The law classifies “prewritten computer software transferred on physical media, transferred electronically, or accessed remotely” as tangible personal property subject to California’s sales and use tax. This covers most B2B SaaS products — even those originally built as custom work, if they are now sold repeatedly to multiple customers.
The state rate is 7.25%. With local district taxes layered on top, effective rates reach approximately 10.75% in high-tax jurisdictions. SaaStr’s analysis estimates an 8–10% cost increase for most California customers. A company spending $2 million annually on SaaS subscriptions could face $160,000–$200,000 in additional costs — with no corresponding tax credit mechanism to offset it.
The projected state revenue: approximately $2 billion annually.
What’s Taxed — and What Isn’t
The law is broad. Standard SaaS products, AI tools, and productivity software are taxable if sold on a subscription or usage basis. Key exemptions include custom software built to a single customer’s specifications, Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), and services where the primary value is human labor delivered electronically.
Consumption-based AI pricing — per-token or per-API-call billing — remains in a gray zone. The California Department of Tax and Fee Administration (CDTFA) has emergency regulatory authority through 2028 and is expected to publish guidance before January 1, 2027, but the rules are not finalized.
Bundled contracts may reduce taxable exposure: if a vendor separates the taxable software component from non-taxable services on invoices, only the software portion is taxable.
What This Means for Buyers and Vendors
Buyers face increased costs with no credit mechanism. The practical options are renegotiating contracts to share the tax burden with vendors, restructuring procurement to shift some spend toward IaaS/PaaS where exemptions apply, or revisiting consolidation of tools that can be replaced with non-taxable alternatives.
Vendors with California nexus — either physical presence or over $500,000 in California digital product sales — must register with CDTFA, classify products, calculate district-level rates, and handle exemption certificates. Companies that cross the $5 million threshold for a single purchaser flip the obligation: the buyer self-assesses and remits use tax directly, rather than the vendor collecting it.
The operational burden is real, particularly for SaaS companies that have never managed sales tax compliance at this level of granularity.
The So What
SB 122 is not a California-specific edge case — it signals that the last major holdout on SaaS taxation has closed the loop, and the rest of the country is watching. For California-based teams, the immediate action items are inventory what you’re spending on taxable software, model the 8–10% impact on 2027 budgets, and engage your SaaS vendors about contract language before January 1. For vendors selling into California, the compliance infrastructure needs to be in place by year-end. The window to prepare is short.
Source: SaaStr
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →