California SaaS sales tax at a glance
State registration and collection triggers
| What triggers a tax collection requirement? |
Meeting either condition, whichever happens first:
|
| What revenue counts toward the $500k limit? | Gross sales of tangible personal property (TPP). |
| Does SaaS revenue count toward the $500k limit in 2026? | No. Pure cloud SaaS is not classified as TPP in 2026, so it does not count toward the threshold. Starting January 1, 2027 under SB 122, SaaS sales will count. |
| Lookback calculation window | Current or previous calendar year, not a rolling 12-month window. |
| Are marketplace sales included? | Yes. Sales made through marketplace facilitators such as Amazon, eBay, Etsy, or Walmart count toward the $500,000 calculation. |
| SST state? | No. California is not a Streamlined Sales Tax member state, so you register and file directly with the state. |
| Primary data sources | Official CDTFA portal and the Streamlined Sales Tax Governing Board. |
Which types of software does California tax?
California taxes software based on how the customer takes delivery, not on what the product is called.
| What you sell | Taxable in California today | From January 1, 2027 |
|---|---|---|
| SaaS, accessed remotely, no download | No | Yes |
| Prewritten software, downloaded | No | Yes |
| Prewritten software on physical media | Yes | Yes |
| Custom software written for one customer | No | No, remains exempt |
| Specified digital products: e-books, audio, video | No | No, excluded |
| SaaS bundled with tangible goods | Split the bundle. Tangible line items are taxable; software follows its own rule. | Split the bundle. If the invoice does not separate the items, the whole charge is exposed. |
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.
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.
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: call a real-time sales tax API, or build and maintain an internal rate engine.
Option 1: Use the Ziptax Sales Tax API
You send the buyer’s rooftop address at checkout, and the API evaluates the exact boundary lines. Ziptax manages 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"
For complete payload structures, review the Ziptax API documentation.
Do three things with the response: multiply by the combined rate instead of assembling it from components; store the jurisdiction on the transaction because rebuilding it later from an address is lossy; and store the effective date so you can answer questions about a past period.
If your catalog handles SaaS, digital goods, or bundles, pass a product taxability code to check product rules dynamically. The Taxability Information Codes documentation explains 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, filings, and remittance, Ziptax Merchant Tools can connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.
Option 2: Build and maintain it yourself
This is a real choice if you already hold jurisdiction data for other reasons. The work has four parts: source rate data for every California jurisdiction, resolve each customer address to the applicable jurisdictions, refresh both on a cadence, and keep a dated history so a past transaction still returns the answer it originally received.
If you take this route, California needs four things handled:
- Address-level rate resolution. The 7.25% to 11.25% spread is real, and it does not follow ZIP boundaries.
- A product-taxability decision separate from rate lookup. In 2026, SaaS is exempt, so the rate is not yet the operative question. In 2027, it becomes one.
- Threshold accumulation on the right basis. Use the current or previous calendar year, include marketplace sales, and apply the TPP basis. Pure SaaS revenue does not accumulate toward the threshold in 2026, but it does from January 1, 2027.
- An effective date on every rule. California is the clearest example of why one current value per state is not enough.
Five things to watch out for:
- ZIP-based shortcuts. A single ZIP can cross city boundaries and special-district lines. Most of ZIP code 95821 sits in unincorporated territory at 7.75%, while some streets bleed into Sacramento city limits at 8.75%. Collect the full street-level address or precise coordinates.
- Assuming destination-only sourcing. California uses a hybrid approach: state and local components follow the seller’s location, while district taxes follow the customer’s. The correct rate under the wrong sourcing rule still produces the wrong amount.
- Two sourcing regimes from 2027. SB 122 sources digital products separately from physical goods. Software on tangible media is sourced where the media sits at the time of sale. An in-person sale at a permitted seller location is sourced there. Ordinary electronic delivery and remote access are sourced to the purchaser’s recorded address.
- Rate changes landing mid-period. A stored rate is right until a district changes it; without effective dates, nothing tells you when that happened.
- January 1, 2027 transition rules. A credit note issued in 2027 against a 2026 invoice must keep the 2026 exempt treatment. Tie the rule to the transaction or invoice date, not the payment-processing date.
When does a SaaS business have to collect sales tax in California?
Registration and collection are separate obligations with different triggers. Conflating them is where many engineering implementations go wrong.
Your application and billing stack must track two operational rules:
Rule 1: Monitor your registration triggers (nexus)
You must register to file with the state when either condition is met:
- Physical presence: an employee working in California, an office, inventory held in the state, or leased server capacity.
- Economic threshold: gross sales of tangible personal property delivered to California customers cross $500,000 in the current or previous calendar year. Pure SaaS revenue does not count in 2026; from January 1, 2027, it does.
Rule 2: Apply the correct timeline logic
- In 2026 (exempt SaaS): if you cross the threshold or have physical presence, you must register, but your billing system should calculate $0 in tax and submit zero-dollar returns on schedule.
- In 2027 (taxable SaaS under SB 122): your billing system must calculate, collect, and remit tax on 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, niche ERP, or B2B SaaS platform, you do not need an enterprise compliance suite just to calculate an accurate checkout rate. You need a fast, reliable endpoint.
Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on the core product.
- Rooftop precisionResolve rates across 12,000+ U.S. tax jurisdictions using exact-address and coordinate-based lookups.
- Engineered for platformsEmbed live tax calculations directly into checkouts, API endpoints, and marketplace billing frameworks.
- Frictionless pricingPay for active calculation calls without committing to a heavy enterprise software contract.
- The TaxCloud runwayAdd filing and remittance when transaction volume or sub-merchant needs grow.
Get California SaaS tax rates from an API
Address-level rates for every California jurisdiction, plus the rest of the U.S., Canada, and select global markets. Start free, then scale with usage-based 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 pure SaaS revenue does not count in 2026. If you also sell hardware, physical media, or bundled goods, those sales do count and can push you over. From January 1, 2027, SaaS sales count too.
Registration and taxability are independent tests. Registration turns on nexus; taxability turns on what you sell. Through December 31, 2026, a SaaS company can be required to register, file on schedule, and remit $0 because every sale was exempt.
Does California tax software differently depending on how it is delivered?
Under 2026 rules, delivery dictates taxability. Remotely accessed SaaS and electronically downloaded prewritten software are exempt; prewritten software delivered on physical media is taxable. Starting January 1, 2027 under SB 122, remotely accessed SaaS and downloaded software become taxable, while custom software written for one customer remains exempt.
Can you use a ZIP code to get the California sales tax rate?
Not reliably. County, city, and special-district boundaries are drawn independently of postal ZIP boundaries. Two customers sharing a ZIP code can owe different tax amounts. Resolve rates using a full street-level address or precise coordinates.
When does California start taxing SaaS?
January 1, 2027. Senate Bill 122 expands California sales and use tax to remotely accessed prewritten software. Custom software written for one customer stays exempt, and specified digital products such as e-books, audio, and video remain outside the expansion. Tie the rule to the invoice’s transaction date, not today’s date.
Sources
- 2026 SaaS exemption: California Department of Tax and Fee Administration, Regulation 1502(f)(1)(D) and Publication 109.
- 2027 SaaS tax expansion: California Senate Bill 122, amending Revenue and Taxation Code § 6016 and adding § 6016.1.
- Economic nexus and the $500k threshold: CDTFA Special Notice L-565 and Publication 77.
- Sourcing and district-tax rules: CDTFA Publication 105 and California Revenue and Taxation Code § 7261.
- Marketplace facilitator rules: CDTFA Marketplace Facilitator Act guide and California Revenue and Taxation Code § 6041.
- Address resolution and jurisdiction boundaries: CDTFA Know Your Rate and interactive map.
- Streamlined Sales Tax status: SST Governing Board membership directory.