California SaaS Tax in 2027: What SB 122 Means for Software Buyers

California’s SaaS tax change could raise your 2027 software costs even if your vendor’s price stays flat. Customers have been asking us what to do before year-end. On the buying side, one question is worth asking now: would an earlier renewal give you room to negotiate better pricing or terms?

‍Key Takeaways

• Starting January 1, 2027, California SB 122 applies sales and use tax to prewritten software and SaaS, at 7.25% statewide and up to 11.25% with local district taxes.
• Under the CDTFA's proposed rules, tax applies to subscription periods on or after January 1, 2027, no matter when the contract was signed. Signing a renewal in 2026 likely won't avoid the tax.
• A few options may reduce or delay the impact (MPU certificates, itemized invoices, reviewing which entity is billed, and SaaS vs. IaaS/PaaS classification), but each one needs tax advisor input.
• The clearest near-term opportunity is negotiation: pulling 2027 renewals into Q4 2026 gives vendors year-end bookings, and buyers can ask for price concessions, price protection, added value or better terms in return.

California will start taxing SaaS and prewritten software on January 1, 2027, which will raise the cost of most affected subscriptions by roughly 7.25% to 11.25% depending on where the buyer is located. Under the proposed rules, signing early won't change whether you owe the tax. It can still change what you pay for the software, because vendors want year-end signatures and SB 122 gives both sides a reason to revisit renewal timing now.

Tropic customers with headquarters or a home base in California have been asking us what this means for them. Below is what we know, what is still in draft, and what we think buyers can do before December 31.

Note: This is not tax or legal advice. And every organization's situation is different. Work with your tax advisors to understand how SB 122 applies to you before acting on anything here. What we are experts in is software and AI negotiation, and are sharing how California SB 122 and the CDTFA's proposed regulations may influence renewal or buying decisions. 

What is California SB 122?

California Senate Bill 122 (SB 122), signed June 29, 2026, expands the state's sales and use tax base to include prewritten computer software and Software as a Service (SaaS), effective January 1, 2027. By reclassifying remotely accessed or downloaded software as "tangible personal property," California ends its historical tax exemption for digital cloud products.

The California Department of Tax and Fee Administration (CDTFA) is implementing the law through proposed regulations. Those regulations are still in draft and may change before or after January 1, and the tax obligation itself starts on January 1 either way.

How much will the California SaaS tax add to software costs?

The tax adds 7.25% to 11.25% to the cost of affected software, depending on the customer's location:

• Baseline state rate: 7.25%
• Total rate with local district taxes: 7.25% to 11.25%

For a company with significant software spend billed to California, that is a new line item in the 2027 budget. Finance and procurement teams should model it now, before renewals start landing next year. There is no single SaaS tax rate, so confirm the rate for each location with the CDTFA's rate lookup by address.

Which software is taxed, and which is excluded?

SB 122 covers prewritten software and SaaS, but the law excludes several digital categories. These include Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), digital books, digital audiovisual works (such as video streaming), music, video games, digital visual works, and cryptocurrency. Custom software (prepared for a single customer) is covered by a separate exemption with its own requirements. Classification depends on what a product does, not what the vendor calls it.

How does California decide where a SaaS purchase is taxed?

For non-in-person sales, the tax rate is based on the purchaser's known address. The CDTFA checks for an address in this order:

1. Billing address
2. Shipping or delivery address
3. Payment instrument address
4. Mailing address

If no purchaser address can be determined, the sale is treated as out-of-state. Software bought outside California but used in California within 90 days is presumed to be California-sourced, according to the CDTFA's guidance for purchasers. An out-of-state address on the invoice doesn't remove the tax on its own, because use in California can still create a use tax obligation.

Who pays the tax: the software vendor or the buyer?

By default, the software seller collects and remits the tax. Once a single buyer's digital product purchases from a single vendor exceed $5 million in a calendar year, the buyer becomes responsible for the tax. The buyer must then obtain a use tax direct payment permit (or request a waiver from the CDTFA) and self-assess and remit the tax. Starting in 2028, the threshold applies based on the current or preceding year.

The threshold is not a tax exemption. It changes who reports and pays the tax, not whether it's owed. If you have any vendor relationship near $5 million a year, flag it for your tax team now.

Does signing a renewal before 2027 avoid the tax?

Probably not. Under the CDTFA's proposed rules, tax applies to subscription periods on or after January 1, 2027, regardless of when the contract was signed. A multi-year deal signed in December 2026 would still be taxed on its 2027, 2028 and 2029 service periods.

There is mixed messaging on this point. Most of the guidance we have seen says early signature won't matter, and a small number of sources suggest that software put into use before 2027 may be treated differently. Because the regulations are still in draft, we'd plan on paying the tax and treat anything else as upside.

What options may reduce or delay the impact of SB 122?

Because tax applies to subscription periods on or after January 1, 2027, options are limited and depend on how each organization is structured. The options below are potential approaches to discuss with your tax advisor, not recommendations. 

1. Consider a Multiple Points of Use (MPU) exemption certificate

