Is SaaS and AI Taxable in Pennsylvania? Yes — 6% Statewide, 8% in Philadelphia

Key Takeaway: Yes — Pennsylvania taxes SaaS, data processing, and information services delivered through software at a 6% state rate, with Philadelphia (8% combined) and Allegheny County (7% combined) imposing significant local additions. Act 84 of 2016 put canned software — "whether electronically or digitally delivered, streamed or accessed" — squarely in the statute.

The Bottom Line

Pennsylvania is one of the most important states in the country for digital sales tax. If you sell SaaS, AI services, data processing, or information services into Pennsylvania, you almost certainly owe sales tax — and the rates matter more than in most states because of the local tax additions.

The state rate is 6%. That alone would make Pennsylvania a mid-range state. But Philadelphia imposes an additional 2%, bringing the combined rate to 8% — one of the highest combined rates in the Northeast. Allegheny County (Pittsburgh and its suburbs) adds 1%, making the combined rate 7%. For SaaS companies with customers concentrated in Pennsylvania's two major metro areas, the effective rate is substantially higher than the 6% headline suggests.

What makes Pennsylvania worth careful attention is the combination of three things: an explicit statutory basis for taxing remotely accessed software (Act 84 of 2016), case law holding that delivery method is irrelevant to software taxability (Graham Packaging), and materially different rates across three geographic tiers. Understanding these elements is essential to getting Pennsylvania right.

I will tell you something that will not make your finance team happy: Pennsylvania requires real attention per compliance dollar. The rates are high in the metros, the statutory language is broad, and the Department of Revenue has a long track record of taxing software transactions however they are packaged. This is not a state you can run on autopilot.

Pennsylvania's Sales Tax Framework

Pennsylvania imposes sales and use tax under 72 P.S. § 7201 et seq. (the Tax Reform Code of 1971). The state rate is 6%. Two local jurisdictions impose additional taxes:

• Philadelphia: 2% local tax, for a combined rate of 8%

• Allegheny County: 1% local tax, for a combined rate of 7%

No other Pennsylvania jurisdictions impose local sales tax. This means the rate map is relatively simple compared to states with hundreds of local taxing jurisdictions — but the three rates that exist are materially different, and getting the rate wrong on a large contract is expensive.

For digital services sold into Pennsylvania, tax is sourced to the customer's location: a Philadelphia customer pays 8%, an Allegheny County customer pays 7%, and everyone else in the Commonwealth pays 6%. Validate customer addresses against the two local jurisdictions — on a $10 million Pennsylvania book of business, the difference between 6% and 8% is $200,000 per year in tax.

How Pennsylvania Treats Digital Services

SaaS & Cloud Computing

Pennsylvania taxes SaaS, and since 2016 the answer has been written directly into the statute. Act 84 of 2016 amended the definition of tangible personal property at 72 P.S. § 7201(m)(2) to cover an enumerated list of digital items — video, books, apps, games, music, and canned software among them — "whether electronically or digitally delivered, streamed or accessed and whether purchased singly, by subscription or in any other manner, including maintenance and updates." For canned software specifically, the statute taxes it "notwithstanding the function performed, including support, except separately invoiced help desk or call center support."

Read those phrases together and the SaaS analysis is over. "Streamed or accessed" captures cloud delivery — the customer does not need to download anything. "By subscription" captures the SaaS billing model by name. And "notwithstanding the function performed" cuts off the argument that the software's purpose (processing data, generating content, producing analysis) changes the classification.

The Department of Revenue's regulation is to the same effect. Under 61 Pa. Code § 60.19, "the sale at retail or use of canned software, regardless of the method of delivery, including updates, enhancements and upgrades is subject to tax."

Custom software — software designed, created, and developed for a single customer — is not taxable. Section 60.19 treats it as a nontaxable computer programming service. But the bar for "custom" is high: the regulation provides that canned software "includes custom software that is transferred pursuant to a sale at retail to a person other than the original purchaser." If the base platform is standardized and only the configuration is customized, it is not custom. True custom software requires genuine bespoke development for one buyer.

Graham Packaging: Delivery Method Doesn't Matter

Before Act 84 codified the rule, the Commonwealth Court had already reached it. In Graham Packaging Co. v. Commonwealth, 882 A.2d 1076 (Pa. Commw. Ct. 2005), the taxpayer sought a refund of sales tax paid on renewal fees for licenses of off-the-shelf software, arguing the renewals were not taxable transfers of tangible personal property.

