For most SaaS companies, California has historically been one of the easier states to deal with from a sales tax perspective. Electronically delivered and remotely accessed software was generally not subject to California sales tax.
That changes on January 1, 2027.
SB 122, signed by Governor Gavin Newsom on June 29, 2026, brings qualifying prewritten software into California's sales and use tax system. That includes software delivered electronically and software customers access remotely, which puts many SaaS products directly in scope.
For software companies, this is not simply a matter of adding a tax rate to invoices.
You may need to revisit how your products are classified, where customer transactions are sourced, whether you need to register, how your billing system calculates tax, and how your contracts handle tax.
The January 1 effective date also means there is a limited window to make these changes.
The basic rule is easier than it first sounds:
Prewritten computer software will generally be taxable regardless of how the customer receives or accesses it.
That includes software delivered on physical media, downloaded electronically, or accessed through the cloud.
For SaaS companies, the important question is whether the software is prewritten or custom.
Prewritten software is developed for general or repeated sale. Custom software is created specifically for one customer's requirements and remains exempt under the new rules.
A useful way to think about it is this:
If you sell substantially the same software to many customers, it is likely prewritten software. If you build software specifically for one customer, it may qualify as custom software.
Separately stated modifications to prewritten software can receive different treatment, so companies that sell both standard software and custom development should review how those charges appear on their invoices.
Not every digital product becomes taxable under SB 122. The law specifically excludes several categories, so companies should review their individual products rather than assuming every digital offering is now taxable.
Additional California guidance is also important for businesses with products that sit between these categories.
Once a SaaS transaction becomes taxable, the next question is:
SB 122 establishes an order for determining the customer's location for electronically delivered and remotely accessed software.
The starting point is generally the customer's billing address. If that information is unavailable or does not provide a California location, other addresses can be considered, including the shipping or delivery address and certain payment or mailing addresses.
Why does that matter? Because California has local district taxes in addition to its statewide rate. The total tax rate can therefore vary depending on where the transaction is sourced.
For a SaaS company with customers throughout California, this means using one California tax rate for every customer may not be enough.
This can become more complicated when one customer has offices, employees, or operations across multiple California locations.
A company might have one billing address but thousands of users spread across the state. How that transaction should be sourced in every situation is an area where additional guidance will be important.
For now, companies with large enterprise accounts should review the location information they maintain for customers and understand how that information feeds into their tax calculation process.
SB 122 also creates a special rule for certain large purchases.
When a customer purchases more than $5 million of qualifying digital products from a retailer during the applicable period, the customer may become responsible for paying the use tax directly rather than having the retailer collect it.
That means large SaaS providers need to know which customers could reach this threshold and understand what documentation is required.
A billing or tax system that only asks, "Is this customer in California?" may not be enough.
It may also need to answer, "How much taxable digital product has this customer purchased from us?"
California's existing economic nexus rules are another important piece of the change.
Once qualifying SaaS and prewritten software become taxable, those sales can count toward California's $500,000 economic nexus threshold.
For example, a SaaS company generating $600,000 in qualifying California sales may now have a California sales tax registration and collection obligation even though it previously did not collect tax on those software sales.
The important point is that the new law can change the answer to a question many SaaS companies have already asked:
"Do we have to collect California sales tax?"
Businesses should review both economic and physical nexus before January 1. A company with employees, contractors, property, or other physical connections to California may have obligations regardless of whether it meets the economic threshold.
If registration is required, companies should leave enough time for the registration process rather than waiting until the effective date.
Preparing for California's SaaS tax change is not one task. It is a series of connected decisions.
The easiest way to manage it is to work through them in order.
The sequence matters.
You cannot configure the right tax treatment until you know which products are taxable. You cannot source transactions correctly without reliable customer information. And you cannot communicate the right treatment to customers until you understand how the new rules affect their transactions.
SB 122 provides the framework, but some practical questions still need additional guidance.
Bundled offerings are one of the biggest issues for SaaS companies. A subscription may include software, implementation, professional services, support, or infrastructure. Businesses need to understand how California will treat these combinations, particularly when taxable and nontaxable components are sold together.
Services involving human effort are another area to watch. SaaS companies that combine automated software with consulting or other human-delivered services may need to determine how those components should be treated.
Contracts that cross January 1, 2027 also deserve attention. A prepaid annual subscription or multi-year agreement signed before the effective date may require a closer review to determine how the new tax applies to the portion of the contract occurring after January 1.
The practical approach is simple: make the decisions you can make today, document your assumptions, and revisit areas that depend on additional California guidance.
California's new SaaS tax is more than a new line on an invoice.
It can affect what you sell, how you classify it, where you source it, whether you need to register, how your billing system calculates tax, and what your customers see on their invoices.
That may sound like a lot. It is.
But breaking the work into manageable steps makes the transition much easier.
Start with your products. Then review nexus. Then sourcing, registration, billing, contracts, and customer communications.
The companies that start now will have time to test their systems and resolve the gray areas before the first taxable transaction hits.
California has set the date. January 1, 2027 is when the new rules begin. Your tax systems should be ready before then.
👉🏻 Book a Strategy Call with CereTax to assess your California SaaS tax readiness and prepare for the 2027 changes.