Is SaaS and AI Taxable in Ohio? Yes for Business Buyers, No for Consumers - and Most States Run It the Other Way

Key Takeaway: Ohio taxes SaaS, AI services and data processing at 5.75% plus county rates - but only when they are provided for use in business. A consumer buying the identical service owes nothing, because consumer purchases of those services are not enumerated. That is the reverse of the B2B exemption pattern most states run, and it means the fact that decides your Ohio tax is not what you sold but who is using it and how. Ohio also presumes every sale taxable until you establish otherwise, so an unknown buyer is a taxable buyer.

The Gate Is the Whole Rule

Ohio's service enumeration reaches "automatic data processing, computer services, or electronic information services" - and R.C. 5739.01(B)(3)(e) attaches a condition most guides mention in passing and then fail to apply. The clause, read at codes.ohio.gov today:

"Automatic data processing, computer services, or electronic information services are or is to be provided for use in business when the true object of the transaction is the receipt by the consumer of automatic data processing, computer services, or electronic information services rather than the receipt of personal or professional services to which automatic data processing, computer services, or electronic information services are incidental or supplemental. Notwithstanding any other provision of this chapter, such transactions that occur between members of an affiliated group are not sales."

The implementing rule says the same thing from the imposition side. OAC 5703-9-46: "The provision of automatic data processing services, computer services, or electronic information services in this state for a consideration for use in business by the consumer is a sale that is subject to the sales tax." And the rule defines "business" to exclude personal activity - expressly, "the activity of an individual in managing and investing the individual's own funds."

So the levy has a gate on it. Business use is inside; consumer use is outside, not by exemption but by non-enumeration - a stronger position, because there is nothing to certify and nothing to lose.

What the Statute Actually Covers

The definitions are in R.C. 5739.01(Y)(1), written for a mainframe world and describing machine learning without any interpretive stretching:

• (Y)(1)(a) Automatic data processing: "processing of others' data, including keypunching or similar data entry services together with verification thereof, or providing access to computer equipment for the purpose of processing data."

• (Y)(1)(b) Computer services: hardware configuration, programming and training - but only "provided in conjunction with and to support the sale, lease, or operation of taxable computer equipment or systems." Narrower than it looks.

• (Y)(1)(c) Electronic information services: "providing access to computer equipment by means of telecommunications equipment" either to examine or acquire stored data, or to place data into the equipment for retrieval by designated recipients.

An inference endpoint that takes a customer's documents, runs them through a model and returns structured output is processing others' data. That is (Y)(1)(a) on its face. Ohio did not need to legislate for AI; it already had the category.

Where the Gate Stops - and This Is the Part People Get Wrong

The business-use gate applies only to ADP, computer services, and EIS. It does not travel.

Specified digital products carry no gate. R.C. 5739.01(B)(12) taxes all transactions by which a specified digital product is provided "for permanent use or less than permanent use, regardless of whether continued payment is required." Division (OOO) limits specified digital products to electronically transferred digital audiovisual works, digital audio works, and digital books. Those are taxable for every buyer. A consumer streaming subscription is taxable in Ohio even though a consumer SaaS subscription is not.

Prewritten software carries no gate either. It is defined at (BBB) and sits inside the tangible personal property definition at (WW), taxable regardless of who buys it or how it is delivered.

The trap is a consumer-facing product that ships a deliverable. If your consumer AI product returns a generated audiobook or e-book you have left the services enumeration and landed in (B)(12), where the exemption you relied on does not exist. Note also what (OOO) does not include: a raw dataset is not an audiovisual work, an audio work or a book, and it is not prewritten software. Data sales sit in genuinely unaddressed space in Ohio.

The Unknown Buyer Is a Taxable Buyer

R.C. 5739.02(C) is short and decisive: "For the purpose of the proper administration of this chapter, and to prevent the evasion of the tax, it is presumed that all sales made in this state are subject to the tax until the contrary is established."

That resolves the operational question the gate creates. A seller who cannot tell whether the buyer is purchasing for use in business does not get to pick the exempt side: collect at the business-use rate and let a documented consumer determination turn the tax off. Practically, build buyer-status capture into checkout for any consumer-facing Ohio product - without it the presumption prices every transaction at the business rate.

Sourcing: Ohio Is Not the Origin State You Were Told It Was

Ohio gets shorthand-listed as an origin-sourcing state. The statute is far narrower. R.C. 5739.033(B)(1) sources to where the vendor receives the order only for "retail sales, excluding the lease or rental, of tangible personal property or digital goods," and only when three conditions are met - including that "the record-keeping system used by the vendor to calculate the tax imposed captures the location where the order is received at the time the order is received."

Services are not in that list. SaaS, ADP and EIS follow the destination hierarchy in R.C. 5739.033(C). Your Ohio services take the buyer's county rate, whether you sell from Cleveland or from Lisbon.

Rates - Including a Correction to Our Own

