Is SaaS and AI Taxable in Illinois? The State Says No — and Its Software Rule Names Your API

Key Takeaway: Illinois does not tax SaaS, and unlike most exempt states it says so in the regulation rather than leaving you to infer it from the absence of a rule. But two things in Illinois deserve more attention than the headline exemption: the same regulation expressly contemplates that a subscriber handed an API or a remote access agent is receiving computer software, and the City of Chicago taxes cloud use at 15% under a lease tax that apportions by counting users.

The Bottom Line

Illinois runs two rulebooks that point in opposite directions.

At the state level, the Retailers' Occupation Tax reaches tangible personal property. Canned software is deemed tangible personal property; remotely accessed software is not reached at all. 86 Ill. Adm. Code 130.1935(a)(3) states it plainly: "Computer software provided through a cloud-based delivery system is not subject to tax. A cloud-based delivery system is one in which computer software is never downloaded onto a client's computer and only accessed remotely." That is an affirmative regulatory exemption, not a gap.

At the city level, Chicago taxes the same transaction. The Personal Property Lease Transaction Tax (Chicago Municipal Code ch. 3-32, Form 7550) applies to nonpossessory computer leases, and the City's published rate schedule reads: "As of 1-1-2026: 15% of receipts or charges for all leases, including the non-possessory lease of a computer to input, modify, or retrieve data supplied by the customer." The prior steps are on the same page — 11% as of 1-1-2025, 9% as of 1-1-2021.

Illinois exempts the transaction. Chicago taxes it at 15%. The city tax is the entire tax, not a layer on top of a state rate.

The Line Is Downloaded vs. Accessed — and It Runs Through Your SDK

Section 130.1935(a) makes canned software tangible personal property "regardless of the form in which it is transferred or transmitted, including tape, disc, card, electronic means, or other media." Subsection (a)(3) then carves out cloud delivery where software "is never downloaded onto a client's computer and only accessed remotely."

Read together, the operative question is not whether your product is called SaaS. It is whether anything lands on the customer's machine. A pure REST API sits inside (a)(3). A client library, SDK, or desktop helper the customer installs does not — nothing was "never downloaded."

Which brings us to the subsection nobody quotes. 86 Ill. Adm. Code 130.1935(a)(4):

"If a provider of a service provides to the subscriber an API, applet, desktop agent, or a remote access agent to enable the subscriber to access the provider's network and services, the subscriber is receiving computer software."

Illinois wrote "API" and "remote access agent" into its software regulation. That does not by itself make the transaction taxable — (a)(3) still exempts what is only accessed remotely, and the two subsections have to be read together — but it does mean Illinois has already decided that shipping an agent-facing interface is a software event rather than a pure service event. Very few states have said anything this specific about the artifacts agent integrations actually ship.

The Click-Through Trap, and the Escape Hatch

If your software is downloaded, it is canned software and taxable at 6.25% plus local rates unless it qualifies as an exempt license. The five criteria in 130.1935(a)(1)(A)–(E) require, among other things, a written agreement signed by licensor and customer, restrictions on duplication and transfer, a replacement-copy policy, and destruction or return of copies at the end of the term.

The first criterion is where most sellers lose. The regulation addresses electronic acceptance directly, in two consecutive clauses:

"(i) An electronic agreement in which the customer accepts the license by means of an electronic signature that is verifiable and can be authenticated and is attached to or made part of the license will comply with this requirement."

"(ii) A license agreement in which the customer electronically accepts the terms by clicking 'I agree' does not comply with this requirement."

Clicking through fails. A verifiable, authenticatable electronic signature attached to the license succeeds.

That distinction cuts in the helpful direction for agent commerce. An agent clicking a checkbox produces nothing that satisfies (i); an agent holding a key and producing an authenticatable signature bound to the license document produces exactly what (i) describes. Illinois is one of the few states where the difference between a click and a signature is written into the regulation as a tax outcome — and where an agent can be built to land on the right side of it.

Two boundaries worth keeping straight. Downloaded content is not software: electronically downloaded books, music, newspapers and magazines are "the transfer of intangibles and are thus not subject to Retailers' Occupation and Use Tax" under 130.2105(a)(3), though that same paragraph confirms "downloads of canned software ... are subject to" the tax. And custom programs prepared to the customer's special order remain exempt under 130.1935(c).

Chicago: 15%, and an Apportionment Affidavit That Counts Users

Per the City's Nonpossessory Computer Leases information bulletin, Code Section 3-32-020(I) covers payments where "the customer obtains access to the provider's computer and uses the computer and its software to input, modify or retrieve data or information." The bulletin restates the principles that matter to a remote seller: location of customer use is key, liability triggers when a Chicago customer makes remote use of a provider's computer even if that computer sits outside the city, labels are irrelevant ("lease, rental, license, or by some other term"), and payment triggers the tax — free use is not taxed.

Three points deserve engineering attention.

