If you run an online store and you've been counting Illinois orders all year to stay under 200 transactions, you can stop. As of January 1, 2026, that number no longer matters. Illinois has eliminated the 200-transaction threshold from its economic nexus rule, leaving a single test: did you sell $100,000 or more of goods to Illinois customers in the trailing 12 months?
It sounds like a simplification, and for many sellers it is. But the change also quietly moves some businesses out of Illinois tax obligations entirely, moves others in for the first time under a rolling calculation they haven't tracked precisely, and arrives alongside a limited-time amnesty program that's worth understanding even if you think you're compliant. Here's what actually changed, who it affects, and what to do about your records before the state's own systems catch up.
The old rule vs. the new rule
Since the 2018 South Dakota v. Wayfair decision let states tax remote sellers based on economic activity alone, Illinois — like most states — used a two-pronged test. A remote retailer had to start collecting and remitting Illinois Retailers' Occupation Tax if, in the preceding 12 months, it hit either:
- $100,000 or more in cumulative gross receipts from sales of tangible personal property to Illinois purchasers, or
- 200 or more separate transactions with Illinois purchasers, regardless of dollar amount
That second prong was the trap. A seller of $8 phone cases or $15 stickers could clear 200 orders to Illinois residents in a matter of weeks while barely making a dent in the revenue threshold — and suddenly owed Illinois sales tax on a business doing a few thousand dollars a year in that state.
Effective January 1, 2026, per Illinois Department of Revenue Bulletin FY 2026-12, the transaction-count prong is gone. The only test now is the $100,000 revenue threshold, measured on a rolling 12-month lookback, reviewed at the end of each calendar quarter.
Who this actually changes
Sellers who cleared 200 transactions but never approached $100,000 in Illinois sales no longer have nexus there. If that describes your business, the Department of Revenue says it will automatically update registration status for affected sellers — but "automatically" and "immediately" aren't the same thing, and relying on a state agency to catch your specific situation is a bad plan. If you registered solely because of the transaction count, you should:
- Pull your trailing-12-month Illinois sales as of December 31, 2025
- Confirm you're under $100,000
- Stop collecting Illinois tax on new sales going forward
- Keep your registration active only if you still expect to cross the revenue threshold, or formally deregister if you don't
Sellers who were under 200 transactions but over $100,000 were already required to collect — nothing changes for you, except one less number to track.
Sellers sitting close to $100,000 with no transaction-count exposure now have a single, simpler line to watch. That's the intended simplification, and it's real: one threshold, checked quarterly, is easier to build a compliance process around than two moving numbers.
The amnesty window nobody should ignore
The same legislative package that dropped the transaction threshold — HB 2755, signed by Governor Pritzker in mid-2025 — also created a remote retailer amnesty program running August 1 through October 31, 2026. It covers eligible tax periods from January 1, 2021 through June 30, 2026, and offers full abatement of penalties and interest for remote sellers who come forward and pay back taxes owed during that window.
If you've been unsure whether you crossed Illinois's threshold in a prior year — maybe you hit 200 transactions in 2023 without realizing it created an obligation, or you assumed a marketplace facilitator was covering everything — this amnesty period is the cheapest way to fix it. Missing it means facing normal penalty and interest exposure if Illinois later flags the gap on audit. The program uses simplified flat rates (9% for standard-rate goods, 1.75% for qualifying food items) rather than requiring you to reconstruct exact local rates for every past transaction, which is a meaningful break from Illinois's usual destination-based sourcing rules.
Why "just Illinois" is the wrong frame
Illinois isn't alone. States have been trending toward dropping or raising transaction-count thresholds specifically because that prong disproportionately burdened low-price, high-volume sellers — the opposite of what economic nexus was designed to target. But the state-by-state variation is exactly what makes this hard to track by memory: some states still use 200-transaction counts, some use different revenue thresholds, some count gross sales while others count only taxable sales, and marketplace-facilitated sales are treated differently depending on where you sell.
The practical mistake most small sellers make isn't ignorance of the rules — it's not having records structured to answer the question quickly when it matters. If someone asked you right now for your trailing-12-month gross receipts to Illinois specifically, separated from your other state sales, could you produce that number in five minutes? For a lot of businesses running on marketplace dashboards and spreadsheet exports, the honest answer is "not without a project."
Set up your books to answer nexus questions on demand
This is the underrated bookkeeping problem behind economic nexus compliance: it's not a tax-rate question, it's a data-structure question. You need sales tagged by destination state, queryable over a rolling window, at any moment — not reconstructed from marketplace CSV exports every time a state changes its rules.
Plain-text accounting handles this well because your ledger is just structured data you can query directly. If you're tracking revenue with per-state tags or accounts (Income:Sales:IL, Income:Sales:CA, etc.), answering "what's my trailing-12-month Illinois revenue" is a one-line query against a text file you control — not a support ticket to your e-commerce platform or a manual reconciliation project. Beancount.io gives you that structure without proprietary lock-in: your books are plain text, version-controlled, and readable by any tool (including AI assistants) that can parse a ledger. When a state changes its nexus rule — and more will, as this trend continues — you want to be answering the question in minutes, not scrambling to rebuild a year of sales history by state.
Keep Your Finances Organized from Day One
Multi-state sales tax rules will keep shifting, and the sellers who handle changes like this smoothly are the ones whose books already answer "how much did I sell where" without extra work. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data—no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.