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

California's SaaS Tax Is Now on the Governor's Desk: The Senate Passed It 28-10

Beardsley Rumble|2026-06-19|4 min read

On June 18, 2026, the California Senate passed S.B. 122 by a vote of 28-10, completing the legislature's action on the budget trailer bill that extends California sales and use tax to prewritten software and SaaS. The Assembly cleared it on June 15. The measure now sits on Governor Newsom's desk. For the first time in this arc, the question is no longer whether the legislature will act — it has — but only whether the Governor will sign what he himself proposed.

When we covered the May 14 proposal, the watch item was the June 15 budget deadline. When we covered the June 15 legislature plan, the watch item was final Senate concurrence. That step is now done. This is the development worth marking: the tax has cleared both chambers in final form and awaits only a signature from the official who authored it.

What Actually Changed This Week

The substance has not moved since May. What moved is finality.

May 14: Newsom proposes extending California's sales and use tax to digital prewritten software, including remotely accessed SaaS, effective January 1, 2027. One governor's budget ask.

June 15: The Assembly adopts the budget plan with the software tax intact, passing it to the Senate.

June 18: The Senate concurs, 28-10. S.B. 122 goes to the Governor as part of a roughly $356 billion FY2027 budget agreement among the Assembly, Senate, and Governor.

The vote margin matters. 28-10 in the Senate is not a squeaker; it reflects a three-party consensus revenue agreement, not a contested floor fight. And because Newsom is a party to that agreement, the probability of a veto on the software provision is, for planning purposes, negligible. We do not call bills law before they are signed, and we are not doing so here. But the compliance posture for AI agent operators should shift this week from "monitoring a proposal" to "preparing for an effective date."

What Gets Taxed — and What Does Not

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." That last phrase — remote access — is the one that captures SaaS. The bill does not stop at downloaded software; it reaches cloud-hosted, subscription-delivered prewritten applications, which is the dominant delivery model for the tools AI agents consume and resell.

The carve-outs are as instructive as the inclusions. The bill does not extend to:

Custom software (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)

That contour tells you the target. 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. For an AI agent operator, that is precisely the layer your stack lives in.

Why This Hits AI Agent Operators Specifically

California has long been the anchor of the "SaaS is not tangible personal property, therefore not taxable" position. Once California flips, the single largest U.S. market moves from SaaS-exempt to SaaS-taxable, and the national taxability map tilts with it. For agent operators, three consequences follow.

Your 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. The agent that quietly provisions a dozen SaaS tools is provisioning a dozen potentially taxable transactions.

Your 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 January 1, 2027. The predominant-character analysis that governs bundled offerings becomes sharper when 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. Autonomous, high-frequency purchasing is exactly the pattern that accumulates unremitted use tax quietly.

What to Do Before January 1, 2027

You have roughly six months. That is enough time 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 California.

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

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

Revisit bundled-offering pricing. Where software is bundled with non-taxable services, the predominant-character determination drives the result. Document it now.

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

The remaining step is the Governor's signature, expected as part of the budget enactment. After that, attention shifts to implementation: the California Department of Tax and Fee Administration will need to issue guidance on situs, bundling, and the prewritten-versus-custom line before the January 1, 2027 effective date. Expect that guidance to be the next substantive development in this 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.