Multiple Points of Use Exemption: A Complete Guide

When a business buys software, sales tax is usually charged based on the billing address. For a company with employees in 10 states, that means paying full tax in one state even though the software is used everywhere.

That is where the multiple points of use (MPU) exemption comes in. MPU lets a business shift tax responsibility away from the seller and self-assess tax based on where the software is actually used. The result is more accurate tax allocation and, often, significant savings.

This guide covers what MPU is, which companies can use it, how it works step by step, how rules vary by state, and what sellers need to do when they receive an MPU certificate.

What Is a Multiple Points of Use Exemption?

Core Definition

A multiple points of use exemption is a provision in sales and use tax law that allows a software buyer to self-assess and remit tax based on where the software is actually used, not where the invoice is billed.

MPU is not a true sales tax exemption. It does not make a purchase tax-free. Instead, it reallocates responsibility: the seller stops collecting tax, and the buyer takes on the obligation to calculate and pay the correct amount in each applicable state.

Why MPU Exists

The old rule was simple: tax applied at the point of delivery. When software arrived on a disk, that was easy to track.

Today, most business software is cloud-based. A single license can be accessed by employees in dozens of states at the same time. Default billing-address taxation creates two problems at once: overpayment in the billing state, and unreported use tax liability everywhere else. The MPU exemption was developed to correct that mismatch.

What Changes When an MPU Certificate Is Provided

When a buyer provides a valid MPU certificate to a seller:

• The seller is relieved of the obligation to collect tax on that transaction.
• The buyer accepts full responsibility for allocating the purchase across all states where the software is used.
• The buyer files use tax returns in each applicable state and pays the appropriate amount based on local rates.

Sound like a hassle? Sphere stores MPU certificates and automatically stops sales tax collection from your MPU customers. 

Which Companies Use MPU Exemptions?

Enterprise Buyers With Distributed Workforces

MPU is most valuable to large companies with employees spread across many US states. Think national retailers, financial services firms, healthcare networks, and insurance companies. The more states involved and the larger the software spend, the bigger the potential savings.

A company with employees in 30 states buying a $500,000 enterprise platform is paying a lot of sales tax in one place. MPU lets them reallocate that based on where people actually sit. Better yet, if some of those states do not tax SaaS, that portion becomes non-taxable.

Products That Qualify

MPU applies to intangible products that can be used simultaneously from multiple locations, including:

• SaaS platforms and cloud-hosted software (often referred to as “prewritten computer software”)
• Enterprise software licenses
• Digital products/digital goods accessed remotely
• Data processing services (as recognized in states like Texas)

Physical goods do not qualify, since they can’t be used in multiple locations at once. Eligibility also varies by state, so verify rules in each jurisdiction before claiming the exemption.

When MPU Is Worth Pursuing

Using an MPU is worth the administrative effort when:

• Software spend is significant (large enterprise contracts or recurring annual subscriptions)
• Employees or users are genuinely spread across multiple jurisdictions (i.e. states) and have remote access
• Some of those states do not have applicable tax on SaaS or have lower applicable rates

It is generally not worth it when users are concentrated in just one or two states, the software purchase is small or one-time, or the filing burden would cost more than the tax savings.

How the MPU Exemption Works

Step 1: Provide an Exemption Certificate to the Seller

The process starts when the buyer provides the seller with a valid MPU certificate at the time of purchase. The timing here matters.  In Minnesota, claims must be made at the time of purchase, and retroactive claims are not permitted. In Washington, retroactive refund claims are allowed. Getting the certificate in before the transaction is the safest approach in any state.

Step 2: Establish an Allocation Method

As the buyer, you’re now responsible for dividing the purchase price across the states where the software is used. Tax authorities say this method must be reasonable, consistent, and supported by business records. The most common approaches:

• Headcount-based allocation is the most widely accepted method. You allocate based on the number of licensed users in each state. If 30 of 100 users are in Massachusetts, 30% of the purchase price is allocated there. This is simple to implement, and widely accepted by auditors.
• Usage-based allocation relies on actual login data or session counts by location. This is more accurate and highly defensible in an audit, but it requires robust data usage reporting.
• Revenue-based allocation divides spend based on revenue generated per state. This method aligns with financial reporting but can be harder to defend because it is indirectly tied to how the software is used.

Whatever method you choose, apply it consistently across periods. Switching methods without a documented reason raises red flags in an audit.

Step 3: Remit Use Tax to Each State

