# Prepare for California's 2027 software tax changes

Prepare your Stripe Tax configuration for California's software tax changes effective January 1, 2027.

California has enacted [software tax changes](https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB122) that make qualifying electronically delivered software and software-as-a-service (SaaS) subject to sales and use tax beginning January 1, 2027. Sellers of covered products must prepare for these changes. Use this guide to review your Stripe Tax configuration, and work with your tax advisor to determine how the rules apply to your products and customers.

Stripe Tax will update tax rates and product taxability rules automatically when the California changes take effect. This guide walks you through the settings and customer information you can review now. It also helps you prepare customer information for the Dashboard workflows Stripe plans to provide for customer exemptions, multiple points of use treatments, and buyer direct payment.

The California-specific capabilities described in this guide aren’t available yet. You can prepare your existing configuration, test in a sandbox, and request access to the existing location-based exemptions private preview through your Stripe sales or account team.

This guide provides general information and isn’t legal or tax advice.

## Before you begin

Before reviewing your configuration, complete these prerequisites:

- [Activate Stripe Tax](https://docs.stripe.com/tax/set-up.md) and make sure you can access your [Tax settings](https://dashboard.stripe.com/settings/tax).
- Identify who maintains product classifications, registrations, customer data, and each integration that creates taxable transactions.
- Work with a tax advisor to determine which products, customers, and transactions the California changes cover.

## Confirm your Stripe Tax settings

Review the settings Stripe Tax uses for your transactions:

1. Open [Tax settings](https://dashboard.stripe.com/settings/tax).
2. Confirm that your **Head office address** is complete and current. Stripe uses it as an input when determining tax treatment.
3. Review the **Preset product tax code**. It applies only when you don’t specify a product tax code explicitly.

## Review affected product tax codes

Use the [product tax code reference](https://docs.stripe.com/tax/tax-codes.md) to match your products to product tax codes (PTCs):

1. Confirm whether you provide downloaded or remotely accessed software, and whether you sell it for personal or business use.
2. Assign the PTC that matches what you sell. We recommend explicit codes for each product. A correct preset code is also appropriate when it accurately classifies products without an explicit code.
3. Create separate products when different uses require different PTCs.
4. Ask your tax advisor to review ambiguous classifications. Don’t select a code only to produce a preferred tax result.

The following table lists the expected PTC taxability updates for the January 1, 2027 law change. This mapping is subject to final implementation guidance. A code’s presence in the reference doesn’t confirm that its future-effective taxability update is available in your testing environment.

| Product tax code | Name | Expected change effective January 1, 2027 |
| --- | --- | --- |
| `txcd_10103000` | Software as a service (SaaS) - personal use | Becomes taxable |
| `txcd_10103001` | Software as a service (SaaS) - business use | Becomes taxable |
| `txcd_10103100` | Software as a service (SaaS) - electronic download - personal use | Becomes taxable |
| `txcd_10103101` | Software as a service (SaaS) - electronic download - business use | Becomes taxable |
| `txcd_10202000` | Downloadable Software - personal use | Becomes taxable |
| `txcd_10202001` | Downloadable Software - non-recreational - personal use | Becomes taxable |
| `txcd_10202003` | Downloadable Software - business use | Becomes taxable |
| `txcd_10105001` | Artificial Intelligence as a Service (AIaaS) - Cloud Based - Personal Use | Becomes taxable |
| `txcd_10105002` | Artificial Intelligence as a Service (AIaaS) - Cloud Based - Business Use | Becomes taxable |
| `txcd_10105003` | Artificial Intelligence as a Service (AIaaS) - Cloud Based & Downloaded - Personal Use | Becomes taxable |
| `txcd_10105004` | Artificial Intelligence as a Service (AIaaS) - Cloud Based & Downloaded - Business Use | Becomes taxable |
| `txcd_10504003` | Electronic software documentation or user manuals - Prewritten, electronic delivery | Becomes taxable |
| `txcd_10702000` | Online Dating Services | Becomes taxable |
| `txcd_10701400` | Website Information Services - Business Use | Becomes taxable |
| `txcd_10701401` | Website Information Services - Personal Use | Becomes taxable |
| `txcd_20060158` | On demand Online Courses - pre-recorded audio or audio visual content (streamed) | Becomes taxable |
| `txcd_20060258` | On demand Online Courses - pre-recorded audio or audio visual content (streamed and downloadable) | Becomes taxable |
| `txcd_20060358` | On demand Online Courses - written material content (viewable or viewable and downloadable) | Becomes taxable |
| `txcd_20120002` | SaaS Implementation and Setup Services - Mandatory | Becomes taxable |
| `txcd_37071001` | Software Maintenance Agreement - Optional, Prewritten, Electronic Delivery, Updates Only | Becomes taxable |
| `txcd_37071002` | Software Maintenance Agreement - Optional, Prewritten, Electronic Delivery, Updates and Services | Becomes taxable |
| `txcd_37071101` | Software Maintenance Agreement - Mandatory, Prewritten, Electronic Delivery | Becomes taxable |

### Test the PTC taxability changes 

Use a sandbox to test the California taxability changes for the PTCs in the table. Follow [Testing Stripe Tax](https://docs.stripe.com/tax/testing.md) to configure your test environment. Rules can change before January 1, 2027, including changes by the applicable tax authority.

1. Configure your sandbox’s Stripe Tax settings and add a California registration effective by the simulated transaction date. Live-mode settings and registrations don’t automatically configure your sandbox.
2. [Create a simulation](https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage.md#create-clock) with its frozen time set to January 1, 2027.
3. [Create a new customer inside the simulation](https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage.md#setup-simulation) and provide a complete California address. For API setup, associate the customer with the simulation’s test clock.
4. Use a sandbox product with an affected PTC and a valid price with the intended tax behavior. Create a subscription or standalone invoice for that clock-associated customer and enable automatic tax.
5. Inspect the invoice generated by the subscription, or the standalone invoice, and finalize it if it’s still a draft. Finalize the invoice, not the subscription. If you’re testing payment collection, pay the invoice using a test payment method.
6. Check the invoice’s calculated tax. Separately, verify the successful test payment and recorded tax transaction when applicable. Calculated tax doesn’t by itself mean payment was collected.

If tax is zero, review [Zero tax amounts](https://docs.stripe.com/tax/zero-tax.md), including registration, location, and product taxability. These simulations test PTC taxability, not customer exemptions, MPU allocations, purchase tracking, or automatic changes to buyer direct payment.

## Review price tax behavior

Confirm how each affected price presents tax to your customer:

- **Exclusive**: Stripe adds tax to the price, increasing the customer’s total when tax applies.
- **Inclusive**: Tax is included in the existing total. When tax applies, the amount you receive excluding tax decreases instead of the customer’s total increasing.
- **Unspecified**: Your default tax behavior can apply where the price doesn’t define one. Review that default in **Tax settings**.

After you explicitly set `tax_behavior` to `inclusive` or `exclusive` on a `Price`, you can’t change it. If you need different behavior, create a replacement price and update the relevant integration, subscription, or payment link to use it. See [Specify product tax codes and tax behavior](https://docs.stripe.com/tax/products-prices-tax-codes-tax-behavior.md).

## Review your California registration

Review [Stripe Tax obligation monitoring](https://docs.stripe.com/tax/monitoring.md) and your California sales records with your tax advisor. A monitoring alert doesn’t determine your legal obligation. Review the [monitoring exceptions and assumptions](https://docs.stripe.com/tax/monitoring.md#exceptions-and-assumptions).

Choose the registration path that applies to your business:

- **Already registered and collecting in Stripe Tax**: Review your existing California registration in [Tax locations](https://dashboard.stripe.com/tax/locations). Don’t add a duplicate or move its start date to January 1, 2027 solely because software taxability changes.
- **Registering directly with CDTFA**: After you legally register with the California Department of Tax and Fee Administration (CDTFA), add your registration to Stripe Tax using the steps in this section.
- **Registering through Stripe**: If eligible, [ask Stripe to register for you](https://docs.stripe.com/tax/use-stripe-to-register/united-states.md). The registration appears automatically in the Dashboard. Review its status and effective date instead of adding it manually.

If you registered directly with CDTFA:

1. Open [Tax locations](https://dashboard.stripe.com/tax/locations) and click **+Add registration**.
2. Select California, choose **I’ve already registered**, provide the requested information, and click **Continue**.
3. Select **Start collecting immediately** if your registration is already active. Otherwise, select **Schedule tax collection** and enter your registration’s future effective date.
4. Confirm the tax rates and click **Start collecting**.
5. Confirm that the registration is active or scheduled for the intended date.

Don’t collect tax in live mode before you’re legally registered. This restriction doesn’t prevent you from adding a sandbox registration for testing. See [Register for sales tax, VAT, and GST](https://docs.stripe.com/tax/registering.md) for the complete workflow.

## Complete customer location data

Provide complete, accurate customer addresses, including the street address, city, state, postal code, and country for US customers. Review the [address hierarchy for your integration](https://docs.stripe.com/tax/customer-locations.md#address-hierarchy). Stripe Tax generally prioritizes shipping over billing for invoices and subscriptions. Checkout and Payment Links use addresses available during the session.

You don’t need hierarchy customization if your integration already provides a complete, accurate billing address for tax calculation and doesn’t use a competing shipping address.

If your integration needs California billing-first address customization, contact your Stripe sales or account team to request testing access. Stripe configures the preference for your account. You don’t need additional Dashboard settings or API parameters.

Before requesting the preference, review these limits:

- The preference depends on the billing address resolving to California. A California shipping address alone won’t trigger it.
- The preference will apply regardless of PTC. It won’t be limited to covered software and could affect other products.
- Checkout can only choose between addresses available for tax calculation. Collecting shipping doesn’t guarantee that a separate billing address is available.
- With explicit Tax Calculations API `customer_details`, you supply a single address and its source. Stripe doesn’t choose between separate billing and shipping addresses in that request.

## Prepare to manage customer exemptions

Prepare customer information for buyer direct payment, legacy-contract exemptions, and multiple points of use (MPU) allocations. Stripe will provide Dashboard workflows for all Stripe Tax users to enter and manage this information. Contact your Stripe sales or account team to discuss early API access.

To prepare now, you can request access to the existing location-based exemptions private preview through your Stripe sales or account team. You can explore its Dashboard workflow and API before the California-specific capabilities become available.

For each customer, work with your tax advisor to determine which treatment applies. Gather the `Customer` ID, applicable dates, and required documentation. For an optional exemption certificate upload, prepare a single file for the planned Dashboard workflow. You must still retain legally required documentation, and an upload alone doesn’t establish eligibility or validate a certificate.

### Buyer direct payment

California’s buyer direct-payment rule can shift responsibility for reporting and paying tax to an eligible buyer after covered purchases from one seller exceed 5 million USD. It isn’t a tax exemption: applicable tax remains due, and the buyer pays it directly.

Identify customers with a qualifying direct payment permit and gather their `Customer` IDs and applicable dates. Stripe will provide a Dashboard workflow to record this treatment for California’s covered software categories. Work with your tax advisor to determine permit eligibility, certificates, measurement periods, and waivers.

Review your purchase records and identify off-Stripe purchases and duplicate `Customer` records for the same buyer. Stripe plans to provide purchase tracking for supported Stripe Tax integrations and monthly notifications about customers approaching or exceeding the threshold. Tracking will count purchases separately for each business–`Customer` pair, without combining off-Stripe purchases or multiple `Customer` records. Confirm integration coverage, including any Connect use, with your Stripe sales or account team, and plan how to reconcile these totals with your own records.

Decide with your advisor whether to manage buyer direct payment yourself or request access to the separate private preview for automatically applying buyer direct-payment treatment. Managing a customer’s treatment in the Dashboard won’t enable that preview. Contact your Stripe sales or account team to discuss access, supported integrations, and timing. Don’t rely on the preview to stop collection on the exact transaction that crosses the threshold.

### Legacy contracts

Identify purchases that qualify for legacy-contract treatment and prepare the customer IDs and exemption start and end dates. Stripe will provide a Dashboard workflow to enter these details for exemptions scoped to California’s covered software categories.

You and your tax advisor determine which purchases qualify. A contract signed before January 1, 2027 doesn’t automatically qualify for an exemption.

### Multiple points of use

For customers using covered software both inside and outside California, prepare each customer’s California usage percentage and applicable dates. Stripe will provide a Dashboard workflow to enter one percentage for the customer’s covered purchases during that period, instead of separate allocations per invoice or line item.

Work with your advisor to determine the allocation and handle obligations outside California. Stripe Tax will calculate California tax on the California share, but won’t calculate other states’ taxes on the remainder.

## Enable automatic tax in every sales flow

Review each integration and existing reusable object, even if automatic tax is already enabled for some sales:

1. For API-created Checkout Sessions, invoices, subscriptions, and Payment Links, set `automatic_tax[enabled]=true` on the applicable creation request. For Dashboard-created transactions, enable automatic tax calculation in that workflow.
2. [Update existing subscriptions](https://docs.stripe.com/tax/subscriptions/update.md) that don’t use automatic tax. If you replaced prices to change tax behavior, update the relevant subscriptions to use the replacement prices.
3. [Update existing payment links](https://docs.stripe.com/tax/payment-links.md) to enable automatic tax and use the intended prices. Enabling tax on new creation requests doesn’t update existing subscriptions or reusable payment links.
4. For a custom `PaymentIntent` integration, follow [Stripe Tax with PaymentIntents](https://docs.stripe.com/tax/payment-intent.md) to calculate tax, collect payment, and record transactions and refunds. Don’t add `automatic_tax` to a `PaymentIntent` request.

See [Set up Stripe Tax](https://docs.stripe.com/tax/set-up.md) for detailed instructions for your integration.

## Official sources

The law establishes the January 1, 2027 tax expansion. Draft regulations address implementation details and can change before they’re finalized. Consult these sources and your tax advisor for guidance on your business:

- [California SB 122](https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB122)
- [CDTFA discussion paper and proposed regulations](https://cdtfa.ca.gov/taxes-and-fees/DigitalProducts-Combined.pdf)
