Is SaaS taxable in California?

What Senate Bill 122 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 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 released proposed emergency regulations for comment on September 1, 2026, which have not been adopted. Until they are, any position taken 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, audiovisual, and visual 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. Digital infrastructure stays out: a cloud service that lets the user create, deploy, scale, or run the user's own software on the provider's platform without maintaining its own hardware, software, and networks (Rev. and Tax. Code section 6016.1). The line runs between using the provider's software, which is taxed, and running the customer's own software on the provider's platform, which is not, and offerings the market brands as infrastructure or platform services will each have to be read against what is sold rather than what the sales page calls it. Services whose value primarily reflects human effort performed after the customer's request stay out through a statutory exemption (section 6372.1) rather than a definitional exclusion, a distinction with audit consequences because exemptions are construed narrowly with the burden on the claimant, and this carve-out 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 the primary-function scrutiny New York has run against SaaS invoices for years. Sales of products purchased solely for use outside California stay out through the exemption of section 6372, which folds the exclusion analysis into the sourcing analysis below, and the right to reproduce or copy a digital product so that copies are distributed for consideration to third parties is exempt under section 6362.4, even when a copy of the product is transferred with the right.

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. For a sale that is not made in person, it does so through a statutory hierarchy of the purchaser's known California addresses in the seller's records maintained in good faith, taken in order: billing address, then shipping or delivery address, then the mailing address of the payment instrument, then the general mailing address (Rev. and Tax. Code section 6010.5, subd. (b)(3)). Unlike New York's user-location rule, which this library's New York SaaS article develops in detail, the billing address is the statute's first answer; use location matters instead to the exemption for products purchased solely for use outside California (section 6372), which a seller supports with the purchaser's certificate, and to any allocation among multiple points of use. The operational lesson follows from that order. The seller's address records are the sourcing file, so the order-to-cash system should hold the billing, shipping, and payment addresses cleanly and keep them current, and the seller who captures use location at the point of sale, on the order form or as a term of the contract, builds its exemption and allocation file at the moment the information is cheap. The statute adds a presumption with audit consequences (section 6010.5.1): a digital product purchased outside California and used in the state within ninety days is presumed purchased for use in California, which converts the where-was-it-bought planning of the tangible era into a documentation question about where use 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. Once a purchaser's electronically delivered or remotely accessed digital-product purchases from a single retailer exceed five million dollars in the current calendar year, or, beginning in 2028, in the current or preceding calendar year, liability shifts to the purchaser, which self-assesses under a use tax direct payment permit instead of paying tax to the seller (Rev. and Tax. Code sections 6052 and 6201.55); the retailer is relieved of the collection obligation from the transaction that crosses the threshold. 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 combined state, local, and district rate at the address the statutory hierarchy selects; the bill applies the same sourcing rule to district taxes (Rev. and Tax. Code section 7254), so the lookup is address-level rather than statewide.

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, for the purchaser who bore it, a recovery that runs through the seller's refund claim where the charge was sales tax reimbursement, and through the purchaser's own claim where the purchaser paid or accrued use tax. For sales tax the retailer is the taxpayer: the retailer claims the refund and must return the excess to its customers or remit it to the state (Rev. and Tax. Code section 6901.5), and the California Supreme Court has held the tax code's procedure exclusive, leaving the customer an action to compel the retailer to seek the refund rather than a claim of its own (Loeffler v. Target Corp. (2014) 58 Cal.4th 1081). Either lane closes on a schedule of its own. Revenue and Taxation Code section 6902 allows a refund claim within three years of the last day of the month following the close of the period for which the overpayment was made, or within six months of the overpayment, whichever expires later. Three years, not the four the income tax side runs on, and the oldest periods drop out of reach one at a time while a review is being scheduled. 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 together rather than in two separate projects.

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 infrastructure boundary first: cloud offerings commonly bundle a platform for running the customer's own software with the provider's own applications in a single subscription, the statute excludes the first and taxes access to the second, 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. The department's proposed emergency regulations would authorize an alternative calculation for digital products available for use in multiple locations, supported by a multiple-points-of-use certificate (proposed Regulation 1600.2), but they are not yet adopted, and until they are, whether the address hierarchy is a starting proxy or the entire answer remains open; 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 where outside ends. And the local reporting mechanics: the rate question is settled, because section 7254 applies the address hierarchy to district taxes and the department's notice on the new tax treats the customer's address as the general place of sale for local and district purposes (Special Notice L-1036), but how the local share is reported and allocated when a seller's address records are incomplete remains for the regulations and for practice. The emergency regulations, once adopted, will reach part of this list; the first audit cycle will reach whatever they leave. As of October 10, 2026, the package is still informal. The department's Business Taxes Committee has posted a September 1, 2026 discussion paper with draft regulations, amendments to Regulations 1502, 1507 and 1699.6 and new Regulations 1502.2, 1600, 1600.1, 1600.2 and 1600.3, took written comments through September 24, 2026, and has filed nothing with the Office of Administrative Law for adoption. Section 34 of the bill deems the adoption an emergency for purposes of the Administrative Procedure Act, so the rules can take effect on filing, but until a filing appears the drafts are draft text and not law. One point in the drafts bears directly on the planning above and is stated here as draft text only. The draft transition rule (proposed Regulation 1600(f)) places the sale at the transfer of the right to access or use the product on or after January 1, 2027, regardless of when the price is paid, so that a license with access delivered in 2026 would be outside the tax however it is paid, while a subscription would be taxed for the periods on and after January 1, 2027. One further point is a reading of the statutes rather than a stated agency position: because the new definitions govern the whole Sales and Use Tax Law (section 6002), a software seller whose representatives, agents, or independent contractors operate in California for the purpose of selling or taking orders will be a retailer engaged in business in this state under section 6203(c)(2) from January 1, 2027, at any sales volume, without regard to the $500,000 threshold of section 6203(c)(4). The bill does not amend section 6203, and the department has published no guidance on the point.

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 infrastructure for running the customer's own software, memorialized in a taxability memo before January 1; whether the order-to-cash system holds each purchaser's billing, shipping, and payment addresses in the form the statutory hierarchy uses, and what the order form must start asking about use location to support out-of-state-use certificates and any multiple-points-of-use allocation; 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 request to the vendor, or a use tax claim of the company's own, waiting to be quantified, and the section 6902 window on the oldest of those periods is running while it waits. On both sides, the emergency regulations are the next event: the department released a proposed package for comment in September 2026, positions taken before it is adopted 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. G&G State Tax Group provides software taxability analysis, SB 122 readiness reviews, and sales and use tax refund and audit representation alongside its state and local tax practice.