Skip to content 
Massachusetts treats prewritten computer software as tangible personal property, taxable regardless of how it is delivered. The regulation lists transfers of rights to use software installed on a remote server among the taxable transfers, which reaches most subscription software. Custom software, data processing, and information services available to multiple subscribers are treated differently.
“We are a SaaS company. Nothing is ever delivered to anyone. How can this be a sale of tangible property?”
“Our platform is really a data service, not software. Does that change the answer?”
“Half our customers use the product from offices in other states. Are we taxing the whole subscription?”
The Sentence Founders Need to Read
The first question at the top is entirely reasonable and rests on a premise Massachusetts abandoned some time ago.
Under 830 CMR 64H.1.3, prewritten computer software is tangible personal property, sitting in the same statutory category as electricity, gas and steam. Nothing physical has to move for a sale to be a sale of tangible property.
Then the clause that answers the question directly. The regulation lists, among taxable transfers of prewritten software, transfers of rights to use software installed on a remote server.
That is a description of subscription software. It was written before anyone used the term SaaS routinely, and it reaches the model precisely: the customer never receives anything, the software stays where it is, and the transfer of the right to use it is the taxable event.
Delivery Is Not the Test
Massachusetts closed the delivery question deliberately. Per the Department’s guidance on transfers of prewritten software, prewritten software sold to a customer in Massachusetts or purchased for use here is a transfer of tangible personal property subject to tax regardless of the method of delivery, including electronic delivery or load and leave.
So the familiar arguments do not work. Nothing downloaded, nothing shipped, the server is in another region, access is by browser: none of these changes the treatment, because the regulation anticipated all of them.
Licences, leases, upgrades and licence upgrades are all listed as taxable transfers, which means an expansion of seats or a plan upgrade sits in the same category as the original sale.
What Is Actually Taxable
| What You Sell | Taxable? | Why |
| A subscription to your standard platform | Generally yes | A transfer of the right to use prewritten software on a remote server is a listed taxable transfer |
| A downloadable application | Yes | Prewritten software is taxable regardless of the method of delivery |
| Software built to one customer’s specification | Generally no | Custom software is treated as a nontaxable personal service transaction |
| Data processing you perform for a client | Generally no | Data processing remains a nontaxable service |
| An information database many subscribers access | Generally no | Information services available to multiple subscribers are treated as nontaxable services |
| A licence upgrade or an added seat | Yes | Upgrades and licence upgrades are listed among taxable transfers |
| Measurement | The product, not the delivery | Where the server sits, how the customer connects, and whether anything is downloaded do not decide it. What the customer is buying does |
Where the Real Exemptions Live
The second question is the one worth taking seriously, because it is where genuine distinctions exist rather than wishful ones.
Three categories are treated differently. Custom software built to a particular customer’s specification is generally a nontaxable personal service transaction. Data processing performed for a customer remains a nontaxable service. And database or similar electronic information services available to multiple subscribers are likewise treated as nontaxable services.
That third category is the one software companies reach for, and it is narrower than the pitch deck suggests. The question is not whether the product contains data; nearly all software does. It is whether what the customer buys is access to information, or a right to use software that happens to present information.
A platform whose value is the tooling, the workflow and the interface is selling software. A service whose value is the underlying data set, with access as the delivery mechanism, may not be. That line is worth analyzing properly at the point where pricing and packaging are decided, rather than defending after an assessment.
Bundled offerings complicate it further, since a single subscription can combine a taxable software right with nontaxable services, and how the contract states and prices those components affects the answer. The wider Massachusetts sales and use tax system applies to all of it once the classification is settled.
The Numbers Behind Software Tax
- 6.25%: the Massachusetts rate applied to taxable software transfers.
- 3: the categories treated as nontaxable, custom software, data processing, and multi-subscriber information services.
- 0: the relevance of where the server sits.
- 1: the certificate that lets a multi-state purchaser apportion the tax.
- 2: the routes to apportionment, the certificate at purchase or an abatement afterwards.
- $100,000: the Massachusetts sales level at which a remote seller must register here.
Multi-State Customers and Apportionment
The third question has a real answer, and it is one of the few genuinely favorable rules in this area.
Where prewritten software will be concurrently available for use in more than one jurisdiction, the tax can be apportioned rather than charged in full to Massachusetts. The mechanism is a multiple points of use certificate given by the purchaser to the seller, at or before the time the transaction is reported for sales or use tax purposes, after which the purchaser self-remits the apportioned Massachusetts share.
The timing is the catch. A seller who does not receive the certificate in that window is required to collect tax on the full sales price, which is how companies end up paying Massachusetts tax on software used mostly elsewhere.
The relief is that the window is not the only route. Massachusetts courts have confirmed that the certificate procedure is not the exclusive means of obtaining apportionment, and that the general abatement process remains available where the certificate was not provided in time. The abatement article sets out that process and its deadlines.
The Upside Nobody Mentions
One consequence of software being treated as tangible property cuts in the founder’s favor, and it appears in the same legislative change. The development and sale of prewritten software is considered a manufacturing activity for certain corporate excise purposes, regardless of how the software is delivered, which the Department’s regulation fact sheet states directly.
That classification can matter to apportionment of income, to investment credits, and to certain exemptions, which is a materially different conversation from the one about collecting 6.25% on subscriptions. It belongs alongside the corporate excise article rather than filed under sales tax.
It is also the reason this question deserves an answer from someone looking at both sides of the ledger. A company that dislikes being told its product is taxable software may also be a company entitled to treatment it is not currently claiming.
What This Means Before Your First Invoice
The expensive version of this problem is always the same. A company decides its product is a service, prices accordingly, invoices for two years, and then discovers the tax was collectible all along.
At that point the tax comes out of margin rather than from customers, because raising an invoice for tax that should have been charged eighteen months ago is a commercial conversation almost nobody wins.
Registration is its own question. A company with Massachusetts operations registers here; a remote seller reaches the same obligation by volume once its Massachusetts sales pass $100,000, and both sit inside the wider founder playbook.
Common Mistakes With Software Tax
- Assuming that nothing delivered means nothing taxable.
- Treating the server location as decisive when the regulation says it is not.
- Calling a software platform a data service without analyzing what the customer actually buys.
- Bundling taxable and nontaxable components without pricing them separately in the contract.
- Missing the apportionment certificate window and assuming the overpayment is lost.
- Claiming the sales tax treatment while ignoring the manufacturing classification that may come with it.
Get the Classification Right Once
This is one of the few areas where a decision made before launch governs everything afterwards. Classify the product properly, price and contract accordingly, register where required, and the question stops being a risk. Leave it, and it becomes an assessment covering every period since the first invoice.
Ed Parsons CPA analyzes software and subscription products against the Massachusetts rules, handles registration and filings, prepares apportionment positions for multi-state customers, and pursues abatements where tax was overcollected, under the firm’s startup tax help service.
Where an assessment has already arrived, start with a Business CPA Tax Resolution Case Analysis to price the exposure before anything is signed or paid. Reach the team through the contact page before the next invoice goes out.
