Samantha Breslow discusses how the sluggishness of legislation does not often adjust itself to the speed and terminology of technology. However, there are a few states that are adapting to overcome the discrepancies. Download a PDF of the full article here.
Debugging the (State Tax) Code: Outdated Sales Tax Terminology
Technology is moving faster than state legislatures can react — much faster. The lag in a proactive response means that states generally still define the taxability of software in rigid, outmoded terms, such as canned or custom, and place too much significance on the delivery of the software, whether by electronic download or via load and leave. These terms were largely adopted by states grappling with a lack of guidance and seeking to compartmentalize software as either tangible personal property or services. However, the terms lack the nuance and sophistication to properly distinguish evolving types of software, including cloud-based software.
Although there are numerous deficiencies in state legislation, this article focuses on two key examples of outmoded terminology in state tax legislation and anticipated efforts by states to address these uncertainties.Read More
I. Do the Terms ‘Canned’ and ‘Custom’ Still Hold Weight?
A. Overview of the Terms
Most states follow the basic precept that canned software is subject to sales tax, and custom software is excluded as a nontaxable service. The concept behind the distinction is most states’ attempt to compartmentalize software as either tangible personal property or a nontaxable service. Whereas canned computer software is generally treated as taxable tangible personal property, the sale of customized software programs is instead treated as the sale of a nontaxable service. As states grappled with defining the taxability of software, this simplified view was intended to provide clarity.
However, the distinction between canned and custom software is tenuous. Most states generally define custom software as software designed and developed by the author or other creator to the specifications of a specific purchaser. However, this is usually the extent of the guidance, as canned or pre-written software is often defined in the alternative as computer software that is not custom software. As a result, taxpayers are often left with limited guidance, especially in the context of modified software. This has led to states moving away from including this language in their statutes.
B. Navigating Characterization Post Ex Parte Russell County Community Hospital
A prime example of a state disregarding this binary treatment of software is the Alabama Supreme Court’s recent decision in Ex parte Russell County Community Hospital LLC v. State Department of Revenue. Pointing to Ala. Admin. Code r. 810-6-1-.37(5), the hospital filed a refund claim for sales taxes paid on computer software, arguing that it purchased nontaxable services in the form of custom software programming. At the time of the decision, the regulation defined custom software programming as “software programs created specifically for one user and prepared to the special order of that user.” Further, the term “custom software” included
“modifications to a canned computer software program when such modifications are prepared to the special order of the customer,” although “only to the extent of the modification[s]” and only to the extent the modifications are separately invoiced to the purchaser.
Relying on its prior decision in Wal-Mart Stores v. City of Mobile, the court held that “there is no distinction for Alabama sales-tax purposes between canned or custom software.” Rather, “all software, including custom software created for a particular user, is ‘tangible personal property’ for purposes of Alabama sales tax.”
However, if a seller tenders an invoice for separately stated nontaxable services that accompany the conveyance of software, such as determining a particular software user’s needs, designing and programming new software for a particular user, modifying or configuring existing software programs to meet a user’s needs, installing software, or training users to operate software, those services are nontaxable. As a result, this case represents a departure from the state’s historic distinction between canned and custom software.
C. What’s Next for Characterizing Software?
Alabama may be at the forefront of a wave of states to move away from these rigid terms and to instead focus on the services performed related to
the software. In response to this decision, the Alabama Department of Revenue proposed amendments to its administrative regulations on computer software in August. If adopted, the amendments will reflect the court’s decision and eliminate references to “canned computer software” and “custom software programming.” The move makes sense as custom software is becoming increasingly more difficult to define. Although software companies often mistakenly view software as custom when an off-the-shelf platform is substantially customized to the user’s requirements, most states still consider the software to be pre-written or canned. The result is that few software programs benefit from taxfree treatment as truly custom.
However, is this change in treatment groundbreaking? Arguably, no, as many states already treat separately stated charges to customize software that are designed and developed to the customer’s specifications as not
subject to tax. As a result, although Alabama’s disregard of the binary terminology of canned versus custom appears novel, the practical application is that they are just codifying the nontaxable treatment of modifications already commonly adopted by many other jurisdictions.
II. Modernizing the Term ‘Load and Leave’
A. Adoption and Significance of the Meaning
The other significant factor that determines whether software is subject to sales and use tax is the means of delivery, including whether it is electronically downloaded, transferred via physical media, or delivered via “load and leave.” Ask a software developer whether software was delivered via load and leave and they may seem puzzled because not only is the term outmoded, but it is hardly a part of the nomenclature of the digital world. But before the internet provided the bandwidth for the electronic delivery of software, taxpayers could only receive software via load and leave or load and return. Although the taxability of preloaded software was first
addressed by a state in a repealed 1999 Pennsylvania ruling, load and leave received widespread acceptance after appearing in the original draft of the Streamlined Sales and Use Tax Agreement adopted in November 2002.
The SSUTA defines load and leave as “delivery to the purchaser by use of a tangible storage media where the tangible storage media is not physically transferred to the purchaser.” In practice, the term refers to the means of delivery of software. Rather than a customer downloading the software or accessing it via the cloud, the creator loads it onto the customer’s computer by a physical medium, such as a compact disk, floppy disk, or external hard drive, and then takes back the physical copy.
There are 23 SSUTA full member states, meaning that the state is in compliance with the SSUTA and its laws, rules, regulations, and policies. As a result, the term “load and leave” has been added to many states’ statutes or regulations. For example, although some streamlined states reacted quickly, such as Minnesota, North Dakota, and West Virginia, which amended their statutes in 2003 to include the term, nonmember states such as Colorado lagged behind, not adding it until 2011.
The means of transfer of software is significant in determining whether it is subject to sales and use tax. However, there is no generally applicable rule. Whereas some states only tax canned software when there is a physical delivery of tangible personal property via load and leave, other states tax canned software regardless of the means of transfer, including electronically downloaded software. For example, in the most recent significant decision addressing load and leave, FileNet Corp. v. Director of Revenue, the Missouri Administrative Hearing Commission held that a load and leave transfer of canned software was not subject to use tax because the transfer did not constitute a sale of tangible personal property. After reviewing evidence that a “person cannot see or touch software” delivered via a USB drive, the commission determined that the software was a nontaxable intangible because it was not “delivered in a tangible medium.” By narrowing the scope of software “delivered in tangible medium” to only those outdated items identified in Missouri’s regulation, such as a CDROM and magnetic tape, the commission further limited the taxability of the already aging term “load and leave.”
B. Is Load and Leave Now Obsolete?
Despite the widespread adoption of the term, did “load and leave” go the way of the floppy disk or compact disk? That’s a loaded question. Because of the decline of physical media, states’ adoption of the term is a step behind — most computers no longer feature an optical drive. The demise of the optical drive is the result of several factors, including consumer pressure to reduce the size of laptops, the diminished need for physical media, and the rise in capacity ofsolid state drives. Although some taxpayers —such as government entities — are resistant to electronic transfer because of security concerns, considering that most computers no longer feature a computer optical drive, the use of load and leave software is uncommon. Instead, taxpayers more frequently remotely install software on a customer’s computer using the cloud.
As the electronic delivery of software increases, will states divert from taxing software based on the means of delivery? For a state interested in increased sales tax revenue and simplification of its laws, it may be a prudent move. States that differentiate between software delivered electronically or by load and leave often leave sales tax dollars on the table. For example, states, such as Iowa and Oklahoma tax prewritten software delivered via load and leave, but sales of pre-written computer software that are delivered electronically are exempt from tax. As a result, most sales of software escape taxation in these states, which is a precarious result from a revenue perspective. To simplify the applicability of their laws, these states could amend them to follow Ohio, which already taxes pre-written software regardless of the mode of transmission.
Alternatively, if a state elects to be even more aggressive, it can mirror Mississippi, which taxes gross receipts from computer software or program sales, regardless of the means of transmission or whether it is characterized as prewritten or custom. If states experience a financial
dip, resulting in increasing expenditures and decreasing revenues, this simplification of the law may be a solution to create additional revenue.
No matter how states react to recent changes in technology, one thing is for sure: Their reaction will be slow. States and localities are still struggling to characterize the taxability of software using rigid and outdated terms that do not allow for the flexibility that is necessary in an evolving industry. Although defining software as either canned or custom perhaps made sense in an economy of tangible goods, the terms lack the
nuance to properly distinguish complex services and varied digital products. Further, considering the ease and accessibility of electronic downloads, limiting taxability based on the mode of transfer now appears shortsighted and could result in states overlooking key sources of sales tax
 This is only a general rule, as some jurisdictions do tax custom software, including the District of Columbia, Hawaii, Louisiana, Mississippi, Nebraska, New Mexico, South Carolina, South Dakota, Tennessee, Texas, and West Virginia. D.C. Mun. Regs. 9 section 474.4; Haw. Rev. Stat. section 237-13(2)(A); La. Rev. Stat. Ann. section 47:301(16)(h); Miss. Code Ann. section 27-65-101(1)(ii); Miss. Admin. Code section 35.IV.5.06; Neb. Admin. R. & Regs. section 1-007.01H; Neb. Admin. R. & Regs. section 1-088; N.M. Admin. Code section 220.127.116.11(F)(2); S.C. Code Regs. section 117-330; S.D. Admin. R. section 64:06:02:80; Tenn. Code Ann. section 67-6-231; Tex. Tax Code Ann. section 151.009 ; Tex. Admin. Code section 3.308(c)(4); W. Va. Code section 11-15-9h(a)(1); W. Va. Code section 11-15-9h(a)(2); W. Va. Code section 11-15-9h(a)(4); and W. Va. Code section 11-15-9h(a)(7).
 See Mo. Code Regs. 10-109.050.
 386 Ill. Admin. Code section 130.1935(c) (defining custom software as prepared for special order of the customer); N.Y. Tax Law section 1101(b)(14) (defining pre-written software as software that is not software designed and developed by the author or other creator to the specifications of a specific purchaser); Wash. Rev. Code section 82.04.215(3), (6) (defining custom software as software created for a single person and pre-written computer software as computer software that is not designed and developed by the author or other creator to the specifications of a specific purchaser).
 86 Ill. Admin. Code section 130.1935(c)(2).
 Ex Parte Russell County Community Hospital LLC v. Department of Revenue, No. 1180204 (Ala. May 17, 2019).
 Ala. Admin. Code r. 810-6-1-.37(5).
 696 So. 2d 290, 291 (1996).
 Ex Parte Russell County Community Hospital. The court determined that although software was originally considered intangible property because it was the information and not the medium that was being sold, because the state became proliferated with “canned” computer software in the 1990s that was conveyed via a tangible medium, software has become tangible personal property. Wal-Mart Stores v. City of Mobile, 696 So. 2d 290, 291 (1996).
 Ala. Admin. Code r. 810-6-1-.37. A public hearing on the proposed rule was held on October 8.
 For example, New York treats the combining of two or more prewritten software programs or pre-written portions of such programs as pre-written software. N.Y. Tax Law section 1101(b)(6); NY Sales Tax Bulletin No. TB-ST-128 (Aug. 5, 2014). Only software uniquely designed and developed for a specific purchaser is excluded as nontaxable custom software. Id.
 For example, New York, Ohio, and Oklahoma do not tax separately stated charges for customization, even if the software is pre-written or canned. See New York, N.Y. Advisory Op. No. TSB-A-98(20)S (Mar. 24, 1998); Ohio Rev. Code 5738.01(DDD); and Okla. Admin. Code 710:65-19- 52(f).
 Pa. SUT Ruling 99-198 (Oct. 25, 1999).
 A list of current SSUTA member states is available online.
 Colo. Rev. Stat. section 39-26-102(15)(c)(I)(C); Ga. Code Ann. section 48-8-3(91); Idaho Code section 63-3616(b); Iowa Admin. Code 701-231.14 (423); Kan. Stat. Ann. section 79-3602(s); Mass. Regs. Code 64H.1.3; Minn. Stat. section 297A.61 (Subd. 17b); Nev. Admin. Code 372.023; N.J. Admin. Code 18:24-25.1A; N.D. Cent. Code section 57-39.2- 02.1(g); N.D. Admin. Code 81-04.1-03-11(4); Okla. Admin. Code 710:65- 19-52(a)(6); R.I. Gen. Laws section 44-18.2-2; Utah Code Ann. section 59- 12-102(63); Code of Vt. Rules 1.9701(7)-1(4); W. Va. Code section 11-15B- 2(b)(31); Wis. Stat. section 77.51(7g); Wis. Admin. Code Tax 11.71(j); and Wyo. Stat. section 39-15-101(xxxiii).
 2012 Colo. Rev. Stat. section 39-26-102(15)(II)(D), amended by 2011 Colo. H.B. 1293; 2003 Minn. Stat. section 297A.61 (Subd. 17b), amended by 2003 c. 127 art. 1 s. 8-16, art. 6 s. 4-7; 2003 N.D. Cent. Code section 57- 39.2-02.1, amended by 2003, ch. 539, section 5; and 2003 W. Va. Code section 11-15B-2, amended by 2003, c. 146.
 Central to determining delivery is the method of delivery indicated on the taxpayer’s invoice, purchase contract, or other documentation. Some states, such as Georgia, presume that if the taxpayer does not meet its burden in establishing electronic transmission, delivery will be presumed to have been made through a tangible medium. Georgia Letter Ruling, No. LR SUT-2018-10 (Aug. 7, 2018).
 Several states, including Arkansas, California, Georgia, Iowa, and Oklahoma, exempt software from taxation if is downloaded, regardless of whether it is canned or custom. Ark. Code Ann. section 26-52- 304(a)(1)(B)(ii); Cal. Code Regs. 18 section 1502(f)(1)(D); Ga. Code Ann. section 48-8-3(91); Iowa Admin. Code 701-231.14 (423); Okla. Admin. Code 710:65-19-52(c); Okla. Stat. section 1357(32); Okla. Admin. Code 710:65-19-156(b)(5); and Oklahoma Letter Ruling, No. LR 00-096 (2000).
 FileNet Corp. v. Director of Revenue, No. 07-0146 (Mo. Admin. Hearing Comm. Aug. 20, 2010).
 Id.; Mo. Code Regs. 10-109.050(3)(A) (“Examples of canned software delivered in a tangible medium would include coding sheets, cards, magnetic tape, CD-ROM or other tangible electronic distribution media on which or into which canned software has been coded, punched or otherwise recorded.”).
 See Mark Kyrnin, “Death of the Computer Optical Drive,” Lifewire (Oct. 11, 2019).
 Iowa Admin. Code 701—231.14 (423); Okla. Admin. Code 710:65- 19-52(c); Okla. Stat. section 1357(32); Okla. Admin. Code 710:65-19- 156(b)(5); and Okla. Letter Ruling, No. LR 00-096 (Sept. 8, 2000).
 Ohio Rev. Code 5739.01(YY), (DDD); and Miss. Admin. Code 35.IV.5.06(101).