Tax on software depends on three separate systems that can all apply to the same purchase: state sales and use tax, federal income tax, and, in some states, business personal property tax. What you owe turns on how the product is classified (prewritten, custom, or a cloud subscription), how it reaches you, and where the buyer sits. A program that carries an 11% combined sales tax rate in one location can be completely exempt one state over, and the federal rules for deducting the cost swing on whether you bought it, built it, or subscribed to it.
How Software Is Classified for Sales Tax
The most important distinction in software sales tax is prewritten versus custom. Prewritten software (sometimes called canned or off-the-shelf) is developed for the general market and sold to multiple buyers without meaningful modification. Most taxing jurisdictions treat prewritten software as taxable personal property, no matter how it’s delivered.
Custom software sits in a different category. To qualify, a developer generally needs to build the code from scratch for a specific buyer, or modify an existing product enough that the result no longer resembles the off-the-shelf version. Many jurisdictions treat custom development fees as nontaxable service charges rather than product sales. Invoice structure often decides the outcome: separately stated design, programming, and consulting fees support the service classification, while a single lump-sum charge for a finished product looks like a taxable sale.
The gray zone is modified prewritten software. Some jurisdictions tax the entire price as prewritten software when a vendor makes minor tweaks. Others let you split the charges, taxing the base software but not the customization labor, as long as both amounts are clearly stated on the invoice. If you’re buying modified software, ask the vendor to itemize the customization charges. That one step can meaningfully reduce your tax bill in jurisdictions that follow the split approach.
Software as a Service and Cloud Products
SaaS breaks the traditional software transaction. Instead of buying a copy you own, you pay for ongoing access to an application running on someone else’s servers. Nothing tangible transfers, which is exactly what makes SaaS hard to fit into tax frameworks built for physical goods.
As of 2025, roughly half of U.S. taxing jurisdictions impose some form of sales tax on SaaS. The legal theories vary. Some treat it as a taxable license to use software, reasoning that the subscriber has “constructive possession” of the program. Others view it as a nontaxable data processing service, since the subscriber only receives the software’s output. A handful tax SaaS under broad authority to tax services generally. The result is that the same $500 monthly subscription can carry tax in one state and none in another.
Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) get different treatment. These products provide raw computing resources or development environments rather than finished applications, and only a small number of states tax them. Most treat IaaS and PaaS as nontaxable because the buyer isn’t accessing a prewritten software product. The lines are blurring as vendors bundle offerings together, so if a cloud bill mixes storage, computing, and application access, each component may need to be separated to determine what’s taxable.
Downloads, Discs, and Load-and-Leave
Software delivered on a physical disc or USB drive is almost universally taxed, because a tangible object changes hands. The harder question is what happens when the same software arrives as a download. A significant number of states tax downloaded software at the same rate as its boxed equivalent, treating the file as functionally identical to the physical product. Others exempt downloads because no tangible property was transferred.
Some jurisdictions recognize a “load and leave” transaction: a technician brings installation media to your location, loads the software onto your computer, and takes the disc or drive away. Because no physical property stays behind, these transactions are exempt in the jurisdictions that recognize the distinction. Colorado and Massachusetts, among others, have formally adopted this rule.
The Streamlined Sales and Use Tax Agreement, which governs tax administration across roughly two dozen member states, does not let member states simply expand their definition of “tangible personal property” to sweep in digital products. Each state must pass separate legislation expressly imposing tax on electronically transferred products, so coverage of digital software varies even inside the Streamlined framework.
Maintenance and Support Contracts
Many software purchases come with a maintenance agreement covering updates, upgrades, and technical support. Whether it’s taxable usually depends on whether the contract is mandatory or optional.
Under the Streamlined Sales Tax rules that multiple states follow, a mandatory maintenance contract bundled with prewritten software is treated as part of the software’s sale price if the two aren’t separately itemized. The whole amount is then taxable at the same rate as the software. An optional maintenance contract can be split: the portion covering support services is characterized as a service sale, and the portion covering software updates and upgrades is treated as a sale of prewritten software. Each state applies its own rules to each component.1Streamlined Sales Tax Governing Board. SST Rules and Procedures – Software Maintenance Contracts
If your vendor offers a choice between bundling maintenance into the software price and listing it separately, the separate-line approach gives you the best chance of reducing tax. A maintenance contract from a third party who didn’t sell you the software is generally characterized as a pure service sale, which may or may not be taxable depending on how your state handles services.
Who Has to Collect, and at What Rate
A seller only has to collect your state’s sales tax if it has enough connection to the state, known as nexus. The 2018 Supreme Court decision in South Dakota v. Wayfair eliminated the older rule requiring physical presence.2Cornell Law Institute. South Dakota v Wayfair, Inc A seller crossing an economic threshold in your state now has to collect and remit tax even without an office, warehouse, or employee there.
The original South Dakota law set the threshold at $100,000 in revenue or 200 separate transactions within the state. Most states adopted similar thresholds, and the trend has been to simplify by dropping the transaction count and keeping the $100,000 revenue trigger. For software sellers making frequent small sales across state lines, that change reduces the number of states where collection is required.
Origin vs. Destination Sourcing
Once a seller has nexus, the applicable rate depends on sourcing rules. About a dozen states use origin-based sourcing, so the rate follows the seller’s location. The rest use destination-based sourcing, where the rate follows where the buyer receives the product. For electronic delivery, that usually means the buyer’s billing address or primary place of use. Two buyers purchasing identical software from the same vendor can owe different tax amounts based on where they sit, and local combined rates run from under 5% to over 11%.
The Streamlined Sales Tax Agreement
Member states of the Streamlined Sales and Use Tax Agreement have adopted uniform definitions, simplified rate structures, and a centralized registration system. Sellers who register through the Streamlined Sales Tax Governing Board get free tax calculation and reporting tools across all member states and can cover every participating state with a single registration.3Streamlined Sales Tax Governing Board. Streamlined Sales Tax Registration is voluntary.
Use Tax When the Seller Doesn’t Collect
This is the piece most software buyers overlook, and it causes real audit problems. When you buy software from an out-of-state seller who doesn’t collect your state’s sales tax, you generally owe the equivalent amount as use tax directly to your state. Use tax exists specifically to prevent buyers from avoiding sales tax by purchasing from remote sellers.
For businesses, the exposure is meaningful. A $50,000 enterprise software license bought from a vendor with no nexus in your state still triggers a self-assessed use tax obligation. Most states require businesses to report use tax on periodic sales and use tax returns. Individuals typically report use tax on their annual state income tax return, though many people don’t realize it.
Use tax tends to fly under the radar until an audit. State auditors routinely pull business accounts payable records and compare software purchases against sales tax paid. If you bought taxable software and no tax was collected or remitted, you’re liable for the full amount plus interest and penalties. Flagging untaxed software acquisitions for your accountant is the simplest way to avoid a surprise.
Common Sales Tax Exemptions
Even in jurisdictions that broadly tax software, some purchases qualify for exemption:
- Resale. Software bought to resell to an end customer is typically exempt, since the tax targets only the final consumer.
- Manufacturing use. Software used directly in manufacturing processes or to control production machinery often qualifies for an industrial exemption. The key word is directly; software running payroll, invoicing, or other back-office tasks usually does not qualify.
- Research and development. Some jurisdictions exempt software purchased primarily for qualifying R&D activities.
Claiming any exemption requires giving the seller a properly completed exemption certificate, ideally at the time of purchase. The certificate shifts liability to you if the exemption doesn’t hold up. Claim a manufacturing exemption but actually use the software for administration, and you owe the back taxes plus interest. Keep documentation that ties each exempt purchase to its qualifying use. Auditors want to see more than the certificate itself; they look for evidence that the software actually served the exempt purpose.
Federal Income Tax Treatment
Sales tax isn’t the only tax that applies. On the federal side, how a business recovers software costs on its income tax return depends on whether you purchased off-the-shelf software, developed software in-house, or subscribed to it.
Purchased Off-the-Shelf Software
When a business buys commercially available software, the cost is generally amortized over 36 months using the straight-line method, starting from the month the software is placed in service.4Office of the Law Revision Counsel. 26 USC 167 Depreciation Salvage value is treated as zero, so the full purchase price is recovered over that three-year window.5eCFR. 26 CFR 1.167(a)-14 Treatment of Certain Intangible Property Excluded From Section 197 This treatment applies to software widely available to the public under a nonexclusive license that hasn’t been substantially modified. Software acquired as part of a business acquisition typically falls under the Section 197 intangible rules with a 15-year amortization period.
In-House Software Development
The rules for developed software have changed. The Tax Cuts and Jobs Act originally required businesses to capitalize and amortize all research and experimental expenditures, including software development, over five years for domestic work and fifteen years for foreign work.
For tax years beginning after December 31, 2024, Congress restored the ability to immediately expense domestic software development costs in the year they’re incurred. Foreign research and experimental expenditures still have to be capitalized and amortized over 15 years.6Office of the Law Revision Counsel. 26 USC 174 Amortization of Research and Experimental Expenditures For companies developing software domestically, that’s a significant cash-flow improvement over the prior regime.
SaaS Subscriptions
Subscription payments for cloud-based software are generally deductible as ordinary business expenses in the year paid, since no asset is being acquired. No capitalization decisions, no amortization schedules, just a current deduction for each payment period.
The Research and Development Tax Credit
Businesses that develop software may also qualify for the federal R&D tax credit under Section 41. The credit equals 20% of qualified research expenses that exceed a calculated base amount.7Internal Revenue Service. Credit for Increasing Research Activities Qualifying expenses include wages for employees performing or directly supervising research, supplies consumed in the research, and a percentage of payments to outside contractors performing qualified research. For startups with limited history, the fixed-base percentage starts at 3% for the first five tax years, which effectively increases the credit during early growth.
Payments to Foreign Software Vendors
Businesses that pay foreign companies for software licenses or subscriptions may face federal withholding obligations. Royalty payments to foreign persons are generally subject to a 30% withholding tax on the gross amount. Software license fees can be classified as royalties when they involve the right to reproduce, distribute, or publicly perform the underlying code.
Tax treaties often reduce the 30% rate. Many treaties bring withholding on software royalties down to somewhere between 0% and 15%. To claim a reduced rate, the foreign recipient has to provide certification, typically on IRS Form W-8BEN or W-8BEN-E. The payer reports the payment and any withholding on Form 1042-S.8Internal Revenue Service. Instructions for Form 1042-S
Not every payment to a foreign software company is a royalty. Subscribing to a SaaS product for internal use, with no right to reproduce or redistribute the software, may be classified as a service payment instead. Service payments to foreign entities follow different withholding rules and may be exempt entirely if the foreign company has no U.S. tax presence. The classification matters enough that businesses making substantial payments to foreign software vendors should get specific guidance before assuming one treatment.
Business Personal Property Tax
Some states impose annual personal property tax on business assets, and software can be caught in that net. Whether it is depends on how your state classifies software for assessment purposes. A number of states treat software as an intangible asset and exclude it from personal property tax. Others include certain categories, particularly prewritten software, in the taxable base.
If your business owns expensive enterprise software in a state that taxes business personal property, check how your state’s assessment rules classify it. Filing requirements and deadlines vary, and failing to report taxable software on a personal property return can trigger penalties. In states that exempt software as intangible property, be prepared to document the classification if an assessor challenges it.