Once the allocation is set, the buyer applies each state's applicable sales tax rate to its allocated portion of the purchase price and files use tax returns in each applicable state. If a state does not tax SaaS, no tax is owed on that portion. This is where businesses can realize tax savings. 

Step 4: Maintain Records for Audit Defence

Buyers using MPU need to retain detailed records for at least four years. Keep user counts by state, location or login data, allocation calculations, and any license agreements specifying usage rights. If a state auditor challenges the methodology, this documentation is your primary defense.

Key State Variations

How Rules Differ

As with all things sales tax, rules are set at the state level, and state requirements vary widely. Factors like eligible products, certificate format, and whether retroactive claims are allowed vary by state. Note that states that are members of the Streamlined Sales Tax (SST) agreement generally permit MPU. But non-SST states vary widely.

State Examples

Note that state rules vary and are subject to change. Always check with your state’s tax authority or a state and local tax expert before claiming a MPU exemption. 

When the MPU Exemption Is Not Worth It

MPU is a tool, not a universal solution. You might find situations where the tax compliance overhead outweighs the benefit to taxpayers.

Limited Multi-State Usage

If your users are concentrated in one or two states, the allocation math does not produce enough savings to justify the extra work. The savings from MPU is most useful when usage is genuinely spread across many states with different tax rules.

Low Software Spend

The savings from MPU are proportional to the total software spend being reallocated. On a small purchase, the savings may not justify the time required to track usage, prepare allocations, and file use tax returns in multiple states.

High Administrative Burden

Using MPU means:

• Tracking users or usage by state
• Filing use tax returns in every state where usage occurs
• Maintaining detailed records for at least four years
• Staying current on rule changes in each state

If your team does not have the infrastructure to support this, the exemption can create more risk than it resolves.

Minimal Tax Rate Differences

If the states where your employees are located all tax SaaS at similar rates, the reallocation savings are minimal. MPU is most valuable when some portion of usage can be allocated to states that exempt SaaS entirely or tax it at a reduced rate.

One-Time or Low-Value Purchases

MPU makes the most sense for large, recurring contracts. An annual enterprise software renewal for $200,000 is a good candidate. A one-time $3,000 software purchase usually is not worth the backend administrative hassle.

How Sphere Helps Sellers Manage MPU Certificates

The Seller's Obligation

When a seller receives a valid MPU certificate from a buyer, the seller's responsibility is clear: stop calculating and collecting tax on that customer's transactions.

This sounds straightforward. In practice, it breaks down quickly. Most businesses have dozens or hundreds of customers. Certificates arrive at different times, for different products, with different effective dates. Tracking this manually in a spreadsheet is a recipe for errors. You'll either continue to charge tax on a customer where you should not, or lose track of a certificate and be unable to produce it in an audit, leaving you on the hook to pay the uncollected tax.  

Certificate Storage and Tax Suppression

Sphere collects and stores MPU certificates, links them to the correct customer account, and suppresses tax calculation on future transactions automatically.

Certificates are stored in an audit-ready format and can be exported on demand. When an auditor requests documentation for a specific customer or transaction, the certificate is already organized and accessible through Sphere.

End-to-End Compliance

Sphere handles the full compliance stack: nexus monitoring, tax registration, calculation, filing, and remittance. Unlike other solutions, which bolt it on separately, exemption certificate management is built into the same platform.

This matters because exemption management does not exist in isolation. The same customer might have an MPU certificate in one jurisdiction and a standard resale certificate in another. Sphere tracks both, applies the correct treatment to each transaction, and keeps everything in one place.

Sphere also covers sales tax, VAT, and GST globally. If your business sells across borders, the exemption certificate workflow sits within the same system as your international compliance.

Ready to automate exemption certificate management?

Schedule a demo with Sphere today.

Book a Call

MPU Compliance Requires the Right System

A valid MPU certificate relieves the seller of sales tax collection obligations, but only if it is properly collected, stored, and acted on. A certificate that sits in an email thread or an unsorted folder does not protect anyone.

As remote work continues to spread employees across more states, managing MPU alongside broader exemption workflows is becoming a standard compliance requirement, not an edge case. Enterprise buyers are increasingly sophisticated about using MPU to manage their tax costs. Sellers need to be equally prepared to handle it correctly.

The mechanics of MPU are manageable with the right process and the right system. Getting the certificate at the time of purchase, applying a consistent apportionment method, filing in every applicable state, and retaining documentation for audit are the four cornerstones. Miss any one of them and the benefit disappears fast.