For years, many SaaS companies operating in California could approach sales tax with a relatively simple assumption: if software was delivered electronically rather than transferred on physical media, the transaction was generally outside California sales tax.

For a CFO building a financial plan today, that assumption now has an expiration date.

Under California legislation enacted in 2026, the state is significantly changing the treatment of digital products beginning January 1, 2027. California will generally apply sales and use tax to retail sales of digital products, including products transferred electronically and products accessed remotely. The new framework specifically reaches certain remotely accessed software arrangements, making the change particularly important for SaaS companies.

That means California sales tax is no longer simply a compliance question to revisit at year-end. For SaaS businesses selling into California, it is becoming a pricing, billing, systems, forecasting, contracting, cash-management, and potentially valuation issue that finance teams should address before the rules take effect.

The Starting Point: Understand the Current California Position

As of 2026, California generally does not impose sales tax on electronically transmitted software and other qualifying electronic data products when they are delivered entirely over the Internet without tangible media.

That treatment has historically distinguished California from states where SaaS and remotely accessed software may already be taxable under different rules.

This is important because SaaS companies frequently grow nationally before developing a formal indirect-tax function. A company may have thousands of customers across the United States while its finance organization remains relatively lean.

For California, the existing treatment may have reduced the immediate sales-tax burden associated with pure electronically delivered software.

But CFOs should not build long-term financial assumptions around the 2026 treatment.

January 1, 2027 Changes the Planning Conversation

Beginning January 1, 2027, California’s new digital-products framework generally expands sales and use tax to retail sales of digital products sold or purchased for storage, use, or other consumption in California.

The definition is broad enough to cover digital products whether they are transferred through physical media, transferred electronically, or accessed remotely.

For SaaS companies, the remotely accessed category is particularly significant.

The change means finance teams should begin analyzing their revenue streams at the product and contract level rather than asking only whether the company “sells SaaS.”

That distinction matters because SaaS companies frequently sell more than one economic component.

A contract might include access to software, implementation, configuration, professional services, support, training, data products, additional modules, or other services.

The tax treatment of a specific arrangement should be determined based on the applicable California rules and the facts of the transaction rather than applying a single assumption to every invoice.

From a CFO perspective, this creates an immediate requirement: know what the company is actually selling before determining how tax affects the financial model.

Sales Tax Should Enter the Product and Contract Discussion

Finance should not wait until an invoice is generated to determine the financial implications.

Imagine a SaaS company sells an enterprise subscription for $240,000 annually.

Management has historically thought about that contract in terms of ARR, gross margin, commissions, implementation cost, collections, and renewal probability.

If sales tax becomes applicable, another question enters the economics:

Is the tax charged to the customer in addition to the contracted price, or does the company effectively absorb some or all of the economic burden?

That question sounds operational. It can have a material financial impact.

If contracts clearly permit applicable taxes to be charged separately, the customer may bear the tax economically while the company administers collection and remittance.

If pricing, contracting, or billing practices do not properly address tax, the company may face a different economic outcome.

The CFO should therefore involve finance, tax, legal, sales operations, and billing teams before the new treatment becomes operational.

California Is Not One Uniform Rate

Another planning mistake is assuming that “California sales tax” means one percentage applied everywhere.

California’s statewide base sales and use tax rate is currently 7.25%. Local district taxes can increase the total rate depending on location, and multiple district taxes may apply in a particular area.

As of July 2026, for example, total rates vary materially among California jurisdictions.

That has an important implication for SaaS finance infrastructure.

It may not be enough for the billing system to know that a customer is located in California. Depending on the transaction and applicable sourcing rules, the company may need sufficiently reliable customer-location information to determine the appropriate treatment and rate.

For companies processing thousands of subscriptions, this becomes a systems problem as much as a tax problem.

The CFO Should Map Revenue Before Modeling the Impact

Before changing the forecast, finance needs to understand the California revenue base.

A practical analysis begins by segmenting customers and revenue rather than applying an assumed tax percentage to total company ARR.

The CFO should be able to identify California customers, revenue associated with those customers, product types, contract terms, billing frequency, customer addresses, renewal dates, and whether taxes can be separately charged under existing agreements.

From there, management can determine which revenue streams require deeper technical review.

This exercise can reveal risks that are invisible in consolidated financial statements.

For example, two SaaS companies with identical ARR may have very different California exposure if one generates 8% of revenue from California customers and another generates 35%.

Their financial planning requirements should not be identical.

From Tax Analysis to Financial Planning

Once the company understands its revenue profile, the CFO can translate the issue into financial scenarios.

This is where the CFO’s role becomes distinct from the tax advisor’s role.

The tax professional determines how the rules apply.

The CFO determines what those conclusions mean for the company.

