California SB 122 and Your Billing Stack: The Operational Action Guide

California SaaS companies have less time than they might think.

SB 122 was signed into law on June 29, 2026, and its digital product provisions become operative January 1, 2027. The law expands California's definition of taxable tangible personal property to include qualifying digital products, including prewritten computer software transferred electronically or accessed remotely. For SaaS businesses that have historically treated many California subscriptions as outside the sales tax base, that changes the billing equation.

And the challenge is not simply deciding whether to charge tax.

Finance and operations teams now have to translate the law into product rules, customer data requirements, contracts, exemption procedures, billing configurations, tax registration, and sourcing logic. The California Department of Tax and Fee Administration (CDTFA) is also developing emergency regulations to implement SB 122, with draft regulations currently under discussion.

In other words, January 1 is a tax deadline. For your billing stack, it is a systems deadline.

What does SB 122 mean for a SaaS billing operation?

The starting point is understanding what has changed.

SB 122 defines a digital product to include prewritten computer software that is transferred on tangible storage media, transferred electronically, or accessed remotely. "Accessed remotely" includes access, for consideration, to prewritten software residing on the vendor's server or a third-party server. That brings many SaaS arrangements directly into the new framework.

At the same time, the law contains important exclusions and exemptions. Custom computer software remains outside the definition of taxable digital products, while certain digitally delivered services involving primarily human effort can qualify for an exemption. The law also excludes categories such as digital books, digital audio works, digital audiovisual works, digital visual works, digital video game products, digital assets, and digital infrastructure from its definition of digital product.

That means your first operational task is not "turn on California sales tax." It is to classify what you actually sell.

Which products and services should your team review first?

Pull your complete California-facing product catalog and identify every revenue stream that could fall within the new definition.

That should include:

‍

This exercise should produce a taxability matrix that your billing system can actually use, rather than a policy document that sits with the tax team.

That distinction matters. If your product catalog says one thing and your billing system applies another tax treatment, SB 122 compliance will break at the transaction level.

Does your contract language need to change?

Possibly, and this is where finance, tax, legal, and sales operations need to work together.

Review customer agreements, order forms, pricing pages, and renewal templates for language around taxes. California rules already recognize that whether a retailer can add sales tax reimbursement depends on the terms of the agreement of sale.

For SaaS businesses moving into California sales tax collection, review whether contracts:

• Address sales tax and applicable tax reimbursement
• Define whether prices are tax-inclusive or tax-exclusive
• Allocate responsibility for taxes appropriately
• Address customer-provided exemption documentation
• Handle multi-year subscriptions and renewals consistently

The objective is not to add generic "plus applicable taxes" language and move on. Your commercial terms should align with how your billing system will actually calculate and present tax.

How should exemption certificate procedures change?

A new taxable product category also means more customers may ask for exemptions.

Your exemption process should be ready before January, not built around the first customer who sends your tax team a certificate.

California's new law specifically provides an exemption for certain digital products purchased solely for use outside California or in interstate or foreign commerce. The seller generally carries the burden of proving that the exemption applies unless it obtains the appropriate certificate from the purchaser in the form and manner prescribed by the CDTFA.

Your workflow should therefore answer:

Who can claim an exemption? What documentation is required? Where is it stored? How is it validated? Which transactions does it apply to?

Those answers need to make their way into the billing and customer master data process.

Does your company need to register with the CDTFA?

If your newly taxable California sales create an obligation to collect California sales or use tax, registration needs to be part of the implementation plan.

The CDTFA states that businesses required to collect California sales tax generally need a seller's permit, while out-of-state retailers engaged in business in California must register and collect California use tax on applicable sales.

Do not leave registration until December. Determine your obligation, gather the required business information, and establish the accounts and filing processes your finance team will need.

How should your billing system handle California district taxes?

This may be the most technically important part of the project.

California does not operate with one single sales tax rate. The applicable rate can include the statewide rate, local tax, and district taxes. The CDTFA provides address-based rate lookup tools, and SB 122 specifically applies its sourcing rules to local and district taxes for qualifying digital products.

For remote SaaS transactions, SB 122 generally looks to the purchaser's known California address maintained by the seller in the ordinary course of business. Where multiple California addresses exist, the law establishes a priority that includes billing address, shipping or delivery address, payment instrument address, and mailing address.

Your billing stack therefore needs more than a California yes/no tax flag.

It needs reliable customer address data, jurisdiction determination, effective-dated tax rates, and the ability to apply the appropriate state and district tax to each transaction.

What should your SB 122 implementation plan look like?

A practical implementation can be organized into five workstreams:

‍

The important point is that these workstreams cannot operate independently.

A product classification decision affects billing. Billing depends on customer data. Customer data affects sourcing and exemptions. Registration affects reporting. And all of it ultimately flows into the sales tax return.

What should SaaS companies do now?

Start with the transaction, not the statute.

Take a representative sample of your California invoices and trace each one through the entire stack: product classification, customer location, exemption status, tax calculation, invoice presentation, general ledger posting, and eventual sales tax reporting.

Then ask a simple question:

If this transaction occurred on January 1, 2027, would our systems calculate and document the right California sales tax without someone manually intervening?

If the answer is no, you have identified your implementation backlog.

The CDTFA's work is still evolving. As of September 2026, the agency is actively working through proposed emergency regulations covering digital products, including rules addressing digital product taxability, custom software, tax liability thresholds, multiple points of use, and purchases solely for use outside California. The agency has also said that some questions will require continued clarification through an industry guide and future rulemaking.

That makes early preparation even more important. Your systems should be designed around the enacted law while remaining flexible enough to accommodate final administrative guidance.

SB 122 is a tax change. Your response needs to be operational.

The companies that wait until December to address California SaaS sales tax will be trying to solve tax policy, contracts, customer data, exemption management, registration, billing configuration, and reporting at the same time.

A better approach is to work backward from the January 1 transaction.

Classify the product. Validate the customer. Determine the jurisdiction. Apply the right tax. Document the decision. Feed the result into reporting.

That is what turning SB 122 into an operationally ready sales tax process looks like.

Ready to make your California sales tax implementation easier? CereTax helps SaaS and technology companies automate sales tax calculation, product taxability, exemption management, jurisdiction sourcing, and compliance across complex transaction environments.

👉🏻 Book a Strategy Call with CereTax to evaluate your billing stack and prepare for California's January 1, 2027 sales tax changes.

Note: This article reflects SB 122 and CDTFA materials available as of September 14, 2026. CDTFA's digital-products regulations are still in the rulemaking process, so implementation details may continue to evolve.