In most states with a sales tax, you will pay sales tax on software licenses, but three variables decide whether the tax applies and at what rate: whether the software is prewritten or custom-built, how it is delivered to you, and where you or your business is located. Five states have no general sales tax at all. Among the rest, the same product can be fully taxable in one state and completely exempt next door, with combined state and local rates reaching above 10% in some jurisdictions.
Prewritten Software Versus Custom Software
Prewritten software, sometimes called canned or off-the-shelf software, is any program designed for the general public rather than built to one buyer’s specifications. An office productivity suite, accounting software, or a graphic design application all qualify. The overwhelming majority of states with a sales tax treat prewritten software the same way they treat furniture or electronics: as tangible personal property subject to the standard sales tax rate. Under the Streamlined Sales and Use Tax Agreement, adopted by 24 member states, prewritten computer software delivered electronically is classified as tangible personal property and sits outside the separate digital-products framework.1National Conference of State Legislatures. Taxation of Digital Products
Custom software is code written from scratch for one specific buyer’s requirements. Most states exempt it entirely, treating the transaction as a purchase of professional programming services rather than a product. You are paying for a developer’s expertise and labor, not acquiring a mass-produced commodity. A small number of states do tax custom software, so the exemption is common but not universal.
The gray zone sits between the two. If a vendor sells you a prewritten program and then modifies it to fit your workflow, states disagree about whether the result is a taxable product or an exempt service. Some tax the entire transaction as a product sale whenever the base code is prewritten, no matter how extensive the customization. Others let you separate the custom work from the license fee and tax only the license portion. If you are buying modified off-the-shelf software, invoice structure matters. Contracts should itemize the license fee separately from customization labor, because a single lump-sum line usually means the entire amount gets taxed.
How Delivery Method Changes the Tax
The way software reaches your device can determine whether tax applies, and this is where states diverge most.
- Software sold on a disc, USB drive, or any other tangible object is taxable in virtually every state that has a sales tax. The physical object makes it tangible personal property under even the narrowest tax codes.
- Most states also tax software delivered as a download, because the end result is identical to receiving a disc: a copy of the program ends up on your device. Roughly ten states exempt electronically delivered software specifically because no physical object changes hands.
- When the software stays entirely on the vendor’s servers and you access it through a browser or thin client, the analysis changes again. That is the SaaS model.
The distinction between download and remote access is the single biggest variable in software taxation right now. On an enterprise license, whether you download a local copy or access everything in the cloud can shift the tax bill by thousands of dollars.
SaaS and Cloud-Based Software
Software as a Service is where a vendor hosts the program on its own servers and you access it through the internet, usually for a monthly or annual subscription. Because nothing is downloaded and no property changes hands, the tax treatment is genuinely unsettled. Approximately 25 states tax SaaS, another handful tax it only when some component is downloaded to the user’s device, and the rest treat it as a non-taxable service.
States that do tax SaaS use different legal theories. Some classify it as a taxable data-processing service. Others expand the definition of tangible personal property to include remote-access software. Others apply a “true object” test that asks what the customer is really paying for. If your primary goal is using the software rather than having the vendor perform a task on your behalf, the subscription is taxable; if you are really buying a service performed for you, it points toward exempt treatment.
Platform as a Service and Infrastructure as a Service usually receive gentler treatment. Because neither involves using a specific software application, most states that tax SaaS still exempt PaaS and IaaS. The closer a transaction looks like using software, the more likely it is taxable; the closer it looks like renting computing power, the more likely it is exempt.
Bundled Licenses and Maintenance Contracts
Enterprise software purchases rarely arrive as a clean, single line item. A typical deal bundles the license with implementation services, training, hardware, and an ongoing maintenance contract. Each component may have a different tax treatment, and how they are invoiced determines what gets taxed.
The core risk is bundling taxable items with exempt services in a way that makes the entire invoice taxable. When a vendor charges one lump sum for a license, custom configuration, and two days of training, many states will tax the entire amount because the taxable component cannot be separated from the exempt ones. Breaking each element into its own line item with a separate price gives you the best chance of paying tax only on the taxable portion.
Maintenance contracts create their own wrinkle. If a maintenance agreement includes software updates or new versions, states often treat part or all of the fee as a taxable transfer of software. If the agreement covers only telephone support and bug fixes without delivering new code, it is more likely treated as an exempt service. Optional and mandatory maintenance agreements may also be taxed differently. The safest approach is to price support services and software updates separately in the contract.
Multi-State Deployments and MPU Certificates
Businesses that deploy software across offices in multiple states face a sourcing problem: which state’s tax rate applies? Most states use destination-based sourcing, meaning the rate is determined by where the buyer uses the software, not where the seller is located. A smaller group use origin-based sourcing, where the seller’s location controls.
For enterprise licenses used simultaneously in several states, a Multiple Points of Use certificate lets the buyer apportion the tax across jurisdictions rather than paying the full tax to one state. When you provide an MPU certificate to the vendor, it relieves the vendor of the obligation to collect tax on the transaction. You then self-assess and remit tax to each state based on proportional usage. Common apportionment methods allocate by the number of licensed users or computer terminals in each state. The method must be reasonable, consistent, and supported by your records.
The tradeoff is real. An MPU certificate shifts the entire compliance burden to the buyer, and failure to remit the correct tax to each state leaves you personally on the hook. Companies without a tax function sometimes prefer to let the vendor collect tax based on a single billing address, even at the cost of overpaying in one state. For large deployments, though, the savings from proper apportionment justify the administrative cost.
When the Vendor Does Not Charge You Tax
If a vendor sells you software without charging sales tax, the transaction is not necessarily tax-free. Almost every state with a sales tax also imposes a use tax at the same rate. Use tax exists specifically to cover purchases where the seller had no obligation to collect, either because the seller lacked nexus in your state or because the purchase was made from out of state.
The use tax falls on the buyer. You calculate the amount and remit it directly to your state’s tax authority, typically on your income tax return or through a separate use tax filing. This applies to businesses and individual consumers alike, though enforcement focuses on businesses because the amounts are larger and the records are auditable.
Since the Supreme Court’s 2018 decision in South Dakota v. Wayfair, most states have adopted economic nexus rules that require out-of-state sellers to collect sales tax once they exceed a revenue or transaction threshold, with $100,000 in in-state sales the most common trigger.2Supreme Court of the United States. South Dakota v Wayfair, Inc More vendors now meet that threshold and charge sales tax on your invoice. Even so, use tax still catches purchases from smaller sellers below the threshold. If you are a business buying enterprise software from a vendor that does not collect your state’s tax, that liability does not disappear. It becomes yours, and state auditors routinely check for unreported use tax during business audits.
Exemptions That Can Eliminate the Tax
Even in states that broadly tax software, several categories of buyers and uses can qualify for exemptions.
- Nonprofits with 501(c)(3) status and government agencies can often buy software tax-free by presenting an exemption certificate at the time of purchase. The vendor must have the certificate on file before removing the tax from the invoice.
- If you buy licenses specifically to resell them to your own customers, a resale certificate lets you avoid tax on the purchase. The obligation shifts to the final end user.
- Some states exempt software used directly in the manufacturing process, particularly programs that control or monitor production machinery. Software used for administrative functions like accounting or payroll typically does not qualify, even in a manufacturing company.
- A number of states offer R&D exemptions that can extend to software used in qualified research. Some fold this into their manufacturing exemption; others treat it as standalone.
- A few states provide targeted exemptions for software used in qualified data centers that meet specific investment and employment thresholds.
Every exemption requires documentation. Keep copies of all exemption certificates and supporting records. The IRS recommends keeping records for seven years in certain situations, and many states apply sales tax audit look-back periods of four years or longer.3Internal Revenue Service. How Long Should I Keep Records A missing certificate during an audit means the exemption gets disallowed and you owe the tax plus penalties and interest.
Penalties for Getting It Wrong
The financial consequences fall on both sides of the transaction. Sellers that should have been collecting tax but were not face penalties that commonly start at 10% of the unpaid tax and can reach 25% or higher, plus interest that accrues monthly. Interest rates on unpaid sales tax liabilities generally range from about 7% to 15% annually, depending on the state.
Buyers are not insulated. If you owe use tax on a software purchase and do not report it, the state can assess the tax, add late-payment penalties, and charge interest back to the original purchase date. For businesses, these assessments often surface during routine audits that examine several years of transactions at once. The exposure compounds quickly when a company has been buying untaxed software licenses for years under the mistaken belief that no tax was owed.