Colorado's Other 2027 Software Tax: Why HB 26-1223 Hits AI Agents Even Harder Than California

While the SALT world has been fixed on California's S.B. 122, Colorado quietly enacted its own software sales tax with the same January 1, 2027 effective date — and for AI agent operators, Colorado's version is arguably the sharper trap. HB 26-1223, signed by Governor Polis on June 4, 2026, repeals Colorado's downloaded-software exemption and folds "computer software" into the definition of taxable tangible personal property. The mechanism is different from California's, the exemptions are narrower, and the one carve-out that might have saved agent transactions is written in a way that agents almost never satisfy.

We have covered California's S.B. 122 four times as it moved from proposal to law. Colorado deserves its own treatment, because two of the largest state software markets are now converging on the same effective date through two different legal routes — and an operator who prepares only for California will be caught flat in Colorado.

What HB 26-1223 Actually Does

California reached SaaS by creating a new taxable category of "digital products." Colorado took the older, blunter path: it amended the definition of tangible personal property itself. Under the new law, "computer software" means, per the enacted language, "coded instructions designed to cause a computer or other electronic device to perform a task, delivered by any means, including physical media, download, or remote access through the internet."

Three words in that definition carry the weight: delivered by any means. Colorado had long exempted software that was not delivered on physical media — the theory that a download or a cloud login was not "tangible." HB 26-1223 repeals that exemption outright. Software held for repeated sale or license is now taxable tangible personal property regardless of how it reaches the customer. Downloaded applications, remotely accessed cloud tools, and subscription SaaS all land in the same taxable column beginning January 1, 2027, at Colorado's 2.9% state rate — before local tax, which in Colorado is a subject unto itself.

The Negotiable-License Exemption Is the Whole Story for Agents

Colorado preserved two exemptions, and the second is where agent operators need to pay attention.

The first is the familiar custom software carve-out: software developed for a single, particular user remains exempt. Mass-market, repeatedly-licensed software does not qualify. Nothing surprising there.

The second is the negotiable license agreement exemption, and Colorado defined it narrowly. To qualify, the license must be individually negotiated between licensor and licensee, and signed by authorized representatives of both parties before or contemporaneously with the customer's access to the software. The statute then does something unusually explicit: it excludes "standard-form agreements, click-through agreements, online terms of service, and other boilerplate contracts."

Read that exclusion against how an AI agent actually acquires software. An agent provisions an API key, accepts a terms-of-service page, or clicks through a subscription checkout. It does not conduct a back-and-forth negotiation and it does not produce a document signed by authorized representatives of both parties. Every ordinary mode by which an autonomous agent obtains software access is, by name, on Colorado's excluded list. The negotiable-license exemption is real, but it is built for enterprise procurement teams, not for machine purchasers accepting boilerplate at transaction speed. For the agent economy, it is functionally unavailable.

That is the sense in which Colorado hits agents harder than California. California's exclusions turn on what the software is — custom versus prewritten, IaaS versus SaaS. Colorado's decisive exclusion turns on how the deal is papered — and agents paper their deals in precisely the excluded way.

The Home-Rule Complication

Colorado is the hardest state in the country to comply with even before you reach a substantive taxability question, because of its home-rule municipalities. Colorado has scores of self-administered home-rule cities that set and collect their own sales tax and do not always follow the state's base. Several of these cities already taxed remotely accessed software before HB 26-1223, and they did not do so uniformly.

The state-level change does not sweep that patchwork away. An agent transaction sourced to a Colorado address may now face the 2.9% state tax plus a home-rule city tax that reaches the same software on its own terms — or, in some jurisdictions, on terms that differ from the state's new definition. Practitioners are advising taxpayers to evaluate each home-rule jurisdiction separately rather than assume the state definition controls locally. For a high-frequency autonomous purchaser transacting across many Colorado destinations, that is not a rounding error; it is a per-jurisdiction classification problem multiplied by transaction volume.

Why This Lands on AI Agent Operators

The consequences track the California analysis, with Colorado-specific edges.

Input costs change. If your agent subscribes to prewritten software, APIs, or model access with a Colorado situs, those inputs may carry sales or use tax starting in 2027 — and the negotiable-license exemption will rarely rescue a click-through acquisition.

Output may become taxable. If your agent resells or provides access to prewritten software to Colorado customers, you may have a new collection obligation, at the state rate and potentially at the home-rule level, sourced to each destination.

Use-tax exposure rises on autonomous purchasing. When an agent buys taxable software from a vendor that does not collect Colorado tax, the use tax obligation falls on the buyer. High-frequency machine purchasing is exactly the pattern that accrues quiet, unremitted use tax — here, across both the state and a shifting set of home-rule cities.

The open questions are real and worth stating plainly rather than resolving prematurely. Where the custom-versus-repeated-license line falls for lightly configured agent tooling, and how each home-rule city conforms its own base to the new state definition, are matters the Colorado Department of Revenue and the individual municipalities will work out through guidance. We will not characterize those boundaries as settled while they remain in motion.

What to Do in the Next Six Months

The runway to January 1, 2027 is the same as California's, so the work can run in parallel.

• Inventory your Colorado software footprint — every prewritten-software input and output with a Colorado nexus, both what your agents buy and what they resell into the state.

• Do not rely on the negotiable-license exemption for agent transactions. Assume click-through and terms-of-service acquisitions are taxable unless a genuinely negotiated, dual-signed agreement exists. If it was accepted by a bot, it almost certainly does not qualify.

• Map your home-rule exposure. Identify the Colorado cities you actually source transactions into and evaluate each one's software-tax treatment separately from the state's.

• Stand up use-tax accrual for agent purchases before the obligation accrues, not after — the state rate at minimum, with a mechanism that can carry local rates as home-rule treatment firms up.

AgentTax classifies each agent transaction against current state taxability rules and flags where the character of the deal — and, in Colorado's case, the manner it was licensed — drives the tax result. As two 2027 effective dates converge, that classification is the difference between a clean cutover and a multi-jurisdiction use-tax cleanup. See how it works at agenttax.io.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.