Local Payroll Taxes: The Complexity Most Payroll Platforms Miss

When companies think about multi-state payroll complexity, they typically think at the state level: 50 states, different rates, different forms. But layered beneath state taxes is another tier of complexity that affects tens of millions of workers and is, if anything, harder to manage systematically than state taxes: local payroll taxes.

City income taxes, county income taxes, school district income taxes, local occupational privilege taxes, metropolitan commuter taxes—these sub-state levies vary wildly in structure, rate, and administration. Many payroll platforms either don’t support them at all or support them in ways that require significant manual intervention. For employers with employees in the affected jurisdictions, getting this wrong has real consequences.

The Scale of Local Payroll Taxation in the U.S.

Local payroll taxes are concentrated in a handful of states, but those states contain enormous populations:

Pennsylvania is the most complex local payroll tax environment in the country. Over 2,500 taxing jurisdictions—municipalities and school districts—impose Earned Income Tax (EIT) on wages. Rates vary by jurisdiction and are imposed on employees based on where they work and where they live. There is a system of “political subdivision tax” and “resident tax” that interact in specific ways. Pennsylvania employers must withhold for both the employee’s work jurisdiction and their resident jurisdiction when the resident rate is higher.

Ohio has over 600 municipal income tax systems. Ohio municipalities can set their own rates up to 3% (or higher with voter approval). The state has a centralized filing option (RITA—Regional Income Tax Agency, or CCA—Central Collection Agency) for some municipalities, but many municipalities run their own collection systems. Employers with employees in multiple Ohio municipalities must navigate this fragmented landscape.

Kentucky has dozens of cities and counties with occupational taxes (also called occupational license taxes or net profit taxes). Louisville/Jefferson County, Lexington, Covington, and many other jurisdictions each administer their own systems.

Indiana counties impose county income taxes (COIT or CEDIT), with rates set by each county. Indiana has 92 counties, and many have different tax rates. Withholding is generally based on the employee’s county of residence, not county of work—which requires knowing where employees live down to the county level.

Maryland counties and Baltimore City impose their own income taxes, with rates varying by jurisdiction. Maryland’s local tax is collected through the state return system, which simplifies things somewhat, but employers must still apply the correct county rate for each employee.

New York City imposes its own personal income tax, effectively a city-level income tax on residents and part-year residents. This is administered through the New York State income tax return but is a meaningfully large obligation—New York City’s top rate is 3.876%, which stacks on top of the state’s top marginal rate.

Detroit and other Michigan cities impose city income taxes. Detroit’s rate is 2.4% for residents and 1.2% for nonresidents who work in the city.

Philadelphia imposes wage tax on both residents (at a slightly higher rate) and nonresidents who work in the city. Philadelphia wage tax is administered separately from Pennsylvania’s broader EIT system and requires separate registration and filings.

The Oregon and Colorado Situations

A few states have created relatively new local or metro-area taxes that caught many employers off guard:

Oregon’s Metro and Multnomah County taxes: As of 2021, Oregon’s Metro regional government (covering greater Portland) and Multnomah County each impose income taxes. These are relatively new, separately administered, and require employer withholding. Many payroll systems were slow to add support for these.

Colorado local income taxes: Denver, Aurora, Glendale, and other Colorado municipalities impose either occupational privilege taxes or earnings taxes that apply to employees working in those jurisdictions.

San Francisco payroll expense tax: San Francisco imposes a payroll expense tax on businesses (not a withholding obligation on employees per se, but an employer-paid tax based on payroll). This is a business tax, not a withholding tax, but it still needs to be planned for.

Why Local Taxes Are Particularly Hard to Manage

Several factors make local payroll taxes especially difficult:

Data requirements. Correct local tax withholding typically requires knowing each employee’s home address and work address down to the ZIP code or municipality level. Many payroll systems track only the primary work location—not employees’ home addresses at the appropriate level of detail. This is a data quality problem that precedes the tax compliance problem.

Rate update frequency. Local jurisdictions can change their rates, often with little fanfare. Pennsylvania municipalities, Ohio municipalities, and Kentucky jurisdictions update rates regularly. Keeping these rates current in a payroll system is more of a data maintenance burden than state rates, where changes are announced officially each year.

Filing infrastructure diversity. There is no single portal for local payroll taxes, no standard form, and no consistent filing schedule. Pennsylvania’s Keystone Collections Group handles some jurisdictions; DCED (Department of Community and Economic Development) handles municipal statistics; individual municipalities handle others. Ohio has RITA, CCA, and individual municipality systems. Managing filings across dozens of local systems simultaneously requires a level of operational infrastructure that most finance teams don’t have.

Employee mobility. Local taxes are often resident-based, meaning the applicable tax follows the employee home—not to the work location. When employees move, local tax withholding changes. In Pennsylvania, for example, an employee who moves from one municipality to another triggers a change in both the resident EIT rate and the allocation of tax between their resident municipality and work municipality.

The Cost of Getting It Wrong

Local tax non-compliance carries similar penalties to state non-compliance—late filing fees, interest, and potentially personal liability provisions. But the detection mechanism is different: local jurisdictions often audit through data sharing with state agencies or through W-2 reconciliation. When an employee files their state return claiming a local tax credit and the credit doesn’t match what the employer reported, that’s a red flag.

Philadelphia is particularly active in enforcement—the city conducts regular audits of employers it believes may have under-withheld, and it can assess back taxes, penalties, and interest going back several years.

What Companies Should Do

Map your local exposure. The first step is simply understanding which local jurisdictions your employees work and live in. For companies in Pennsylvania, Ohio, Kentucky, or other high-complexity states, this may require a systematic review of employee addresses.

Use a payroll provider with robust local tax support. Not all payroll platforms support local taxes equally. Verify that your platform has current rates, filing capabilities, and support for the specific jurisdictions where you have exposure.

Don’t assume the state handles it. Unlike some states where local taxes are collected through the state system, most local payroll taxes require separate filings, separate payments, and separate account registrations. Paying state income tax correctly doesn’t satisfy local obligations.

Build regular audits into your process. Given the rate update frequency in local systems, an annual audit of local rates in your payroll system against published rates is a worthwhile control. Errors are common and often go undetected until an employee or agency raises a discrepancy.

Local payroll taxes are genuinely complex—more so, in some ways, than state taxes—precisely because of their fragmentation and lack of standardization. Companies that acknowledge this complexity and build appropriate processes around it will avoid the expensive surprises that catch less-prepared teams off guard.