Is SaaS Taxable in Colorado? Not by the State Until January, and Denver Has Been Taxing It All Along

Key Takeaway: Colorado is the state where "is SaaS taxable" has two answers at the same address. The state does not tax remotely accessed software until January 1, 2027. Denver taxes it now and will keep taxing it on its own terms afterwards. And the act that flips the state answer — HB 26-1223, signed June 4, 2026 — does two things almost nobody has written about: it deletes the sentence that kept cloud-hosted software out of Colorado's separate tax on computer access, and it repeals the only proration rule a multi-state buyer had.

The Short Answer

Under current state law, remotely accessed software is not taxable in Colorado. The Department of Revenue's publication Sales & Use Tax Topics: Computer Software states the test plainly: Colorado sales tax applies to a sale of computer software only if all three conditions are met — it is prepackaged for repeated sale or license, its use is governed by a tear-open nonnegotiable license agreement, and it is delivered in a tangible medium. Software provided through an application service provider, delivered electronically, or transferred by load and leave fails the third condition and is not taxed. Cloud software has been exempt because it arrives as nothing you can hold.

That publication carries one more sentence that governs the whole of this post: its guidance "applies to sales taxes administered by the Colorado Department of Revenue, including state sales tax, as well as city, county, and special district sales taxes, but does not apply to sales taxes administered by any home-rule city." Colorado's self-collecting cities write their own base. Denver wrote a different one.

What HB 26-1223 Actually Deletes

The enrolled act is titled Modifying Certain Tax Expenditures, and the software repeal is there to fund an income tax credit. Section 9 makes the base change apply to transactions on or after January 1, 2027.

Read with the strikethroughs visible, it is a demolition rather than an amendment. Section 2 reduces § 39-26-102(15)(c) to two sentences. "Tangible personal property" simply includes computer software — the three conditions are struck. "Computer software" is redefined as 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, and it expressly includes mobile applications.

Then the vocabulary goes. The definitions of application service provider, electronic computer software delivery, load and leave, prepackaged for repeated sale or license, tangible medium and tear-open nonnegotiable license agreement are all struck. So is the firmware provision at (III). Colorado did not narrow its delivery-method rules; it erased them.

Two deletions deserve more attention than they have had.

One: the cloud carve-out from computer access. Colorado already taxes something adjacent to SaaS. The Department's Colorado Sales Tax Guide (revised May 2026) lists mainframe computer access among taxable sales of tangible personal property, defining it as "the provision of access to computer equipment for the purpose of storing or processing data." Renting compute to process data is taxable in Colorado today. It has not swallowed cloud software only because § 39-26-102(5.7) carried a sentence excluding access "incident to electronic computer software delivery" or "incident to the use of computer software hosted by an application service provider." HB 26-1223 strikes that sentence, and strikes the ASP definition it depended on. From January, the statutory wall between "you rented equipment" and "you used hosted software" is gone. What survives is the exclusion for access "for the purpose of examining or acquiring data maintained by the vendor" — a retrieval carve-out, not a hosting one.

Two: the proration rule. Old § 39-26-102(15)(c)(IV) let a Colorado buyer of multiple software licences pay tax only on the licences "actually used in Colorado," on a written statement that relieved the retailer of liability for the rest. It is struck. Every other jurisdiction we have looked at this quarter is building a use-apportionment denominator. Colorado is expanding its base to remote access while deleting the only one it had.

The Exemption Agents Cannot Use

Section 6 adds § 39-26-713(3), exempting computer software where the sale "is either governed by a negotiable license agreement or developed for use by a particular user." Custom software survives. The other branch does not survive contact with machine purchasing.

Subsection (b) says "individually bargained" excludes any standard, form or boilerplate agreement offered on a nonnegotiable or substantially nonnegotiable basis to multiple licensees — regardless of whether it bears a handwritten or electronic signature, and including terms "presented as part of the terms and conditions of any website or application through which the software is acquired, accessed, or used."

Subsection (c) is the sentence to design around. "Signed in writing by authorized representatives" excludes acceptance "on a click-through, browse-wrap, shrink-wrap, embedded signature, implied, account creation, or any other automated basis," while expressly permitting DocuSign-style authenticated signatures.

