Is SaaS taxable in California? A developer's guide to 2026 rules and SB 122

California SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does California tax?

California taxes software based on how the customer takes delivery, not on what the product is called. If you're mapping your own catalog against this, review Taxability Information Codes (TICs) to confirm how a given product classifies.

Bundles are where implementations break. Apply taxability per line item, not per order: if a subscription ships a physical component, the tangible portion stays taxable even when the software portion is exempt. For mixed SKUs, search for the correct product code on each line rather than guessing from the bundle as a whole.

How do you charge the correct sales tax rate for SaaS in California?

Under 2026 rules, you do not. Because cloud-delivered SaaS is exempt, the sales tax on a remotely accessed subscription sold to a California customer is $0.

However, that changes on January 1, 2027 under SB 122. If any component of a transaction is considered taxable (such as downloading a hybrid client or shipping a physical token), the entire bundle risks becoming taxable.

When the 2027 rules go live, engineering teams have two options for calculating the correct tax rates: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Use the Ziptax Sales Tax API

You send the buyer's rooftop address at the point of checkout, and the API evaluates the exact boundary lines. The platform manages the jurisdiction tracking, database mapping, and special district reorganizations automatically.

To calculate a live rate against a California address, use the v60 endpoint:

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=350 S Grand Ave, Los Angeles, CA, 90071"

Explore the REST API documentation to verify complete payload structures.

Three things to do with that response. Multiply by the combined rate rather than assembling it from the components. Store the jurisdiction on the transaction, because rebuilding it later from an address is lossy. Store the effective date too, because it is what lets you answer a question about a past period.

If your product catalog handles complex items like SaaS, digital goods, or bundles, you can also pass a product taxability code to dynamically check product rules.

Review the Taxability Information Codes (TICs) documentation to see how the response returns product-specific tax flags and exemptions.

What an API will not tell you: your company's physical presence or economic registration status in California. Tracking whether you have crossed a nexus threshold and must legally register remains on your side of the integration.

To automate threshold tracking, tax filings, and remittance, you can use Ziptax Merchant Tools to connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.

Option 2: Build and maintain it yourself

A real choice if you already hold jurisdiction data for other reasons. The work here is in four parts: source rate data for every California jurisdiction, resolve each customer address to the jurisdictions that apply to it, refresh both on a cadence, and keep a dated history so a past transaction still returns the answer it originally got.

If you take this route, California needs four things handled:

1. Address-level rate resolution. The 7.25% to 11.25% spread is real and it does not follow ZIP boundaries.
2. A product taxability decision separate from the rate lookup. In 2026 the answer for SaaS is exempt, which means the rate is not the operative question yet. In 2027 it becomes one.
3. Threshold accumulation on the right basis. Current or previous calendar year, not rolling. Marketplace sales included. And the tangible personal property basis, which means pure SaaS revenue does not accumulate toward the threshold in 2026 but does from January 1, 2027.
4. An effective date on every rule. California is the clearest case for why a single current value per state is not enough.

Five things to watch out for:

1. ZIP-based shortcuts. A single 5-digit ZIP code can cross multiple city boundaries and special district lines. For example, the majority of ZIP code 95821 sits in unincorporated territory with a sales tax rate of 7.75%, but a few streets bleed directly into Sacramento city limits where the rate jumps to 8.75%. As noted on the official CDTFA Know Your Rate tool, you cannot rely on flat ZIP lookups. To prevent calculation errors, your checkout engine must collect and evaluate the full street-level address or precise geocoded coordinates.
2. Assuming destination-only sourcing. California uses a hybrid approach, where state and local components follow the seller's location and district taxes follow the customer's. A correct rate under the wrong sourcing rule still produces the wrong amount.
3. Two sourcing regimes from 2027. SB 122 sources digital products separately from physical goods. Software on tangible media is sourced to where the media sits at the time of sale. An in-person sale at a seller location with a seller's permit is sourced to that place of business. Everything else, meaning ordinary electronic delivery and remote access, is sourced to the purchaser's address as shown in your records. So from January 1, 2027 a transaction line's sourcing rule depends on what the line is, not just where the customer is.
4. Rate changes landing mid-period. A stored rate is right until a district changes it, and nothing tells you when that happened.
5. January 1, 2027 transition rules. A credit note issued in 2027 against a 2026 invoice has to carry the 2026 exempt treatment. The system rule must be tied to the transaction/invoice date rather than the payment or billing processing date.

When does a SaaS business have to collect sales tax in California?

Registration and collection are two separate obligations with completely different triggers. Conflating them is where most engineering implementations go wrong.

To remain fully compliant, your application and billing stack must track these two operational rules:

Rule 1: Monitor your registration triggers (nexus)

You must legally register to file with the state the moment either of these conditions is met:

• Physical presence: an employee working in California, an office, inventory held in the state, or leased server capacity.
• Economic threshold: your gross sales of tangible personal property delivered to California customers cross $500,000 in the current or previous calendar year. In 2026, pure SaaS revenue does not count toward this figure. From January 1, 2027, it does.

