California Senate Bill 122 (SB 122) is a legislative measure that expands the state’s sales and use tax to include Software as a Service (SaaS) and prewritten computer software. Starting January 1, 2027, SB 122 applies a 7.25% tax to digital products transferred electronically or accessed remotely, including standard enterprise software platforms used by government agencies. This law creates a significant structural cost increase for public sector procurement teams, as understanding how California SB 122 impacts government software budgets is now essential for every agency, as most software transactions with a California nexus will now require additional budget allocation.
Key Takeaways
- California SB 122 mandates a 7.25% sales tax on SaaS and prewritten software starting January 2027.
- Public sector agencies face significant cost increases because the law lacks a government-specific tax exemption.
- Large-scale software purchases exceeding $5 million require the agency to self-assess and remit use tax.
- Procurement teams must audit existing software contracts to identify tax pass-through clauses before renewal dates.
- Updating Total Cost of Ownership models is critical to account for new, non-negotiable tax liabilities.
How California SB 122 Redefines Taxable Software for Public Sector Agencies
For decades, California treated cloud-based software and SaaS the same way it treated other electronic deliverables: not taxable.
SB 122 redefines “tangible personal property” under California’s Revenue and Taxation Code to include digital products, which the law defines as prewritten computer software transferred on tangible storage media, transferred electronically, or accessed remotely. In plain terms: if it’s a standard software platform delivered over the internet, it’s now taxable regardless of delivery method.
The law was enacted as part of California’s 2026–27 budget package. The state projects the expansion will contribute approximately $900 million to the general fund and generate roughly $1.1 billion in local sales tax revenue annually.
What makes this particularly significant for public sector procurement is the absence of a government carve-out. Unlike some state tax provisions that exempt governmental purchases, SB 122 applies broadly to retail sales of prewritten software. A few specific categories do remain exempt — custom software built for a single customer, digital books, video content, and audio works — but the standard enterprise SaaS platforms that government agencies rely on for budgeting, procurement, payments, permitting, and grants management are firmly within the scope of this law.
This tax expansion compounds the rising costs that procurement professionals identify as their primary challenge. In Euna’s 2026 State of Public Procurement survey, rising costs ranked as the number one pain point for procurement teams for the third consecutive year. SB 122 is a structural cost increase arriving on a fixed date, and the planning window before that date is short.
Calculating the Financial Impact of SB 122 on Government Technology Budgets
California’s base sales and use tax rate is 7.25%. Local district taxes vary by purchaser location and can push the effective rate higher. For planning purposes, the state rate alone is enough to make the picture clear:
- A $500,000 software contract that was previously tax-free carries more than $36,000 in additional liability starting in 2027.
- A $2 million enterprise implementation could trigger well over $150,000 in added costs.
- Agencies in higher-rate districts will pay more on top of that.
SB 122 includes a self-assessment provision for taxable software purchases exceeding $5 million annually. For these large-scale transactions, the obligation to report and remit use tax shifts from the vendor to the purchaser. In those cases, the agency itself becomes responsible for calculating and remitting the tax directly to the California Department of Tax and Fee Administration (CDTFA). This puts the burden directly on procurement and finance teams to track and report accurately.
The budget reality is straightforward: technology budgets will buy less software beginning in 2027. And unlike a vendor price increase that can be negotiated, a state tax obligation is fixed.
Strategic Steps for Public Procurement Teams to Prepare for SB 122 Implementation
January 1, 2027 is roughly six months away. That’s not a long runway for agencies managing large software portfolios with multi-year contracts and staggered renewal timelines.
Public procurement teams should immediately inventory active software contracts, including ERP platforms and financial management tools, to assess tax liability. This involves mapping each contract against a few key questions:
When does this contract renew?
Agreements renewing after January 1, 2027 will be subject to the new tax unless the vendor has a separate arrangement. Agreements renewing before that date represent a potential window for locking in current pricing structures.
What does the contract say about tax pass-through?
Many SaaS agreements include language that allows vendors to pass tax obligations to the customer. Reviewing that language now tells you whether the additional cost will appear as a separate line item or as a rate adjustment at renewal.
Is the software prewritten or custom?
The exemption for custom software remains intact under SB 122. If any of your agency’s software was purpose-built for your specific workflows, it may qualify for the exemption. That determination is worth making before you budget for the tax.
Is any portion of use outside California?
There is an exemption for software purchased solely for use outside California or in interstate commerce. However, unlike states such as New York and Texas, California’s law does not include a multistate allocation mechanism, meaning there is currently no clear method for apportioning a subscription across states for agencies with mixed-use scenarios.
Working through these questions systematically is the difference between proactive budget management and a mid-year budget shortfall.
Incorporating SB 122 Sales Tax into Total Cost of Ownership (TCO) for Strategic Sourcing
One of the quieter effects of SB 122 is what it requires of procurement evaluation processes going forward.
For years, public sector agencies could compare software proposals using a relatively clean cost model: licensing or subscription fee, implementation costs, and ongoing support. That model now has a new, non-negotiable line item — California sales tax — and the failure to account for it in the evaluation phase will produce budget projections that are wrong before the ink dries.
Going forward, every software evaluation in California should include the following adjustments to the Total Cost of Ownership (TCO) model:
Gross up the price. Apply the applicable rate (7.25% plus local district taxes for the purchaser’s location) to all prewritten software components of a proposal. This includes the core subscription, any bundled add-on modules, and SaaS-delivered implementation tools.
Separate taxable from exempt components. Implementation services that primarily involve human effort performed after the customer requests them may be exempt. Asking vendors to break out service fees from software subscription fees creates both pricing clarity and potential tax savings.
Identify self-assessment thresholds early. For large-scale implementations approaching or exceeding $5 million in software spend, agencies should be coordinating with their finance and legal teams now on how to structure use tax reporting and whether a direct payment permit is needed.
Build tax into multi-year projections. Multi-year contract comparisons should reflect the compounding effect of tax liability across the full term. A vendor offering a lower base subscription rate but with a larger software scope may carry a higher TCO once tax is included.
The Bottom Line: Why Proactive Compliance with SB 122 is Essential for Government Budget Integrity
In the 2026 State of Public Procurement survey of over 100 public sector procurement professionals, rising costs ranked first among procurement challenges for the third year running. That finding reflects a reality most procurement professionals already know from daily experience: the gap between what technology budgets can fund and what agencies need to operate is already tight. SB 122 narrows that gap further, on a mandatory timeline, without any negotiating leverage on the rate itself.
What procurement teams can control is everything that comes before the tax hits. That means auditing the contract portfolio now, flagging renewals that fall in the wrong window, reviewing vendor agreements for tax pass-through language, and updating TCO models to reflect the new cost reality before the next round of sourcing decisions begins.
If rising software costs are already stretching your procurement budget, it’s worth taking a closer look at where you can find stronger return on investment across your technology stack. Euna Procurement is built specifically for public sector organizations navigating exactly this kind of pressure, giving teams the visibility, compliance tools, and strategic capabilities to do more with constrained budgets. Whether you’re evaluating your current vendor landscape or planning for what 2027 looks like financially, we can help you build a procurement operation that holds up under scrutiny and delivers measurable value.
Frequently Asked Questions
How does California SB 122 impact government software budgets?
California SB 122 impacts government software budgets by imposing a 7.25% sales and use tax on SaaS and prewritten software starting in 2027. Because there is no government exemption, agencies must account for this mandatory cost increase in their procurement planning and Total Cost of Ownership models for all future technology acquisitions.
What software purchases are subject to the new California tax?
The tax applies to prewritten computer software transferred electronically or accessed remotely, including standard enterprise SaaS platforms used by government agencies. While custom software built for a specific customer remains exempt, most commercial-off-the-shelf software platforms used for budgeting, procurement, and financial management fall squarely within the scope of this new tax.
Who is responsible for remitting the tax on large software contracts?
For software purchases exceeding $5 million annually, the responsibility for reporting and remitting use tax shifts from the vendor to the purchaser. Agencies must coordinate with their finance and legal teams to ensure accurate calculation and direct payment to the California Department of Tax and Fee Administration for these large-scale transactions.
How can procurement teams prepare for the 2027 tax deadline?
Procurement teams should immediately audit active software contracts to identify renewal dates and tax pass-through language. By reviewing vendor agreements and updating Total Cost of Ownership projections, agencies can proactively manage the financial impact of this tax expansion and avoid unexpected budget shortfalls when the new legislation goes into effect.
