Pennsylvania Act 21 of 2026 moves the local sales tax in Philadelphia and Allegheny County from what was generally the point of sale, where the vendor is located, to the point of destination, where the product or service is delivered. The Pennsylvania Department of Revenue says the change became law on July 12, 2026, with a retroactive effective date of tax years after December 31, 2025, and that the department will not begin enforcing the new rules until October 1, 2026.
Philadelphia's combined sales tax rate stays 8%: Pennsylvania's 6% state tax plus Philadelphia's 2% local tax. Allegheny County's local tax is 1%. What changes is the sourcing of the local component.
For any vendor outside those counties, a tax calculation that once depended on the seller's location now needs the customer's delivery address. Billing systems, tax engines, and customer records need that address from October 1, 2026.
Before Act 21, the Pennsylvania Department of Revenue generally based local sales tax on the point of sale, meaning where the vendor was located. Local sales tax is now based on the point of destination, meaning where the product or service is delivered. The same rule covers Philadelphia's 2% tax and Allegheny County's 1% tax. State sales tax rules have not changed, and use tax rules have not changed: if sales tax is not collected at the time of purchase, the purchaser still owes use tax when taxable items or services are used in Philadelphia or Allegheny County.
Consider a simple example.
A company operates outside Philadelphia and sells a taxable product to a Philadelphia customer. Before the change, the seller's location decided the local portion of the tax. Under destination sourcing, the Philadelphia delivery address decides it, so the seller collects the 2% Philadelphia local tax if it is already required to collect Pennsylvania's 6% state sales tax. A delivery into Allegheny County works the same way at 1%.
Across thousands of transactions, the systems processing them need to know where the customer receives the product or service and apply the local tax consistently.
The rule applies to vendors already required to collect and remit Pennsylvania's 6% sales tax. For Philadelphia, the City of Philadelphia says that includes businesses outside Philadelphia that already collect the 6% tax.
The Pennsylvania Department of Revenue states that vendors already required to collect and remit the Commonwealth's 6% sales tax must also collect and remit Philadelphia's 2% local sales tax on taxable sales made to Philadelphia customers.
For remote sellers, that makes the first question less about Philadelphia and more about Pennsylvania:
Are you already registered and collecting Pennsylvania sales tax?
Pennsylvania's economic nexus rule applies to businesses that made more than $100,000 of gross sales into the Commonwealth in the previous 12 months (Sales and Use Tax Bulletin 2019-01). The measure is gross sales on all channels, including taxable and nontaxable sales, with no transaction count.
If you already have that Pennsylvania obligation, Philadelphia's new local sourcing requirement should be on your implementation list.
If you do not currently collect Pennsylvania sales tax, the Philadelphia change is not, by itself, a reason to assume you have a new collection obligation. Your broader Pennsylvania nexus and taxability position needs to be evaluated first.
Because "Philadelphia customer" is not a sufficient tax calculation input.
Your systems need to distinguish between customer records, billing addresses, shipping addresses, delivery locations, and the actual location relevant to the transaction. That becomes especially important for businesses with multiple sales channels, distributed customers, complex fulfillment, or automated recurring billing.
A ZIP code alone may not provide the precision your tax calculation requires.
And the issue is not limited to checkout.
A destination-based change can touch the entire transaction flow:
| Area | What to review |
|---|---|
| Customer data | Confirm complete and accurate customer and delivery addresses |
| ERP | Review tax codes and local tax treatment |
| Billing | Confirm Philadelphia and Allegheny County tax is calculated at transaction time |
| E-commerce | Test Philadelphia and Allegheny County delivery scenarios |
| Tax engine | Validate destination-based sourcing logic |
| Exemptions | Make sure valid exemption treatment continues to flow correctly |
| Returns | Confirm Philadelphia tax is separately captured for reporting |
| Audit records | Retain the location and tax determination data supporting each transaction |
A rate table update covers part of this change. The system also needs the delivery address to decide when the 2% or 1% rate applies.
The City of Philadelphia itself recommends that businesses review their sales and delivery information, update point-of-sale and online checkout systems, and review tax collection and filing processes ahead of the enforcement date.
A practical implementation should go further.
Pull recent Pennsylvania transactions and identify which customers and deliveries go into Philadelphia or Allegheny County.
Do not rely on customer state alone. You need enough address information to separate those destinations from other Pennsylvania locations.
The new law does not change which products and services are taxable. It changes how Philadelphia's local tax applies to taxable transactions.
That means your existing product taxability decisions should remain the starting point. The new question is whether your sourcing logic correctly identifies a Philadelphia destination.
Run transaction scenarios before you rely on the new logic.
At minimum, test:
Verify that the 6% state component and the 2% Philadelphia or 1% Allegheny County component are determined, recorded, and reported correctly, not only that the invoice total is right.
Philadelphia's local sales tax is collected and remitted through the Pennsylvania Department of Revenue, not directly to the City.
Your finance team should therefore confirm that the additional local tax flows correctly into the Pennsylvania filing and reconciliation process.
This is also a good opportunity to make sure transaction-level reporting can explain how the Philadelphia amount was calculated.
When an auditor asks why your Philadelphia tax treatment changed, "the system was updated in October" is not much of an answer.
Maintain documentation showing:
That creates a defensible trail from the law to the invoice.
Enforcement starts October 1, 2026. A sourcing error repeats across every qualifying transaction until someone finds it, which is what makes destination sourcing a systems issue.
If your tax calculation still assumes that the seller's location determines Philadelphia's or Allegheny County's local tax, it is automating an outdated rule.
Philadelphia's 2% local tax and Allegheny County's 1% local tax are not new. The delivery address now decides when a vendor collects them.
For businesses already collecting Pennsylvania sales tax, that calls for a focused review of customer location data, destination sourcing, billing logic, tax engine configuration, and reporting.
The best time to find a sourcing problem is during testing, not after hundreds or thousands of invoices have gone out.
Ready to put Philadelphia and Allegheny County destination sourcing to the test? CereTax helps businesses automate transaction-level sales tax calculation with destination sourcing, jurisdiction logic, rate updates, and audit-ready documentation.
