Same Tax, Different Address: What California's New Software Tax Reveals About America's Double Standard on Digital Taxation

The author is Shourya Singh, a Second Year B.A. LL.B. Student from National Law University Jodhpur.

Keywords: Digital Taxation

Introduction

For close to a decade, the United States has cast itself as the world's loudest opponent of taxing the digital economy. When France, the UK, Spain, and Italy rolled out Digital Services Taxes (DSTs) on Big Tech between 2018 and 2020, Washington answered with Section 301 investigations and the threat of retaliatory tariffs. When Canada finally brought its own DST into force in 2024, President Trump cut off all trade talks with Ottawa overnight, and Canada folded within 72 hours of the 2024 act s enactment in June 2025. The UK's DST has survived so far, but it remains under sustained US pressure, with American officials calling it an unfair shot at US firms dressed up as a "stopgap" measure.

Which makes it a little awkward that on 18 June 2026, California's legislature passed Senate Bill 122, bringing cloud software and SaaS products into the state's sales tax net for the first time. The bill cleared the Senate 28–10 and the Assembly 56–20, part of a $356 billion FY2027 budget deal now sitting on Governor Gavin Newsom's desk. The companies most exposed Microsoft, Salesforce, Oracle, Adobe, and a fast-growing list of enterprise AI vendors happen to be the same firms whose overseas tax bills the US Trade Representative has spent years trying to shrink. So this piece asks two questions: what does SB 122 actually do, and how much daylight is there really between it and the DSTs Washington fought so hard to kill?

What Sb 122 Actually Does

California has taxed "tangible personal property" since the 1930s, and that old framework produced an odd gap: software bought on a disc, or pre-loaded onto a laptop, was taxable, while the exact same program downloaded or accessed through the cloud was not. Newsom pitched the fix as plain fairness at a press conference earlier this year: "I'm at Best Buy often, and I'm paying sales tax on a lot of this pre-written software, and then I find out all my friends... they're downloading it and they're not paying sales tax. Well, how is that fair?"

SB 122 extends the state's 7.25% base sales tax to "prewritten" digital software no matter how it's delivered: download, local hosting, or remote cloud access. That sweeps in everyday business tools like Microsoft 365, Adobe Creative Cloud, Slack, QuickBooks Online, and Workday, plus a growing crop of enterprise AI platforms. The tax kicks in on 1 January 2027 and is projected to raise $1.1 billion in its first year, climbing toward $2 billion annually which Sacramento needs badly, having spent the past few years riding the volatility of capital gains driven budgets. California's own Legislative Analyst's Office has noted that the bulk of the revenue, an estimated 75%, will come from business-to-business transactions rather than consumer subscriptions, which means foreign software vendors selling into California, not just domestic giants, will now need to register, collect, and remit tax on sales they never had to touch before.

The Playbook Washington Used Against Canada And The UK

To see why SB 122 sits so uncomfortably next to US trade policy, it helps to remember what a DST actually is. Unlike an ordinary sales tax, a DST is a flat levy, typically 2–3%, on the gross revenue large digital platforms earn from users in a given country, whether or not the company has any taxable physical presence there. France introduced the modern template in 2019, and the US response was immediate: a Section 301 investigation under the Trade Act of 1974, followed by threatened tariffs on French goods that were only shelved once both sides agreed to wait for the OECD's reform process to play out.

Canada's experience was the more dramatic one. Its 3% levy on advertising, marketplace, social-media, and data revenue earned from Canadian users applied retroactively to 2022, and would have landed Amazon, Google, and Meta with a roughly $2 billion bill in first-year payments alone. Ottawa held its ground publicly right up until the week the first payments fell due. Then Trump announced he was "terminating ALL discussions on Trade with Canada," and within 48 hours Canada rescinded the law entirely. Canadian tech journalist Paris Marx in his interview with Al Jazeera summed up the episode bluntly: it proved Canada could be pushed around.

The UK has held on, just about. Its DST raised £944 million in 2025–26 alone, and campaigners at TaxWatch UK have argued that giving it up under American pressure could cost the Treasury upwards of £5 billion over time, and would tell every other large economy that tax policy is now something you can simply threaten your way out of. UK Treasury officials keep insisting that a scheduled 2025 review of the tax is not code for repeal even while ministers privately concede to the BBC that the whole thing is "under discussion" with Washington.

