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 Clears Its Biggest Test: The Legislature Just Put It in Their Own Budget

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

On June 15, 2026 — California's constitutional budget deadline — the Legislature moved to adopt its own 2026-27 budget plan, and the sales tax on prewritten software survived. Lawmakers signed on to Governor Newsom's proposal to apply California sales and use tax to "most company software," with reporting specifically naming everyday business tools like Slack and Microsoft's productivity suite. The provision is no longer just a line in the Governor's May Revision. It is now in the Legislature's own plan.

When we covered Newsom's May 14 proposal a month ago, we flagged one watch item above all others: the June 15 budget deadline, where "the provision either survives the Senate/Assembly conference or it doesn't." It survived. That is the development worth marking — not because the tax is now law (it is not), but because the single largest procedural risk to it just cleared.

What Actually Changed Today

The substance of the tax has not moved since May. What moved is its political standing.

May 14: Newsom proposes extending California's sales and use tax to digital prewritten software — including remotely accessed SaaS — effective January 1, 2027. At that point it is one governor's budget ask.

June 15: The Legislature, facing its constitutional deadline, adopts a budget plan that keeps the software tax in. Both elected branches now back the measure. Final terms still get negotiated with the Governor through the end of June.

That is the difference between a proposal and a near-certainty. A budget tax measure that one branch wants and the other rejects usually dies in conference. A measure both branches have written into their plans usually lands. We are now in the second situation.

The Two-Thirds Detail That Matters

California's constitution requires a two-thirds vote of each chamber to raise any taxpayer's liability. A simple-majority budget can authorize spending; it cannot, on its own, impose this tax. So the relevant signal today is not merely that the budget passed — it is that the software tax was carried as part of a revenue package the majorities are prepared to supply two-thirds support for.

For agent operators, the takeaway is procedural but consequential: there is no ballot measure, no multi-year rulemaking runway, and no voter approval standing between this and an effective date. Once the Legislature and Governor agree on final budget language — expected by the end of June — the statutory hook is in place, and the January 1, 2027 effective date is roughly six months out.

Why This Is Still Not Settled Law

I will not overstate where this sits. My comfort that the tax becomes law substantially as proposed is now More Likely Than Not — an upgrade from the Reasonable Basis I would have assigned on May 14, driven entirely by the Legislature's buy-in. But "More Likely Than Not" is not "Substantial Authority," and three things still genuinely move:

Final budget language. The Legislature's plan and the enacted budget are not the same document. Carve-outs, effective-date tweaks, and threshold language get rewritten in the last week of June. The shape of the tax can still narrow.

The B2B-versus-consumer line. Newsom justified excluding streaming on the ground that "75% of those transactions are business-to-business." That logic deliberately points the tax at enterprise software — which is exactly where AI agent platforms sell. Whether any business-input exclusion survives is the variable I would watch hardest.

CDTFA implementation. Sourcing, resale treatment, and the custom-versus-prewritten line will be resolved in agency guidance, not in the budget bill. Those determine how the tax actually applies to a hosted API call far more than the statute does.

What AI Agent Operators Should Do Now

The case for waiting got weaker today. With both branches aligned, the base rate for enactment is high enough that preparation is the conservative posture, not the aggressive one.

Treat January 1, 2027 as a live cutover date, not a hypothetical. If you bill California-domiciled businesses for hosted model access, hosted orchestration, or agent runtimes, model your collection obligation as beginning that day. California is the single largest state that currently passes through the AgentTax engine as exempt; plan for that row to flip.

Pull your California exposure now. Count and gross-revenue your California-billed customers over the trailing twelve months. You want that number before you are reading enacted statute, not after.

Confirm your contracts pass tax through. Most enterprise SaaS agreements push sales tax to the buyer, but a midterm taxability change only helps you if the pass-through clause survives it. Check the California contracts specifically.

Map offerings to likely classification. Hosted, remotely accessed software is squarely in scope under the proposal's framing. On-prem deployments, SDK distributions, and genuinely custom engagements retain a stronger exclusion argument — but "we configured it for the customer" is not the same as "custom," and California will press that line.

Watch the end-of-June final language, not the headline. The vote that matters for scope is the enacted budget, not today's plan. Read the carve-outs when they land.

What to Watch Next

End-of-June final budget agreement. The Legislature-Governor reconciliation sets the actual statutory text. This is the next hard trigger.

Any business-input or resale exclusion. If one appears, it reshapes the M2M and embedded-SaaS analysis materially.

First CDTFA guidance. Once the statute lands, sourcing and resale rules for remotely accessed software become the whole ballgame for cross-border agent transactions.

A month ago this was a governor's proposal with a credible path. Today it is a measure both legislative chambers have adopted into their own budget, six months ahead of a fixed effective date. The largest enterprise software market in the country is now far more likely than not to start collecting sales tax on SaaS — and AI agent platforms, which sell exactly the hosted, remotely accessed software the tax targets, sit at the center of it.

If you need to model what a California-taxable run does to your pricing before the final language lands, the AgentTax engine lets you simulate a California-taxable scenario today. We are tracking the end-of-June final budget and will update the AI Agent Sales Tax landing page and the 50-state SaaS guide as enacted text and CDTFA guidance arrive.

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