Is SaaS Taxable in Missouri? No, and Neither Are Downloads. The Line Is a Physical Medium.

Key Takeaway: Missouri does not tax SaaS, and it does not tax software delivered by download either. The Department of Revenue's software rule says so in plain words: "The sale of software as a service is not subject to tax." Tax applies only to canned software "delivered in a tangible medium." For an AI agent business, the question in Missouri is not where the code runs, as it is in Kansas, but whether anything physical changes hands. And since 2016 the state constitution has barred Missouri from extending its sales tax to a service that was untaxed on January 1, 2015.

What I Read

This guide rests on the current text of RSMo 144.020 (the imposition section), 144.010 (definitions), 144.605 (remote seller definitions, including the economic threshold) and 144.610 (use tax), all from the Missouri Revisor of Statutes; on the Missouri Constitution, article X, section 26, and article IV, sections 43(a) and 47(a); and on 12 CSR 10-109.050, Taxation of Software, read in full, including all twelve of its examples. The rule was last amended effective July 2014. I found no later rule replacing it.

SaaS: Not Taxed, and the Rule Says So

RSMo 144.020.1 levies the tax "upon all sellers for the privilege of engaging in the business of selling tangible personal property or rendering taxable service at retail in this state." The taxable services are a short list: admissions, utilities, telecommunications, telegraph, meals and lodging, intrastate transportation, and rentals of tangible property. Software access is not on it.

Many states leave you to infer the SaaS answer from that kind of structure. Missouri states it outright. 12 CSR 10-109.050(2)(C) defines software as a service as "on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services)," and says the term "includes platform as a service model, infrastructure as a service model, and similar service models." Section (3)(I) then says: "The sale of software as a service is not subject to tax."

The definition is broad enough to cover most agent products as they are sold today: a hosted agent, a model API, a GPU rental billed by the hour, a vector store. One limit matters: the definition "does not include any service model that gives the purchaser the right to use specifically identified tangible personal property." In my reading, a dedicated, named server leased to one customer starts to look like a rental of tangible property, which 144.020.1(8) taxes. Pooled capacity does not.

The same subsection also puts a cost on the seller: "The service provider must pay sales or use tax on any tangible personal property used to provide the service that is purchased or used in Missouri." Servers you buy for a Missouri data center are taxed when you buy them, even though your customers pay nothing.

Downloads Are Not Taxed Either

This is where Missouri differs from Kansas next door, which treats prewritten software as tangible property however it is delivered. Missouri does not. Section (3)(A): "Tax applies to the sale of canned software delivered in a tangible medium to the purchaser." Example (4)(A) applies it: "The sale of video games on disk is subject to tax. The sale of video games by electronic download is not subject to tax."

Two more examples mark the line, and both are worth keeping in front of anyone who ships a desktop agent:

• Example (K): software delivered "through an electronic transfer" with a copy also mailed "on a compact disk" is taxable.

• Example (L): software delivered electronically with only an instruction manual mailed is not taxable.

So a downloadable CLI, a local model runner or a plug-in is not taxed in Missouri. The same product on a USB stick is. Do not ship physical media you do not need to. Our September post on LR 8405 covers a ruling in which a disc was held to be a mere means of conveyance. That ruling involved records, not software, and the software rule's examples still treat a disk as decisive.

Licenses added later. Under section (3)(G), additional licenses sold after an original tangible-medium sale are not taxed if "no additional transfer of tangible personal property" occurs, "unless the sale was part of the original transaction." Section (3)(H) is the trap: "Any future periodic payments required to continue to use software purchased on a tangible format are subject to tax."

Custom Work and Maintenance

Custom software is not taxed, but the definition is narrow. Section (1) treats customized software, "where the true object or essence of the transaction is the provision of technical professional service," as a nontaxable service. Section (2)(B) takes a lot out of that category: "minor changes to canned software will not be sufficient," software "unique to a special industry" does not qualify, and "software that is sold in modules will not qualify." Section (2)(A) adds that software "may be canned even if it requires some modification, adaptation, or testing to meet the customer's particular needs."

Modifications. Section (3)(D) treats programming changes that adapt canned software to a customer's equipment or business processes as "fabrication or production labor that are a part of the sale," and therefore taxable. Example (4)(F) carves out new interfaces and custom reports "not provided by the canned software," which are not taxed "if separately stated." A fine-tuning engagement belongs on its own invoice line, described as what it is.