The state rate is 5.75% (R.C. 5739.02(A)(1)). Counties add a piggyback rate plus, in some counties, a transit levy. Ohio administers the locals centrally: one registration, one return. From the Department of Taxation's own published rate table (document dated March 31, 2026, rates in effect as of October 2025):

| County | Metro | County | Transit | Total |
|---|---|---|---|---|
| Cuyahoga | Cleveland | 1.25% | 1.00% | 8.00% |
| Franklin | Columbus | 1.25% | 1.00% | 8.00% |
| Hamilton | Cincinnati | 1.25% | 0.80% | 7.80% |
| Lucas | Toledo | 1.50% | 0.50% | 7.75% |
| Summit | Akron | 0.50% | 0.50% | 6.75% |

Two of those disagree with our own engine, and the honest thing is to say so in the paragraph where I publish the correct number. AgentTax currently computes 7.50% for Columbus and Toledo ZIPs against ODT's 8.00% and 7.75% - both look like pre-increase county rates that were never stepped. The direction is under-collection, which is the expensive direction: an under-collecting seller gets no refund from the customer at audit, it pays out of margin. Rate changes are guardrailed here and cannot be made by the agent that finds them, so a correction is filed for approval rather than shipped. Cleveland, Cincinnati and Akron reconcile exactly.

The Commercial Activity Tax, With Current Numbers

Ohio's separate gross-receipts tax is where dated guidance does the most damage. H.B. 33 restructured it and the numbers most checklists still carry are dead. R.C. 5751.01(R) defines the exclusion amount as "three million dollars beginning in 2024 and six million dollars beginning in 2025." R.C. 5751.03 sets the rate at "two and six-tenths mills per dollar" - 0.26% - applied to taxable gross receipts, and no annual minimum tax appears in that section. Bright-line presence under (I) is $500,000 of Ohio taxable gross receipts, $50,000 of property, $50,000 of payroll, or 25% of total property, payroll, or receipts in Ohio.

On $10 million of Ohio receipts you owe 0.26% of $4 million - $10,400 - not 0.26% of the whole book. A model still carrying a $150,000 threshold and a $150 minimum predates the restructuring and overstates exposure by roughly forty times at the low end.

How AgentTax Handles Ohio

Verified against the live engine while writing this, not from documentation:

• The gate is modeled, and it is explicit-only. An explicit is_b2b=false computes $0 on SaaS, API access, compute, storage, cloud infrastructure, data processing, model access, and subscriptions. is_b2b=true computes 5.75% plus county.

• Omitting the flag does not get you the exemption. A caller who sends no is_b2b is taxed at the business-use rate and receives a B2B_STATUS_UNKNOWN advisory naming Ohio's presumption statute and the flag that releases the tax. This is deliberate: our internal default for is_b2b is false, and in Ohio the false leg is $0, so honoring the default would silently under-tax every caller who forgot the field.

• Digital goods and licenses never take the gate. digital_good and license compute 5.75% plus county for every buyer, including an explicit consumer - which is the (B)(12) and (WW)/(BBB) answer.

• Information services are held taxable for every buyer - a conservative hold, not the law. Research-flagged work computes 5.75% even for a declared consumer, because we cannot yet tell an access-only EIS product from a productized deliverable that would be a specified digital product. Stated plainly: the consumer leg of that hold is a knowing over-collection, and unlike the SaaS path it fires no advisory telling you so. A consumer-facing research product in Ohio has a real exemption argument our engine does not surface.

• Data purchases are also held at the taxable answer for every buyer. data_purchase routes to the digital-goods cell and computes 5.75% even for a declared consumer, though a raw dataset is not on the (OOO) list. Treat that as our conservative posture, not a settled Ohio position.

• Sourcing is scoped correctly. Origin treatment applies only to intrastate license and digital_good transactions, with an OH_ORIGIN_SOURCING_CONDITIONS advisory recording the (B)(1) record-keeping condition. Services stay destination-sourced.

• Coverage is five metros. Cleveland, Columbus, Cincinnati, Akron and Toledo ZIPs resolve to a combined rate; other Ohio ZIPs return 5.75% with a ZIP_UNKNOWN advisory rather than guessing a county. Economic nexus is tracked at $100,000 or 200 transactions.

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

What to Watch

Whether the Department of Taxation ever addresses AI output against the (Y)(1) categories - the boundary between the three has never been drawn for a model that does all three in one call. It changes nothing today, since all three ride the same gate, but it matters the moment one of them is treated differently. Whether the (B)(3)(e) true-object refinement gets litigated for AI: a professional deliverable with automated processing inside it falls outside the levy when the processing is "incidental or supplemental," and nobody has said where that line sits when the processing is the product. And whether the affiliated-group carve-out - intra-group ADP, computer services and EIS transactions are "not sales" - draws attention as enterprises route internal agent traffic through shared platforms.

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.