Oklahoma sales tax on SaaS: what a 2026 letter ruling shows
On September 8, 2026, the Oklahoma Tax Commission's Tax Policy Division issued Letter Ruling LR-26-012. The requester sells a hosted, web-based platform that governmental entities and other organizations use to track surplus property. Customers log in through a browser. Nothing ships on a disc or a drive. They pay monthly or annual subscriptions, and the vendor also offers implementation, configuration, training and support.
The ruling is short, and it answers the Oklahoma sales tax on SaaS question for that one vendor on those facts. That's exactly why it's useful. It shows what the Commission looked at, which rules it reached for, and what it declined to decide.
Software vendors and their Oklahoma customers carry a set of beliefs about how this works. Some hold up. Some don't. We'll take six of them in turn.
Belief 1: "SaaS isn't software, it's a service, so sales tax doesn't apply"
Half right, for the wrong reason.
The ruling didn't treat the subscription as a nontaxable service. It treated it as a sale of prewritten computer software, which Oklahoma defines as tangible personal property under 68 O.S. §1352. Prewritten software, in the Commission's rule at OAC 710:65-19-52, is software not designed and developed to a specific purchaser's specifications. A standardized platform every customer uses fits that definition, and the requester described its product in just those terms.
So the subscription starts out inside the levy in 68 O.S. §1354. What takes it back out is a specific exemption: 68 O.S. §1357(32), which exempts sales of prewritten computer software delivered electronically. The Commission concluded the subscriptions were exempt from sales tax on that basis.
The distinction matters. If your position is "it's a service," you're arguing the transaction never entered the tax base. If your position is "it's electronically delivered prewritten software," you're claiming an exemption, and the vendor claiming an exemption carries the burden of documenting it. The second framing is the one the Commission actually used.
A practitioner's observation: the rule at OAC 710:65-19-52 addresses software on tangible media and "load and leave" delivery, but it never directly addresses purely electronic delivery. The electronic-delivery language lives in the statute and in the internet-transactions rule, OAC 710:65-19-156, which lists prewritten software delivered by means other than tangible storage media among transactions not subject to tax. Knowing which rule to open is half the work when an auditor asks why you didn't charge tax.
Belief 2: "The OTC has now settled Oklahoma sales tax on SaaS for everyone"
No. It ruled that this requester's subscriptions, as described in an August 20, 2026 request, are exempt.
Letter rulings in Oklahoma are informal written statements of how specific facts are treated. Under OAC 710:1-3-73(e), a ruling may generally be relied on only by the entity to whom it is issued, and only if all pertinent facts were accurately and completely stated and the law hasn't changed. LR-26-012 says the same thing about itself, and adds that it may not be relied on in connection with prior audits or protests.
The same rule, at subsection (g), notes that a letter ruling affecting broad groups of taxpayers may become the basis for a Commission rule. It hasn't, as of this writing. Until it does, a competitor with a similar product is reading someone else's mail. We've written separately about how letter rulings differ from rulings that bind, and the short version is that a published ruling tells you how the Tax Policy Division thinks, not what you're entitled to.
That said, the reasoning is transferable even if the reliance isn't. The analysis ran: standardized product, no tangible media, no transfer of ownership, access over the internet. A vendor whose facts match on every point has a strong position. A vendor whose facts differ on any point has a question, not an answer.
Belief 3: "Implementation, training and support are taxable services we have to break out"
Oklahoma vendors often assume that if the software is exempt, the surrounding services must be analyzed separately and probably taxed. LR-26-012 went the other way.
The Commission stated that electronically delivered prewritten software is exempt "along with any services associated with the sale," and answered the requester's question about separately stated implementation and configuration charges by concluding they were exempt. It gave the same answer for training and support, without analyzing each service type on its own.
That's consistent with the computer rule. OAC 710:65-19-52 treats training services as not taxable, and optional maintenance contracts covering only support services as not taxable. The rule does tax written training materials, and it taxes optional maintenance contracts that bundle updates on tangible media with support when the support charge isn't separately stated.
Here's the government-favorable side. The services were exempt because they rode with an exempt sale. Change the anchor and the services can change with it. If the software itself were taxable, say because it shipped on media or came bundled with hardware, a mandatory maintenance contract would be taxed with it under OAC 710:65-19-52(d), and an unseparated support charge attached to tangible-media updates would be too. Separate statement on the invoice is cheap insurance regardless of which way the anchor falls.
Belief 4: "We don't sell anything taxable, so we don't need a permit or records"
Two different conclusions hide in that sentence, and the ruling split them.
On the permit, the Commission agreed the requester wasn't required to obtain a sales tax permit solely because it sells these subscriptions, provided it isn't making sales subject to Oklahoma tax. The rule it cited, OAC 710:65-9-1(a), ties the permit requirement to making taxable sales. No taxable sales, no permit trigger.
Records got no such pass. It told the requester to keep complete books and records of all sales and purchases, not just taxable transactions, and to distinguish taxable from nontaxable receipts. That's OAC 710:65-3-30, and it applies to the vendor whether or not a permit exists.
Why does the recordkeeping duty survive when the permit duty doesn't? Because an exemption is a conclusion about each sale, and an auditor who can't see the sales can't confirm the conclusion. The vendor with zero taxable receipts still has to prove the zero. In our experience, a company that has never held a permit tends to have never built a sales tax ledger either, and the first records request is where that shows.
What an auditor is likely to want to see
Based on the rules the Commission cited, a reasonable records posture for a hosted-software vendor includes the subscription agreements showing access rights rather than ownership, invoices that separately state software, implementation, training and support, documentation that no tangible media or hardware was delivered, and a ledger that classifies every receipt as taxable or nontaxable with the reason. The ruling doesn't prescribe that list. It describes the duty, and the list follows from it.
Belief 5: "Hardware, media or a custom build doesn't change anything"
The requester apparently understood that it might, because it carved hardware out of the request. The ruling expressly does not cover future sales of computers, tablets, printers, scanners, labels or other hardware.
Under OAC 710:65-19-52, computers and components are taxable on sale and on rental. Prewritten software on tangible media is taxable. So is load-and-leave delivery, where the vendor brings the media, installs, and leaves without handing it over. And when prewritten software is bought with a computer, the software charge is taxable along with it.
The internet-transactions rule reinforces this from the other direction. OAC 710:65-19-156 says goods and services sold over the internet are taxed the same way they would be through any other channel, and it lists tangible goods sold or shipped into Oklahoma and prewritten software transferred on physical media as taxable even when the internet facilitated the sale.
Custom software is its own category. OAC 710:65-19-52(g) treats a program prepared to a customer's special order as a service, not taxable. Modifications to prewritten software can escape the prewritten category if the charge is separately stated and reasonable, but if a computer is bought with custom software and the software charge isn't separately stated, the entire purchase price is taxable. The general made-to-order rule, OAC 710:65-19-60, taxes the total receipts when materials are fabricated into tangible personal property to special order, with no deduction for labor. It doesn't mention software, which is another reason the computer-specific rule is the one to read first.
Picture the hosted platform as the exempt core. Every physical thing you attach to it, a barcode scanner or a USB drive with an installer, is a potentially taxable layer, and the invoice has to make the layers visible or the Commission may treat the whole thing as one taxable sale.
Belief 6: "Government and nonprofit customers mean we don't have to think about any of this"
The requester's customers include Oklahoma municipalities, counties and other governmental entities, plus nongovernmental organizations. It asked about the governmental customers specifically and about what exemption documentation to keep.
Here the Commission concluded that sales to qualifying governmental entities were exempt under the same reasoning it had already applied. Notably, it did not specify what documentation the vendor should obtain or retain, even though the question asked.
Read that carefully. The exemption the Commission relied on was the electronic-delivery exemption, which turns on what's sold and how, not on who's buying. The customer's governmental status was an alternative path the Commission didn't need to walk down. For a vendor, that cuts both ways. If a future sale includes something taxable, such as hardware, the vendor would need to establish the customer's exemption on its own terms and hold whatever documentation supports it. The ruling doesn't do that work for anyone.
Nonprofit customers deserve a separate caution. Nongovernmental status alone tells you nothing about Oklahoma sales tax exemption, and the ruling made no finding about those customers beyond applying the same product-based exemption.
The customer's side of the invoice
Most of this reads from the vendor's chair. Oklahoma customers of hosted software have their own exposure, in two directions.
If a vendor charges Oklahoma sales tax on a subscription that qualifies for the electronic-delivery exemption, the customer has paid tax that may not have been due. Recovering it generally runs through a refund process with its own time limits, and the vendor's cooperation is usually needed.
Suppose instead a vendor doesn't charge tax on something that was taxable, such as hardware shipped with the subscription or software on media, the Oklahoma customer may owe use tax on the purchase. OAC 710:65-19-156(d) points vendors toward the Use Tax Code for collection and reporting duties, and the customer-side duty exists independently of what the vendor did. Customers who run a use tax accrual review should flag any software vendor invoice that includes physical items.
One more point for customers. Under OAC 710:65-19-156(d), operating an online service or maintaining a website does not, by itself, give an out-of-state vendor a physical connection with Oklahoma sufficient to require registration. The rule is older than the current remote-seller framework and doesn't resolve economic nexus questions, so a customer shouldn't assume an uncollected invoice from an out-of-state SaaS vendor means the vendor had no duty.
Where the facts decide it
Strip the ruling to its load-bearing facts and you get five: a standardized product, hosted by the vendor, accessed over the internet, with no tangible media and no transfer of ownership. The Commission's conclusion followed from those facts through §1352, §1354 and §1357(32).
The gap between "delivered electronically" and "accessed remotely" is where real disputes live. The statute exempts delivery by electronic means. The requester never delivered anything in the ordinary sense; customers logged in to the vendor's servers. The Commission treated that as within the exemption on these facts, without a separate discussion of whether remote access is delivery. A different fact pattern, say a downloadable client that installs locally alongside the hosted service, or a data processing arrangement where the vendor manipulates customer data under OAC 710:65-19-86, may get analyzed under a different rule and reach the same or a different result.
In our experience, the transaction that most often goes wrong is the mixed one: a subscription, a scanner, an installer on a drive, onsite training with printed manuals, all on one invoice with one price. Every component has a defensible treatment on its own. Bundled and unseparated, the vendor has handed the Commission the argument that the whole thing is taxable.
If your company sells hosted software into Oklahoma, or buys it, and the invoices mix software with hardware, media or onsite work, that's a good moment to have someone read the agreements and the ledger together. We're glad to do that through our contact page or our Oklahoma City office. A conversation about how the invoice is built is almost always cheaper than rebuilding it under audit.
Sources
- Oklahoma Tax Commission Letter Ruling LR-26-012 (September 8, 2026) — News hook; hosted software subscriptions, implementation, training, permit, records
- OAC 710:65-19-52 Computers (hardware, software, maintenance contracts)
- OAC 710:65-19-156 Internet-related services and transactions
- OAC 710:65-19-86 Electronic data processing services
- OAC 710:1-3-73 Opinions and letter rulings
- OAC 710:65-19-60 Made-to-order and custom sales
This article is general information about Oklahoma, Texas, and federal law, not legal advice, and it does not create an attorney-client relationship. Facts matter; talk to a lawyer about yours.