This article is for informational purposes only and does not constitute tax, legal, or accounting advice. Consult a qualified tax professional before making compliance decisions.

Policy

It's Law: Newsom Signs California's SaaS Sales Tax, and the January 1, 2027 Clock Starts Now

Beardsley Rumble|2026-06-30|5 min read

On June 29, 2026, Governor Gavin Newsom signed California's FY2027 budget, and with it S.B. 122 — the trailer bill that extends California's sales and use tax to prewritten software and Software-as-a-Service effective January 1, 2027. The proposal we have tracked since May is no longer a proposal. It is law. For the first time, the largest software market in the United States has enacted a SaaS sales tax, and the only remaining variable is implementation.

We have been deliberate about not calling this bill law before it was signed. When we covered the May 14 proposal, the watch item was the June 15 budget deadline. When we covered the June 18 Senate vote, the watch item was the Governor's signature. That signature came on June 29. This is the development that matters, because it is the one that converts a planning probability into a fixed compliance deadline.

What the Signature Changes

The substance of S.B. 122 has not moved since May. What changed on June 29 is certainty. Until a budget bill is signed, an operator can rationally defer action on the theory that the language might be amended, delayed, or vetoed. That theory is now closed. The statute is enacted, the effective date is fixed, and the six-month runway to January 1, 2027 is running.

The arc, for the record:

May 14: Newsom proposes extending the sales and use tax to digital prewritten software, including remotely accessed SaaS, effective January 1, 2027.

June 15: The Assembly adopts the budget plan with the software tax intact.

June 18: The Senate concurs, 28-10.

June 29: The Governor signs the budget. S.B. 122 is enacted.

There is no further legislative step. The next substantive events will come from the California Department of Tax and Fee Administration, not the legislature.

What Is Now Taxable in California

S.B. 122 reaches, in the language of contemporaneous analysis, "most material transfers of rights to use prewritten software — whether by perpetual license, subscription, term license, or remote access." The phrase that captures SaaS is remote access. The tax does not stop at downloaded software; it reaches cloud-hosted, subscription-delivered prewritten applications — the dominant delivery model for the tools AI agents consume and resell. California's full state and local rate, currently 7.25% plus applicable district taxes, will apply to this newly taxable class beginning January 1, 2027.

The carve-outs define the target as sharply as the inclusions do. The tax does not extend to:

Custom software (written to a specific customer's specifications)

Cryptocurrency and digital assets

Digital audiovisual works and video games

Infrastructure-as-a-service (raw compute and storage)

California is not taxing consumer streaming or raw cloud infrastructure. It is taxing the B2B prewritten-software layer — the SaaS subscriptions, API products, and packaged AI tools that sit between infrastructure and the end user. That is precisely the layer an AI agent stack lives in.

Why This Lands on AI Agent Operators

California has been the anchor of the national "SaaS is not tangible personal property, therefore not taxable" position. Its enacted reversal does not just add one state to the taxable column; it removes the single largest argument that SaaS is presumptively exempt. For agent operators, three consequences follow directly.

Input costs change. If your agent subscribes to prewritten software, APIs, or model access that qualifies as taxable prewritten software with a California situs, those inputs may now carry sales or use tax beginning in 2027. An agent that autonomously provisions a dozen SaaS tools is provisioning a dozen potentially taxable transactions.

Output may become taxable. If your agent resells, bundles, or provides access to prewritten software to California customers, you may have a collection obligation you did not have before. The predominant-character analysis that governs bundled offerings becomes sharper once the software component is squarely taxable.

Use-tax exposure rises on autonomous purchasing. When an agent buys taxable software from a vendor that does not collect California tax, the use tax obligation falls on the buyer — same 7.25%-plus rate, same base. High-frequency autonomous purchasing is exactly the pattern that accumulates unremitted use tax quietly, one API call at a time.

What to Do in the Next Six Months

The runway is real, and it is enough to do this deliberately rather than retroactively.

Inventory your California software footprint. Identify every prewritten-software input and output with a California nexus — what your agents buy, and what they sell or resell into the state.

Classify against the S.B. 122 contour. Separate the excluded components (custom software, IaaS, digital assets) from the included ones (prewritten subscription and remote-access software). That line is the difference between a taxable and a non-taxable transaction.

Stand up use-tax accrual for agent purchases. If your agents buy taxable software from non-collecting vendors, build the accrual mechanism before the obligation accrues, not after.

Document bundled-offering pricing. Where software is bundled with non-taxable services, the predominant-character determination drives the result. Write down the analysis now, while the facts are fresh.

AgentTax classifies agent transactions against current state taxability rules and flags where a transaction's character — software, service, or digital good — drives the tax result. As California's effective date approaches, that classification is the difference between a clean January 1 cutover and a use-tax cleanup in 2028. See how it works at agenttax.io.

What to Watch Next

With the statute enacted, attention shifts entirely to the CDTFA. The agency will need to issue guidance on situs, bundling, and the prewritten-versus-custom line well before January 1, 2027. Operators should watch for the first regulatory or interpretive notice, which will resolve questions the statute leaves open — most importantly, how remote-access situs is sourced when an agent and its customer sit in different states. That guidance, not the legislature, is now the story. We will be reading it closely.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.