California taxing SaaS is one of the biggest US software changes in years.
On June 29, 2026, Governor Gavin Newsom signed Senate Bill 122 (SB 122), a budget trailer bill that extends California's sales and use tax to digital products, including prewritten software and Software as a Service (SaaS). The change takes effect for transactions occurring on or after January 1, 2027.
California was one of the few large states that did not tax electronically delivered or cloud-accessed software. That exemption is going away. If your company sells software into California, or buys it for use there, this affects you, whether or not you are based in the state.
Beginning January 1, 2027, California's full state and local sales and use tax (7.25% state rate, plus local district taxes that vary by buyer location) applies to prewritten software regardless of how it is delivered. That includes software:
The law amends California's definition of "tangible personal property" to include digital products. In plain terms, the format no longer matters. If it is prewritten software, it is taxable.
Not everything digital is swept in. SB 122 preserves several important exclusions:
The key dividing line is "prewritten" versus "custom." If you sell the same software to many customers, it's almost certainly prewritten and taxable. If your software was built from scratch for one client, it's custom and stays exempt. Modifications to prewritten software are a gray area: the modification itself may qualify as custom, but the underlying prewritten product remains taxable.
Two things must be true. First, what you sell must qualify — prewritten software or SaaS, not custom software or infrastructure services. Second, you need a connection to California, known as “nexus,” which happens either way:
Not having a California office does not get you off the hook. A lot of software companies that have never registered in California will need to for the first time based on Economic nexus.
There are two primary types of indirect taxes in the U.S. Both are taxes on the same thing, but differ on who is responsible for paying it:
Some B2B customers, including resale buyers and qualifying exempt entities, won't owe California tax. But you can only skip charging them if you have a valid California exemption or resale certificate on file. Without one, you must charge them. Identify those customers and collect certificates before January 1.
SB 122 includes a mechanism most states do not have. For large software relationships, the obligation to remit tax can move from the seller to the purchaser.
If a retailer's gross receipts from digital product sales to a single purchaser exceed $5 million in the applicable period, the purchaser assumes responsibility for self-assessing and remitting use tax rather than the seller collecting it. If your business has large software vendors or large software customers, model this threshold now.
Six months is less runway than it sounds like, because system changes, contract updates, and registrations take time. Practical steps:
SB 122 leaves several questions open, including the exact line between custom and prewritten software, bundled transactions, resale treatment, and transition rules for multi-year contracts that straddle the effective date. The California Department of Tax and Fee Administration (CDTFA) is expected to issue clarifying guidance, with a workshop scheduled for Tuesday, July 21, 2026. Until then, taxpayers should document their positions and the facts supporting them.
If your business sells or buys software or SaaS with any California footprint, now is the time to assess your exposure. Our team can help you classify your offerings, evaluate your systems and contracts, and build a compliance plan well ahead of the deadline.
Reach out to your Brinker Simpson tax advisor to start the conversation.