Exemption 11 will not save an AI service. Code Section 3-32-050(11) exempts use that is "de minimis and the related charge is predominantly for the information transferred to the customer rather than for the customer's use or control of the computer." That sounds like it was written for an inference API. It was not, and the City closed the door: the bulletin records that Ruling #12 narrowed the exemption to passive receipt, stating that "a subscription to an interactive web site will be subject to the lease tax, and will not be exempt, even if most or all of the information available on the web site is fleeting or transitory," expressly including "a web site that provides financial research, information and analytical tools." An API that takes a request and returns generated output is interactive by construction.

There is a small new business exemption, and most AI startups fit it. Code Section 3-32-050(A)(13), as set out in the bulletin, exempts the nonpossessory lease of a computer where the lessor or lessee is a small new business — under $25 million in gross receipts in the most recent full calendar year, in operation fewer than 60 months, holding a current business license. Either side of the transaction qualifying is enough. The City's tax page still links a "Transaction Tax Exemption Application for Small New Businesses." If you are a four-year-old company selling into Chicago, this is worth an afternoon.

Chicago already runs the apportionment regime California is about to write. The City's Affidavit for Apportionment of Use of Nonpossessory Computer Leases quotes Ruling #12: where a customer has users inside and outside Chicago, "a charge that covers both the Chicago use and the non-Chicago use should be apportioned," and "for any given individual assigned an access code, seat, license or other ability to use the provider's computer, all of that individual's use will be presumed to take place at the individual's principal office location." The affidavit's arithmetic is bluntly simple: Chicago Percentage of Use equals the number of Chicago users divided by the total number of access codes, seats or licenses.

That denominator is the open question in California's forthcoming Regulation 1600.2, "Digital Products Purchased for Multiple Points of Use" — one of the new regulations in the CDTFA package implementing S.B. 122, whose interested parties meeting is set for September 10, 2026. Chicago has been running a users-based denominator for a decade. Michigan, as we covered yesterday, built a multiple-points-of-use certificate for software and repealed it in 2009. Anyone drafting an apportionment rule for digital products now has one live example and one abandoned one.

The presumption is where agents break it. "The individual's principal office location" assumes a person with a desk. An autonomous agent assigned an access code has no principal office, and a seat-counting denominator has no natural way to express a workload that runs wherever capacity is.

What This Means for Your Business

Economic nexus. Illinois uses a $100,000 revenue threshold with no transaction count, measured on a rolling 12-month period. Gross receipts drive the measurement, so a seller of exempt SaaS can owe Illinois registration while collecting state tax only on its taxable items.

Chicago is a separate registration, through the Department of Finance on Form 7550, independent of Illinois DOR filing and audit. Source by city limits, not metro area — Evanston, Oak Park and Naperville are outside the tax, and a ZIP prefix is not a city boundary. Treat the rate as an annually verified input: the published schedule moved 5.25% to 7.25% to 9% to 11% to 15% across a decade, always in a budget ordinance.

How AgentTax Handles Illinois

Verified live against the engine while writing this post:

• Every service category computes $0 at the state level. SaaS, API access, compute, cloud infrastructure, storage, AI model access, subscription, service, AI labor, consulting, marketplace fee, data processing and data purchase all return $0 for an Illinois buyer with no Chicago ZIP.

• Software licenses are the exception, at 6.25%. A license transaction computes $6.25 on $100 statewide, reflecting the click-through analysis above. A transaction that genuinely satisfies all five criteria in (a)(1) can be exempted through an exemption certificate.

• A Chicago ZIP switches the whole calculation to the PPLTT. A 606xx buyer computes $15 on $100 for SaaS, API access, compute, storage, data processing and AI model access — 15%, city only, with no Illinois state portion stacked underneath.

• A software license in Chicago is not a lease. It computes at 10.5% — the 6.25% state rate plus Chicago's local sales tax — because a sale of software is a sale, not a nonpossessory lease. Purchased digital content computes $0.

• Dated replays resolve at the rate in force, and refuse when they cannot. A 2025-dated Chicago transaction computes 11%, not 15%. A 2024-dated one does not silently compute 9% — it fails closed with AS_OF_DATE_BEFORE_MODELED_WINDOW, because the 9% step is documentation and we would rather reject a replay than invent one.

• Two things we do not model, said plainly. We do not model the small new business exemption or the de minimis exemption — a Chicago buyer who qualifies will be over-collected by our calculation and should claim it directly. And we do not apportion: one destination, one answer. Chicago's affidavit contemplates splitting a single charge across users inside and outside the city, and we do not do that today.

Try it on your own transaction types. Get a free API key, or see how Illinois compares in the 50-state SaaS taxability guide and the AI agent sales tax hub.

What to Watch

Whether CDTFA's Regulation 1600.2 adopts a users-based denominator like Chicago's, something closer to consumption or benefit, or declines to pick — the discussion paper had not posted as of this writing, with the interested parties meeting on September 10. Whether any other Illinois home-rule municipality follows Chicago into cloud lease taxation. And whether Illinois revisits 130.1935(a)(4) now that "remote access agent" describes a much larger share of the market than it did when the language was written.

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.