If your business is headquartered or billed in California but many of your software users are outside the state, this may help reduce your tax burden. Under proposed Regulation 1600.2, buyers would be able to issue an MPU certificate allocating software use between California and non-California users.

• How it may work: Use a reasonable, consistent, documented method (such as user or seat counts) to show the share of use outside California. Allocation by server location is not expected to be accepted.
• Example: If 90% of users are outside California, only the remaining 10% would likely be subject to California sales tax.

2. Request itemized invoices

SB 122 doesn’t specify how bundled charges are taxed. A single blended price could expose the full amount to tax.

• How it may work: For software that includes significant configuration, setup, data migration, or training, ask the vendor to list those costs separately.
• Potential result: Separately stated charges, such as custom modifications, may be treated as nontaxable, which could reduce the taxable amount. Treatment of specific service types should be confirmed with a tax advisor.

3. Review which entity is billed

The sourcing hierarchy is driven by customer address records, starting with the billing address.

• How it may work: Multistate organizations may already buy some enterprise-wide applications through an out-of-state entity or office.
• Potential result: If no California address appears in the hierarchy, the seller would likely not charge California sales tax at the point of sale. Note: California entities using the software may still owe use tax, and software used in California within 90 days of purchase is presumed to be California-sourced. This option likely affects timing and who remits the tax more than whether tax is owed. Tax advisor input is especially important here.

4. Evaluate the SaaS vs. IaaS/PaaS boundary

IaaS and PaaS are expected to remain exempt under SB 122, though how CDTFA classifies specific products may continue to evolve.

• How it may work: When evaluating new solutions, understand whether a product is likely to be classified as SaaS or as a platform or infrastructure offering, since classification may affect tax treatment.
• Potential result: Where a PaaS or IaaS approach already fits the business need, it may fall outside SB 122. Tax treatment should be one factor in the decision, not the driver.

Should you pull 2027 software renewals into 2026?

For many buyers, it's worth asking. SB 122 gives customers and suppliers a natural reason to revisit renewal timing. Even if tax will still apply to service periods on or after January 1, 2027, moving a renewal into Q4 2026 can create real leverage, since many SaaS vendors are focused on closing business before year-end.

Take a renewal that isn't due until April 2027. If you open the conversation in December, you get a quote and a set of terms you can compare against whatever April brings. You aren't obligated to take it, but you have the option. A lot of suppliers look favorably on an early renewal, especially one at the end of the year. 

What to ask for in exchange for an early signature:

• Lead with timing as the value you’re offering. An early year-end signature helps the vendor’s 2026 bookings and quota. Ask for something in return rather than renewing early at current terms.
• Ask for price concessions. Request a lower unit rate, a larger discount, or at the very least waived price increases in exchange for signing early.
• Lock in price protection. Push for multi-year caps on renewal increases (for example, 0% to 3% per year) to help offset the new tax cost in future years.
• Negotiate added value. Request no-cost add-ons such as extra seats, premium support, training credits, sandbox environments, or modules you’ve been evaluating.
• Improve terms. Use the early renewal to get better payment terms, flexible downsizing rights, or alignment with the end dates of your other agreements.
• Act quickly. Vendors are usually most flexible in the final weeks of their fiscal quarter or year. Starting conversations in as soon as possible leaves time for approvals before year-end.

What should finance and procurement teams do now?

Start with an inventory and get it to your tax team before the first 2027 invoices arrive.

• Identify the software contracts and California users that may be affected, including subscriptions that already run into 2027.
• Once identified, talk to your tax advisors about those specific contracts and create an action plan 
• Ask vendors how they plan to bill the tax in 2027, whether they'll itemize charges, and which certificates they'll accept.
• Track annual spend by vendor, especially anywhere near the $5 million threshold.
• Prioritize renewal conversations where earlier timing could get you better pricing or terms.

How can Tropic help with early renewals before year-end?

If you're a Tropic customer, send us any renewal due in the first half of 2027 and we'll look at whether an early renewal makes sense and what to ask for. If you're not a customer, reach out and we'd love to discuss how we can help.

Frequently Askes Questions:

When does California start taxing SaaS?‍

January 1, 2027. SB 122, signed June 29, 2026, applies California sales and use tax to prewritten software and SaaS for subscription periods on or after that date.

How much is the California SaaS tax?

‍The state rate is 7.25%. With local district taxes, the total ranges from 7.25% to 11.25%, depending on the buyer’s address.

Does signing a renewal before January 1, 2027 avoid the tax?

‍Probably not. Under the CDTFA’s proposed rules, tax applies to service periods on or after January 1, 2027, regardless of when the contract was signed.

Who pays the tax, the vendor or the buyer?

‍The vendor collects it by default. Once a buyer spends more than $5 million with a single vendor in a calendar year, the buyer must self-assess and remit the tax.

Are IaaS and PaaS taxed under SB 122?

‍No. IaaS and PaaS are excluded, along with custom software, digital books, streaming video, music, video games, digital visual works and cryptocurrency.

What should buyers ask for if they renew early?

‍Price concessions, multi-year caps on increases, no-cost add-ons such as extra seats or premium support, and better payment or downsizing terms.