Is SaaS Taxable in Massachusetts? Yes — but the Exemption Next Door Is Illustrated Entirely by Machines

Key Takeaway: Massachusetts taxes SaaS at 6.25%, flat, no local add-on: prewritten software is tangible personal property, and the regulation says in terms that a transfer of the right to use software on a remote server is a taxable transfer. One subsection away sits a data-processing exemption whose three worked examples are ATM terminal driving, electronic funds transfer and credit-card verification — three services with no human anywhere in them, exempted in 2006. That is the most agent-shaped exemption text in any state regulation I have read.

The Short Answer

M.G.L. c. 64H, § 2: "An excise is hereby imposed upon sales at retail in the commonwealth, by any vendor, of tangible personal property or of services performed in the commonwealth at the rate of 6.25 per cent of the gross receipts of the vendor." There is no local layer in Massachusetts. A ZIP changes nothing; 6.25% in Boston is 6.25% in Pittsfield.

Prewritten software is inside that base by definition — 830 CMR 64H.1.3(2): "Tangible personal property includes electricity, gas, steam, and prewritten computer software." Then (3)(a) closes the delivery argument before anyone can make it:

Taxable transfers of prewritten software include sales effected in any of the following ways regardless of the method of delivery, including electronic delivery or load and leave: licenses and leases, transfers of rights to use software installed on a remote server, upgrades, and license upgrades.

That sentence sits in a regulation effective October 20, 2006. Massachusetts settled the hosted-software question two decades ago in a single clause and has not needed to revisit it. Sell an agent tool, a model API or a vector store into Massachusetts and the starting position is that you are selling prewritten computer software and owe 6.25%.

Two Definitions That Do the Work

License is "the right to use, copy, or access software, regardless of the location or ownership of any server on which the software may be installed." Server location is not merely unhelpful in Massachusetts; the regulation removes it from the analysis by definition.

Prewritten Software reaches further than most operators expect: software "modified or enhanced to any degree" to a purchaser's specification remains prewritten software unless the modification carries a reasonable, separately stated charge. A hosted agent product configured per customer is prewritten software with configuration, not custom software.

The genuine custom exit at (6)(a)-(b) is narrow and was drawn for people — it applies where "the principal object of the purchaser is the professional and personal services of a programmer, systems analyst, or other person," with the medium an inconsequential element, generally under 10% of the contract price. You reach it by pointing at humans who did the work for you specifically. Almost no agent input qualifies.

The Find: An Exemption Written for Machines

Here is what makes Massachusetts worth a careful read rather than a rate lookup.

830 CMR 64H.1.3(9)(a):

Charges for processing data furnished by customers are generally exempt from sales tax, regardless of the method of delivery of the processed information to the customer. Processing data may include the following: summarizing data, computing data, extracting data, sorting files, and sequencing data as well as services that provide the customer or subscriber with additional, different, or restructured information. The following are examples of exempt data processing: charges automated teller machine (ATM) terminal driving services, electronic funds transfer services, or credit card or check verification services.

Read the three examples again. ATM terminal driving, electronic funds transfer and card verification are each a machine answering a machine. Massachusetts chose, as its illustrations of an exempt service, three services in which no person participates at all — in 2006, for reasons that had nothing to do with artificial intelligence.

I have spent this quarter cataloguing state place-of-use definitions that assume a human at a desk: Maryland is the only one whose text names equipment outright, and Washington's reaches machines only by the accident of the word "agents." This is the inverse. Massachusetts's exemption side is the one written without people in it, and the description — take the customer's data, return "additional, different, or restructured information" — is a plain-English description of an inference call.

I am not claiming Massachusetts exempts model APIs. I am claiming the argument exists in the state's own words, that it is better than the equivalent argument in any other state I have read, and that no Massachusetts authority addresses machine-performed processing either way. That is an unsettled question, not a position.

The Line That Decides It

The regulation supplies the boundary, and it is not about technology. It is about control. 830 CMR 64H.1.3(13)(b), describing the neighbouring exemption for database access: "In a database service transaction, the customer does not direct or control the entry of data into the database but merely selects data for retrieval."

That is the test. Retrieval is exempt; operation is not. And it is exactly where an agent transaction gets uncomfortable, because a prompt is not a retrieval request — it is an instruction that directs functionality task by task. Querying a vendor's corpus sits on the retrieval side. Submitting open-ended instructions that steer what the vendor's software does is operating it, which lands back inside (3)(a).

(14)(a) states the general rule and its single, conjunctive exception:

