Five Deadlines, Not One: What Actually Changes for AI Agent Sales Tax on January 1, 2027

Four state laws take effect on January 1, 2027, and a fifth date — October 1, 2026 — arrives before any of them. The commentary has collapsed all of this into a single phrase, "the 2027 software tax," and that collapse is the most expensive mistake available right now. An operator who prepares for one deadline prepares for one fifth of the problem, and probably not the fifth that applies to them.

We have covered each of these individually: California S.B. 122, Colorado HB 26-1223, Illinois S.B. 3019, Utah S.B. 287, and the DC rate step. This piece does the thing none of those could do alone: it sorts them. The sorting is the whole value, because the five obligations differ on every axis that determines whether you owe anything.

The Actual Calendar

| Effective | Jurisdiction | Tax | Who pays |
|---|---|---|---|
| 2026-07-01 | Utah | S.B. 162 — seller-hosted prewritten software taxable | Buyer, collected by seller |
| 2026-10-01 | District of Columbia | General rate 6.5% to 7.0% on an existing base | Buyer, collected by seller |
| 2027-01-01 | California | S.B. 122 — prewritten software and SaaS taxable, 7.25% + district | Buyer, collected by seller |
| 2027-01-01 | Colorado | HB 26-1223 — software becomes taxable TPP, 2.9% + home rule | Buyer, collected by seller |
| 2027-01-01 | Illinois | S.B. 3019 — 10% targeted advertising occupation tax; 0.2% digital asset privilege tax | The provider, on its own receipts |
| 2027-01-01 | Utah | S.B. 287 — annual targeted advertising entity tax, reported at 4.85% | The entity, on apportioned receipts |

Two of these dates have already passed or are two months out. Utah's seller-hosted software provision has been live since July 1 and is the one that is quietly costing people money today, while everyone models a date eighteen months away. DC's October 1 step is a rate change on a base that has been taxable for years — the District treats SaaS as a "data processing service" under D.C. Mun. Regs. §9-474.4 — so there is no new registration question, only a new number.

Three Questions That Sort All Five

1. Do you collect it, or do you owe it?

California and Colorado are transaction taxes. You collect from your buyer, you remit, and if you get the classification wrong you are liable for tax you never charged. Illinois's advertising tax and Utah S.B. 287 are the reverse: they are levies on your own gross receipts, with no customer to collect from and no invoice line to add. Illinois's is styled an occupation tax and Utah's is an annual entity-level tax. The Illinois digital asset privilege tax is a third animal — 0.2% on businesses that exchange, transfer, or store digital assets for a customer, which lands on the rail rather than the sale.

This distinction determines which system you change. Collect-and-remit obligations mean touching billing, tax calculation, and registration. Entity-level obligations mean touching your year-end provision and nothing else. They are different projects with different owners.

2. Does the tax turn on what you sell, or on how you sell it?

California and Colorado define their base by category: prewritten versus custom, software versus infrastructure. Illinois and Utah define theirs by conduct. Illinois writes "machine learning algorithms" into its definition of "programmatic." Utah asks three questions about the mechanics of the transaction — is space sold through a bidding process, are individualized data profiles used to deliver, can the viewer interface with the placement to buy something.

Conduct tests are the harder ones to plan around, because you cannot reclassify your way out of them. You can restructure a software license. You cannot restructure the fact that your system bids in real time.

3. Is there a threshold, and is it a real one?

This is where the noise inverts. The two loudest laws are the two least likely to reach an agent operator. Utah S.B. 287 requires all three of $1 million in Utah targeted-advertising receipts, $100 million in worldwide targeted-advertising receipts, and targeted advertising at 50% or more of total gross receipts. That $100 million gate excludes essentially every company reading this. Illinois's advertising tax needs $1 million in Illinois receipts from targeted advertising services — lower, but still a threshold, and still measured against advertising receipts specifically.

