California’s New SaaS & AI Tax: What SB 122 Means for Buyers and Vendors

Get Ready: California’s New Software Tax is Coming

For readers tracking the shift, A significant change is on the horizon for any business buying or selling software in California. Effective January 1, 2027, Senate Bill 122 (SB 122) will extend California’s sales and use tax to a wide range of prewritten software and SaaS (Software as a Service) offerings, regardless of how they are delivered.

This move marks a pivotal shift for the Golden State, which was one of the last major holdouts in taxing cloud-based software. Prepare for an estimated 8-10% increase in your software costs, a change that will impact budgets and operational strategies for both buyers and vendors.

Meanwhile, For three decades, California differentiated between software on a disc and software accessed via a browser. That distinction is now gone.

California joins over 20 other states in taxing SaaS, anticipating roughly $2 billion annually in new state and local revenue. Understanding the nuances of SB 122 is crucial for navigating these impending financial and compliance challenges.

Understanding SB 122: The Core Changes

SB 122 doesn’t introduce an entirely new tax. Instead, it amends the definition of “tangible personal property” to encompass “digital products.” This includes prewritten computer software transferred physically, electronically, or accessed remotely. The tax rate applied will be California’s full stack: 7.25% state tax plus local district taxes, pushing the total to anywhere from 7.25% to 10.75%, typically hovering between 8-10% for most metro areas.

What’s Taxable Under SB 122?

• Prewritten Software: Any software developed for general or repeated sale. This broadly covers almost every B2B software product on the market, even if it originated as a custom build but is now sold multiple times.
• SaaS Access: Software accessed remotely, streamed, or used in a browser.

What’s Exempt?

Not all digital products or services fall under the new tax. Key exemptions include:

• Custom Software: Software explicitly prepared for a single customer’s special order. Modifications to prewritten software are exempt only if separately stated and to the extent of the modification.
• Digital Infrastructure (IaaS/PaaS): Services like AWS, GCP compute, or similar platforms where the customer deploys and runs their own software. The focus here is on whose software performs the task; if you’re running your code on their machines, it’s infrastructure.
• Human Effort Services: Services delivered electronically where the effort is initiated after a customer’s request. This carve-out does not apply to general SaaS access rights.
• Other Digital Goods: Digital books, music, video, video games, and cryptocurrency.

Sourcing and Nexus Rules

For remote sales, the tax is sourced to the purchaser’s known California address (billing, shipping, payment instrument, or mailing address, in that order). There’s a presumption of California use for anything bought outside the state but used within it within 90 days.

SB 122 doesn’t create new nexus thresholds; it simply makes software sales count towards the existing ones: physical presence or $500,000 in California sales for remote sellers. Many B2B companies new to California’s tax authority (CDTFA) will now need to register.

The $5 Million Flip

For example, An important provision for large organizations: if a single vendor’s digital product sales to one purchaser exceed $5 million in a calendar year, the collection obligation shifts. The vendor is relieved, and the purchaser becomes responsible for self-assessing and remitting use tax directly. This shift occurs on the transaction that crosses the $5M threshold and requires the purchaser to obtain a use tax direct payment permit.

Implications for Software Buyers in California

Get ready for a direct hit to your software budget. An 8-10% price increase on existing tools is an expense that adds no new functionality but significantly impacts your bottom line.

• Budgetary Impact: A company spending $2 million annually on taxable software could face an additional $160,000-$200,000 in unnegotiated costs.
• Stacking Costs: This tax stacks on top of any annual vendor price increases. A 7% vendor uplift combined with a 9% tax means a 16-17% increase for the same service.
• Non-Recoverable Expense: Unlike VAT, this is not an input credit or refundable tax. It’s a direct cost that reduces your gross margin.
• Bundling is Key: How vendors invoice matters. If a contract bundles software access with implementation, support, and managed services into a single line item, the entire amount may be taxable. Separately stating these services could mean only the software subscription is taxed. Start asking your key vendors now about their 2027 invoicing plans.
• Compliance for Large Buyers: If you cross the $5 million threshold with a vendor, your finance team will need to establish a new use tax self-assessment function, including issuing exemption certificates and reporting local use tax by county/city of first use.
• Location Matters: Simply changing your billing address won’t evade the tax. SB 122 focuses on the “place of use” – where the person accessing the software is physically located. While future regulations might introduce allocation mechanisms, clean user/device location data will be essential.

Navigating the Change: Advice for Software Vendors

That said, For SaaS and AI companies selling into California, proactive preparation is essential to avoid penalties and maintain customer relationships.

