Is SaaS taxable in Pennsylvania? A developer's guide to PA's software tax rules

If you're building a product that needs to calculate SaaS sales tax for your customers, this guide is for you. It's part of Ziptax's SaaS Sales Tax by State series, and it covers Pennsylvania's SaaS tax rules and rates, what to account for when you build sales tax calculation into your product, and how Ziptax returns accurate Pennsylvania rates through an API without you building and maintaining a rate engine.

Pennsylvania SaaS sales tax at a glance

Product Taxability Rules

State Registration & Collection Triggers

Which types of software does Pennsylvania tax?

Pennsylvania doesn't draw its line at delivery method the way most states do. Under Act 84 of 2016 and 61 Pa. Code § 31.32, a buyer who can use the software is treated as having possession of tangible personal property, whether it arrives on a disk, as a download, or through a live cloud connection.

Bundles are where implementations can break. Make sure you apply taxability per line item, not per order. Pennsylvania's version of this problem is narrower than most states' because SaaS, downloads, and physical media all land in the same taxable bucket anyway.

The line that actually matters here is custom development and consulting work, which stays exempt only when it's priced and billed separately from anything canned.

How do you charge the correct sales tax rate for SaaS in Pennsylvania?

Every SaaS sale sourced to Pennsylvania carries tax: 6% everywhere in the state, 7% in Allegheny County, and 8% in Philadelphia. There's no $0 category to apply and no future law change to build toward the way there is in California or Colorado.

The SaaS tax rate-calculation work in Pennsylvania isn't about whether to charge tax; it's about resolving which of those three numbers applies to a given sale, and whether a specific line item on the invoice qualifies for the custom-development carve-out.

Engineering teams have two options for calculating the correct tax rate: call a real-time sales tax API, or manually build and maintain an internal rate engine.

Option 1: Use the Ziptax Sales Tax API

The Ziptax Sales Tax API takes the buyer's address at the point of checkout and evaluates whether that address sits inside Allegheny County, inside Philadelphia, or in the rest of the state, then returns the combined rate. The platform manages the jurisdiction boundaries so you don't have to hardcode a two-item lookup table and hope those boundaries stay put.

To calculate a live rate against a Pennsylvania address, use the v60 endpoint:

Bash

curl -G https://api.zip-tax.com/request/v60 \
    -H "X-API-KEY: <apiKey>" \
    -d key=your-api-key \
    --data-urlencode "address=1600 Market St, Philadelphia, PA, 19103"

To verify complete payload structures, explore the REST API documentation.

What an API will not tell you: whether a given B2B customer qualifies for Pennsylvania's multi-state apportionment option, or whether your company has crossed the $100,000 nexus threshold. Both stay on your side of the integration.

To automate threshold tracking, tax filings, and remittance, you can set up merchant management to connect TaxCloud automated compliance for your own business or for sub-merchants building on your platform.

Option 2: Build and maintain it yourself

Worth exploring if you have the in-house resources, since Pennsylvania's local layer is about as simple as a taxable state's gets: only two local jurisdictions to track, both riding on the same state registration and return as the 6% rate.

If you take this route, Pennsylvania needs four things handled:

1. Address-level resolution for exactly two overlays. Allegheny County adds 1% and the city of Philadelphia adds 2%. The combined-rate math is simple once you know which of the three buckets an address falls into; the work is in resolving that correctly at the boundary rather than guessing from a ZIP code.
2. Threshold accumulation on a previous calendar-year basis. You must track all gross sales into the state. If you cross $100,000 in a calendar year, you are required to begin collection on April 1 of the following year.
3. A narrow but real classification carve-out. Separately stating custom development or consulting work keeps it exempt; folding it into a canned-software invoice line pulls the whole charge into tax.
4. B2B apportionment tracking. Pennsylvania allows a Multiple Points of Use (MPU) exemption. Multi-state business customers can apportion tax by providing a PA Exemption Certificate (Form REV-1220) stating the percentage of users or license seats sitting outside the state. Your billing system needs a way to manage exemption certificates and apply that percentage reduction rather than defaulting every B2B invoice to full tax.

Five things to watch out for:

