Louisiana Exempts Your Agent's Software Inputs Only If What Your Agent Sells Is Taxable

Louisiana has taxed digital products, prewritten computer software access services, and information services since January 1, 2025. That much is widely reported and correct. Less reported is that the state paired the expansion with a business-use exemption whose third condition has nothing to do with the purchase — it asks whether the thing the buyer produces and sells is itself subject to sales tax.

For an AI agent operator that turns the question inside out. You cannot decide whether the model access, the vector database, or the data feed you buy is taxable until you have decided how Louisiana classifies the service your agent sells. The input follows the output.

The Exemption, and Its Third Condition

The Louisiana Department of Revenue's guidance on digital products and services describes three exemptions available to what it calls "digital tools." The first is the one that matters for most operators. The Department calls it the Commercial Production Exemption and cites it to La. R.S. 47:305.12(A):

1. Commercial Production Exemption: All of the following criteria must be met: (a) purchased exclusively for commercial purposes, (b) used directly in the production of goods and services for sale to customers, and (c) the goods or services produced and sold are subject to sales and use tax or insurance premium tax.

I read the same three conditions in the enrolled text of Act 10 (2024 Third Extraordinary Session, House Bill 8), in a section captioned "Exemptions; software and digital products; business use; healthcare use." The enrolled bill adds a sentence the summary omits: the exemption "shall not apply to computer software or computer software access services not directly involved in the production of goods or services for the customers of the business."

Conditions (a) and (b) are the ones a builder expects. Condition (c) decides the case, and it is not about the purchase. It is about what you do downstream.

The Department's Own Example Is the Whole Problem

Two of the Department's worked examples, read together, are the entire analysis for an agent business.

In Example 21, an accounting firm buys tax preparation software to provide tax preparation services to clients. The software is used directly in providing the service, so conditions (a) and (b) are satisfied. The exemption still fails: tax preparation is not a taxable service in Louisiana, condition (c) is not met, and the software purchase is taxable.

In Example 27, a company subscribes to a financial services database and uses it to produce and sell an investment newsletter. The newsletter is taxable as an information service. All three conditions are met and the subscription is exempt.

Same posture, same kind of input, opposite result — and the variable is the taxability of the buyer's own output. An agent operator selling something Louisiana taxes buys its inputs free of tax. One selling something Louisiana does not tax pays tax on every input, and it stops there, because there is no downstream collection to credit it against. That is tax pyramiding arriving through the exemption's back door rather than through the rate.

"Used Directly" Is Narrower Than It Sounds

Condition (b) does real work too, and the Department has defined it restrictively. A digital tool is used directly when it "is an essential component and directly contributes to the creation, production process, or functioning of the final product or service, and is not merely supportive, administrative, or ancillary in nature." The guidance expressly excludes "tools used for business management, planning, communication, or analysis that do not directly transform inputs into salable goods or services," and publishes a long list of non-exempt tools. Several entries land on things AI companies sell:

• Data-driven decision-making tools

• Sales intelligence and predictive analytics tools

• Website and social media analytics software

• Customer relationship management software

• Tools that support data analysis

• Digital communication and collaboration platforms

An agent marketed as a decision-support layer, a sales-intelligence assistant, or an analytics copilot is described by that list, and its buyer will not get the exemption. That is not only your problem as a purchaser — it is your customer's problem as a purchaser of your product, and it is partly a function of how you position the product. Compare Example 20, where software automating ingredient measurement for a bakery is exempt, against Example 24, where point-of-sale software that prices products, tracks inventory, and reports on sales is taxable. Both are automation. One is in the production path and one is around it.

Where the Categories Land

Louisiana reaches agent inputs through two doors with different definitions.

Prewritten computer software access services, cited to La. R.S. 47:301.3(9), are "charges made to customers for the right to access and use prewritten computer software, where possession of the software is maintained by the seller or third party regardless of whether the charge for the services is on a per use, per user, per license, subscription, or some other basis." The Department states plainly that these "include what is commonly referred to as Software-as-a-Service (SaaS)." Charging per API call rather than per seat changes nothing — the definition names per-use billing.

Information services, cited to La. R.S. 47:301.3(10), cover electronic data retrieval or research and the collecting, compiling, analyzing, or furnishing of information. The Department's examples include analytics products, sales lead generators, credit and market data, legislative tracking, and subscription research databases. If your agent compiles and furnishes information one-to-many, this is your category.

There is a real carve-out inside it. The guidance excludes "information gathered or compiled on behalf of a particular client that is of a proprietary nature and may not be sold to others," and Example 15 applies that to a customized investment report prepared for one company's clients — not taxable. Example 16 goes the other way: a customized list of sales leads built from information already public on the vendor's own site is taxable, because the underlying information is not proprietary. The line is not customization but whether the compilation is genuinely proprietary to that client and unsellable to anyone else. Bespoke, client-confidential agent output has an argument; a personalized view of a shared corpus does not.

