California Will Tax SaaS Starting January 1, 2027: What Software Companies Need to Know

What SB 122 Actually Does

California's sales tax has historically been limited to tangible personal property: things you can physically see, touch, or hold. Electronically delivered software and cloud-based SaaS sat outside that definition. SB 122 erases that line. The law amends the Revenue and Taxation Code to define "digital products" as "prewritten computer software transferred on tangible storage media, transferred electronically, or accessed remotely," meaning a disc, a download, and a cloud login now receive identical tax treatment.

The language is written to capture the full range of how software reaches customers today: enterprise SaaS platforms accessed through a browser, subscription tools billed monthly or annually, hosted applications where the customer never downloads anything, and AI-enabled products that deliver standardized functionality on demand. The CDTFA is expected to issue implementation guidance on bundled transactions, exemption documentation, and product classification. Watch for that guidance closely if your product structure is complex.

Who Is Affected: The $500,000 Nexus Threshold

Not every SaaS company selling into California owes California sales tax under SB 122. The trigger is physical presence in California or California's $500,000 economic nexus threshold. Once a remote seller crosses $500,000 in annual California sales of tangible personal property, it must register for a California seller's permit and begin collecting. That $500,000 threshold predates SB 122; it has been California's economic nexus standard since 2019. What SB 122 does is reclassify prewritten software and SaaS as tangible personal property, which automatically triggers that existing threshold for the first time against software revenue. California is the largest state economy in the country. If you have any real market presence there, run the numbers now.

One additional threshold for larger enterprise relationships: when a single purchaser's digital product spend with one retailer exceeds $5 million in a calendar year, SB 122 shifts the collection obligation from the vendor to the purchaser. The purchaser must then self-assess and remit use tax directly to the CDTFA. This is a per-purchaser, per-retailer spend threshold, not a measure of the vendor's total SaaS revenue. In 2027 only the current year counts; starting January 1, 2028, either the current or prior year triggers the threshold.

What Counts as Taxable Software

SB 122 focuses its new taxability on prewritten computer software, defined as software "held or existing for general or repeated sale or lease, even if the prewritten software was initially developed on a custom basis for in-house use, including the combination of two or more prewritten programs." If you sell or license the same software, or substantially the same software, to more than one customer, it is prewritten software under this law. Configuration is not customization in the eyes of the statute. SaaS platforms accessed through a browser or API, downloaded software, AI-enabled tools where the core is standardized functionality, and any subscription access billed monthly, annually, or per seat all fall within the taxable definition.

What Is NOT Taxable

The legislature carved out several categories, and misclassifying a taxable product as exempt is exactly the kind of position CDTFA auditors will challenge.

Custom software. Software built entirely to the special order of a specific customer and not available for general or repeated sale remains exempt. The exemption does not extend to prewritten components incorporated into a custom project.

Digital infrastructure. SB 122 excludes platforms like AWS, Google Cloud, and Azure, where the customer builds and runs their own application on top of rented compute resources.

Exempt digital goods. Digital books, audio and audiovisual works, visual works, video games, and digital assets including cryptocurrency remain outside the taxable definition.

Service-based offerings. An exemption exists for digital products where the value delivered is primarily the result of human effort performed after the sale. Bundled offerings require documented allocation between taxable and exempt components.

How Sourcing Works: Where Is the Sale?

Because software sold remotely has no physical location, SB 122 establishes a customer-based sourcing hierarchy. For the vast majority of SaaS and electronically delivered software, the primary sourcing location is the purchaser's billing address in the seller's records, then the shipping or delivery address, then the address on the payment instrument, then the most recent mailing address on file.

A SaaS company based in Austin, with servers in Virginia, selling to a customer whose billing address is in San Francisco, is making a California sale. The local rate applied will be the combined state and district rate for San Francisco, which is currently 8.625%. California's combined rates range from 7.25% (the state base) to 11.25% in some jurisdictions.

What SaaS Companies Should Do Now

January 1, 2027 is not far away. Start here.

Step 1: Classify your product catalog. Determine for each product whether it is prewritten software (taxable), custom software (exempt), or digital infrastructure (potentially exempt). Document your reasoning. CDTFA auditors will want to see it.

Step 2: Run your California numbers. Pull all revenue sourced to California customers for the past 12 months. Above $500,000 means you need to register before January 1, 2027.

Step 3: Register with CDTFA and audit your billing data. Registration is through the CDTFA online portal. Remote sales are sourced to the customer's billing address, so if your CRM or billing system does not reliably capture validated California addresses, close that gap now.

Step 4: Update contracts and invoicing. For multi-year contracts signed before January 1, 2027, confirm tax pass-through language exists.

Step 5: Consider your prior exposure. SB 122 creates prospective liability from January 1, 2027. But if you have been selling products already taxable under California law without registering, prior exposure may exist. California's voluntary disclosure program is the path to address it before CDTFA does.

What Happens When CDTFA Finds You First

I have seen SaaS founders get surprised by this at the worst possible moment: due diligence on an acquisition. A buyer's tax counsel runs a nexus analysis, identifies California economic nexus based on years of revenue above $500,000, and asks for documentation of compliance. There is nothing to produce. The acquisition pauses. Sometimes it falls apart entirely.

CDTFA's standard audit lookback is three years under California Revenue and Taxation Code Section 6487, measured from the last day of the calendar month following the period in question. For companies that failed to file at all, the lookback extends to eight years. For companies that find a problem before CDTFA does, California's voluntary disclosure program gives you a path to come forward and limit that exposure. A VDA typically reduces the lookback period and waives penalties. That option disappears the moment CDTFA makes first contact.

Bottom Line

SB 122 takes effect in less than six months. The companies that come through this clean will classify their products, register before January, and start collecting on day one. The companies that get hurt will assume it does not apply to them and find out otherwise when CDTFA makes contact. Do not be the second company. Use Sales Tax Helper's free tools to check your California nexus position, and if you have prior exposure or a complicated product structure, talk to a sales tax attorney before the clock runs out.