Sales tax on software maintenance agreements usually turns on one distinction: an agreement that delivers software updates is generally taxable, and an agreement that delivers only human technical support generally isn’t. Most contracts bundle both into a single price, and that is where the rules get complicated and where the answer starts to depend on your state, your invoice, and the fine print of the contract itself.
Updates Are Taxed Like Software; Support Is Taxed Like a Service
Every jurisdiction starts from the same split. Updates modify the underlying code, deliver new features, or patch security holes, and tax authorities treat them the same way they treat the original software sale: as a transfer of a product. Technical support is a person answering questions, troubleshooting errors, or walking a user through a configuration. That labor is typically classified as a service.
The Streamlined Sales and Use Tax Agreement, which governs sales tax administration in its member states, codifies the split in Rule 327.5. When a maintenance contract’s charges for support services and for updates are separately stated on the invoice, each component keeps its own tax character. The support portion is treated as a service, and the updates portion is treated as a sale of prewritten software.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts
Separately stated is doing a lot of work in that sentence. When the charges are lumped into a single invoice line, the protection disappears and the analysis shifts to how the state treats bundled transactions.
When One Price Covers Both
Where support and updates share a single price tag, tax authorities often apply the “true object” test. The question is straightforward: what is the customer actually paying for? If the main reason a business buys the agreement is to receive software updates, the entire contract price may be taxable. If the customer is really paying for access to a help desk and the updates are incidental, the contract may escape tax entirely.
Under the Streamlined Sales Tax framework, a transaction that combines a taxable product with a service is not treated as a bundled transaction when the product is merely essential to the service and the true object of the purchase is the service itself. The determination is fact-specific. It considers what the seller’s business primarily does, whether the product is available separately from the service, and what the buyer’s actual objective is.2Streamlined Sales Tax Governing Board. Bundled Transaction Issue Paper
The same framework has a de minimis safe harbor. If the taxable portion of a bundled transaction represents 10% or less of the total price, the entire transaction is not treated as bundled. A $10,000 maintenance agreement that includes $900 of updates and $9,100 of support may fall below the threshold and avoid tax on the full amount.2Streamlined Sales Tax Governing Board. Bundled Transaction Issue Paper Sellers applying the test must use either their purchase price or their sales price consistently and cannot mix the two.
Mandatory vs. Optional Agreements
Whether the maintenance contract is required or voluntary changes the analysis even when the invoice is itemized. A mandatory agreement exists when the customer cannot buy the software without also buying the maintenance, or when continued use of the software depends on renewing the agreement. Under the Streamlined Sales Tax rules, a renewal the customer must purchase as a condition of continuing to use the software is classified as mandatory regardless of how the contract is labeled.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts
When a mandatory contract’s price is not separately itemized from the software itself on the invoice, the maintenance charge is treated as part of the software’s sales price and taxed at the same rate. The full invoice amount, including years of future maintenance, becomes the taxable base of the original software sale.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts
Optional agreements give sellers and buyers more room to manage the outcome. When the customer can decline the maintenance and still use the software, the agreement stands on its own for tax purposes. If the seller separately states support services and updates, only the updates portion is characterized as a sale of prewritten software. Support provided by a third party rather than the original vendor, with no updates or upgrades involved, is characterized entirely as a service.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts
Custom Software and SaaS Follow Different Rules
The tax treatment of the underlying software heavily influences the maintenance agreement. Prewritten software, sometimes called canned or off-the-shelf, is designed for the general market and sold to many customers. Most states treat it as taxable tangible personal property or a taxable digital product, and maintenance agreements that include updates inherit that classification.
Custom software, built from scratch for a single client, is often treated as a non-taxable service. Under the Streamlined Sales Tax rules, both mandatory and optional maintenance contracts relating to non-prewritten software are characterized the same way as the non-prewritten software itself.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts If the jurisdiction exempts the custom software, it typically exempts the maintenance too.
The gray area is modified prewritten software. A company buys an off-the-shelf product and then pays the vendor to customize it heavily. Some jurisdictions will reclassify the software as custom once the modifications are substantial enough, but the threshold varies and is not consistently defined across states.
AI-assisted development has added a further wrinkle. At least one state revenue department has taken the position that software incorporating artificial intelligence components does not qualify as custom software, even when the AI adapts its behavior to user-specific data. The reasoning is that AI-driven personalization is a feature of the prewritten product rather than bespoke development for a single client. To qualify for a custom software exemption, modifications must be created exclusively for a single customer and separately stated on the invoice.
Cloud-Based Maintenance
The shift from installed software to cloud delivery has complicated things further. When software runs entirely in the cloud and the customer never downloads or installs any code, many jurisdictions treat the transaction differently than a traditional software sale. Roughly half of U.S. states do not tax Software-as-a-Service at all, while approximately 25 jurisdictions tax it in some form, with combined state and local rates running from under 2% to over 11% where the product is taxable.
The dividing line is usually whether the customer receives a copy of the software. Jurisdictions that exempt SaaS generally do so because the customer accesses the software remotely without taking possession of a transferable copy. If the same software requires a download or installation, many of those same jurisdictions will tax it. That distinction carries over to maintenance: a contract that delivers patches through remote updates the customer never downloads may be treated differently than one that sends installable update files.
Infrastructure-as-a-Service and Platform-as-a-Service arrangements add another layer. Maintenance tied to underlying cloud infrastructure may be treated as a technology service rather than a software transaction. Some jurisdictions that exempt SaaS still tax data processing or information services, which can capture cloud infrastructure maintenance.
Multi-State Buyers and Sourcing
Which state gets to tax a maintenance agreement depends on sourcing rules. Most jurisdictions have shifted to destination-based sourcing, so the rate is the one where the buyer uses the software rather than where the seller is located. A handful of states still use origin-based sourcing and apply the seller’s home rate regardless of the customer’s location.
For a single-location buyer, that’s simple. It gets harder when a business has employees using the same software in multiple states. The Streamlined Sales Tax Agreement addresses this through Multiple Points of Use provisions. A business buyer that knows the software will be concurrently available in more than one jurisdiction delivers an MPU exemption form to the seller. Once the seller receives it, the obligation to collect tax shifts to the buyer, who self-assesses and pays tax to each state using a reasonable apportionment method based on actual business records.3Streamlined Sales Tax Governing Board. Sourcing Issue Paper
The apportionment method must be consistent and uniform, but the framework doesn’t mandate a specific formula. Companies typically allocate based on the number of licensed users or servers in each jurisdiction. The MPU form stays in effect for all future purchases from the same seller until the buyer revokes it in writing, though the actual apportionment must be recalculated for each purchase to reflect current usage.4Streamlined Sales Tax Governing Board. Section 312 – Multiple Points of Use
The Use Tax Trap for Buyers
When a software seller does not charge sales tax on a maintenance agreement, the buyer’s obligation doesn’t necessarily disappear. Most states impose a complementary use tax on purchases where the seller didn’t collect. Buy a maintenance agreement from an out-of-state vendor that has no nexus in your state, and you likely owe use tax on the taxable portion at your state’s rate. The tax exists specifically to close this gap, and it applies whether or not the seller mentions it.
Businesses are expected to self-assess and remit use tax, typically on the same return used for sales tax. In practice, use tax compliance on software maintenance is one of the most commonly missed obligations in corporate tax departments. Auditors know this, and software-related use tax is a frequent audit target. The buyer who assumes “no charge on the invoice means no tax owed” is making the mistake auditors are specifically trained to find.
For multi-state companies using MPU exemption forms, the buyer takes over the full responsibility for use tax remittance. That means tracking user counts and server locations, calculating the tax owed in each jurisdiction, and filing returns accordingly. Getting the apportionment wrong doesn’t just shortchange one state; it can trigger assessments in every jurisdiction the agreement covers.
Invoicing That Protects You
The single most effective thing a seller can do to reduce a customer’s tax burden is itemize invoices correctly. When an invoice shows a lump-sum price without breaking out support services and updates, tax authorities in most jurisdictions treat the entire amount as taxable. Separately stating each component allows the non-taxable service portion to be excluded from the tax base.1Streamlined Sales Tax Governing Board. Rule 327.5 – Computer Software Maintenance Contracts
Each invoice should include the service period, specific software identification, and the primary location of use. Those details let auditors verify the correct rate was applied and confirm that sourcing rules were followed. For multi-state agreements, the invoice should also reflect the apportionment method used if the buyer has filed an MPU exemption form. Exemption certificates, MPU forms, and resale certificates must be collected and stored before or at the time of the transaction, not scrambled together later when an audit letter arrives.
Fixing Past Mistakes Before an Audit
Companies that discover past noncompliance before an audit notice arrives have a better option than waiting to be found. The Multistate Tax Commission runs a Voluntary Disclosure Program that lets businesses come forward, file back returns, and pay overdue tax plus interest in exchange for a waiver of penalties. The standard arrangement covers a lookback period of prior complete tax filing periods, and the state waives tax liability for anything before that window.5Multistate Tax Commission. Multistate Voluntary Disclosure Program
The catch is that prior contact from the state about the tax type disqualifies the taxpayer, and the minimum estimated liability must be at least $500 per state. Interest is still owed on the lookback period unless a state specifically waives it. For businesses selling maintenance contracts across many states, voluntary disclosure is often the most cost-effective way to clean up accumulated exposure. The window closes the moment a state sends an audit inquiry, so the time to act is before that letter arrives.