1. ZIP-based shortcuts for the two local overlays. Philadelphia and Allegheny County boundaries don't necessarily follow postal ZIP lines. For example, ZIP code 19131 spans both Philadelphia (8%) and Montgomery County (6%) right down City Avenue. ZIP 15090 in Wexford spans Allegheny (7%) and Butler (6%) counties. A ZIP-only lookup will misfire. Resolve the full street-level address.
2. Assuming delivery method matters. If your tax engine inherited "SaaS is treated differently from downloads" logic from another state, that logic will break in Pennsylvania: SaaS, downloads, and physical media are all taxed identically here.
3. Missing the B2B apportionment option. A billing system that always taxes the full invoice amount for multi-state business customers may be over-collecting relative to what Pennsylvania actually allows, which is a pricing and competitiveness problem even when it isn't a compliance one.
4. Folding custom consulting into a canned-software line item. An unseparated invoice line pulls an entire services engagement into tax, even when most of its value was labor rather than software.
5. Treating the Philadelphia and Allegheny overlays as self-administered local jurisdictions. Both ride on the same state registration and PA-3 return as the 6% rate, unlike home-rule cities in states such as Colorado. A system built to treat every local jurisdiction as a separate filing obligation will create compliance overhead Pennsylvania doesn't actually require.

When does a SaaS business have to collect sales tax in Pennsylvania?

Rule 1: Monitor your registration triggers (nexus)

You must register to file with the state the moment either of these conditions is met:

• Physical presence: an employee working in Pennsylvania, an office, inventory, or other property in the state.
• Economic threshold: check economic nexus thresholds. Your total gross sales (taxable and exempt) delivered into Pennsylvania cross $100,000 in the previous calendar year. Registration and collection enforcement kicks in on April 1 of the following year.

Rule 2: Apply the correct billing logic

Because SaaS is taxable in Pennsylvania from the first sale, there's no $0 period to manage the way there is in an exempt or pending-change state. Once you cross either trigger above, your billing system needs to do two things on every invoice:

1. Apply the correct rate—6%, 7%, or 8%—based on whether the sale sources to the rest of the state, Allegheny County, or Philadelphia;
2. And, for B2B customers who can provide an MPU exemption certificate, apply the state's apportionment rules instead of taxing the full invoice by default.

Where Ziptax helps

If you're building a custom billing engine, a niche ERP, or a B2B SaaS platform, you don't need an enterprise compliance suite just to calculate an accurate checkout rate. You just need a fast, reliable endpoint.

Ziptax handles the infrastructure layer of sales tax calculation so your team can focus on your core product.

• Rooftop Precision: Resolves rates across 12,000+ U.S. tax jurisdictions using exact address and coordinate-based lookups, eliminating the accuracy liabilities of ZIP-based shortcuts.
• Engineered for Platforms: Built specifically to embed live tax calculations directly into checkout workflows, API endpoints, and marketplace billing frameworks.
• Frictionless Pricing: Designed for cost-conscious development teams who want to pay strictly for active calculation calls without committing to heavy enterprise software contracts.
• The TaxCloud Runway: When your transaction volume scales or your users demand automated filing and remittance services, you can pair Ziptax with TaxCloud for the rest of compliance. You get a lightweight API to deploy today and a filing and remittance backend ready when you need it.

Get Pennsylvania SaaS tax rates from an API

Address-level rates for every Pennsylvania jurisdiction, plus the rest of the US, Canada, and select other markets.

Frequently asked questions

Do you have to register in Pennsylvania if you only sell SaaS? Yes, if you have a physical presence in the state or if you cross $100,000 in gross sales delivered into Pennsylvania in the previous calendar year. Unlike an exempt state, there's no edge case where a pure-SaaS seller crosses the threshold on paper but has nothing taxable to report: Pennsylvania counts SaaS revenue toward the threshold and taxes it identically to standard software.

Does Pennsylvania tax software differently depending on how it's delivered? No. Pennsylvania amended its tax code via Act 84 of 2016 to explicitly capture software "whether it is downloaded, streamed, or otherwise accessed." The one real distinction in Pennsylvania's rules is between canned (prewritten) software and genuine custom development, not between delivery methods.

Can you use a ZIP code to get the Pennsylvania sales tax rate? Not reliably at the boundaries. Pennsylvania only has two local sales tax overlays, Allegheny County and Philadelphia, which makes the rate table simpler than most states', but a ZIP code can still span territory on both sides of either boundary (e.g., ZIP 19131 dividing Philadelphia and Montgomery County). Resolve the full street-level address to avoid misapplying or missing a local add-on near a border.

What happens if I bundle custom development work with my SaaS subscription in Pennsylvania? It depends on how the invoice is structured. If the custom development or consulting work is billed as its own separately stated line item, it stays exempt while the SaaS or canned-software line is taxed normally. If the two are combined into a single undifferentiated charge, the whole amount becomes taxable.

Sources

1. Pennsylvania Act 84 of 2016 (Amending 72 P.S. § 7201)
2. Pennsylvania Department of Revenue, Sales and Use Tax Bulletin 2019-01 (Economic Nexus)
3. Pennsylvania Department of Revenue, Local Sales, Use and Hotel Occupancy Tax
4. Streamlined Sales Tax Governing Board, Pennsylvania State Detail