Are The Two Taxes Really The Same

Not quite, and the distinction is more than semantic. A DST is a bespoke, revenue-based levy aimed almost exclusively at a small set of large, mostly American, platforms, which is exactly why the US has called it discriminatory. SB 122, on the other hand, is a consumption tax: an extension of an existing sales tax category to a product (software) that was already taxable in physical form. It applies the same way to any seller above the relevant threshold, American or not, large or small, at the identical rate already charged on a boxed software CD at Best Buy.

That formal difference is the whole point of how SB 122 was drafted, and it tracks a real boundary in US federal law. The practical effect on the companies paying the bill looks a lot like a DST regardless: the same handful of large tech firms now owe a new, recurring percentage tax on digital revenue earned from users in a jurisdiction, defended in both cases as closing a fairness gap between old-economy and new-economy taxation. For the foreign vendors now caught in California's net, plenty of them headquartered in India, Israel, and across the EU, the line between "this is a sales tax" and "this is basically a digital tax" probably won't feel like much comfort once the compliance notices start arriving.

The Federalism Wrinkle

Here's the part worth flagging for tax lawyers specifically. The federal Internet Tax Freedom Act (ITFA), made permanent in 2016, bars state and local governments from imposing "multiple and discriminatory taxes on electronic commerce." At first glance, that looks like exactly the weapon Washington could turn on its own state. Except ITFA carves out a tax that is of "general application... imposed... in a uniform and non discriminatory manner on transactions involving similar property, goods, services, or information accomplished through other means." Because California taxes keep downloaded and cloud software at the same rate it already taxes boxed software, SB 122 is built specifically to fall inside that carve-out, not the prohibition. Compare that to Maryland, whose digital advertising tax has drawn years of litigation precisely because it taxes digital advertising while leaving print advertising alone. California's drafters look like they did their homework on that case before writing this bill.

That's the structural reason California can plausibly get away with something close to what Canada and the UK were strong-armed out of doing at the national level. It anchored its new tax to a tax base that already existed and was never in legal dispute, rather than inventing a freestanding levy aimed at platform revenue. Whether the courts agree is still untested. But the design looks deliberate, not accidental.

What This Means For India

For Indian IT and SaaS exporters serving California clients, this is worth tracking as a compliance question, not waving off as someone else's domestic politics. An India-based software company selling prewritten or cloud-hosted products to Californian buyers above the relevant threshold may now need to register, collect, and remit California sales tax, on top of whatever it already handles under GST at home.

It's also a useful data point for India's own running debate on taxing the digital economy, from the now withdrawnEqualisation Levy to the unresolved question of how to define nexus for non-resident digital businesses. Even the US, the loudest critic of unilateral digital taxes anywhere in the world, couldn't resist the fiscal pull of taxing the digital economy once its own budget pressure got acute enough. The lesson for countries still negotiating the stalled OECD/G20 Pillar One process is not a comfortable one: a global consensus on digital taxation is no closer than it was five years ago, US opposition to other countries' unilateral measures hasn't stopped an American state from adopting something structurally similar, and folding under bilateral trade pressure, as Canada did, doesn't make the underlying revenue gap disappear. It just resurfaces somewhere else, a few months later, under a different name.

Conclusion

California's software tax and the DSTs in Canada and the UK aren't legal twins, but they're unmistakably political cousins. Both respond to the same basic fact: digital revenue has outgrown twentieth-century tax categories, and both end up pulling new money from the same handful of dominant technology companies. The difference is that Sacramento built its version to survive the very preemption argument Washington could, in theory, use against it, by tying the new tax to a base that was already settled law rather than inventing a platform-specific one from scratch. For governments elsewhere still weighing whether to go after Big Tech, that's the real lesson in SB 122: a generally applicable tax that simply stops pretending software in the cloud is different from software in a box is far more likely to survive both a courtroom and a trade negotiation than a bespoke "tech tax" aimed at a handful of foreign giants ever was.