Muhlenberg Township to Reading
Pennsylvania Act 32 local earned income tax · BERKS to ADAMS County · tax year 2026
Home rate
1%
Muhlenberg Township, residents
Work rate
1%
Reading, non-residents
You pay
1%
the higher of the two
Cost of the commute
$0
a year, above the home rate
What this commute costs you
no extra local taxThe two rates are identical, so the test is a wash — but this pair sits exactly at the line, and any rise in Reading's commuter rate would start costing you. You pay the solid bar only — Pennsylvania charges the higher of the two rates, never their sum. Local earned income tax only; state, federal and payroll tax apply on top.
What this commute actually costs
- Good news for this commute. Working in Reading costs you nothing extra. Muhlenberg Township charges residents about 1%, at least as much as Reading asks of people who work there but live elsewhere. The higher rate wins, so your home rate is simply the rate. That is $600 a year, wherever you work.
- This route is one of 5 into Reading tracked here, ranking 4 by how many people travel it. Around 572 make the trip. Seen from the other end, Reading is Muhlenberg Township's number 1 destination of 1.
- For the Muhlenberg Township to Reading commute the residence governs. Muhlenberg Township's resident rate of about 1% equals or exceeds Reading's non-resident rate, so Pennsylvania's greater-of test resolves to the resident rate and the effective burden is about 1%, or $600 at the reference salary. The workplace adds nothing; the entire amount is remitted to the residence. This is the majority outcome and the one most commuters need confirmed.
- Of 5 recorded inflows to Reading, this route ranks 4 by worker count, carrying 572 commuters from Muhlenberg Township. Viewed from the origin it is that municipality's 1 destination of 1 recorded — neither the largest catchment nor a marginal one.
Where the money goes
A $75,000 salary
- Federal income tax$7,670
- Social Security and Medicare$5,738
- State income tax$2,303
- Yours$59,290
| Federal income tax10.23% | $7,670 |
|---|---|
| Social Security and Medicare7.65% | $5,738 |
| State income tax3.07% | $2,303 |
| Yours79.05% | $59,290 |
The arithmetic, side by side
| If you worked in Muhlenberg Township | $600 |
|---|---|
| Working in Reading | $600 |
| Difference | $0 |
On a reference salary of $60,000 a year. The local tax is flat, so every figure scales with your own pay.
What this page does not cover
- One thing worth being clear about, because it catches people out. You are not charged by both places. Muhlenberg Township and Reading do not add their rates together. Pennsylvania picks the higher of the two, and that is what you pay. Adding them would roughly double the bill.
- Only one tax is on this page. It is the local earned income tax that Muhlenberg Township and Reading levy. State tax, federal tax and Social Security all still apply. All three are the same wherever in Pennsylvania you work.
- The dollar figures use a flat reference salary of sixty thousand a year. That is a benchmark, not an average for Muhlenberg Township. No wage data exists for single municipalities, and inventing one would be worse. Scale the numbers to your own pay. The rate for the Reading commute is what matters, and it does not change with income.
- Two practical cautions. Postal addresses and taxing boundaries do not always agree. Your post may say Muhlenberg Township while your taxing municipality is a different one. Pennsylvania publishes an official lookup to settle it. The same caution applies at the Reading end. Philadelphia is a special case too, with its own wage tax.
- Pennsylvania's local rule is a greater-of rule, not an additive one: the liability for a Muhlenberg Township resident working in Reading is the higher of the two applicable rates, not their sum. The distinction is worth stating plainly because the additive reading is intuitive and would overstate the charge by roughly a factor of two. What is divided between the municipalities is the remittance, not the worker's liability.
- The scope here is the municipal earned income tax alone. State, federal and payroll taxes are unaffected by the choice between Muhlenberg Township and Reading and are therefore outside the model. A total tax position requires adding them; a comparison of the two locations does not.
- Dollar amounts are computed against a stated reference salary rather than a municipal wage average, which does not exist for Pennsylvania municipalities in any published source. Because the local tax is flat, the rate is invariant to income and the figures scale linearly — the Muhlenberg Township to Reading differential doubles at twice the salary and halves at half of it.
- Two caveats bear on accuracy. First, postal addresses and municipal taxing boundaries diverge frequently in Pennsylvania, so a Muhlenberg Township address should be confirmed against the DCED municipal lookup before relying on the Muhlenberg Township rate. Second, Philadelphia administers its wage tax outside this framework, with its own resident and non-resident rates and its own credit arrangements, so any pairing touching it should be checked against the city's own schedule.
Questions people ask
Do I pay local tax twice — once where I work and once where I live?
Only once, at the higher rate. Between Muhlenberg Township's about 1% and Reading's about 1%, the larger governs — the two are never added together.
Does working in a different town cost me anything?
Nothing extra. The tax is redirected rather than increased, so this particular crossing costs you no more than working in Muhlenberg Township would.
Which town's rate am I actually paying?
Muhlenberg Township's, because it is the higher of the two. Where you live sets the rate on this route, so working across the boundary does not raise what you owe — it only changes who collects it.
Is this commute common enough for the numbers to mean anything?
572 workers make this journey — enough to be published, but not a major corridor. The tax rules do not depend on how many people travel a route, so the figures hold regardless; the count only tells you how typical this pairing is.
Both towns charge the same — does the boundary matter at all then?
The rates match at about 1%, so the crossing moves money between authorities rather than out of your pocket.
How does Pennsylvania's local earned income tax law allocate liability between two districts?
Pennsylvania's local earned income tax law assigns the higher of the residence rate (about 1%) and the non-resident work rate (about 1%); liabilities are never summed. The employer withholds at the governing rate and remits through the work district's collector, which then distributes to the residence district.
Why is the marginal cost of this crossing zero?
Marginal liability from working outside the residence jurisdiction is zero on this route. The crossing alters the distribution of revenue between jurisdictions but not the employee's total. ⚠️ This is route-specific and does not generalise to other pairs in the same dataset.
Which district's rate governs on this route?
The residence rate equals or exceeds the work district's non-resident rate and therefore governs. Working outside the residence district does not increase employee liability on this route; it affects only inter-district distribution.
What is the measurement basis for a route of this size?
Route volume is 572 workers per Census LODES, above the publication floor but below the dataset's upper quartile. Liability is determined by jurisdictional rates and residence rules alone; commuter volume has no bearing on it and is reported only as context.
What is the effect of identical rates either side of the boundary?
Both jurisdictions levy about 1%, so the governing rate is identical regardless of which rule allocates it. The boundary affects revenue attribution between authorities, not employee liability.