That is, so far as I have read, the first American sales-tax exemption withdrawn from automated acceptance by name. An autonomous agent provisions an API key and accepts terms; that is account creation and it is automated, which fails (c) twice. A DocuSigned enterprise contract clears (c) only to meet (b), which asks whether the terms were individually bargained. Two independent tests, and agent commerce fails the first by construction.

The state's own revenue model assumes the opposite of the agent case. Legislative Council Staff's final fiscal note, dated September 3, 2026, estimates the change raises $44.4 million in FY 2026-27 and $92.2 million in FY 2027-28 — on the assumption that "20 percent of total downloadable software sales arise from nonnegotiable agreements and would become subject to state sales tax." Colorado priced this law expecting the exemption to cover four fifths of the base. The agent economy sits entirely in the taxable fifth.

Denver Never Waited

Denver's Tax Guide Topic No. 18 imposes sales or use tax on "software programs, software as a service, software license fees, and software maintenance agreements," and states that the delivery method does not affect taxability — disk, download, load and leave, or cloud. Three consequences matter for agents.

Denver taxes what the state will exempt. Example 5 has a Denver company owing use tax on custom software, and Denver has no negotiated-licence concept at all. From January, one Colorado purchase can be state-exempt and Denver-taxable at once. Nothing in HB 26-1223 aligns them.

Metered usage rides along. In Example 7, a Denver company licenses software on a server in Florida and pays a mandatory monthly CPU usage charge. Both the licence fee and the usage charge are taxable. Per-call and per-token billing for a hosted model is the same shape.

Denver apportions by where the software is used. Software used in Denver is taxable "regardless of where the software resides," and a purchaser using software inside and outside Denver owes tax "only on the portion of the purchase price attributable to the software used in Denver" — measured by the users in Denver accessing it. A home-rule city runs the apportionment rule the state just repealed.

What AgentTax Computes for Colorado

Verified live against the engine this session, $1,000 business-to-business:

• A Denver SaaS transaction today returns $51.50 — Denver's 5.15% municipal rate alone. The engine applies the home-rule portion only and withholds the 2.9% state and 1.1% state-collected local layers, because the state base does not reach cloud software yet. Every response carries a CO_HB26_1223_SOFTWARE advisory naming the dated change.

• The same transaction replayed at January 15, 2027 returns $91.50 at the full 9.15% combined rate. The flip fires on the date, not on a redeploy. Boulder moves $38.60 to $91.95; Loveland $30.00 to $59.00.

• Compute, API access, storage, cloud infrastructure and data processing already compute at the full combined rate, on the mainframe-computer-access head rather than the software head — the right side of the line for renting equipment to process data. It is disclosed as a conservative result for retrieval-shaped work: the Department excludes access for "examining or acquiring data maintained by the vendor," and our matrix carries no Colorado cell for information services, so those calls take the state default. Logged for classification review, not filed as a defect.

• We carry 17 Colorado ZIPs, each split into a self-administered municipal rate and a state-collected rate, with a self_administered_locality advisory. A ZIP we do not carry returns the state figure with ZIP_UNKNOWN rather than a guess — which in a home-rule city means $0 today where the city itself would charge. That is the honest gap in Colorado, and the rates above are ours: not reconciled against each city's published schedule this session.

What to Watch

Whether the Department's rules answer the (5.7) question. With the ASP exclusion struck, a bundled AI subscription can sit inside both the software head and the computer-access head, and nothing in the act says how to split it. The August 6 workgroup opened on a blank page.

Whether anything replaces the repealed proration rule — Colorado will tax remote access from January with no mechanism for a buyer whose users span states — and whether the guidance catches up. The publication served today at the Department's own address is revised February 2021 and states the three-condition test as current law, with no mention of the change. There are fewer than four months to go.

And whether the conformity gap closes: per the fiscal note, state-collected locals pick up the new base only where voters approve it at a local election, and self-collecting home-rule cities are outside the state base entirely, before and after. No Colorado authority has addressed agent-initiated commerce directly. Everything above applies human-drafted categories to machine transactions — analysis, not settled law.

Try it on your own transaction types. Run a Colorado SaaS transaction now (no account), or get a free API key. Compare it with our reading of HB 26-1223 when it passed, California's flip on the same date, Chicago's self-administered lease tax and Maryland's apportionment statute; see every state in the 50-state SaaS taxability guide and the AI agent sales tax hub.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.