Is SaaS Taxable in Maryland? The 3% Rate Turns on Use — and Maryland Already Wrote the Sourcing Rule for Machines

Key Takeaway: Maryland taxes SaaS, cloud services, data processing, and AI services. The much-repeated "3% for businesses, 6% for consumers" summary is wrong, and it is wrong in a way that matters for anyone wiring a rate into code: the rate turns on whether the purchase is solely for use in an enterprise computer system, not on who signed the invoice. And buried in the apportionment machinery is something no other state has: a statutory definition of where a service is used that names equipment, not only people.

The Framework

Maryland imposes sales and use tax under Title 11 of the Tax-General Article; I read the operative sections as currently published this morning. The general rate is 6% (§11-104(a)(2)(i)), and there are no local sales taxes to layer on, because §11-102(c)(1) forbids counties and municipalities from imposing one. Six percent is the whole answer, statewide.

The 2025 expansion added two clauses to the definition of "taxable service": §11-101(m)(14), "a data or information technology service described under NAICS Sector 518, 519, or 5415," and (m)(15), "a system software or application software publishing service described under NAICS Sector 5132." NAICS means the 2022 edition, per §11-101(c-12). Then §11-104(l)(1): "The sales and use tax for a sale of a taxable service described under § 11-101(m)(14) and (15) of this subtitle is 3% of the taxable price."

Read on its own, that provision contains no buyer condition at all. Which is why the next one matters. §11-104(l)(2): "If a different rate from the rate specified under paragraph (1) of this subsection could be applied to a sale or use of tangible personal property, a digital code, a digital product, or a taxable service, the higher rate shall apply to the sale."

The Split Is a Use Test

So where does 6% come from? From the definition of "digital product." Maryland taxes digital products at 6%, and §11-101(c-4)(3)(vi) carves out of that definition:

computer software or software as a service purchased or licensed solely for commercial purposes in an enterprise computer system, including operating programs or application software for the exclusive use of the enterprise software system, that is housed or maintained by the purchaser or on a cloud server, whether hosted by the purchaser, the software vendor, or a third party.

The Comptroller's Technical Bulletin No. 56 (June 10, 2025, revised June 30, 2025), which I read in full this morning, states the consequence directly. Q5: SaaS "meets the definitions of both a digital product and a software publishing service." Q6: SaaS "not purchased or licensed solely for use in an enterprise computer system, such as a purchase for use by an individual, is a digital product and is therefore subject to taxation at the 6% rate," while "the same SaaS is taxed at the 3% rate when sold for use in an enterprise computer system."

That is not a buyer-status rule. A business buyer whose purchase is not solely for enterprise-computer-system use falls on the 6% side, and (l)(2) puts it there. The correlation with buyer type is strong enough that the shorthand survives; it is not what an auditor will apply. Note also that "enterprise computer system" is defined nowhere in the statute or the bulletin, and Maryland prescribes no certificate for this axis — there is no form that makes the 3% posture official.

Two timing rules from TB-56 are worth knowing: the customized-software exemption was repealed effective July 1, 2025 (Q7), and contracts executed before that date stay outside the tax even where payment and delivery fall after it (Q13-Q20) — though a change order expanding scope is a new sale (Q16).

The Find: Maryland Named the Machines

Here is the part that is in no summary I have read.

A buyer who will use a taxable service both inside and outside Maryland may present a multiple points of use certificate under §11-403(e), implemented at COMAR 03.06.01.49; it shifts the collection obligation to the buyer, who then apportions. §11-403(e)(3) governs the method: any "reasonable but consistent and uniform method of apportionment that is supported by the buyer's records as they exist at the time of the sale and accurately reflects the primary use location in the State." COMAR 03.06.01.49G says the same in regulation.

Everything therefore rests on "primary use location," defined at §11-101(e-1)(1) — and subparagraph (ii) is the sentence:

if the buyer is not an individual, the location of the buyer's end users, including employees, or equipment that makes use of the digital code, digital product, or taxable service.

Equipment. Not "an employee or agent of the purchaser in the performance of their duties," which is how California's draft Regulation 1600.2 defines a user, and not the seat counts every practitioner comment in California's record assumed. Maryland's statute contemplates that the thing making use of a service may be a machine, and tells you to source to where that machine is.

The Comptroller's own guidance does not use it. TB-56 Q32 gives exactly two examples of a "reasonable method": Maryland employees over total employees, and Maryland licenses over total licenses. Both are seat denominators. Neither describes a buyer whose consumption of an inference API happens on rented capacity in three regions with no seats at all.