If you're tracking this across multiple states, check economic nexus thresholds rather than assuming California's $500,000 figure applies elsewhere.

Rule 2: Apply the correct timeline logic

• In 2026 (exempt SaaS): If you cross the $500,000 threshold or have physical presence in the state, you must register, but your billing system should calculate tax at $0 and submit zero-dollar returns on schedule.
• In 2027 (taxable SaaS under SB 122): Your billing system must begin calling the Ziptax API at checkout to calculate, collect, and remit tax on all active SaaS subscriptions, using rates resolved from the customer's address under California's sourcing rules.

Where Ziptax helps

If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.

Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.

• Rooftop Precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, eliminating the accuracy liabilities of ZIP-based shortcuts.
• Engineered for Platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
• Frictionless Pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
• The TaxCloud Runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it. Start with set up merchant management once you're ready to onboard a given entity.

Get California SaaS tax rates from an API

Address-level rates for every California jurisdiction, plus the rest of the US, Canada, and select other markets. Free starter plan, then usage-based pricing (view Ziptax pricing).

Frequently asked questions

Do you have to register in California if your SaaS product is exempt there?

Yes, if you cross California's $500,000 threshold. The threshold is measured on gross sales of tangible personal property, so in 2026 pure SaaS revenue does not count toward it. If you also sell anything tangible into California, such as hardware, physical media, or bundled goods, those sales do count and can push you over on their own. From January 1, 2027, SaaS sales count toward the threshold as well.

Registration and taxability are independent tests. Registration turns on whether you have nexus in California, through the threshold above or through physical presence. Taxability turns on what you sell. A software company can be required to register, file returns on schedule, and remit $0 because every sale was exempt. Through December 31, 2026, that is the normal position for a SaaS business in California, not an edge case. For the full registration mechanics beyond California specifically, view collection requirements and nexus.

Does California tax software differently depending on how it is delivered?

Under current 2026 rules, the method of delivery dictates taxability. Software accessed strictly online with no download (SaaS) and prewritten software downloaded electronically are both exempt. Only prewritten software delivered on physical media (like a flash drive or CD) is subject to sales tax. Starting January 1, 2027, under SB 122, this distinction disappears: both remotely accessed SaaS and downloaded software become taxable, while custom software written for a single customer remains explicitly exempt.

Can you use a ZIP code to get the California sales tax rate?

Not reliably. California's county, city, and special district boundaries are drawn independently of postal ZIP boundaries. A single 5-digit ZIP code can cross multiple local jurisdictions with different special district tax rates. Because of this, two customers sharing the same ZIP code can owe different tax amounts. To ensure build accuracy and protect against audit liabilities, your application must resolve tax rates using the full street-level address or precise coordinates.

When does California start taxing SaaS?

January 1, 2027. Under Senate Bill 122, California expands its sales and use tax base to include remotely accessed prewritten software. Custom software written for a single customer stays exempt, and specified digital products such as e-books, audio, and video sit outside the expansion. Because SaaS remains exempt through December 31, 2026, your billing implementation must look at the specific transaction date of the invoice rather than today's date to determine whether to apply the tax.

Browse SaaS Sales Tax by State for the full state-by-state breakdown.

Sources

1. 2026 SaaS Exemption: California Department of Tax and Fee Administration (CDTFA) Regulation 1502(f)(1)(D) (Computer Programs, Processes and Procedures) & CDTFA Publication 109 (Internet Sales). https://cdtfa.ca.gov/lawguides/vol1/sutr/1502.html https://cdtfa.ca.gov/formspubs/pub109/
2. 2027 SaaS Tax Expansion (SB 122): California Senate Bill 122 (Chapter 23, Statutes of 2026), amending Revenue and Taxation Code § 6016 and adding § 6016.1. https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB122
3. Economic Nexus and the $500k Threshold: CDTFA Special Notice L-565 (information update on AB 147, Wayfair implementation), and CDTFA Publication 77, Out-of-State Sellers: Do You Need to Register with California? https://cdtfa.ca.gov/taxes-and-fees/l565.pdf https://cdtfa.ca.gov/formspubs/pub77
4. Sourcing & District Tax Rules: CDTFA Publication 105 (District Taxes and Sales Delivered in California) & California Revenue and Taxation Code § 7261. https://cdtfa.ca.gov/formspubs/pub105/basic-rules.htm
5. Marketplace Facilitator Rules: CDTFA Marketplace Facilitator Act Guide & California Revenue and Taxation Code § 6041. https://cdtfa.ca.gov/industry/MPFAct.htm
6. Address Resolution & Jurisdiction Boundaries ("Know Your Rate"): CDTFA Tax Rate Address Lookup Engine & Interactive Map Tool. https://cdtfa.ca.gov/taxes-and-fees/know-your-rate.htm https://maps.cdtfa.ca.gov/
7. Streamlined Sales Tax (SST) Status: Streamlined Sales Tax Governing Board State Membership Directory. https://www.streamlinedsalestax.org/