Generally, charges for the access or use of software on a remote server are subject to tax. However, where there is no charge for the use of the software and the object of the transaction is acquiring a good or service other than the use of the software, sales or use tax does not apply.

Both prongs, not either. The worked example is a person bidding in an online auction: software was used, but the object was the clothing and the software was free. That is precisely the shape of agent-mediated commerce, and the prong that decides it is the pricing one. If the software access is unpriced, the exception is live. The moment you charge for the call, you are selling the software.

What Massachusetts Does Not Tax

(14)(b) is worth quoting for anyone building a price list:

Charges for web site hosting, designing computer systems, designing data storage and retrieval systems, consulting services, feasibility studies, evaluations of bids, technical analysis, programming, and the like are generally not taxable if they are not part of a sale of computer hardware or prewritten software.

Bundle them into a taxable software sale as a mandatory component and they become taxable; keep them genuinely separate and they are not — and under (14)(d) the place where they are performed "is immaterial."

One more line matters to an invoice. Under (8)(a), reports "sold or intended to be sold to two or more purchasers" are taxable standard information; (8)(b) exempts a report of individual information not substantially incorporated into reports furnished to others. The same compiled output sold to many buyers is taxable; the one-off result computed for you is not.

Sourcing: Apportionment Does Not Wait for the Certificate

Massachusetts runs the most developed multiple-points-of-use regime in the country, and we read the mechanics against agent facts last month. One provision is routinely missed. 830 CMR 64H.1.3(3)(b) imposes apportioned Massachusetts use tax on prewritten software concurrently available for use in multiple jurisdictions "without regard to" the jurisdiction where the purchaser takes delivery, the location or ownership of any server, or "whether the purchaser gives the seller an MPU exemption form."

Apportionment in Massachusetts is a feature of the tax, not a favour granted for paperwork. (15)(b) then lets a seller who knows the software is multi-jurisdictional work with the purchaser on "any reasonable, but consistent and uniform, method of apportionment" supported by business records, with relief from further collection obligation absent bad faith. For an operator whose footprint is realized over a billing period rather than known at purchase, that back-end route is the one that fits.

How AgentTax Handles Massachusetts

Verified against the live engine this morning, $1,000 into Massachusetts with nexus configured:

• SaaS, API access, compute, data processing, model access, digital goods, licenses and subscriptions all compute at 6.25% — $62.50. No local layer; a Boston ZIP returns the same figure as no ZIP at all, and the advisory says so rather than leaving the zero to be inferred.

• Cloud infrastructure and storage return exempt — $0. Both cells were adjudicated against Department guidance on cloud computing, and the boundary is in the engine's own reason text: bare capacity where you run your own stack is exempt; a "storage" product that actually grants use of vendor application functionality is taxable and belongs on SaaS.

• Data processing computes at 6.25%, a deliberately conservative answer against the (9)(a) exemption above. The taxable side holds live authority, no Massachusetts authority addresses automated processing, and transaction data alone cannot tell us which side of the control line a customer sits on. We collect the higher number and disclose the argument rather than quietly taking the exemption on your behalf. If your facts are pure pattern — fixed processing function, per-job pricing, individual output, no right to use or access the software — you have a credible exemption or abatement claim, and it is yours to make.

• Consulting computes at 6.25%. Against (14)(b) that is an over-collection on separately sold advisory work — an instance of a known cross-state classification defect already logged for review rather than a new Massachusetts finding, and Massachusetts is the ninth state where the same routing produces the same over-charge.

• We do not compute multiple points of use in any state. A calculation returns the full-price figure: the correct amount to remit before an apportionment claim, and the wrong amount to treat as final if your workload spans jurisdictions.

What to Watch

The Department circulated a working draft rewrite of 830 CMR 64H.1.3 dated November 2024 that has never entered the formal notice-and-hearing channel — dormant now roughly twenty-two months. If it is finalized, its treatment of platform services, where vendor software is essential to deploy the customer's own code, would move the cloud-infrastructure line, and every determination above would need re-reading against the adopted text.

Beyond that: whether the Department ever addresses automated processing under (9)(a) directly, which is the single most valuable thing it could publish for this industry; and whether the control test at (13)(b) is applied to a prompt-driven service before a taxpayer has to litigate it.

No state has issued guidance addressing agent-initiated commerce directly. Everything above applies human-drafted categories to machine transactions, which is analysis rather than settled law.

Try it on your own transaction types. Run a Massachusetts SaaS transaction now (no account), or get a free API key. Compare it with Washington's digital automated services hook, California's 2027 base change and New York's user-apportionment metering; see every state in the 50-state SaaS taxability guide and the AI agent sales tax hub.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.