California Just Taxed SaaS: A State-by-State Guide to Software Subscription Sales Tax in 2026 and 2027

For most of the modern software era, the biggest prize in the American market came tax-free. California — home to more software buyers than any other state and, until now, one of the most SaaS-friendly tax jurisdictions in the country — did not apply its sales tax to software subscriptions. You could sell a $99-a-month dashboard to a customer in Oakland and not collect a cent of sales tax, while the identical sale to a customer in Seattle carried over 9%.

That era ends on January 1, 2027. On June 29, 2026, Governor Gavin Newsom signed Senate Bill 122, which adds "digital products" — including software-as-a-service — to the definition of tangible personal property subject to California sales and use tax. If you sell software subscriptions to California customers, your invoices change in a few months. If you buy them, roughly 7.25% to 9.5% gets added to the bill depending on where your business is billed. And California is not alone: Colorado flips the same day, and a queue of states has been quietly rewriting their tax bases since 2023.

Here is what actually changed, the full state-by-state map as of August 2026, and a practical checklist for the window you have left.

What California's SB 122 Actually Does​

The mechanics matter, because they determine which of your products are caught.

California's sales tax historically applied to "tangible personal property" — physical goods. Software delivered electronically, and software never delivered at all (just accessed in a browser), fell outside that definition. SB 122 amends the definition to include digital products and related intellectual property interests. A digital product, under the new law, is "prewritten computer software delivered on tangible storage media, transferred electronically or accessed remotely."

Read that last clause again: accessed remotely. That is SaaS. The delivery method no longer matters — download, API, or browser tab, the subscription is taxable.

The change is prospective: everything begins January 1, 2027. The state projects roughly $1.4 billion in new revenue for fiscal year 2027, which tells you enforcement will not be sleepy.

Three operational details deserve attention:

1. The rate is the customer's, not yours. California's statewide base rate is 7.25%, but district add-ons push combined rates above 9% in many cities. For remotely delivered software, the sale is sourced to the customer's billing address — so the rate you charge depends on where each customer is billed, not where your company sits.
2. Sourcing tiers. Software on physical media is sourced to where the transfer happens; software delivered in person (say, at a trade show) is sourced to your place of business; everything delivered electronically is sourced to the billing address. If no California address can reasonably be identified, the sale is treated as outside the state.
3. The five-million-dollar pivot. If a single purchaser buys more than $5 million a year in digital products from one retailer, the retailer can be relieved of its collection duty — and the purchaser must self-assess and remit use tax directly. Small sellers selling to big enterprises need to understand this rule; so do big enterprises buying from small sellers.

What Counts as a Digital Product — and What Escapes​

Not everything with a login screen becomes taxable. The law carves out meaningful territory:

Taxable from January 1, 2027:

• Prewritten software subscriptions (SaaS), regardless of how delivered
• Downloaded apps, plugins, themes, and licenses to off-the-shelf software
• Hosted tools and dashboards built on prewritten code

Still exempt:

• Custom software written for a single client — the classic consulting engagement stays out
• Services primarily involving human effort — consulting, configuration, implementation, and training sold as genuine services rather than software access
• Digital content: digital books, digital audio works (music), digital audiovisual works (streaming video), digital video game products, digital visual works, and digital assets such as NFTs
• Raw cloud infrastructure (IaaS) under certain conditions — platforms where the customer deploys their own software, rather than using the vendor's prewritten application
• Purchases made solely for use outside California, and purchases for resale

The boundary cases are where money is won and lost. A subscription that bundles software access with real consulting hours is part taxable, part not — and you need a defensible split. An AI tool built on a third-party model with proprietary prompting may or may not be "prewritten software accessed remotely," depending on how the service is structured. If a meaningful share of your revenue sits near one of these lines, a taxability review before the new year is not optional.

Colorado Flips the Same Day — and the 2026 Wave Behind It​

California's headline obscures the broader pattern. Colorado's House Bill 26-1223, signed June 4, 2026, adds computer software — including downloads and remote access — to taxable tangible personal property effective January 1, 2027, at Colorado's 2.9% state rate plus whatever home-rule cities impose. One wrinkle worth knowing: Colorado's exemption for negotiable software licenses expressly excludes click-through agreements and online terms of service — the way virtually all modern software is actually licensed. In other words, don't count on the license exemption.

They join a queue that has been moving for several years:

Notice the technique: almost nobody passes a law called "the SaaS tax." States redefine tangible personal property or digital products and let the software fall in. That is why a classification you settled years ago can silently expire.

The State-by-State Map as of August 2026​

SaaS taxability splits into four rough buckets. Treat this as a map for orientation, not a compliance ruling — states keep moving, and several tax under narrower rules than a simple yes/no captures.

States that generally tax SaaS (19 states plus the District of Columbia):

Arizona, Connecticut, Hawaii, Kentucky, Louisiana, Massachusetts, Mississippi, New Mexico, New York, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Washington, and West Virginia — plus Washington, D.C. and Puerto Rico for sellers with customers there.

Conditional — depends on the customer or the charge:

• Iowa — taxable for consumers, exempt for qualifying business purchases
• Ohio — taxable as an "automatic data processing" service, with fact-specific exceptions
• Connecticut — 6.35% for personal use, but only 1% when purchased for business use
• Texas — taxes SaaS as a data processing service, but only 80% of the charge is taxable, effective ~5% on the full invoice
• Maryland — a genuinely unsettled patchwork of digital-products gross-receipts levies and enterprise-software carve-outs; get current advice before relying on either direction

