Illinois’ Digital Asset Privilege Tax Act: A New Compliance Minefield

July 14, 2026

Illinois has enacted the Digital Asset Privilege Tax Act (“DAPTA”), the first state tax in the nation aimed specifically at digital-asset transactions. This post walks through what the law does, what could happen to it before it takes effect, and the practical compliance headaches it is likely to create for the businesses that must administer it.

Background

Beginning January 1, 2027, DAPTA imposes a tax on the privilege of receiving digital asset business activity in Illinois at a rate of 0.2% of the value of the digital asset involved. Importantly, the tax is measured by the value of the asset rather than by the fee the business charges for its service. The law applies to “digital asset brokers,” meaning businesses engaged in exchanging, transferring, or storing digital assets for customers, and it is the broker’s duty to collect the tax on each transaction and remit it to the Illinois Department of Revenue. Its reach extends beyond Illinois-based companies: an out-of-state broker with $100,000 or more in gross receipts from sales to Illinois customers is treated as maintaining a place of business in the State and must register, collect, and file returns. Brokers must register with the Department before operating, file monthly returns, and keep detailed records, and violations such as failing to file or filing a fraudulent return are a Class 3 felony. In short, the law creates a new, value-based transaction tax on exchanges, custody providers, and transfer services touching Illinois customers.

What Could Happen Next: Procedural and Rulemaking Considerations

Because the tax is not imposed until January 1, 2027, there is a meaningful window in which the law could change before it ever applies. Setting aside the potential for litigation to challenge the tax, the other potential path is legislative: the Illinois General Assembly can amend, delay, or repeal an enacted statute by passing new legislation, and a novel, first-of-its-kind tax facing organized industry concern is a natural candidate for a follow-up “trailer” bill that narrows its scope, clarifies its mechanics, or pushes back the effective date. Any such change itself would have to move through both chambers and be signed into law, so its timing and content are far from guaranteed. Currently, the only opportunity to do this before January 1, 2027, would be during the November/December Veto Session, a six-day session wherein any legislation passed with an effective date before June 1, 2027 (such as something amending DAPTA) would require a ⅗ majority vote (rather than simple majority).

A retroactive veto, by contrast, is not available. (As a practical matter, we understand that the Governor’s office was the proponent of DAPTA in the first place.) In Illinois, the Governor’s veto powers, including the amendatory veto that lets the Governor propose changes as a condition of signing, operate only during the review window before a bill becomes law, not after it has been signed and enacted. Once a bill is signed, the executive branch cannot unwind it by veto; the Governor’s practical levers are limited to supporting amendatory legislation or shaping how the Department of Revenue implements the law through rulemaking.

That rulemaking process is the other major variable. DAPTA expressly adopts the Illinois Administrative Procedure Act and authorizes the Department of Revenue to adopt implementing rules and forms. Under that Act, a rule generally must clear a First Notice period of at least 45 days that begins when the proposed rule is published in the Illinois Register, during which the public may comment and may request a public hearing within 14 days. The agency then files for a Second Notice period, during which the Joint Committee on Administrative Rules (JCAR) reviews the rule at a meeting scheduled within 45 days, extendable by another 45 days by agreement between JCAR and the affected agency. Rulemaking also carries a one-year completion deadline, and separate emergency rulemaking (effective immediately, up to 150 days) exists if the Department needs to move faster. (Emergency rulemaking can only be used when the Agency determines there is a threat to the public interest, safety, or welfare, not applicable here). Practically, this means the Department must begin the formal process well in advance to have final, enforceable rules in place before the January 1, 2027, effective date, and affected businesses will want to participate during the First Notice comment period to influence the details that the statute leaves open. Although it is best to get comments in as early as possible, comments can still be submitted during the Second Notice period, but they must be submitted to both JCAR and the affected agency. Comments may be submitted on any part of the rule, but the agency cannot promulgate rules that conflict with the statute or exceed their statutory authority. Public comments may be most impactful regarding sections of the rule where the agency has discretion.

Practical Problems with DAPTA

