Massachusetts sales tax on SaaS is 6.25% on every renewal. Custom software built to one customer's specification is generally a nontaxable service. On a $120,000 annual software budget, the tax is $37,500 over five years.
Massachusetts sales tax on SaaS is 6.25%, charged on every subscription renewal, because the Department of Revenue treats remotely accessed software as prewritten software. Custom software built to one customer's specification is generally treated as a nontaxable professional service instead. On a large, multi-year software budget, that distinction is a real line item.
This is the tax angle on a decision covered more broadly in self-hosted vs cloud: the real tradeoffs. That piece weighs control, cost, and operational burden. This one isolates a single Massachusetts-specific number that rarely makes it into the comparison spreadsheet.
The governing rule is the Department of Revenue's computer industry regulation, 830 CMR 64H.1.3. It states that sales in Massachusetts of prewritten computer software, regardless of the method of delivery, are generally subject to sales tax.
The regulation is explicit that taxable transfers include licenses, leases, upgrades, and transfers of rights to use software installed on a remote server. That last phrase is what captures SaaS. Whether your team installs the software or opens it in a browser makes no difference to its tax treatment.
The rate is a flat 6.25%. Massachusetts has no local option sales tax layered on top, so a company in Worcester, Shrewsbury, or Boston pays the same rate on the same subscription.
The current approach traces to statutory changes effective April 1, 2006, which the Department reflected in this regulation. Cloud delivery arrived later, and the regulation's remote server language is how the state has kept subscription software inside the same rule.
The regulation defines custom software as a program prepared to the special order of a customer that is not prewritten software. Prewritten software is the inverse: software not designed and developed to the specifications of a specific purchaser.
Under the regulation's custom software provision, sales of custom software are treated as professional services rather than taxable sales of tangible personal property. Practitioner guidance summarizing the Department's position notes that custom application software designed to run on a prewritten operating system is still treated as custom software, rather than as a modification of the operating system.
The test is who the software was built for. A system designed around your workflows, your data model, and your integrations, for you, sits on the custom side of the line. A product built once and sold to many customers sits on the prewritten side, however much configuration it allows.
This is where most real projects live, and the rule is narrower than people assume. When someone modifies software they did not author, the regulation treats them as the author only of their own modifications.
Practitioner guidance on the Department's position adds the condition that matters in practice: for the modification work to be treated as nontaxable, the charges for custom modifications generally need to be separately stated and reasonably allocated on the invoice. A single bundled price for "the platform plus our customizations" can pull the whole amount onto the taxable side.
That makes invoice structure a decision worth making on purpose. If you are paying a firm to configure and extend a commercial platform, ask how the quote separates the license from the build work. Your accountant will want to see the split, and so will an auditor.
Many SaaS vendors based outside Massachusetts do collect it. The Department's remote seller rule, 830 CMR 64H.1.9, effective October 1, 2019, generally requires remote retailers with more than $100,000 in Massachusetts sales in a calendar year to collect. The Department's remote seller FAQ explains how that threshold is measured.
Smaller vendors, or vendors who have simply not registered, may not charge it. The obligation does not disappear. Massachusetts use tax applies at the same 6.25% to taxable items used in the state when the seller collected nothing, and electronically transferred software is within its scope. The buyer owes it directly.
This is a common audit finding precisely because it is invisible in day-to-day operations. Nobody notices a missing tax line on a subscription invoice. It surfaces later, across years of renewals, which is the same pattern described in why the sticker price is the smallest line item.
On its own, rarely. A tax rate is a poor reason to build software, and building something a mature product already does well is usually the more expensive path. The reasons to build are fit, ownership, and control, which we cover in own versus rent and what self-hosting actually costs.
Where the number earns attention is scale and duration. A company spending $120,000 a year on subscription software pays $7,500 a year in Massachusetts sales tax on it, or $37,500 over five years, before any price increases. That figure belongs in the comparison when the alternative is a system built once and owned.
The honest framing is that the tax is one input among several. It strengthens an ownership case that already stands on its merits. It does not create one. The same discipline applies to the migration cost of leaving a platform, laid out in what it costs to leave HubSpot or Webflow.
Possibly in its wording, not yet in force. On November 15, 2024, the Department published a working draft that would repeal and replace 830 CMR 64H.1.3 under a new title, Computer Software and Related Transactions. A working draft is a proposal. The current regulation remains the rule until a replacement is formally adopted.
If you are signing multi-year software agreements, it is worth asking your tax advisor whether the draft affects anything you are about to commit to. None of this is tax advice, and specific transactions turn on their facts.
We build custom systems at Kief Studio for companies across Central Massachusetts and beyond, so read this knowing which side of the build-or-buy question our work sits on. We still recommend commercial products when they fit. The point is that the comparison should include every real cost, and in Massachusetts, sales tax on SaaS is one of them.
The method behind how two people deliver custom builds at the output of a much larger team is at ltfi.ai, and the developer tools we publish are at kief.dev. For the full set of inputs we require before recommending anything, see recommendation before diagnosis.
Yes. Massachusetts treats remotely accessed software as prewritten software under 830 CMR 64H.1.3, so SaaS subscriptions are generally subject to the 6.25% sales tax regardless of how the software is delivered.
Generally no. Software prepared to the special order of a specific customer is treated as a professional service rather than a taxable sale. Modifications to prewritten software can qualify only for the modification work, and typically only when those charges are separately stated on the invoice.
The buyer generally owes Massachusetts use tax at the same 6.25% rate on taxable software used in the state when the seller did not collect. Remote sellers with more than $100,000 in Massachusetts sales in a year are generally required to collect under 830 CMR 64H.1.9.
No. Massachusetts has no local option sales tax on top of the 6.25% state rate, so the rate on a software subscription is the same in every Massachusetts city and town.
Not on its own. It is one real cost among several, and on large multi-year budgets it is material enough to include in the comparison. The stronger reasons to build are fit, ownership, and control. Confirm specifics with a tax advisor.
Chapter 30B sets how Massachusetts towns buy technology: sound business practice under $10,000, three written quotes up to $50,000, and sealed bids or proposals above that. School districts can use quotes up to $100,000.
Chapter 93A section 11 lets a Massachusetts business recover two to three times actual damages, plus attorneys' fees, from a vendor whose conduct is willfully unfair or deceptive. No demand letter is required first.
MarketsandMarkets puts the managed services market at $460.59 billion in 2026, and analyst estimates disagree by nearly $90 billion. To evaluate a managed service provider, start with what is excluded.
Work With Us
Kief Studio builds, protects, automates, and supports full-stack systems for businesses up to $50M ARR.
Newsletter
Strategy, psychology, AI adoption, and the patterns that actually compound. No spam, easy to leave.
Subscribe