Do Not Confuse Tax Collected With Revenue

Once a company begins collecting sales tax, accounting discipline becomes essential.

Amounts collected from customers on behalf of a taxing authority generally should not be treated as operating revenue merely because the cash enters the company’s bank account.

Finance needs appropriate liability accounts and reconciliation procedures so management can distinguish company cash from amounts that ultimately need to be remitted.

This becomes particularly important in SaaS businesses where automated billing systems process large transaction volumes.

If tax calculations, invoices, payment processors, accounting records, and tax filings do not reconcile, differences can accumulate quickly.

A scalable process should allow finance to move from invoice-level tax calculations to the general ledger and ultimately to filed returns and payments with a clear reconciliation trail.

That control becomes more important as transaction volume grows.

Pricing Strategy Deserves Executive Attention

The new environment can also create strategic pricing questions.

Suppose a SaaS company charges $100,000 annually for a product and a customer becomes subject to an applicable sales-tax rate above the statewide base rate because of local district taxes.

If the tax is separately charged, the customer’s total invoice increases.

For a large enterprise customer, that may simply become another procurement cost.

For a price-sensitive SMB customer, the increase could have a different commercial impact.

The CFO and commercial leadership therefore need to determine whether sales teams understand how applicable taxes will appear on quotes, contracts, and invoices.

This does not mean sales tax should dictate pricing strategy.

It means pricing strategy should not be designed as though sales tax does not exist.

Existing Contracts Need a Different Review From New Contracts

Timing creates another challenge.

New contracts can be designed with the future tax environment in mind.

Existing agreements may not be as straightforward.

A company may have annual or multi-year contracts extending beyond January 1, 2027. Some may contain clear tax provisions. Others may have negotiated all-inclusive pricing or customized commercial language.

That makes contract review a useful part of financial preparation.

Finance should work with legal and tax professionals to understand how existing contractual structures interact with the new rules and whether operational changes are required before renewals.

The objective is not to renegotiate every customer contract.

It is to avoid discovering contractual limitations after tax obligations have already arisen.

Enterprise SaaS Companies Need to Understand the $5 Million Customer Threshold

California’s new framework also contains a significant rule involving very large transactions with the same purchaser.

For 2027, where aggregate gross receipts from digital products transferred electronically or accessed remotely to the same purchaser exceed $5 million during the calendar year, specific rules may shift the responsibility for the tax from the retailer to the purchaser under qualifying circumstances.

Beginning in 2028, the framework looks to the current or preceding calendar year, and the threshold is subject to future adjustment.

This will not affect the majority of SaaS customer relationships.

For enterprise software companies with very large customers, however, it should be included in the tax analysis.

The important CFO lesson is that scale can change tax mechanics. A process designed around hundreds of smaller customers may not necessarily apply identically to a multimillion-dollar enterprise relationship.

The Billing System May Become a Finance-Control Issue

As SaaS companies scale, indirect tax increasingly becomes dependent on technology.

The billing environment may need to determine customer location, apply the correct tax logic, generate appropriate invoices, track exemptions where relevant, record liabilities, and preserve information necessary for reporting.

This is particularly important in California because local district taxes can cause rates to vary by location.

A CFO should therefore evaluate the complete transaction flow:

Customer record → contract → billing address → product classification → invoice → tax calculation → payment → accounting → liability reconciliation → filing → remittance.

A weakness anywhere in that chain can create discrepancies downstream.

The goal should be automation with financial control, not automation without oversight.

The Forecast Should Be Updated Before 2027 Begins

Waiting until the first taxable invoice is issued would be poor financial planning.

For a SaaS company with meaningful California revenue, the 2027 operating plan should already consider the new environment.

Management should model at least three potential outcomes.

Scenario 1 – Tax is largely passed through to customers. The principal financial impact may involve systems, administration, compliance costs, customer communication, and cash-flow mechanics.

Scenario 2 – Commercial pressure causes the company to absorb part of the economic impact. Gross margins and pricing assumptions may need adjustment.

Scenario 3 – Product or contract complexity creates mixed treatment. Finance may need more sophisticated revenue segmentation, billing logic, and reconciliation processes.

The purpose of these scenarios is not to predict tax conclusions before the technical analysis is complete.

It is to prevent a material change in the operating environment from being absent from the financial plan.

Multi-State SaaS Companies Need a Broader Perspective

California should also not be analyzed in isolation.

A SaaS company selling nationally may already have sales-tax obligations or registration requirements in other states depending on the applicable rules and its activities.

That means the California change should trigger a broader question:

Has the company’s indirect-tax infrastructure scaled at the same speed as its revenue footprint?

For an early-stage startup, manual processes may have been sufficient.

