aerial view of the bay bridge

7 July 2026 • 5 minute read

California expands sales and use tax base to digital products: Key takeaways

Beginning January 1, 2027, California will significantly expand its sales and use tax base to include certain digital products, including Software-as-a-Service (SaaS). This represents a shift in California’s sales tax landscape, which has historically not imposed sales tax on most digital transactions.

The legislation will have immediate implications for vendors and customers of SaaS due to the nature of the sourcing rules – which focus on whether the software is actually used in California – and increased compliance obligations.

In this alert, we discuss key aspects of the sales and use tax base expansion and provide takeaways for companies.

Scope of the expansion

On June 29, 2026, California Governor Gavin Newsom signed Senate Bill (SB) 122 into law. SB 122 expands the definition of “tangible personal property” for California sales and use tax purposes to include “digital products,” which are defined as “prewritten computer software transferred on tangible storage media, transferred electronically, or accessed remotely.”[1]

Under the new law, transfers – including retail sales, leases, or licenses of applicable prewritten software – are subject to both state- and district-level sales and use tax beginning on January 1, 2027.

For SaaS arrangements, the key statutory expansion is the new definition of “accessed remotely,” which broadly covers access for consideration to prewritten computer software residing on a vendor’s (or third party’s) server.

In contrast to the Streamlined Sales and Use Tax Agreement concept of “specified digital products,” California specifically carves out the following items from the definition of “digital product”:

  • Video games, digital books, digital audio works, digital visual works, and digital audio-visual works: A host of specific audio and visual assets are excluded.

  • Cryptocurrency: Digital assets are specifically excluded from the definition of digital product.

  • Custom software: Software developed specifically for a single customer remains outside the scope of the tax.

Sourcing rules

One of the more uncommon aspects of this law is the sourcing provision for electronically transferred or remotely accessed digital products.

For sales of electronically transferred or remotely accessed digital products (other than in-person sales), the transaction is sourced to the purchaser’s known California address using the following hierarchy: purchaser’s billing address, shipping or delivery address, payment-instrument mailing address, and mailing address.

If none of these sourcing rules reveal a California address, the sale is deemed to occur outside of California. This approach offers relative certainty for sellers, but may raise constitutional questions where a purchaser’s address, actual use, and seller nexus do not align.

Purchaser certificates for out-of-state use

SB 122 provides a safe harbor for sellers with respect to out-of-state use. Specifically, sellers are excused from their obligation to collect sales tax if they receive a certificate from the purchaser, certifying that the property is purchased solely for use outside of California or in interstate or foreign commerce.

The California Department of Tax and Fee Administration (CDTFA) is expected to release additional guidance regarding this certificate before the effective date of the new sales tax.

Seller vs. purchaser tax obligation: The $5 million threshold

SB 122 introduces a mechanism that shifts collection and remittance responsibility from the seller to the purchaser when annual gross receipts from sales to a purchaser, other than in-person sales, exceed $5 million in the aggregate in the current calendar year[2]:

  • Below the $5 million threshold: The seller generally remains responsible for sales tax or use tax collection and remittance unless another statutory relief provision applies.

  • Above the $5 million threshold: The remittance obligation shifts from the seller to the purchaser, who becomes liable for use tax once the annual $5 million is exceeded after taking into account related adjustments. The purchaser must then self-assess and pay the use tax directly to the CDTFA after obtaining a use tax direct payment permit from the CDTFA. However, the CDTFA may waive the requirement for the purchaser to remit the use tax and require the seller to continue to collect and remit the sales tax if the CDTFA determines that this is necessary for the efficient administration of the new sales tax on SaaS.

Until additional guidance is published, the new legislation raises several questions, including whether sales to related purchasers are aggregated.

Key takeaways and potential action items

Companies are encouraged to consider how this impacts their businesses from a financial perspective and also prepare to address who will remit the tax so as to avoid unnecessary liability.

Potential action items include:

  • Evaluate tax obligations: Companies selling and buying SaaS can evaluate whether California will assert that they have a tax collection or remittance obligation under the new law.

  • Review Transaction Tax Advisories: Review existing technology transfer agreements and licensing agreements that include a prewritten computer software component and consider who financially bears the responsibility of such transactions.

  • Assess availability of exemptions: Determine exemption eligibility, including for research and development, custom software, video games, digital infrastructure, or other categories.

  • Identify opportunities for out-of-state use certificate: Prepare to issue or receive these certificates where appropriate so that the seller need not collect the sales tax.

  • Implement sourcing procedures: Adopt internal processes consistent with the hierarchical sourcing methodology to ensure accurate and defensible return positions, including confirmation of an accurate billing address.

For more information, please contact the authors.

 

[1] Cal. Rev. & Tax. Code §§ 6016, 6016.1, as amended by SB122 (effective Jan. 1, 2027).

[2] Beginning January 1, 2028, the test looks to the current or preceding calendar year.