Is SaaS Taxable in Texas? Yes, at 80% — and the Rule Exempting Professional Judgment Was Rewritten in 2025 to Describe a Human

Key Takeaway: Texas has taxed the substance of AI agent work for decades, under a data processing category that predates the web, and gives every buyer an automatic 20 percent statutory discount on it. The part worth your attention is not the rate. It is the test that separates taxable data processing from untaxed professional service. The Comptroller rewrote that test effective April 2, 2025 — deep into the agent era — and left it resting on the "certified opinion of an accounting professional" and the "opinion or skills of a legal professional." Under the rule as written, an agent that reaches the same conclusion as the accountant does not inherit the accountant's exemption.

The Framework

Texas imposes a 6.25 percent state sales and use tax. Local jurisdictions — cities, counties, transit authorities, special purpose districts — may add up to 2 percent, for a maximum combined rate of 8.25 percent. Most of the Texas economy sits at that cap.

Economic nexus is a safe harbor rather than a threshold. Under 34 Tex. Admin. Code § 3.286(b)(2)(B)(i), the Comptroller will not enforce the permit or collection obligation on a remote seller whose total Texas revenue in the preceding twelve calendar months is under $500,000. No transaction count. That revenue figure includes taxable, nontaxable, and exempt sales across every channel, and you have until the first day of the fourth month after crossing to get permitted.

One definition in that rule matters more than the number. For a service, § 3.286(b)(2)(C)(iii) defines "use" in Texas as "the derivation in this state of direct or indirect benefit from the service." Not delivery. Not where the code runs. Benefit.

SaaS and Agent Work Are Data Processing

Texas does not have a SaaS category. It has a data processing category, defined by Tex. Tax Code § 151.0035 and elaborated at 34 Tex. Admin. Code § 3.330, which the Comptroller amended effective April 2, 2025.

Rule 3.330(a)(1) defines data processing service as "the computerized entry, retrieval, search, compilation, manipulation, or storage of data or information." That sentence covers essentially everything an agent does with a customer's data. Subsection (c)(3) removes the two arguments an operator might reach for first: a charge is taxable "regardless of the ownership of the computer or whether the data is provided by the customer or the customer's authorized designee."

Two of the rule's examples reach agent infrastructure directly. Under (b)(6), internet hosting is taxable data processing when the user stores data on the provider's hardware or processes data on software owned, licensed, or leased by either party — which describes inference on rented capacity. Under (b)(5), effective October 1, 2025, marketplace provider services may themselves be taxable data processing when they involve storing listings, maintaining transaction records, and compiling analytics. Agent marketplaces should read that one twice.

The 20 Percent Rule Is Real, and It Is Narrower Than Advertised

Tex. Tax Code § 151.351 reads in full: "There is exempted from the taxes imposed by this chapter 20 percent of the value of information services and data processing services." It has been on the books since October 1, 1999, and Rule 3.330(c)(4) restates it.

So the effective state rate on data processing is 5.0 percent, not 6.25, and the effective ceiling is 6.6 percent rather than 8.25. On a million-dollar contract in Austin that is a $16,500 difference every year.

The limit is in the second sentence of (c)(4): if the service is also taxable as another kind of taxable service other than an information service, the 20 percent exemption does not apply. Sell something Texas taxes on a different theory and the discount disappears. Digital goods are the everyday case — a data purchase or a software license computes on the full charge, not on 80 percent of it.

The Find: Texas Exempts Judgment, and Describes It as a Person's

Texas's professional services are untaxed, because Tex. Tax Code § 151.0101 enumerates taxable services and does not list them. The operative question is therefore where data processing stops and professional service begins, and Rule 3.330(a)(1)(C)(iv) is where the Comptroller answers it.

The test asks "the extent to which the service provider exercises discretion or judgment in individual applications of the processed data based on knowledge of the physical sciences, accounting principles, law, or other fields of study." Then it gives the two poles. "The routine or repetitive manipulation of data by the seller is a factor suggesting that the data processing activity is not ancillary to another service and should be taxable as a data processing service." Conversely, manipulation "that depends on the external knowledge and discretionary judgment of the service provider in individual applications suggests that the data processing activity is ancillary." And a sentence that closes off the obvious rejoinder: "The provider's skill, experience, or expertise, in processing data or information is not a factor."