Maintenance contracts turn on the medium too. Section (3)(F): a mandatory maintenance agreement for canned software "provided on a tangible medium" is taxable whether or not the charges are separately stated. An optional agreement is taxable only if it provides updates "delivered on a tangible medium." Updates pushed over the network fall outside both rules.

Data Processing, Outputs and Information Services

None of these is an enumerated service, so none is taxed. The statute also reaches the point directly for computer output. RSMo 144.010.1(13)(ii) says that selling "computer printouts, computer output or microfilm or microfiche" so that a purchaser can obtain "the desired information" contained in them "shall be considered as the sale of a service and not as the sale of tangible personal property." That text predates AI by decades, but in my reading it is the closest statutory description of what a research or analysis agent sells: information delivered as output. See our Missouri information services page.

Why This Is Unlikely to Change Soon

Article X, section 26 of the Missouri Constitution, adopted November 8, 2016, provides that state and local sales and use taxes "shall not be expanded to impose taxes on any service or transaction that was not subject to sales, use or similar transaction-based tax on January 1, 2015." SaaS and electronically delivered software were untaxed on that date: the current text of the software rule took effect in July 2014. On its face, section 26 keeps the legislature from taxing them by statute.

Voters were asked to loosen that in August and declined by a wide margin; see Missouri Voters Reject Amendment 5. Any expansion now needs another constitutional amendment.

Rates, Remote Sellers and Buyers

Rates. The 4% in 144.020.1 is not the whole state rate. The constitution adds "one-eighth of one percent" for conservation (art. IV, §43(a)) and "one-tenth of one percent" for parks and soils (art. IV, §47(a)), for 4.225%. Local taxes come on top.

Sellers. RSMo 144.605(2)(e) reaches a seller whose "gross receipts from taxable sales from delivery of tangible personal property into this state in the previous calendar year or current calendar year" exceed $100,000, tested quarterly on a trailing twelve-month basis. The test counts taxable sales of tangible property. A seller whose Missouri revenue is all SaaS and downloads accrues nothing toward it. A seller who also ships hardware does. Physical presence is a separate route to nexus and is not affected.

Buyers. The use tax in RSMo 144.610 applies to "storing, using or consuming within this state any article of tangible personal property." A Missouri company buying SaaS or downloaded software from an out-of-state vendor owes no use tax on it. A disk-delivered product bought from a vendor that does not collect is another matter.

How AgentTax Handles Missouri

I ran the engine today for a Missouri business buyer on a $1,000 purchase, using St. Louis City ZIP 63101 (9.515% combined).

• $0: saas, api_access, ai_model_access, ai_labor, compute, data_processing, storage, cloud_infrastructure, data_purchase, digital_good, license, consulting, subscription, web_hosting, payment_processing_fee, it_support and marketplace_fee. All are answered by a category rule, not a fallback.

• Software maintenance: $0 with no contract facts. Send maintenance_contract with update_delivery: "tangible" and a contract that includes updates and it returns $95.15, the section (3)(F) answer. The field accepts "tangible" or "electronic". Other spellings are ignored.

• Custom software: an attested custom build returns $0. If you declare is_modification_of_prewritten: true, the engine taxes the modification at the full rate even when the work is separately stated and delivered electronically. That is a conservative choice under section (3)(D), and it may overstate the tax on an Example (F)-type interface build.

What the engine does not model: canned software sold on a physical medium. A license call assumes electronic delivery and returns $0. If you ship disks or drives into Missouri, that sale is taxable and you should not rely on the $0.

Our rate table carries seven Missouri ZIPs, including Kansas City (9.645%), Columbia (7.725%) and Springfield (7.805%). Any other ZIP returns the 4.225% state rate with a ZIP_UNKNOWN advisory, which matters only for the taxable sales above. For sellers, the engine returns $0 with NEXUS_NOT_CONFIGURED until Missouri is set in your nexus configuration. To run the numbers, use the playground or the AI agent sales tax API. For the contrast with a state that taxes downloads, see Is SaaS taxable in Kansas?, and for marketplaces, see our post on Missouri LR 8408. For other states, see the 50-state SaaS guide.

What to Watch

First, whether the Department rewrites 12 CSR 10-109.050. It is more than a decade old, and agent products test its edges, especially the "specifically identified tangible personal property" limit on the SaaS definition as dedicated inference hardware becomes common. Second, any new effort to amend article X, section 26. Until one passes, the useful question for an agent seller in Missouri is whether anything you sell arrives in a box.

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.