Local taxes inside otherwise-exempt states:

• Chicago applies its ~9% personal property lease transaction tax to cloud software even though Illinois doesn't tax SaaS at the state level
• Alaska has no state sales tax, but boroughs tax and a growing number participate in a remote-seller commission
• Colorado has 60+ home-rule cities that set their own rules — and after January 1, 2027, the state layer turns on as well

Generally not taxable at the state level:

California and Colorado (both only through December 31, 2026), Alabama, Arkansas, Florida, Georgia, Idaho, Illinois, Indiana, Kansas, Maine, Michigan, Minnesota, Missouri, Nebraska, Nevada, New Jersey, North Carolina, North Dakota, Oklahoma, Virginia, Wisconsin, and Wyoming. Five states — Alaska, Delaware, Montana, New Hampshire, and Oregon — have no state-level sales tax at all.

Two cautions. First, several of these "exempt" states tax downloaded prewritten software even where they don't tax pure browser-based access — Wisconsin is a classic example. Second, exemption from taxability is not exemption from registration once you cross a nexus threshold; most states measure the threshold on gross sales, so exempt subscription revenue still counts toward it, and the correct posture is to register and file a return showing zero taxable sales.

Do You Actually Have to Collect? Nexus in Two Minutes​

Taxability and nexus are separate questions. A state can tax SaaS but leave you alone because you have no nexus there; it can leave SaaS exempt but still expect you to register because you do.

Since the Supreme Court's 2018 South Dakota v. Wayfair decision, every state with a sales tax can assert economic nexus — an obligation to register and collect based on sales volume alone, no office or warehouse required. The common threshold is $100,000 in sales or 200 transactions in a calendar year, but the outliers matter:

• California requires $500,000 in total combined sales into the state before an out-of-state seller must register
• New York uses $500,000 in sales plus 100 transactions
• Texas uses $500,000

So the realistic scenario for a small SaaS business: you already collect in the twenty-plus taxing jurisdictions where you have enough customers, and you've ignored California because the product wasn't taxable there anyway. On January 1, 2027, that second question becomes live. If your California revenue across all products exceeds $500,000 a year, you register, collect, and remit. If it's below the threshold, you don't — but your California customers now owe use tax on their own purchases, and sophisticated buyers will start asking whether your pricing is tax-inclusive.

Your Pre-January Checklist​

The window between now and January 1 is enough time if you start now, and uncomfortable if you don't.

1. Build a product taxability matrix. List every SKU: prewritten software, custom work, consulting hours, bundled offerings, digital content. Classify each against the taxable and exempt categories above, and document the reasoning — documentation is what survives an audit three years later.
2. Clean up billing addresses. California sources remote sales to the customer's billing address, and "no identifiable California address" is treated as out-of-state. If your checkout captures only a credit card ZIP, you have a data problem before you have a tax problem.
3. Run a nexus review. Tally 2025 and 2026 calendar-year sales by state, on gross revenue. This tells you where you must register once taxability flips, and where you arguably should already be filing zeros.
4. Effective-date your systems. Configure your billing or tax engine so California tax applies to charges on and after January 1, 2027 — annual subscriptions billed in December for a January–December service year are exactly the kind of edge case worth getting right in advance.
5. Decide pricing presentation. Tax-exclusive (a visible line item) or tax-inclusive (absorbed into the sticker price) is a business decision; making it deliberately beats discovering it on your first February remittance.
6. Collect exemption certificates. Resale certificates, custom-software engagements, and out-of-state-use attestations are only worth what your documentation proves.
7. If you're the buyer, inventory your software subscriptions. Vendors below California's $500,000 threshold won't collect, which means you owe use tax — and if you spend more than $5 million a year with a single vendor, the self-assessment duty is explicit. Your AP process needs a way to flag uncollected tax on software invoices, not just on equipment.

What This Means for Your Books​

Multi-state sales tax turns bookkeeping from a chore into a control system. You need revenue tracked by state, because nexus thresholds are measured on state-level grosses. You need a sales-tax-payable liability account per jurisdiction, because collected-but-unremitted tax is your money only in the sense that you're holding it for the state. And you need a monthly reconciliation between what your tax engine says you collected, what your bank says you remitted, and what your ledger claims — the three-way match that catches a misconfigured rate before it becomes a penalty.

This is also where plain-text accounting earns its keep. A ledger where every tax accrual, remittance, and adjustment is a dated, reviewable transaction — diffable like code, auditable like code — makes "prove it" a query rather than an archaeology project. If that appeals, the plain-text accounting documentation is a good place to start.

Keep Your Compliance Clock Honest​

The states are not done. Vermont, Utah, and Louisiana have all moved in the last two years; D.C. raises its rate this October; California and Colorado flip together in January. The businesses that get hurt are not the ones that misjudge a hard case — they're the ones that never rechecked the map after 2019.

Put a recurring date on the calendar: one pass a year through your taxability matrix and nexus numbers, timed to your fiscal year-end close. California just demonstrated how fast "settled" expires.

Simplify Your Financial Management​

As sales tax obligations multiply across states, keeping clean, auditable books stops being optional. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — every tax accrual and remittance version-controlled, queryable, and yours to keep. Get started for free and see why developers and finance professionals are switching to plain-text accounting.