Do You Owe Use Tax on the SaaS Your Company Already Buys?
Do You Owe Use Tax on the SaaS Your Company Already Buys?
TL;DR
California SB 122 and Colorado HB 26-1223 both repeal their SaaS and software tax exemptions effective January 1, 2027, making previously exempt purchases taxable.
When a vendor does not charge sales tax on a now-taxable purchase, you owe use tax and must self-assess and remit it directly to the state.
Use tax is your obligation as the buyer, and it sits on your books regardless of what the vendor's invoice shows.
Exposure concentrates in multi-year contracts spanning the effective date, auto-renewing subscriptions, bundled invoices, and purchases invoiced before 2027 but consumed after.
Start now by inventorying SaaS contracts, confirming vendor collection status, and registering for use tax where you are not already registered.
Why Two State Laws Make Use Tax a Finance Team Problem Right Now
California SB 122 and Colorado HB 26-1223 both repeal their SaaS and software tax exemptions on January 1, 2027, and the compliance work that follows lands on your books. When a vendor charges sales tax, the vendor collects and remits it for you. When a vendor does not charge tax on a purchase the state now treats as taxable, that obligation shifts to you as use tax, and you self-assess and remit it directly to the state.
Use tax is the buyer-side mirror of sales tax. The two carry the same rate and cover the same transaction, but the party responsible differs. A vendor outside your state, or one that simply hasn't updated its billing, may hand you an invoice with no tax line at all. That silence is not an exemption. You still owe the tax, and you still have to calculate it, record it, and file it.
The January 2027 date reads as distant, but your contract cycles do not respect it. Annual renewals negotiated in 2026 will run straight through the effective date. Multi-year agreements signed today already span it. Auto-renewing subscriptions cross it without anyone signing anything. Each of those creates use tax that most finance teams have never accrued for software, because software was exempt.
The setup work, meaning registration, accrual entries, and a filing calendar, takes months to stand up cleanly. Starting after the first taxable invoice arrives means reconstructing liability instead of accruing it in real time.
What California and Colorado Changed
Both states repeal their software and SaaS tax exemptions on the same day, but the rate mechanics diverge enough that a buyer operating in both cannot copy one accrual process into the other.
State | Law | Effective Date | What Becomes Taxable | Applicable Rate | Primary Source |
|---|---|---|---|---|---|
California | SB 122 | January 1, 2027 | Prewritten software and SaaS | 7.25%–11.5% (state + district; use CDTFA rate lookup per address) | |
Colorado | HB 26-1223 | January 1, 2027 | Prewritten software and SaaS | State base + home-rule city rate |
California layers district taxes on top of a single statewide base, so a purchase used in one county carries a different rate than the same purchase used in another. You determine the correct rate from where the software is used. Your headquarters location is irrelevant. The CDTFA lookup returns the combined figure by address, which is why no single percentage covers every California purchase.
Colorado runs a harder problem because its home-rule cities administer their own sales and use tax outside the state system. Denver, Boulder, and Colorado Springs each set and collect their own rates, and a state-level figure tells you nothing about what a Denver-used subscription actually owes. You have to check the state rate and the applicable home-rule city rate as two separate determinations.
Treat the two laws as similar in intent and different in execution. Both flip formerly exempt software into taxable purchases on January 1, 2027, and both push the self-assessment burden onto you when a vendor does not collect. The rate calculation, the taxing jurisdictions, and the lookup process differ, so a buyer with usage in both states runs two distinct accrual tracks rather than one.
What Use Tax Self-Assessment Actually Requires
Self-assessing use tax is a four-step operational sequence, and every step generates documentation you must retain for audit. The steps are identical in structure across California and Colorado, but the filing mechanics diverge at the end. Treat the sequence as a repeatable monthly or quarterly process. Running it once before January 2027 is not sufficient.
Verify buyer-side use tax filing setup
Confirm your company's use tax filing setup in each state where you use taxable software. In California, consumer use tax registration is a separate track from a seller's permit or sales tax license, and holding one does not cover the other. If your company already collects and remits sales tax in California as a seller, do not assume that registration satisfies your buyer-side obligation. Register for the consumer use tax account directly with CDTFA. In Colorado, no separate registration is required. File directly through Revenue Online or by paper return (Form DR 0252).
Identify purchases the vendor did not tax
Review every software invoice for a sales tax line. When a vendor charges tax, your obligation on that purchase is satisfied. When the vendor charges nothing on a purchase that became taxable on January 1, 2027, the liability passes to you, and you must flag that invoice for accrual. Productivity, collaboration, communication, payroll, and expense software all fall into scope once the exemptions repeal.
Accrue the liability at the correct rate
Apply the rate for the jurisdiction where the software is used. California rates vary by district, and Colorado layers home-rule city rates on top of the state base, so the correct figure depends on your usage location within each state. Record the accrued amount as a liability on your books at the time of the taxable transaction. Filing comes later; the accrual entry belongs at the point of purchase.
File and remit on schedule
File through each state's system on the cadence the state assigns, which depends on your liability volume. California and Colorado use different portals and different return forms, so a single filing workflow will not serve both. Retain the invoices, rate calculations, and accrual entries that support each return.
Where Finance Teams Get Exposed
Multi-year contracts that span January 1, 2027 create the largest unaccrued liability because the taxability of the subscription changes mid-term. A three-year collaboration platform contract signed in 2025 was fully exempt when you booked it, and it becomes taxable on the portion of service delivered from 2027 forward. Your accounting system will keep processing those invoices at the original exempt treatment unless someone flags the effective date and splits the accrual.
Auto-renewing subscriptions cross the effective date without anyone reopening the terms, which is exactly why they slip through. A productivity or communication tool that renews annually in October rolls into a taxable period on renewal, but the renewal generates no procurement review and no new contract signature. The invoice amount looks identical to last year's, so nothing in your workflow signals that use tax now applies to the renewed term.
Bundled invoices expose you when a single line item hides a mix of taxable and non-taxable charges. A payroll or expense platform often bills software access alongside professional services, implementation, or support that may fall under different tax treatment. If you accrue use tax on the full invoice, you overpay. If you skip it entirely because part of the bundle is non-taxable, you underaccrue on the software component. You need the vendor to itemize, and many will not do so unless you ask.
Purchases invoiced before the effective date but consumed after it turn on when the taxable event actually occurs under each state's rules. A prepaid annual license for productivity software billed in November 2026 but granting access through late 2027 raises a timing question the invoice date alone does not answer. The transaction date on the invoice reads 2026, yet the access period extends well into the taxable window. California and Colorado each define the taxable moment through their own statutory language, so you cannot assume the invoice date settles it. Consult the CA SB 122 chaptered bill text and CO HB 26-1223 on how each treats access periods before deciding whether that prepayment escapes accrual.
Across all four scenarios, the common failure is that your accounts payable process treats the vendor's tax treatment as final. When the vendor does not charge tax, your system records no tax, and the liability sits unbooked until an auditor finds it.
Pre-January 2027 Checklist for Buyers
Work through these steps in order. Each one depends on the data produced by the step before it, so skipping ahead leaves gaps you will have to backfill under deadline.
Inventory every SaaS and software contract by state of use. (Owner: AP / Procurement) Pull every active subscription and license, and tag each one to the state or states where your team actually uses it. Software used across multiple states may create liability in both California and Colorado. Record where your team actually uses each contract. The billing address on file does not determine the state of use.
Flag contracts that span January 1, 2027. (Owner: AP / Procurement) Mark any agreement with a term, renewal date, or access period that crosses the effective date. These generate mixed liability, where charges before the date stay exempt and charges after become taxable.
Confirm each vendor's collection status. (Owner: Tax / Finance lead) For every flagged contract, determine whether the vendor will charge sales tax on post-2027 invoices. Where a vendor will not collect, you owe use tax and must self-assess it. Do not assume a vendor's silence means the purchase is exempt.
Confirm use tax filing setup in California and Colorado. (Owner: Tax / Finance lead) California requires a separate consumer use tax account registration through CDTFA if you do not already hold a seller's permit. Colorado does not require a separate registration. File directly through Revenue Online or by paper return (Form DR 0252).
Establish accrual entries in your general ledger. (Owner: Tax / Finance lead) Build a recurring accrual for each taxable, untaxed purchase at the correct combined rate for the state and locality of use. Colorado home-rule cities set their own rates, so a single blended figure will misstate the liability.
Set a filing and remittance calendar. (Owner: Tax / Finance lead) Map each state's use tax filing frequency and due dates, and assign a named person to file and remit on schedule. Match the calendar to your accrual cycle so accrued amounts and remitted amounts reconcile every period.
Treat this as a working document. Assign owners, set target dates, and review completion before the accrual entries go live in January 2027.
How Taxwire Handles Use Tax Accrual and Filing
The four requirements in the self-assessment section describe manual work most finance teams are not staffed to run at scale. Taxwire's in-house tax team executes those steps directly, rather than handing you a dashboard and leaving the accrual and filing to your controller. The distinction matters because the failure point in use tax compliance is not seeing the liability, it is booking and remitting it correctly, every filing period, across every jurisdiction.
Taxwire's filings service covers buyer-side consumer use tax as a distinct track from seller remittance. In California, that means opening and managing the separate CDTFA consumer use tax account a company needs even if it already holds a seller's permit. In Colorado, where no separate registration is required, Taxwire's team handles the filing mechanics directly through Revenue Online. Keeping the California buyer-side account separate from seller returns prevents the reconciliation errors that occur when consumer use tax gets mixed into seller remittance.
On accrual, Taxwire's team books the liability entries for taxable purchases your vendors did not tax, applying the correct rate for the jurisdiction where the software is used. That covers the California district-rate variation and the Colorado home-rule city rates, so a purchase used in Denver is accrued at Denver's combined rate and a purchase used in Los Angeles is accrued at its own. Applying rates at the jurisdiction level is the step where in-house teams most often default to a single state figure and under-accrue.
For filing, Taxwire's team prepares and submits your use tax returns on each state's cadence and reconciles the accrued liability against what actually gets remitted. When you owe in both California and Colorado, Taxwire runs the multi-state reconciliation so the two states' different filing mechanics do not produce a mismatch between your books and your returns.
What you get is a tax team that owns the accrual entries, the rate application, and the filing calendar as a service. If your exposure spans both states and multiple software categories, Taxwire runs the buyer-side use tax mechanics end to end.
Does my SaaS vendor's invoice have to show a line for use tax?
No. A vendor that does not collect sales tax on a taxable SaaS purchase has no obligation to print a use tax line on your invoice. A clean invoice with no tax line is not a defense. Read the absence as your cue to self-assess, and record the accrual entry against that purchase.
Do I still owe use tax for the period before my vendor started collecting?
Yes. Use tax liability accrues at the time of each taxable transaction. A retroactive vendor correction does not erase what you already owe for earlier periods. The only clean reversal is a credit memo from the vendor, documented and matched to the original invoice.
Are we exempt if our contract was signed before 2027?
No. When you signed the contract does not determine taxability. Both California and Colorado tie taxability to the transaction date: the invoice, delivery, or access period that falls under the new rules. Confirm the specific mechanics against the CA SB 122 chaptered bill text and HB 26-1223 for how each state applies the effective date to existing contracts.
Do we still owe use tax if our vendor is outside California and Colorado?
Yes. Use tax is imposed on the buyer based on where the software is used. A vendor headquartered in Texas or Ireland does not change your obligation if your California or Colorado teams access the software after January 1, 2027. Track these purchases by location of use, and apply the correct state rate regardless of the vendor's mailing address.
Conclusion
The use tax on your California and Colorado SaaS is your liability to assess, not your vendor's to collect. When a vendor stops short of charging tax after January 1, 2027, that obligation lands on your books, and you self-assess and remit it directly. The date is fixed and the same for both states, so the only variable you control is how ready your accrual process is when the first taxable invoice arrives.
Your multi-year contracts, auto-renewals, and bundled invoices already carry the exposure, and none of it accrues itself. Start with the pre-January 2027 checklist above, assign each item to an owner, and work through it while you still have room to register and set up filings without rushing. If you would rather hand the accrual and buyer-side filing mechanics to a tax team, that is where Taxwire comes in.