The Variable Nobody Captures: Buyer Type and AI Agent Sales Tax

Most of what is written about AI agent sales tax concerns what is being sold: is the output a service, a digital product, prewritten software, data processing. There is a second variable that decides the answer in a handful of states and gets almost no attention, because in a web checkout it was never in doubt — who is buying. In agent commerce it is frequently unknown at the moment of the transaction, and it is not recoverable afterward.

Yesterday I wrote that Ohio operators should start capturing buyer type. This is the general version of that advice, and the part that makes it more than bookkeeping: the states that care about buyer type do not care in the same direction.

Iowa: the buyer's status is an exemption

Iowa Code § 423.3(104) exempts specified digital products, prewritten computer software, and a list of enumerated services when sold to a commercial enterprise and used exclusively by that commercial enterprise. This is the cleanest of the five rules and the largest in effect: the answer moves from taxable to exempt entirely.

Two conditions carry weight. The purchaser must meet the statutory definition of a commercial enterprise at § 423.3(104)"b"(1) — not merely "a business." And the exclusive-use requirement is real: Iowa Admin. Code r. 701—225.7 provides that use in the ordinary course of the enterprise's business is exclusive use, and that use by anyone else is not. A product bought by an operator and made available to consumers does not qualify because the operator happens to be a company.

Connecticut: two rules that are usually reported as one

Connecticut is where most secondary summaries compress two rules into one. You will commonly read that "Connecticut taxes SaaS at 1 percent for business use and 6.35 percent for personal use." That is a serviceable shorthand for SaaS and a poor description of the statute.

Computer and data processing services are taxable at 1 percent under Conn. Gen. Stat. § 12-408(1)(D)(i), with the service defined at § 12-407(a)(37)(A). That rate does not depend on who is buying. A consumer purchasing genuine computer and data processing services pays 1 percent.

Electronically accessed or transferred canned or prewritten software is the rule with the buyer-type split. P.A. 19-117 raised digital goods and electronically accessed prewritten software to the standard 6.35 percent rate effective October 1, 2019, while retaining 1 percent for prewritten software electronically accessed by a business for business use. DRS Special Notice SN 2019(8) sets this out.

The distinction matters to agent operators specifically, and it cuts in their favor. An operator selling processing output — the agent retrieves, compiles, transforms, returns a result — is selling a computer and data processing service, which sits at 1 percent for every buyer. The 6.35 percent exposure attaches to selling access to the software itself to a consumer. Whether a given agent product is one or the other is a true-object question, and it is the kind of question where the packaging and the substance can diverge. Our 50-state guide carries the per-state detail, including the $100-versus-$635 spread on a $10,000 compute purchase.

Maryland: buyer type reaches the answer through classification

Maryland does not write a B2B exemption. It arrives at a buyer-type split by a different route. Md. Code, Tax-Gen. § 11-104(l)(1) sets a 3 percent rate for data and information technology services in NAICS 518, 519, 5415 and 5132, effective July 2025. But § 11-104(l)(2) mandates the higher rate where the same sale also qualifies as tangible personal property, a digital code, or a digital product.

The practical result is that commercial use of SaaS — used in an enterprise computer system — lands at 3 percent as a service, and individual use lands at 6 percent as a digital product. Same product, same seller, different statutory character depending on the purchaser's use. Maryland also permits a Multiple Points of Use certificate for purchases used inside and outside the state, which shifts apportionment and remittance to the buyer.

Ohio: the mirror image

Ohio is the one that breaks the pattern, and it breaks it completely. R.C. 5739.01(B)(3)(e) reaches automatic data processing, computer services, and electronic information services only when they are provided for use in business. Consumer purchases are not exempt from an otherwise applicable tax; they are outside the imposition.

So in Ohio the business buyer is not the favored party. The business buyer is the only taxable party.

Set the four side by side and the shape of the problem is clear:

• Iowa — business buyer pays nothing.

• Connecticut — business buyer pays 1 percent instead of 6.35, on software; everyone pays 1 percent on services.

• Maryland — business buyer pays 3 percent instead of 6.

• Ohio — business buyer pays; the consumer does not.

• Texas, as the control, does not ask. Tex. Tax Code § 151.351 applies its 20 percent exemption to the value of the data processing service regardless of who bought it.

An operator who implements a single boolean meaning "business buyers get relief" is correct in Iowa, correct in Maryland, correct in Connecticut for software and irrelevant for services, and exactly backwards in Ohio — where that flag would suppress tax on the only transactions Ohio actually taxes, and apply tax to transactions it does not reach. That is not a rounding difference. It is wrong in both directions at once, in the state where the flag looks most obviously applicable.

The part that is specific to agents

Every one of these rules turns on a fact about the purchaser's use, not about the purchaser's legal form. Iowa asks about exclusive use in the ordinary course of the enterprise. Ohio asks whether the service is provided for use in business. Connecticut asks whether a business bought it for business use. Maryland asks whether it runs in an enterprise computer system.

In a web checkout that fact arrives with the buyer. In machine-to-machine commerce it frequently does not arrive at all. The counterparty is another agent, and the use is a fact about the principal standing behind that agent — an entity the seller may never see. The wire carries an address and an amount.

Whether an agent operator purchasing inputs on behalf of a consumer principal is making "business use" of those inputs is a question no state has answered for this fact pattern. There is an argument that the operator's own use is commercial regardless of who benefits, and an argument that the exclusive-use and business-use conditions look through to the ultimate consumer. I am not going to tell you which way Iowa or Ohio will come out, because neither has said, and this is precisely the sort of question where an intermediary structure that was invisible when the statutes were drafted does the work.

What is not in doubt is the operational consequence. Buyer-type facts must be captured at transaction time and substantiated — Iowa's exemption is documentation-driven, and an assertion made eighteen months later during an audit is worth very little. This is a schema decision before it is a tax decision, and it is the kind of field that is cheap to add now and impossible to backfill.

What to watch

The CDTFA S.B. 122 discussion draft remains the top item, still expected by the end of August 2026 and still not circulated as of this morning. It is worth noting what California's 2027 regime does not contain: no B2B exemption, no reduced business rate, no business-use limitation. Neither does Colorado's HB 26-1223. The two largest additions to the taxable base arriving on January 1, 2027 both treat buyer type as irrelevant, which means the five-state pattern above is not a trend — it is a set of legacy accommodations, and the new statutes are not adopting it.

Ohio has issued no guidance on whether agent output delivered to a business is automatic data processing, computer services, or electronic information services. The three categories carry the same rate, so the classification stakes are low today; the business-use line is not low-stakes at all.

As always: no state has issued guidance addressing agent-initiated commerce directly. Every determination above applies a human-drafted category to a machine transaction, which is analysis rather than settled law.

AgentTax models buyer-type rules per state and per category — Iowa's statutory exemption, Connecticut's 1 percent computer and data processing rate, Maryland's service-versus-digital-product split, Texas's 80 percent base — and returns an explicit advisory when a calculation lands in Iowa or Maryland without buyer status supplied, rather than silently assuming one. Ohio's business-use limit is not yet modelled as a per-category rule; that gap is disclosed in the response's source marker and is with our engineering team. See how it works at agenttax.io, or start with our AI agent sales tax hub.

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.