Colorado Is Ending Its Software Tax Exemption in 2027: What SaaS Companies Need to Do Now

What HB 26-1223 Does

Before HB 26-1223, Colorado took a narrow view of what software was taxable at the state level. The state generally taxed only software delivered on a physical, tangible medium, such as a disc or tape, prepackaged for repeated sale. Electronically delivered software was exempt. Software delivered via an application service provider was exempt. The result was that almost every modern software transaction, including SaaS subscriptions, downloaded applications, and cloud-hosted software, was untaxed at the state level.

HB 26-1223 replaces that framework entirely. The bill redefines computer software as "a set of coded instructions that are both designed to cause a computer or other electronic device to perform a task and are delivered by any means, including compact disc, download, or remote access through the internet." The phrase "remote access through the internet" is the language that captures SaaS. By treating software as tangible personal property regardless of delivery method, the bill eliminates the delivery-method distinctions that Colorado software sellers have structured their compliance decisions around for fifteen years.

The repeal applies to all sales, storage, use, and consumption of in-scope software on or after January 1, 2027. Not prospectively from a future registration date. From that date forward, regardless of when a company gets around to registering.

What Stays Exempt: The Carve-Outs Are Narrow

Two exemptions survive under HB 26-1223. Both are narrow and both come with documentation requirements that most companies are not currently set up to meet.

Custom software developed for use by a particular user remains exempt. This means software written from scratch for a specific client and not available for repeated sale. Off-the-shelf products with some configuration do not qualify.

Software governed by a negotiable license agreement also remains exempt. To qualify, the agreement must be individually bargained between the licensor and the licensee and signed in writing by authorized representatives of both parties before, or at the time of, access. The bill expressly excludes from this exemption any standard, form, or boilerplate agreement offered on a nonnegotiable basis to multiple licensees. It also excludes agreements accepted by click-through, browse-wrap, or shrink-wrap methods, with one exception: authenticated electronic signatures such as DocuSign can satisfy the writing requirement.

If your customers click "I agree" on a standard terms page, that agreement does not qualify for the negotiated license exemption. Get those agreements reviewed now, before January.

Who This Hits and the Nexus Question

HB 26-1223 applies at the state level. Colorado's economic nexus threshold is $100,000 in gross sales into the state in the current or prior calendar year. There is no separate transaction count prong under Colorado's current rules.

One more layer: Colorado has a dual-layer sales tax system. The state's self-administering home-rule municipalities, including Denver, manage their own sales and use taxes and have independent authority over their own definitions and rules. Several Colorado home-rule cities, including Denver, have been taxing software and SaaS for years already. Out-of-state SaaS sellers may have separate registration and compliance obligations at the local level depending on where their Colorado customers are located.

The Retroactive Audit Risk

Most of the conversation around HB 26-1223 is about going-forward compliance: register, configure the tax engine, start collecting on January 1. That is the right instinct, but the audit exposure does not start on January 1, 2027. For companies that have had Colorado nexus without registering, the window is already open.

I have had SaaS founders come to me after receiving a Colorado notice who did not realize they had nexus at all. They had been selling into the state for years, crossed the $100,000 threshold, and simply never registered because their software was exempt. That is the exposure pattern Colorado's Department of Revenue is already running, and HB 26-1223 gives them another data point to work from.

Colorado's general statute of limitations for sales tax assessments is three years from the date a return was due. For companies with substantial understatements, the period can extend to six years. For companies that failed to file at all, there is no limitation; the Department of Revenue can assess for any period the obligation existed. A voluntary disclosure agreement filed before an audit opens is worth considerably more than the same disclosure filed after one starts.

The California Parallel: This Is Not Isolated

Colorado is not acting alone. California's SB 122, signed by Governor Newsom on June 29, 2026 and also effective January 1, 2027, extends California's sales and use tax to prewritten computer software whether transferred electronically or accessed remotely. SaaS sold into California will be taxable on the same date that SaaS sold into Colorado becomes taxable.

Two of the largest states for software and SaaS companies are moving simultaneously. What most people miss is that the coordination between these states signals direction of travel for the rest of the country. If your company sells SaaS nationally and has been relying on state-level exemptions, 2026 is the year to audit every state in your customer footprint.

What SaaS Companies Should Do Before January 1, 2027

The runway is shorter than it feels. Here is the sequence that matters.

Step 1: Map your Colorado customer footprint. Determine how much revenue you have generated from Colorado customers in the past three years and whether you have exceeded the $100,000 economic nexus threshold in any of those years.

Step 2: Analyze your products against the exemptions. For each product line, determine whether the custom software or negotiated license agreement exemption could legitimately apply. This is a legal analysis, not a sales team judgment call.

Step 3: Assess historical exposure. If you had nexus before January 1, 2027 and were not collecting on taxable transactions, quantify that exposure. Do not guess. Pull the actual revenue data.

Step 4: Consider voluntary disclosure. Colorado has a voluntary disclosure program administered directly through the Colorado Department of Revenue. A voluntary disclosure filed before an audit opens generally limits the lookback period, reduces or eliminates penalties, and provides a structured path to compliance without the threat of an assessment.

Step 5: Register and configure before January 1. If you do not have a Colorado registration and will need one, file it. Configure your billing and tax systems to collect at the correct state rate on the first transaction after midnight on January 1, 2027.

If you have already received a notice from the Colorado Department of Revenue, do not respond without counsel. Contact Sales Tax Helper to assess your exposure before the response deadline runs.

The Clock Is Already Running

HB 26-1223 does not take effect until January 1, 2027. The preparation window, the voluntary disclosure window, and for some companies the existing audit exposure window are all open right now.

The businesses that come through this in the best position are the ones that used 2026 to get their footing: mapped their exposure, made a decision about voluntary disclosure, got their contracts reviewed, and arrived at January 1 with systems configured and a clean registration.

Use Sales Tax Helper's free tools to identify your Colorado nexus position and your exposure window. If your exposure is significant or you have already received a notice, speak with a sales tax attorney before January. The voluntary disclosure window is open now. It closes the moment the DOR opens an audit.