If you're building a product that needs to calculate SaaS sales tax for your customers, this guide is for you. It covers Colorado's SaaS tax rules and rates at both the state and home rule level, what to account for when you build sales tax calculation into your product, and how Ziptax returns accurate Colorado rates through an API without you having to build and maintain a rate engine.
Colorado SaaS sales tax at a glance
Product Taxability Rules
| Does Colorado tax SaaS in 2026? | No, at the state level. Home rule cities set their own rules and some, including Denver, already tax it. |
|---|---|
| Will Colorado tax SaaS in 2027? | Yes, statewide, starting January 1, 2027, under HB 26-1223. |
| Does every Colorado city follow the state's timeline? | No. Home rule cities write and administer their own sales tax codes. Denver's code already taxes "software programs, software as a service, software license fees, and software maintenance agreements," independent of state law and the 2027 change. |
| Base State Tax Rate | 2.9% |
| Local Combined Rate Range | 2.9% to 11.2%. The 2.9% state rate is the floor, not the total. County, city, special-district, and home rule city taxes stack on top of it. Colorado's self-administered home rule system means the combined total must be resolved by exact address. |
| Primary Data Sources | Colorado Department of Revenue, City and County of Denver Treasury Division (Tax Guide Topic No. 18: Software), Colorado General Assembly |
State Registration & Collection Triggers
| What triggers a state-level tax collection requirement? | Meeting either of these conditions:1. Economic nexus: retail sales into Colorado exceeding $100,000 in the current or previous calendar year (C.R.S. § 39-26-102(3)(c)). No separate transaction-count threshold.2. Physical nexus: an office, employees, inventory, or other property in Colorado. |
|---|---|
| Does SaaS revenue count toward the $100,000 threshold in 2026? | Yes. Colorado's economic nexus threshold is based on gross retail sales. Even though SaaS is generally an exempt service at the state level prior to 2027, those exempt sales are included when calculating whether you have crossed the $100,000 line. |
| Are marketplace sales included in the $100,000 count? | No, for your own registration trigger. Colorado's marketplace facilitator guidance directs multichannel sellers to exclude sales facilitated (collected and remitted) by a marketplace from their own threshold count. Only direct sales count toward your own trigger. (This is the opposite of California's rule, where marketplace sales do count). |
| Lookback Calculation Window | Current or previous calendar year: a fixed calendar-year test, not a rolling 12-month window. |
| SST State (Streamlined Sales Tax)? | No. Colorado is not a Streamlined Member state, so you register and file directly with the state, and separately with any home rule city where you have local nexus. |
| Do home rule cities have their own registration requirements? | Yes. Each home rule city licenses and administers its own sales tax separately from the state. Many home rule cities, including Denver and Boulder, accept filings through the state's SUTS portal as a convenience, which is not the same as being state-administered. |
Which types of software does Colorado tax?
Colorado layers two systems: a state-level rule that is exempt today and taxable from January 1, 2027, and a set of independent home rule city rules that some cities, like Denver, are already applying now.
| What you sell | Taxable at the state level today | From January 1, 2027 (HB 26-1223) | Taxable in a home rule city like Denver, today |
|---|---|---|---|
| SaaS, accessed remotely, no download | No | Yes | Yes, in cities such as Denver that already tax software as a service under their own code |
| Prewritten software, downloaded | No | Yes | Yes, in cities such as Denver |
| Prewritten software on physical media | Yes | Yes | Yes |
| Custom software written for a single customer | No | No (stays exempt) | No, Denver's guide excludes work-for-hire coding |
| Software under a negotiated license agreement | No | No (stays exempt) | No, Denver also explicitly exempts individually negotiated licenses |
| Specified digital products (e-books, audio, video) | Yes | Yes | Yes |
| SaaS bundled with tangible goods | Split the bundle; the tangible line is taxable on its own terms | Same split logic applies | Same split logic applies |
Two things break implementations here.
First, a line-item split, not an order-level one: if a subscription ships a physical component, the tangible portion stays taxable even where the software portion is exempt. (If not separately stated, the entire transaction may become taxable under the true object test).
Second, and specific to Colorado: a transaction can be exempt at the state level and taxable at the home rule city level in the same invoice, today, in 2026, with no 2027 trigger involved at all. Confirming your customer's billing jurisdiction against the home rule city list is not optional diligence here; it is the determining fact.
How do you charge the correct sales tax rate for SaaS in Colorado?
Under 2026 state rules, you charge nothing at the state level for a remotely accessed SaaS subscription. But if your customer is in a home rule city that taxes software today, such as Denver or Aurora, you may owe that city's local tax right now, regardless of what the state does in 2027.
From January 1, 2027, state-level tax applies on top of whatever the applicable home rule city already charges.
Engineering teams have two options for getting this right.
Option 1: Use the Ziptax Sales Tax API
You send the buyer's rooftop address at checkout, and the API evaluates the exact state, county, city, home rule, and special-district lines that apply.
To calculate a live rate against a Colorado address, use the v60 endpoint:
Bash
curl -G https://api.zip-tax.com/request/v60 \
-H "X-API-KEY: <apiKey>" \
-d key=your-api-key \
--data-urlencode "address=200 E Colfax Ave, Denver, CO, 80203"To verify complete payload structures, explore the REST API documentation.
\Three things to do with that response:
- Multiply by the combined rate rather than assembling it from components you store separately.
- Store the jurisdiction on the transaction, not just the rate, because Colorado's home rule layer means the same ZIP code can sit partly inside and partly outside a taxing city.
- Store the effective date too, since that is what lets a credit or amendment on a past invoice apply the rule that was actually in force then.
If your catalog handles complex items like SaaS, digital goods, or bundles, you can also review Taxability Information Codes (TICs) to check product-specific rules, or search for the correct product code for your catalog.
What an API will not tell you: your company's physical presence or economic registration status in Colorado, or in any specific home rule city. Tracking whether you have crossed a state or city nexus threshold and must legally register remains on your side of the integration.
To automate threshold tracking, filings, and remittance once you know where you owe, you can set up merchant management and connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.
Option 2: Build and maintain it yourself
If you take this route, Colorado requires extreme precision, because of home rule. The work splits into four parts: source rate and taxability data for every applicable jurisdiction, including home rule cities that write their own rules; resolve each customer address down to the specific state, county, city, home rule, and special-district lines that apply to it; refresh all of it on a cadence, since home rule cities change their own codes independent of the state legislature; and keep a dated history so a past transaction still returns the answer it originally got.
If you take this route, Colorado needs these things handled:
- Address-level jurisdiction resolution, not just rate resolution. A home rule city boundary determines which tax code applies to a sale.
- A product taxability decision that is separate per jurisdiction. The state says exempt through 2026 and taxable from 2027. A home rule city can say taxable now.
- Parallel exemption tests and the repeal of MPU. HB 26-1223 repeals Colorado's Multiple Points of Use (MPU) exemption, removing the framework for allocating software sales based on users' locations across states. Businesses must rely on upcoming DOR sourcing guidance for apportioning enterprise software. You also must manage negotiated-license certificates separately from custom software tests.
- Threshold accumulation. State economic nexus is $100,000 in gross retail sales for the current or previous calendar year. A home rule city's nexus posture is an entirely separate threshold.
Watch out for:
- Treating "no state tax" as "no tax." The single most common Colorado implementation error. A SaaS sale can be fully exempt at the state level and taxable the moment the same invoice is billed inside a home rule city.
- ZIP-based shortcuts. Home rule city boundaries do not reliably follow ZIP code lines.
- Treating the SUTS portal as proof of state administration. Several home rule cities accept filings through Colorado's state-run SUTS portal as a convenience. That does not make them state-administered jurisdictions.
- Rules changing mid-period, at two levels instead of one. A home rule city can change its own code on its own schedule, separately from whatever the state legislature does. A stored rule is only right until either one of them moves.
- The January 1, 2027 transition date. A credit note issued in 2027 against a 2026 invoice must carry the 2026 state-level treatment backward.
When does a SaaS business have to collect sales tax in Colorado?
Registration and collection are two separate obligations, and Colorado adds a third layer most states don't have: your home rule city obligations sit alongside your state obligations rather than inside them.
Rule 1: Monitor your registration triggers, at both levels
You must register with the state the moment either of these is met:
- Physical presence: an employee working in Colorado, an office, inventory, or other property in the state.
- Economic nexus: your gross direct retail sales into Colorado cross $100,000 in the current or previous calendar year. Sales facilitated and collected by a marketplace facilitator do not count toward this figure.
Separately, you may need to register with one or more home rule cities under their own local ordinances. That trigger is set by each city's own code, not by the state threshold above, and a state-level registration does not substitute for it.
Rule 2: Apply the correct timeline logic, per jurisdiction
- State level, in 2026 (exempt SaaS): if you cross the $100,000 threshold, you must register with the state, but your billing system should calculate state tax at $0 on SaaS and submit zero-dollar state returns on schedule.
- State level, in 2027 (taxable SaaS): your billing system must begin calling the Ziptax API at checkout to calculate, collect, and remit state-level tax on SaaS.
- Home rule city level, now: if your customer's billing address sits inside a home rule city that already taxes SaaS, such as Denver or Aurora, your billing system needs to calculate, collect, and remit that city's tax today.
Where Ziptax helps
If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, Ziptax handles the infrastructure layer of sales tax calculation:
- Rooftop Precision: Resolves rates and jurisdictions using exact address and coordinate-based lookups, catching the home rule city boundaries that ZIP-based shortcuts miss.
- Engineered for Platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
- Frictionless Pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
- The TaxCloud Runway: When your transaction volume scales, you can pair Ziptax with TaxCloud for automated filing and remittance, including direct filing capabilities for Colorado's self-collecting home rule cities.
Get Colorado SaaS tax rates from an API
Address-level rates for every Colorado jurisdiction, state and home rule, plus the rest of the US, Canada, and select other markets.
Frequently asked questions
Do you have to register in Colorado if your SaaS product is exempt there? Yes. If you cross Colorado's $100,000 gross sales threshold, you must register. Even though SaaS is currently treated as a nontaxable service at the state level in 2026, exempt sales count toward that $100,000 threshold. You may be required to file and remit $0 in state tax while owing local tax in a home rule city.
Does Colorado tax software differently depending on how it is delivered? At the state level, not from January 1, 2027 onward. HB 26-1223 taxes software "regardless of method of delivery," placing remotely accessed SaaS, downloaded apps, and software on physical media onto the exact same taxable footing. Custom software built for a single customer and software under a genuinely negotiated license remain exempt.
What is a home rule city, and why does it change the answer? Colorado's constitution allows certain cities (like Denver, Boulder, and Aurora) to write and administer their own sales tax codes instead of adopting the state's definitions. A SaaS business needs to check both the state rule and the local rule in any home rule city where it has customers.
When does Colorado start taxing SaaS at the state level? January 1, 2027, under House Bill 26-1223. The bill explicitly expands sales and use tax to software "accessed remotely through the internet," bringing SaaS directly into the state tax base. However, home rule cities such as Denver tax SaaS today under their own codes, with no connection to this 2027 date.
Sources
- 2026 state-level exemption and 2027 change (HB 26-1223): Colorado General Assembly, House Bill 26-1223, "Modifying Certain Tax Expenditures," 2026 Regular Session, signed June 4, 2026, effective for this provision January 1, 2027.https://leg.colorado.gov/bills/hb26-1223
- Economic nexus threshold: Colorado Revised Statutes § 39-26-102(3)(c), as cited by the City of Boulder's Guidance for Remote Sellers.https://bouldercolorado.gov/guidance-remote-sellers
- Marketplace facilitator treatment of the seller's own threshold: Colorado Department of Revenue, Sales & Use Tax Topics: Marketplaces (revised September 2020), citing HB 19-1240.https://tax.colorado.gov/sites/default/files/SUTT_Marketplaces.pdf
- Streamlined Sales Tax (SST) status: Streamlined Sales Tax Governing Board, state membership status for Colorado.https://www.streamlinedsalestax.org/state-details/colorado
- State sales tax rate: Streamlined Sales Tax Governing Board, state membership status for Colorado (state rate 2.9%).https://www.streamlinedsalestax.org/state-details/colorado
- Home rule city taxability of software (Denver): City and County of Denver, Department of Finance, Treasury Division, Tax Guide Topic No. 18: Software.https://www.denvergov.org/content/dam/denvergov/Portals/571/documents/TaxGuide/TaxGuideTopic18_Software.pdf
- Home rule city remote seller and registration guidance (Boulder): City of Boulder, Guidance for Remote Sellers.https://bouldercolorado.gov/guidance-remote-sellers
- Colorado rate publication and lookup: Colorado Department of Revenue, DR 1002 Colorado Sales/Use Tax Rates, and the Colorado Sales Tax Lookup Tool.https://tax.colorado.gov/DR1002