The court disagreed, holding that "the sale of all canned software, whether transmitted electronically or on a physical medium, is taxable as the sale of tangible personal property." The court looked to the essence of the transaction rather than its packaging — "it is the nature of the software itself, not the package in which it comes, which must determine whether the software and accompanying license is tangible personal property" — reasoning that this approach "does not exalt form over substance; it results in the uniform tax treatment of all canned software; and it avoids the potential for parties to structure their transactions to avoid tax liability."

Two years later the same court applied it again: in Dechert LLP v. Commonwealth (Pa. Commw. Ct. 2007), a law firm's challenge to tax on canned software licenses failed because Graham Packaging was "directly on point and... controlling."

Two lessons for AI companies. First, Pennsylvania courts will not let delivery mechanics drive taxability — electronic transmission, license renewals, and remote access all land in the same place as shrink-wrapped disks. Second, the essence-of-the-transaction framing means the Department and the courts ask what the buyer is really acquiring. Where the answer is the use of standardized software — and for nearly all SaaS and AI platforms, it is — the transaction is taxable.

AI and Automated Services

Pennsylvania has not issued AI-specific sales tax guidance. Under the existing framework, AI services are analyzed the same way as any other software-delivered offering: is the buyer paying for the use of canned software, accessed remotely?

For most commercially available AI tools — chatbots, content generators, data analysis platforms, automation tools — the answer is yes. The AI is standardized software; the customer is paying to use it; § 7201(m)(2) taxes canned software "streamed or accessed"; and "notwithstanding the function performed" forecloses the argument that generating analysis rather than, say, tracking projects takes the product out of the base.

For AI offerings that deliver outputs more akin to professional services — where human professionals use AI as a tool and deliver bespoke advisory work product — there is a genuine classification question, because Pennsylvania does not tax professional services. The essence-of-the-transaction inquiry asks whether the buyer is purchasing software access or professional judgment. The Department has historically been skeptical of professional-service characterizations for automated processes, and if the software is the service, there is no non-taxable service to fall back on. Take that position only with strong factual support, and ideally a letter ruling.

Data Processing & Information Services

Companies sometimes assume "we're a data processor, not a software vendor" or "we sell information, not software" changes the Pennsylvania answer. Since Act 84, that framing rarely helps. The statutory hook is the software itself: if your customers access canned software — an API, a dashboard, a hosted model — the charge is taxable under § 7201(m)(2) regardless of whether the function performed is processing the customer's data or delivering compiled information. That is precisely what "notwithstanding the function performed" is there to say.

Information products delivered as digital goods (reports, publications, media) sit in the same § 7201(m)(2) list independently of the software analysis. Either way, the Pennsylvania answer for AI-delivered data processing and information offerings is: taxable.

What This Means for Your Business

Economic Nexus Thresholds

Pennsylvania's economic nexus threshold is $100,000 in gross sales into the state during the prior calendar year. There is no transaction count threshold. This threshold applies to all sellers, not just marketplace sellers, and includes sales of both tangible and digital products.

For SaaS companies with enterprise clients in the Philadelphia and Pittsburgh metro areas, the $100K threshold is easily reached. Pennsylvania has one of the largest state economies in the nation, a robust financial services sector, a major healthcare industry, and a growing tech presence. Significant SaaS purchasing activity flows through Pennsylvania.

What to Collect

Collect at the rate for the customer's location:

• Philadelphia customers: 8%

• Allegheny County customers: 7%

• All other Pennsylvania customers: 6%

This three-tier rate structure must be accurately maintained in your billing system. For SaaS companies with recurring subscriptions, ensure that customer addresses are validated against the correct rate zone.

B2B vs. B2C

Pennsylvania does not provide a broad B2B exemption for software or digital services. Business purchases of SaaS are taxable on the same basis as consumer purchases. There are exclusions for property used directly in manufacturing, farming, processing, and certain utility operations (built into the "sale at retail" and "use" definitions), but these do not apply to general business-use software.

The manufacturing exclusion is worth noting for SaaS companies selling to Pennsylvania manufacturers. Software used directly in manufacturing operations — controlling production equipment, managing manufacturing processes — may qualify. But enterprise SaaS used for business operations (CRM, HR, finance, project management) does not meet the directly-in-manufacturing standard.

Edge Cases and Watch Items