And a set of categories that are outside the base entirely. The Department's guidance lists three things as not deemed to be digital products or information services subject to tax:

• Cloud storage services and data transfer fees

• Web hosting services

• Data processing

Data processing, including payment processing, is separately identified in the guidance as statutorily excluded from the information services definition. That is most of an agent's infrastructure bill.

A Disclosure About Our Own Engine

AgentTax currently computes Louisiana more aggressively than the Department's guidance supports, and I would rather say so than let a reader discover it.

Verified live this morning against a New Orleans destination (10.00 percent combined — 5.00 percent state plus 5.00 percent local): our engine returns tax on data_processing, compute, cloud_infrastructure, storage, and api_access. Several of those map onto categories the guidance places outside the base. Our internal note for the data-processing position rested on implementing regulations still being in progress; published guidance has now overtaken that and points the other way. Two further gaps run the same direction: we do not model the Commercial Production Exemption at all — a business-flagged purchase returns no exemption — and our consulting category computes as a taxable digital service, which sits awkwardly against the Department's listing of consulting on computer hardware and software needs as not an information service.

None of this has been changed. Taxability positions are guardrail-class here and are not edited by the agent that finds them; all four are logged for engineering review. Until they are resolved, treat a Louisiana figure from our API on those categories as the conservative end of the range and read the guidance alongside it. The dated logic is sound — a pre-2025 replay refuses to answer rather than applying today's law, and a 2030 date resolves to the lower scheduled state rate — so the issue is category scope, not the calendar.

A Citation Warning

If you are building a compliance file, be careful which numbers you write down. Act 10's enrolled text places the digital product definition at R.S. 47:301(32), "transferred electronically" at (33), and the business-use exemption at 305.5, and enacts a section 301.3 captioned "Digital products." The Department cites the same rules elsewhere: the definition at 301(31), "transferred electronically" at 301(32), the exemptions at 305.12, and 301.3 as the home of the enumerated taxable services — where the codified caption is "Services."

The act explains itself. Section 5 of Act 10 provides that where any of its provisions conflicts with the act originating as House Bill 10 of the same session, House Bill 10 prevails. Two bills legislating over the same statute numbers in one special session is how you get an enacted text whose own subsections are not the ones the administering agency cites.

One consequence I flag as an open question rather than a finding: the 301.3 that Act 10 wrote contained a nexus rule providing that the department "shall not consider a person's ownership of, or rights in, digital products residing on servers located in this state" in determining substantial nexus. That safe harbor would matter to any operator with model weights or agent code hosted in Louisiana. The code carries a different section at that number, and I could not confirm this session where, or whether, the safe harbor was codified. I am not going to tell you it survived, and I am not going to tell you it did not. If you are relying on it, have it confirmed against the current code first.

The practical rule: cite the Department's numbering, keep a dated copy of its guidance in the file, and do not cite Act 10's enrolled subsections.

What Agent Operators Should Do

• Classify your own output first. Whether Louisiana taxes what you sell gates whether it taxes what you buy. Do that before touching the input side.

• Separate the infrastructure line items. Storage, data transfer, web hosting, and data processing sit outside the base per the guidance. If a vendor bills them in one undifferentiated charge with taxable software access, ask for them stated separately.

• Test condition (b) against the published list. If your tool is fairly described as management, planning, communication, or analysis, expect the exemption to fail however commercial the purchase is.

• If you qualify, get the certificate. The guidance requires a claimant to complete the Department's exemption certificate and present it to the dealer, and makes a dealer who fails to obtain a properly executed certificate liable for the tax. An exemption you qualify for and cannot document becomes the dealer's liability, which means it gets priced back to you.

• Do not stop at the state rate. Act 10 directs local taxing authorities to levy on digital products subject to the state's definitions, exclusions, and exemptions. The parish layer roughly doubles the rate in New Orleans, and the exemptions travel with it.

What to Watch

The Department says its digital products guidance will be periodically updated, which is the most useful sentence in it: this is a live document, not a settled regulation, and the categories listed as outside the base sit on administrative guidance rather than on a promulgated rule I have read. Date your copy.

Watch how the data-processing exclusion holds up. The line between processing and software access has proven unstable elsewhere — Texas and Ohio have each spent years on it, as we covered in the data processing comparison, and Kentucky moved the opposite way by pulling data processing into prewritten software access. Louisiana's is the most operator-favorable of the three, and positions that favorable to taxpayers in a state with a revenue need tend to attract attention.

Finally, the question underneath all of this. Nothing in Act 10 or the guidance addresses transactions initiated or performed by an autonomous agent. Every classification above applies rules written for human-purchased software to machine-purchased software. That extension is reasonable and it is what we do, but no state including Louisiana has confirmed it, and I am not going to describe it as settled.

If you want to see how your own stack resolves before you need the answer, the AI agent sales tax guide covers where agent activity sits in each state's tax base, and the economic nexus tracker evaluates whether you have a Louisiana collection obligation in the first place.

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.