The worked examples say the quiet part plainly. Payroll processing is taxable under (b)(1) because it is "the routine and repeated simultaneous application of the same process to different data." Preparing financial statements is not taxable under (b)(3) because characterizing the data "depends upon the discretion and certified opinion of an accounting professional." Inserting data into loan documents is taxable under (b)(4); preparing a title opinion is not, because "the result is solitary and depends upon the opinion or skills of a legal professional."

Line those up and Texas's exemption is not really for judgment. It is for a credential. The exempt side of every example is occupied by a certified accountant or a lawyer producing a solitary result. The taxable side is defined by repetition at scale — which is not a description of what agents do badly. It is a description of what they are for.

This is the newest state record we have read this quarter that was drafted around an assumption no longer holding, and the first where the assumption is a person rather than a denominator. The Comptroller had this rule open in March 2025 and reissued it with the accountant and the lawyer still standing in it. None of which makes the professional-service argument unavailable. It makes it uphill, and it tells you exactly what you would have to show.

Sourcing: Texas Splits the Receipt, and Hands the Job to the Buyer

Rule 3.330(g)(1) repeats the benefit definition: "use" means "the derivation in Texas of direct or indirect benefit from the service." From there, (g)(3)(B) is unambiguous — a data processing service performed in Texas for use both inside and outside the state "is exempt to the extent that the service is used outside Texas."

The mechanism is in (g)(6). A purchaser asserting use at business locations in multiple states may issue the provider a Comptroller form asserting concurrent multistate business use and representing that it will report and pay tax on the taxable portion. Under (g)(6)(A) that purchaser "may use a reasonable and consistent method supported by its business records to allocate the service between its business locations." A provider accepting the certificate in good faith is relieved of collection. Subsection (h)(3) runs the same machinery for multi-city benefit inside Texas.

Two things distinguish this from every other apportionment regime we have examined. First, the burden runs the other way: New York's bulletin directs the seller to split a single receipt across user locations, while Texas puts the certificate, the method, and the liability on the buyer. Second, the denominator is neither seats nor employees. It is "business locations" — a better fit than headcount for a customer with offices, and no fit at all for a customer whose consumption is an API key and whose benefit is derived wherever its own users happen to be. Texas at least defines the thing being apportioned as benefit rather than bodies. It simply assumes the benefit lands somewhere with an address.

How AgentTax Computes Texas

Verified against the live engine this morning, $1,000 into Texas.

• Compute, API access, SaaS, agent labor, model access, hosting, and storage all resolve to data processing and compute on 80 percent of the charge. An Austin buyer returns $66.00 — 8.25 percent applied to $800 of $1,000 — and Houston, Dallas, and El Paso return the same. The response states the taxable base and the § 151.351 basis rather than just the number.

• Data purchases and software licenses compute on the full charge — $82.50. That is the (c)(4) carve-out working as written, not an inconsistency.

• Consulting computes as a taxable digital service, and Texas is the state where that hold is best supported. Our engine has routed agent consulting away from the professional-service exemption since April 2026, reasoning that there is no licensed practitioner behind it. Everywhere else that has been a conservative judgment call on our part. Rule 3.330(a)(1)(C)(iv) and its examples are the first primary text we have read that says the same thing in a state's own words.

• San Antonio is missing from our ZIP table. A 78205 calculation returns the 6.25 percent state rate and a ZIP-unknown advisory, where the city sits at 8.25 percent. It fails visibly, which is the right failure, but the seventh-largest city in the country deserves an anchor.

• A calculation with no ZIP at all returns the bare state rate and raises nothing. An unrecognized ZIP warns; an absent one is silent. We found this in New York yesterday and took it for a New York artifact. It is not — it is the engine's default everywhere, and it belongs on the backlog as such.

• We do not apportion, and Texas is where that costs least. One destination state, one answer. Because Texas puts allocation on the purchaser's certificate rather than the seller's invoice, our number is the right starting point for a single-location buyer and an explicit floor for a multistate one.

Try it on your own transaction types. Run a Texas data processing transaction now (no account), or get a free API key. Compare Texas against the 50-state SaaS taxability guide and the AI agent sales tax hub, see the data processing category beside Ohio's, and see the buyer-side allocation rule against the seller-side one in New York and Maryland.

What to Watch

Whether the Taxpayer First Project touches Rule 3.330. The Comptroller's commitment to govern data processing through public rulemaking rather than internal directives is the mechanism that would surface an agent-specific reading of the ancillary test, and the April 2025 amendment shows the rule is not frozen. The question any future amendment has to answer is whether discretionary judgment is a property of a reasoning process or of the person performing it. Texas has never had to choose, because until recently the two were the same thing.

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.