1. Register and Collect: If you have nexus in California and your products are taxable, you must register with the CDTFA and collect the tax. Failure to do so means you still owe the tax, plus interest, if discovered. This involves classifying each SKU, integrating district-rate calculations into your billing system, and establishing an exemption certificate process.
2. Restructure Invoicing: This is perhaps the biggest actionable item. Separately stating charges for implementation, training, support, and managed services from the core software subscription can significantly reduce your customers’ tax burden. A bundled, single-line item invoice will likely be fully taxable. Make these billing adjustments before Q4 2026.
3. Consider Q4 2026 Early Renewals: The CDTFA indicated that a taxable transaction on or after January 1, 2027, requires both a right to use and consideration given after that date. This opens a potential window for customers to prepay for 2027 terms in December 2026, potentially saving 8-10%. Vendors can benefit from pulled-forward revenue and cash flow. Include a tax gross-up clause to protect against future regulatory changes and clearly communicate this as a potential saving, not a guarantee.
4. Arm Your Sales and CS Teams: The last thing you want is a customer surprised by a new line item on their January invoice. Prepare a clear, concise explanation of the tax, identify affected accounts, and outline any authorized concessions (e.g., waiving annual uplifts for at-risk accounts, but be mindful of the margin impact).

The Murky Waters of AI and Hybrid Platforms

One of the most significant areas of uncertainty lies in how SB 122 will apply to AI tools and consumption-based models, particularly those that blur the lines between software and infrastructure.

• AI Application Subscriptions: Seat-based AI products (like Microsoft 365 or specific AI-powered SaaS tools) are likely in scope and will be taxable.
• Consumption-Based AI/LLM APIs: Paying per token or API call for model access is less clear. Is it “remotely accessed prewritten software” (taxable) or “digital infrastructure” where you run your own software (exempt)? The statute doesn’t explicitly resolve this. The CDTFA has flagged usage-based pricing and freemium models as open items, acknowledging that the boundary may require legal opinions or litigation.
• Hybrid Platforms: Many modern platforms combine infrastructure with an application layer (e.g., data warehouses, developer platforms, managed AI services). The test is “whose software performs the task.” If you’re running your code on their machines, it’s infrastructure. If you’re using their code to do a job, it’s prewritten software. For vendors in this “gray” area, pick a classification, document your reasoning, and separate infrastructure and application charges on invoices. A single-line hybrid bill defaults to fully taxable.

Interestingly, For California CFOs, this means a potential 9% swing on one of the fastest-growing budget lines with no clear forecast. For AI product founders, misclassification can lead to either overcharging customers or incurring significant future tax liability with interest.

What’s Next: The Regulatory Landscape

The California Department of Tax and Fee Administration (CDTFA) has two-year emergency regulatory authority to iron out the details of SB 122. They are expected to circulate discussion drafts and hold interested parties meetings in the coming months, with submission to the Office of Administrative Law anticipated in early December 2026, just before the effective date.

However, Key areas that these regulations are expected to clarify include transition rules for existing contracts, detailed guidance on bundling, the specifics of the human effort exemption, and mechanisms for multiple points of use (i.e., how to allocate tax for software used across states). Public comment periods will be crucial. Engaging a tax advisor to submit your product’s fact pattern now could save significant costs down the line if the classification is incorrect.

Prepare Now, Avoid Surprises Later

California’s decision to tax SaaS and AI tools marks a significant shift in the digital economy. While the January 1, 2027, effective date seems distant, the complexity of compliance and the financial impact on both buyers and sellers demand immediate attention.

Proactive planning, clear communication, and careful review of invoicing practices are essential to navigate this new tax landscape successfully. Remember, California is not alone; Colorado is implementing similar changes on the same day, signaling a broader trend that businesses should monitor across other states.

Expert Perspective

From an industry angle, the clearest signal around California SaaS Tax is how it may influence software. The story reads less like a one-day spike and more like a marker of broader movement.

The next phase will depend on how quickly teams, regulators, or customers react. In practice, that gives California SaaS Tax room to reshape expectations across california over the near term.

For readers focused on practical impact, the best next step is to watch what changes around digital once attention turns into execution.

Frequently Asked Questions

Why does California SaaS Tax matter right now?

Get Ready: California’s New Software Tax is ComingFor readers tracking the shift, A significant change is on the horizon for any business buying or selling software in California.

What broader change could California SaaS Tax signal?

Effective January 1, 2027, Senate Bill 122 (SB 122) will extend California’s sales and use tax to a wide range of prewritten software and SaaS (Software as a Service) offerings, regardless of how they are delivered.This move marks a pivotal shift for the Golden State, which was one of the last major holdouts in taxing cloud-based software.

What should the market watch next around California SaaS Tax?

Prepare for an estimated 8-10% increase in your software costs, a change that will impact budgets and operational strategies for both buyers and vendors.Meanwhile, For three decades, California differentiated between software on a disc and software accessed via a browser.

Source: https://www.saastr.com/california-is-taxing-saas-and-ai-tools-and-is-about-to-make-your-software-8-10-more-expensive-heres-what-sb-122-does-to-buyers-and-vendors/