Two statutes, two different definitions. DAPTA borrows its definition of “digital asset” from the Digital Assets and Consumer Protection Act (“DACPA”) but then defines the key operative term, “digital asset business activity,” on its own terms, and the two definitions do not line up. Under DACPA, “digital asset business activity” is broad: it covers exchanging, transferring, or storing digital assets, but also “digital asset administration” and any other activity the regulator designates by rule, and it expressly carves out peer-to-peer exchanges, decentralized exchanges, software development, issuance of a non-fungible token, and running a node. DAPTA’s version is narrower on its face, using the phrase “any single occurrence of exchanging, transferring, or storing,” and it omits both the “administration” prong and, critically, DACPA’s list of exclusions. The practical consequence is real: activities that Illinois deliberately chose not to regulate under DACPA (for example, peer-to-peer or certain decentralized activity) are not clearly excluded from the tax under DAPTA’s text, so a business cannot safely assume that “exempt from regulation under DACPA” means “exempt from tax.” Compounding this, DAPTA defines a taxable “digital asset broker” by reference to the federal Internal Revenue Code’s broker definition rather than to DACPA’s “covered person” or “registrant,” so the population that is regulated and the population that is taxed are drawn with different tools. Businesses will have to reconcile two mismatched definitional frameworks to figure out what is taxed.

Section 3-35(f) puts the tax on people who cannot realistically compute it. DAPTA provides that any person who purchases digital asset business activity on which the tax was not charged must pay the tax directly to the Department by the 20th day of the following month. This is a backstop borrowed from the sales-and-use-tax world, but it fits poorly here. The customer usually has none of the information needed to know whether tax was owed and left uncollected: whether the transaction was properly sourced to Illinois, what the “value of the digital asset” was at the relevant moment, and whether the counterparty was even a registered broker are all facts that sit with the broker, not the customer. Most retail customers will not know this obligation exists, will not receive a statement flagging that tax was omitted, and have no established mechanism to self-remit a 0.2% privilege tax on a crypto transaction. The likely result is widespread, inadvertent noncompliance concentrated among the parties least equipped to detect or cure it, which is an enforceability problem baked into the collection design.

The 12-month look-back is hard to track and internally inconsistent. The remote-seller threshold turns on whether a broker had $100,000 or more in gross receipts from Illinois customers over a rolling 12-month period, tested quarterly at the end of March, June, September, and December. Once a broker crosses the threshold, it must collect, remit, and file for a full year; at the end of that year, it re-tests the preceding 12 months, and if it no longer qualifies it drops back to quarterly testing. This creates several compliance burdens at once. First, a broker cannot even measure the threshold without first solving the harder problem of correctly identifying which customers are “in this State,” a determination governed by a rebuttable presumption based on IP or billing address, with the burden of proof placed on the broker. Second, the cadence itself is confusing: quarterly testing before crossing but annual testing afterward means a broker whose Illinois volume falls can remain locked into collection for a year, and must build systems to track a moving 12-month window on two different clocks. Third, the threshold is measured by “gross receipts from digital asset business activity sales,” while the tax itself is 0.2% of asset value, which are two different measuring sticks that a broker must compute and reconcile in parallel. Determining and documenting all of this in time to register before January 1, 2027, is a substantial system and data-governance undertaking.

Additional problems: valuation, custody economics, and rules that do not yet exist. The single largest practical difficulty is valuation. The tax is 0.2% “of the value of the digital asset,” yet the statute does not define how or when that value is fixed, leaving a serious gap for volatile and illiquid tokens whose price can vary by the second and can differ across trading venues. Crypto’s price volatility and the absence of settled valuation standards are well-documented tax-compliance pain points, and they are acute for a “storing” event, where the statute is unclear about whether ongoing custody is a one-time or recurring taxable occurrence and at what moment the asset must be valued. If a resident “stores” crypto with a custodian like Coinbase, does the resident pay 0.2% of the value of the asset stored each month? Each year? The statute is silent.

Because the tax tracks asset value rather than the fee earned, the burden on custody and high-value transfers can exceed the revenue the broker actually makes on the service, creating pressure to raise prices or exit the Illinois market. The statute’s rule that each service in a bundle is a separate sale adds further line-item complexity. Finally, much of the machinery that would make compliance workable, including how value is to be stated, what forms and records are required, and how sourcing data must be maintained, is left to Department rules that have not yet been written, even though felony-level penalties attach to getting compliance wrong. With the rulemaking process itself requiring months to complete before the January 1, 2027, effective date, businesses face a narrow runway to translate an ambiguous statute into functioning tax-collection systems.

Written by Max Markoff, Michael Frisch

This post is for general informational purposes only and does not constitute legal or tax advice. For further information, contact: Michael Frisch (mfrisch@crokefairchild.com), David Lopez-Kurtz (dlopezkurtz@crokefairchild.com), Tanner Dowdy (tdowdy@crokefairchild.com), Ariella Guardi (aguardi@crokefairchild.com), Bakhtawar Mirjat (bmirjat@crokefairchild.com), or Max Markoff (mmarkoff@crokefairchild.com).