But Q32 says methods "include" those two, and §11-403(e)(3) and COMAR 03.06.01.49G(2) permit any reasonable method supported by contemporaneous records. A buyer whose end users are machines has statutory text pointing at equipment location. The method must be consistent, uniform, and documented at the time of sale — which for an agent operator means keeping the regional call and capacity records you already generate.

This is live law, in a state collecting the tax now. California's interested-parties meeting on its digital-products regulations is September 10, 2026, and as I wrote last week, the sourcing question for a transaction with no human user is absent from that entire written-comment record. Maryland is the working example nobody in the file cited.

What Sits in the 3% Base

TB-56's Section IV enumerates them. NAICS 518 covers cloud computing, cloud storage, IaaS, PaaS, application hosting, automated data processing, colocation, and cryptocurrency mining; 519 covers internet search portals and archives; 5415 covers custom software programming and support, systems integration design, computer software consulting — and, notably, industrial robot programming, machine vision software development, and robotics applications software development.

What appears nowhere in those twelve pages: artificial intelligence, machine learning, or models. "Agent" appears once, describing a prime contractor acting as agent of the federal government. Classification also does not follow your own filed NAICS code — TB-56 Q2 and COMAR 03.06.01.48D require each service to be evaluated individually against the activity descriptions.

Resale, and Why the Agent Stack Pays Twice

The resale exemption is narrower here than most people expect. TB-56 Q22: it applies "if the taxable service is in the same form when resold by the buyer as it was when purchased by the buyer, and has not been used by the buyer," and "use of a service includes a use to fulfill the obligations of a contract." The bulletin's own example is a web hosting provider that may buy cloud storage tax-free to resell as cloud storage — but not if it uses that storage to provide some other service. An agent platform that buys model access and inference capacity and then sells an outcome is using those inputs, not reselling them, and Q17 and Q23 confirm the pattern for contractors: the intermediate purchase is taxable and the cost of performance goes up.

The only service-specific exemptions are narrow — cloud computing sold to a qualified cybersecurity business, and sales to or by a qualified company in the University of Maryland Discovery District (TB-56 Q27; COMAR 03.06.01.48F) — and no certificate is issued for either, so the buyer carries the documentation.

The Digital Advertising Tax Is a Different Tax

Maryland's digital advertising gross revenues tax lives in Title 7.5 and has nothing to do with the analysis above. It also no longer stands: on August 14, 2026 the Maryland Tax Court granted summary judgment to the taxpayer on all counts in Apple Inc. v. Comptroller of Maryland, No. 23-DA-OO-0456, reversing the Comptroller and ordering refunds with interest — one of three decisions issued that day. We covered it here. If you sell software or services, it was never yours.

How AgentTax Handles Maryland

Verified against the live engine this morning, $1,000 into Maryland with nexus asserted:

• SaaS with is_b2b: true computes at 3% — $30 — with an advisory saying in as many words that buyer status is a proxy for the fact Maryland actually taxes on, and that a caller who cannot establish the "solely" fact should reserve at 6%.

• A use_context declaration moves the number. enterprise_system holds 3% and records the attestation; individual or mixed returns $60 at 6% citing the higher-rate override. The declaration is echoed and retained — self-generated audit documentation, not a state-blessed safe harbor, because Maryland offers none.

• SaaS to a consumer computes at 6% — $60, as does a call that sends no is_b2b flag at all.

• Data processing, API access, compute, and cloud infrastructure compute at 3% flat — $30 — for every buyer: the §11-104(l)(1) category rate behaving as written. Generic digital goods compute at 6% through the state default.

• Consulting computes at 3%, not as an exempt professional service. Maryland excludes professional services obtained electronically from the digital-product definition (§11-101(c-4)(3)(iv)), and generic advisory work is not obviously a NAICS 5415 computer service — a conservative result rather than a confident one, logged for review.

• We carry no Maryland ZIPs, so a calculation with a ZIP returns the state rate plus a ZIP-unknown advisory. As in Michigan, that costs nothing: there are no local rates to miss.

• We do not apportion. One destination state, one answer. In a state with a live multiple-points-of-use certificate that is a real limitation, and we would rather say so than imply an MPU position we do not compute. Economic nexus is $100,000 or 200 transactions, per the threshold the engine carries.

Try it on your own transaction types. Run a Maryland SaaS transaction now (no account), or get a free API key. See how Maryland compares in the 50-state SaaS taxability guide, the AI agent sales tax hub, and Michigan's repealed MPU experiment.

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.