Separately stated services. If your SaaS contract includes non-taxable components — training, consulting, implementation — separately state them on the invoice. Note the statutory trap in § 7201(m)(2): canned-software support is taxable unless it is separately invoiced help desk or call center support (and the Department reads that exception narrowly — separately stated help desk support where the vendor does not access the software). Bundle everything into one subscription price and the Department will treat the entire amount as taxable canned software.

The Philadelphia differential. The 8% rate in Philadelphia is not a minor detail. For SaaS companies with significant Philadelphia customer bases — financial services, healthcare, education, legal — the 2% local addition represents a meaningful cost. Many national SaaS companies have substantial Philadelphia revenue. Budget accordingly.

Cloud infrastructure and hosting. Pure infrastructure — server space and compute without canned-software functionality — presents a different analysis than SaaS, because the § 7201(m)(2) hook is the software. In practice, most "hosting" offerings bundle managed software layers, dashboards, and tooling, and the Department can be expected to examine the essence of the transaction. If you sell infrastructure into Pennsylvania, get a professional review of the actual deliverables rather than relying on the product's marketing category.

Professional services. The essence-of-the-transaction inquiry leaves room for genuinely bespoke, human-delivered advisory services that happen to use software as a tool. Do not stretch it to cover automated services. The Department's consistent direction — in the statute's "notwithstanding the function performed" language and in the case law — is toward taxing standardized software however sophisticated its output.

Maintenance, updates, and upgrades. All taxable when tied to canned software, per 61 Pa. Code § 60.19. Do not assume a separately priced "maintenance plan" escapes the base.

Beardsley's Position

Pennsylvania taxes SaaS and software-delivered digital services broadly. The 6% state rate is significant, and the local additions in Philadelphia (8%) and Allegheny County (7%) create some of the highest effective digital tax rates in the Northeast.

Standard SaaS is taxable. The statute (72 P.S. § 7201(m)(2), as amended by Act 84 of 2016), the regulation (61 Pa. Code § 60.19), and the case law (Graham Packaging, applied again in Dechert) all point the same direction, and they were written to close the delivery-method arguments, not to invite them.

For AI services that deliver professional-grade analysis through standardized software, plan on taxability. The essence-of-the-transaction analysis creates room for argument only where human professional judgment is genuinely the deliverable, and the Department's track record is to tax automated services regardless of how sophisticated the output is.

Pennsylvania demands attention. The three-tier rate structure and the breadth of the digital-goods statute combine to create a state where getting it wrong is expensive. My advice: invest in getting Pennsylvania right. Register, collect at the correct rates (and make sure your rate determination accounts for Philadelphia and Allegheny County), and separately state genuinely non-taxable service components on every invoice.

This is a state where the cost of compliance attention is lower than the cost of an audit.

How AgentTax Handles Pennsylvania

When you pass a Pennsylvania transaction through the API, the engine:

• Computes SaaS, data processing, and information services as taxable at the 6% state rate, per Pennsylvania-specific rules in its taxability matrix — consistent with 72 P.S. § 7201(m)(2) and 61 Pa. Code § 60.19. Declared B2B status does not change the result, because Pennsylvania offers no general B2B exemption for software.

• Applies the local additions by ZIP code. The engine's rate table carries the Philadelphia +2% and Allegheny County +1% additions — a transaction with a covered Philadelphia ZIP computes at the 8% combined rate, and a covered Allegheny ZIP at 7%. Coverage is explicit by design: when a calculation is sourced to a Pennsylvania ZIP the table does not cover, the engine returns the 6% state-rate calculation and says so with an explicit ZIP-unknown advisory rather than silently guessing the local layer. If your Pennsylvania book is concentrated in the two metros, resolve customer addresses to ZIP and pass them — the difference is real money.

• Tracks the $100,000 economic nexus threshold (no transaction-count prong) through its nexus monitoring.

• Returns the full audit trail — classification, rate composition, and sourcing — with every response, and discloses via advisory when a digital category is computed from the state-wide digital default rather than a Pennsylvania-specific category rule.

AgentTax handles Pennsylvania automatically. One API call per transaction returns the classification, the ZIP-aware rate, and the citation trail. Get your free API key (no credit card), or see how Pennsylvania compares in our 50-state SaaS taxability guide.

This analysis is for informational purposes only and does not constitute legal or tax advice. Consult a licensed tax professional for compliance decisions.