Is SaaS taxable in California?
Edvin Givargis Published 11 minute read
The short answer
Not yet, and then yes, and the date between the two answers is January 1, 2027. For nearly four decades California has taxed prewritten software only when it is transferred on tangible media, the rule long administered under Regulation 1502, which left electronic delivery and remote access outside the tax: a customer who downloaded the product or logged into it over the internet bought nothing California treated as tangible personal property, and the receipt was not taxable however large it grew. Senate Bill 122 (SB 122; Stats. 2026, ch. 23), signed June 29, 2026, ends that era. The bill amends Revenue and Taxation Code section 6016 and adds section 6016.1, extending sales and use tax to prewritten software transferred on tangible media, transferred electronically, or accessed remotely, which reaches software as a service ("SaaS"), operative January 1, 2027. The boundary between the eras now runs through every software contract with a California customer, and it cuts in both directions. Ahead of it, sellers of remote-access software inherit a collection obligation, a sourcing rule built on the purchaser's known addresses, and a statute whose exclusions will have to be applied invoice by invoice. Behind it, the old rule keeps governing every open period, which means tax collected on electronically delivered software for those periods was never due, and the same analysis that builds the 2027 compliance file surfaces the refunds the prior era still owes.
What Senate Bill 122 actually does
The mechanism is definitional. California's sales and use tax reaches sales of tangible personal property, and software had always entered the tax, when it entered at all, by riding on property: the disk, the drive, the load-and-leave installation. Section 6016.1 closes the gap by reaching prewritten software directly, in all three of its commercial forms. Software transferred on tangible media was already taxable and remains so. Software transferred electronically, the download, becomes taxable. And software accessed remotely, the subscription under which the customer runs the vendor's product on the vendor's infrastructure, becomes taxable as well, which is the change that matters, because remote access is how the modern software economy delivers nearly everything and it had been California's cleanest nontaxable lane. The word carrying the load is prewritten. The statute taxes the product sold to the market; software prepared to the special order of a single customer stays outside, the same line the tangible-media era drew, and the same line every audit of it will police. A configured instance of a standard platform is still the standard platform, and sellers who plan to reclassify subscription revenue as custom development should expect the label to be read against the product catalog, the contract, and what the customer actually received.
Two administrative facts frame everything else. The operative date is January 1, 2027, not the signing date, so the current period runs under the old rule to the end of 2026. And the California Department of Tax and Fee Administration is expected to issue emergency regulations before the operative date. The regulations will resolve the questions the statute leaves open, and any position taken now on an open question should be written down as an assumption to revisit, not an answer to defend.
What stays outside, and the line-drawing that will decide audits
The statute's exclusions are a catalog of the fights it anticipates. Custom software stays out, as above. Digital books, audio and audiovisual works, and video games stay out: this is a software statute, not a general digital-goods tax, and receipts from content are not swept in by the fact that content arrives through software. Digital assets stay out. Infrastructure offerings sold as computing capacity rather than software access stay out, which is the line between selling the customer a product to use and renting the customer machinery to run its own: the platform subscription is inside the tax, the racked capacity underneath someone else's stack is not, and the offerings the market brands as infrastructure or platform services will each have to be read against what is actually sold rather than what the sales page calls it. Services whose value primarily reflects human effort performed after the customer's request stay out, and this exclusion will do the heaviest work, because nearly every software invoice carries service lines: implementation, integration, training, managed services, support, custom analysis. A charge whose value is the hours of the people performing it is not a charge for software, but a service label on an access fee will not move the fee, and the primary-value test invites exactly the primary-function scrutiny New York has run against SaaS invoices for years. Sales for use outside California stay out, which folds the exclusion analysis into the sourcing analysis below.
California has policed a boundary like this before. The advertising-art regulation spent decades separating nontaxable conceptual services from taxable finished art, and its lesson, developed at length in this library's design-services article, transfers whole: the invoice is the unit of audit, separately stated charges keep their own character, bundled charges take the character an examiner assigns them, and the records that win are the contracts and line items written before anyone was examined. A seller with California subscription revenue should be mapping every product and invoice line to a statutory category now, in a standing taxability memo, so that the January 1 switch flips collection on a catalog that has already been sorted.
Sourcing, the ninety-day presumption, and the five million dollar shift
For a product nobody ships, the statute has to say where the sale happens, and it does so through a hierarchy of the purchaser's known addresses: the sale is sourced against the addresses the seller has for the purchaser, worked in order, ending at a purchaser address in California. The design is familiar from income-tax market sourcing and from New York's user-location rule, and it carries the same operational lesson this library's New York SaaS article develops in detail: the billing address is data the seller happens to have, not the answer, and the seller who captures use location at the point of sale, on the order form, as a term of the contract, builds its sourcing file at the moment the information is cheap. The statute adds a presumption with real audit consequences: a digital product purchased outside California and used in the state within ninety days is presumed a California use, which converts the where-was-it-bought planning of the tangible era into a documentation question about where use actually began. Purchasers with mobile workforces and multistate seats should expect the presumption to be the examiner's opening position and should hold the seat and usage records that answer it.
The largest buyers change roles entirely. Once a purchaser's digital-product purchases from a single retailer exceed five million dollars in a year, collection shifts to the purchaser, which self-assesses under a direct payment mechanism instead of paying tax to the seller. Enterprise sellers need to know which accounts cross the threshold, because collecting from a direct-pay purchaser is collecting tax that was not due from that party, and enterprise purchasers need the accrual infrastructure, the use-tax account, the allocation method, the reconciliation, that self-assessment assumes. Exemption certificates under the new statute carry conditions, and the certificate file deserves the same discipline as a resale-certificate file: taken in good faith, complete on their face, retained against the audit that will ask for them. On rates, a taxable California sale bears the destination's combined state, local, and district rate, an address-level lookup rather than a single statewide number; how district taxes apply to remotely accessed software is among the questions the emergency regulations should be expected to address, and it belongs on the assumptions list until they do.
The era boundary works both ways: refunds behind, exposure ahead
The transition planning writes itself from the operative date, but only if both directions are worked. Forward: contracts that span January 1, 2027 need tax clauses that say who bears the new tax and how it is invoiced; subscription billing that straddles the date needs a position on the period the charge covers; renewal pricing needs to decide whether tax is absorbed or added; and registration posture needs review, because a remote seller whose California receipts were nontaxable services yesterday may find its economic-nexus arithmetic transformed when those receipts become taxable sales, the threshold mechanics this library's representative-nexus article covers. Sellers already registered for other product lines have the easier build: taxonomy, sourcing capture, invoice discipline, certificate files.
Backward is where the money already sits. The old rule governs every period through December 31, 2026, and those periods stay open to examination and to refund for years. In the tangible-media era, tax charged on software delivered solely electronically, with nothing tangible passing then or later, was tax on a nontaxable transaction, and the pattern was common: sellers collected on the whole invoice because collecting was safer than sorting, purchasers paid because the line item looked official, and accrual systems self-assessed use tax on downloads no statute reached. Every dollar of it is the excess-collection problem this library's companion article works through, with obligations on the seller who collected it and a refund lane for the purchaser who bore it, and the four-year clock disposes of a claim year at a time. The same file supports both eras: the inventory of what was sold, how it was delivered, and where it was used answers the 2027 collection question prospectively and the pre-2027 overpayment question retrospectively, which is why the two analyses belong in one engagement rather than two.
G&G's founder represented software sellers and their customers in California sales and use tax examinations throughout the tangible-media era; the delivery-and-documentation disciplines described here are drawn from that practice.
What the statute leaves open, and where the tensions will run
A statute that draws this many lines leaves work for the regulations, and each open item below has interests pulling in both directions. The capacity-versus-access boundary first: real cloud offerings bundle computing capacity with software tooling in a single subscription, the statute taxes the access and excludes the capacity, and how a bundled offering is characterized, or must be unbundled, is the exclusion question with the most revenue riding on it. The human-effort test next: value that primarily reflects human effort will have to be measured somehow, by price, by cost, or by what the customer principally receives, and every managed-service, analytics, and support offering sits on the answer, because a test stated as a principle becomes an allocation fight on an invoice. Multi-user allocation: the sourcing hierarchy runs on the purchaser's known addresses, and the statute does not say on its face how a single subscription used by seats inside and outside California is divided, the question New York answers with user-location allocation; whether the regulations adopt something comparable decides whether the address hierarchy is a starting proxy or the entire answer, and enterprise sellers and purchasers should care about that one more than any other. The edges of the excluded categories: video games and digital assets are outside the statute, and the purchases made inside a game, or the software functions wrapped around an excluded digital work, will test exactly where outside ends. And the local question: for a product that never ships from anywhere to anywhere, which local jurisdiction's rate applies and which jurisdiction receives the local share is a question the address hierarchy raises rather than settles, and the history of local-allocation disputes over e-commerce suggests it will not settle quietly. The emergency regulations are expected to reach most of this list; the first audit cycle will reach whatever they leave.
Practice notes
The screening questions for a seller of software or software services into California: which invoice lines are prewritten software in any of the three delivery forms, which are custom, which are services whose value is human effort, and which are capacity rather than access, memorialized in a taxability memo before January 1; what the order-to-cash system knows about purchaser use location, and what the order form must start asking; which accounts approach the five million dollar single-retailer threshold; and what the contract says about tax on charges that span the operative date. The screening questions for a California purchaser run the other way: which vendors will begin charging tax and on what base, whether any relationship crosses the direct-pay threshold and what self-assessment will require, how the ninety-day use presumption reads against the company's actual deployment of things bought elsewhere, and whether the accounts-payable file shows California tax paid on electronic deliveries in open pre-2027 periods, because that review is a refund claim waiting to be quantified. On both sides, the emergency regulations are the next event: positions taken before they issue are assumptions, the assumptions belong on a calendar, and the live version of this statute, through the regulations and into the first audit cycle, sits on this site's Watchlist while the framework above stays put.
This article states the law as of September 17, 2026
Statutes, rates, thresholds, and agency practice change, and a different set of facts can change the answer. Before acting on anything discussed above, contact G&G State Tax Group to confirm what has changed since this was written and how the rules apply to a specific situation.
G&G State Tax Group, LLC is a state and local tax advisory firm. The firm provides state and local tax consulting and representation in state and local tax controversies. G&G does not prepare or file tax returns, perform attest services, or provide bookkeeping, and is not a CPA firm.