California and Colorado have no equivalent. Beyond ordinary economic nexus, the software tax applies from the first dollar. The quiet law is the one that bills you.

The Divergence Everyone Gets Backwards

California and Colorado reach the same destination — taxable SaaS on the same day — by different legal routes, and practitioners tend to assume the routes are interchangeable. They are not, and the difference runs opposite to the intuition.

California excludes by category: raw IaaS, custom software, and pure information services stay out. Colorado excludes by paperwork: it preserved a custom-software carve-out and a negotiable-license exemption, and it expressly wrote standard-form agreements, click-through agreements, and online terms of service out of that exemption.

Run three fact patterns through both:

• Prewritten SaaS on click-through terms. Taxable in California (prewritten), taxable in Colorado (click-through excluded from the license exemption). The agent-economy default case, and it loses twice.

• Raw compute. Exempt in California by express carve-out. Also, in my reading, outside Colorado's base — HB 26-1223 taxes "coded instructions," and rented capacity is not coded instructions. Same answer, different reasoning, which means it can diverge later.

• A negotiated enterprise license, signed by both parties. Exempt in Colorado. Taxable in California, because negotiation is irrelevant to whether software is prewritten.

That last row is the one to internalize. Colorado's exemption rewards procurement formality that California ignores entirely. An enterprise buyer with real contracts is better off in Colorado; an agent operator accepting boilerplate at machine speed is worse off in both, and worse off in Colorado than the statute's exemption list suggests at first read.

What To Do Before January

• Classify what you sell, once, against the California category line. Prewritten software, custom software, raw infrastructure, or information service. This single classification drives your California answer and most of your Colorado answer. Do it now, while the CDTFA's guidance is still forming and you can adjust product packaging cheaply.

• Check Utah S.B. 162 against your July and August invoices. That obligation is live. If you sell seller-hosted prewritten software into Utah, you may already be under-collecting.

• Update the DC rate on October 1, and only that. No base change.

• Test the two entity-level taxes against your revenue mix and stop there. If targeted advertising is not 50% of your gross receipts, Utah S.B. 287 is not your problem and should not consume a planning cycle. Document the conclusion so you can re-test annually.

• Preserve contemporaneous usage records now. The CDTFA has signalled allocation approaches keyed to user or device location — units an autonomous agent does not produce in usable form. Whatever allocation mechanism lands, the defensible input will be records you kept during the period, not an election made up front.

One caveat I keep restating: no state has addressed agent-initiated commerce directly. Every one of these five obligations was drafted with a human purchaser in mind, and the fit to machine transactions is an interpretive question, not a settled one. Plan conservatively and document the reasoning.

What To Watch

The CDTFA discussion draft, expected by the end of August 2026. This is the single most consequential item on the list. It should be followed by an interested-parties meeting in late August or September and submission to the Office of Administrative Law in early December. The statute delegated most operative detail — the contours of "digital product," the treatment of human effort, allocation mechanics — to a rulemaking that has not happened yet.

Illinois litigation, and a correction to my own call. In June I wrote that Illinois should expect a complaint against S.B. 3019 "within weeks." Eight weeks on, no suit has been filed. The active NetChoice litigation is NetChoice v. City of Chicago, filed March 13, 2026 in the Circuit Court of Cook County, challenging Chicago's separate social media levy — not the state statute. I was wrong about the timing, and the practical consequence is that operators should not assume the Illinois provisions will be enjoined before they take effect.

Utah State Tax Commission implementing rules for S.B. 287, which will settle the rate ambiguity — most alerts report 4.85%, at least one cites 4.7% — and define how impressions are counted.

Five deadlines, four tax types, two that will actually bill you. Knowing which of your transactions fall on which side of each line, in each state, on each date, is not a spreadsheet problem for long. AgentTax resolves taxability by jurisdiction and transaction date, so the California and Colorado flips apply automatically when they arrive. See how it works at agenttax.io, or start with our AI agent sales tax hub and the 50-state guide.

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.