For a Series B or Series C SaaS company with customers throughout the United States, a fragmented state-by-state process can become difficult to control.

At that stage, finance should understand where the company has customers, where it has employees or other business activity, which products it sells, where it is registered, how tax decisions are documented, and how liabilities reconcile with the general ledger.

This is financial infrastructure, not merely tax administration.

Five Financial Actions SaaS CFOs Should Prioritize

For California planning, the finance roadmap should follow a logical sequence.

1. Quantify California revenue. Determine the proportion of ARR, bookings, and customer concentration associated with California.

2. Classify the revenue model. Separate software access, digital products, implementation, professional services, support, and other material components for technical review.

3. Review customer and contract data. Determine whether billing addresses and other relevant location data are reliable and whether contracts appropriately address taxes.

4. Test billing and accounting infrastructure. Make sure systems can support required calculations, invoicing, liability accounting, reconciliation, and reporting.

5. Incorporate the results into the 2027 plan. Update pricing assumptions, operating costs, cash forecasting, internal responsibilities, and relevant financial scenarios.

This process should happen before the effective date, not after the first filing deadline.

How ERB Proximo Can Support SaaS Companies Through the Transition

A regulatory change of this kind illustrates why a growing SaaS company needs finance leadership that connects technical requirements with business economics.

The tax determination itself is only one part of the work. Management also needs to understand how the conclusion affects contracts, billing operations, accounting, cash forecasting, margins, budgeting, financial reporting, and potentially fundraising assumptions.

ERB Proximo can support that broader financial process.

For a growing SaaS company, the work may begin with accounting and Controller-level infrastructure, then extend into FP&A, management reporting, cash planning, tax coordination, and CFO-level analysis. As the company expands across states, raises additional capital, or prepares for a transaction, the financial model can evolve accordingly.

The objective is not simply to become compliant with another California requirement.

It is to ensure that when the regulatory environment changes, management understands the financial consequences early enough to make informed decisions.

For California SaaS companies, January 1, 2027 should therefore be treated as a planning date – not merely a tax date.

Frequently Asked Questions

1. Is SaaS currently subject to California sales tax in 2026?

Electronically transmitted software and qualifying electronic data products are generally not taxable under California’s current 2026 treatment when transferred entirely electronically and without tangible media. However, transaction-specific facts matter, and companies should obtain professional advice regarding their particular products and arrangements.

2. What changes for California digital products in 2027?

Beginning January 1, 2027, California generally expands sales and use taxation to retail sales of digital products, including products transferred electronically or accessed remotely. The change is particularly important for companies providing remotely accessed software.

3. Does this mean every SaaS invoice will automatically be taxable?

Companies should not make that assumption. The tax treatment depends on the product, transaction structure, customer circumstances, and applicable statutory rules and exceptions. SaaS companies should classify their revenue streams and have the relevant treatment reviewed before configuring billing systems.

4. What is California’s sales tax rate?

California’s statewide sales and use tax rate is currently 7.25%, but local district taxes can increase the total rate. The applicable total rate can therefore vary by location.

5. Why should the CFO be involved if sales tax is primarily a tax issue?

Because the financial consequences extend beyond the return itself. Sales tax can affect pricing, contracts, billing, cash movement, accounting, forecasting, systems, controls, customer experience, and potentially margins. The CFO should coordinate those financial implications while technical tax professionals determine the appropriate treatment.

6. Should sales tax collected from customers be included in SaaS revenue?

Amounts collected as sales tax for remittance generally should be accounted for separately from the company’s operating revenue. Finance should establish appropriate liability accounting and reconciliation procedures.

7. Should existing SaaS contracts be reviewed before January 2027?

For companies with material California revenue, reviewing contracts that extend into 2027 can be prudent. Finance, legal, and tax professionals should understand whether tax provisions, pricing language, customer-location information, and billing arrangements are appropriate for the new environment.

8. How could California sales tax affect SaaS financial forecasts?

The effect depends on whether tax is passed through to customers, absorbed economically through pricing decisions, or varies among products and transactions. Companies may also incur additional technology, compliance, advisory, and administrative costs. Those assumptions should be incorporated into the 2027 financial plan.

9. What should a multi-state SaaS company do beyond reviewing California?

California’s change is a useful reason to review the company’s broader U.S. indirect-tax infrastructure. Finance should understand customer geography, product classification, registration status, billing capabilities, tax liabilities, and reconciliation processes across relevant states.

10. When should SaaS companies begin preparing for the California change?

Companies with meaningful California revenue should begin before January 1, 2027. Product classification, contract review, customer-data validation, billing configuration, accounting design, testing, and financial forecasting can require coordination across several teams. Starting early gives management time to address the change as a planned financial project rather than a compliance emergency.