You just hired your first employee who works in Ohio. Your payroll provider set up federal and Ohio state withholding, marked the setup "complete," and you moved on. Nobody mentioned RITA. Nobody mentioned the 20-day rule. Eighteen months later, a notice arrives from a tax collector you have never heard of, billing you for tax you never withheld, plus penalty and interest — and the liability is the employer's, not the employee's.
This is the local withholding trap, and it catches small employers constantly. Thousands of cities, counties, and school districts across the United States levy their own income or payroll taxes, and in most of them the employer — you — is legally required to withhold, remit, and reconcile. Your payroll software will happily compute whatever you configure. But registering with each local collector, learning each jurisdiction's rules, and keeping up when employees move or work hybrid schedules is work no software does for you automatically. This guide walks through the four systems that generate the most small-business grief — Ohio, Pennsylvania, New York City, and Yonkers — plus a quick tour of the rest of the map, how local tax shows up on the W-2, and the five mistakes that generate notices.
The Uncomfortable Truth: Local Withholding Is Your Job, Not Your Software's
There is no national system for local payroll taxes. Each state that allows them built its own structure: sometimes the state administers local taxes through the regular withholding return, sometimes regional collectors do, and sometimes every city runs its own shop with its own forms, deadlines, and penalty rules. A payroll provider can remit to a collector only after you have registered as an employer with that collector and mapped each employee to the right locality code. Skip that setup step and the money never moves — while the liability quietly accrues in your company's name.
The exposure is easy to underestimate because the rates look small: 1% here, half a percent there. But local collectors charge penalties and interest just like the IRS does, and "my software didn't do it" is not a defense. The fix is unglamorous but cheap: know which local taxes apply to each work location and each employee residence, register with every collector involved, and reconcile what you withheld against what each collector received. Start with the big four below.
Ohio: 600+ Cities, Two Big Collectors, and a 20-Day Clock
Ohio has the most intricate municipal income tax system in the country. More than 600 municipalities levy an earned income tax, typically 1% to 3% of qualifying wages, and many school districts levy their own income taxes on top (those are administered by the state through the regular Ohio return, which at least keeps them in one place).
Collection is split three ways. Two regional agencies — the Regional Income Tax Agency (RITA) and the Central Collection Agency (CCA) — collect for hundreds of member municipalities between them. The largest cities, such as Columbus and Cincinnati, administer their own taxes directly. So a single employee can easily create filing obligations with two or three different collectors: the city where they work, the city where they live, and possibly a school district.
The 20-day rule for mobile and hybrid workers
Ohio's signature complication is the 20-day rule. When an employee whose principal place of work is in one Ohio municipality performs services in a different Ohio municipality, you keep withholding for the principal workplace for the first 20 days in the new location — then you must switch withholding to the municipality where the work is actually performed. With hybrid schedules and work-from-home days, that means tracking where each employee works, day by day, against a running 20-day clock per municipality.
There is one mercy rule: Ohio excuses very small employers — those under $500,000 in prior-year gross revenue — from withholding for municipalities outside their home base. If you qualify, take the exception; if you have outgrown it, you need a location-tracking habit, because the 20-day count resets and accrues per employee per municipality.
Registration, frequency, and the annual reconciliation
Register as an employer with RITA, CCA, or each self-collecting city where you have a withholding obligation — registration is per collector, not per employee. Filing frequency follows your volume: if you withheld $2,400 or more in the preceding calendar year, or more than $200 in any one month of the preceding calendar quarter, you file and pay monthly, due the 15th of the following month. Below that, you file quarterly. Then comes the annual reconciliation — RITA's Form 17 is the canonical example — due the last day of February, matching every W-2 against everything you remitted. Treat that February deadline with the same seriousness as your federal W-3: it is the document collectors use to find what you missed.
Pennsylvania: Withhold the Higher Rate, Remit to One Collector
Pennsylvania overhauled local collection with Act 32 of 2008, and the resulting system is simpler than Ohio's but full of its own traps. Nearly every municipality levies an earned income tax (EIT), typically around 1%, and the employer's core rule fits in one sentence: withhold the higher of the tax rate where the employee lives and the tax rate where the employee works.
You then remit everything to the single tax collector assigned to the county where the work is performed — most famously Keystone Collections Group and Berkheimer, plus Jordan Tax Service in the Pittsburgh area. That collector distributes the money to the employee's home municipality. You do not send separate payments to each town; one collector per work county receives it all.
PSD codes and the new-hire form that matters
The linchpin of the whole system is the Political Subdivision (PSD) code — a six-digit number identifying the employee's municipality of residence. It tells the collector where to send the money. Collect a Residency Certification Form from every new hire (and again every time someone moves) and keep the PSD code in the payroll record. Wrong PSD code means the right dollars land in the wrong town's account, and the employee's home municipality will come looking for its share — with the employer holding the withholding liability.
Remit quarterly and file an annual employer reconciliation, generally due by the end of February. Two things sit outside this system and surprise newcomers: Philadelphia runs its own city wage tax entirely outside Act 32, with separate resident and nonresident rates that adjust every July 1 — if you have people working in the city, that is a second registration and a second set of returns. And many municipalities add a Local Services Tax of up to $52 per year per worker, with a low-income exemption for workers earning under $12,000 — small dollars, but a separate line item to withhold and remit. One more note for remote teams: an out-of-state employer with no Pennsylvania presence is not required to withhold PA local tax, but you should tell the employee in writing so they can make quarterly estimated payments themselves instead of discovering the gap at filing time.
New York: NYC Residents Only, Yonkers Both Ways
New York is the friendly case — the state administers New York City and Yonkers local taxes through the regular withholding system, so there is no separate collector to register with. The complexity is all in who owes what, and the most common multistate error in the country lives right here.
New York City's personal income tax — roughly 3.1% to 3.9% depending on bracket — applies to city residents only. Commuters from New Jersey, Connecticut, or upstate New York owe zero New York City tax, no matter how many days they work in Manhattan. Yet employers routinely withhold NYC tax for every employee with a Manhattan work location, handing nonresidents an interest-free loan to the city that they must then reclaim on their state return. If any of your people work in the city but live outside it, verify that your payroll setup distinguishes residence from work location for city purposes.
Yonkers cuts the other way: it taxes both sides. Residents pay a surcharge equal to 16.75% of their state tax liability, and nonresidents pay a 0.5% earnings tax on wages for work performed in the city. The paperwork runs through two state forms — employees who live in the state or city file the IT-2104 withholding certificate, while nonresidents working in Yonkers (or anywhere in the state) file Form IT-2104.1, the certificate of nonresidence and allocation, stating what percentage of their services is performed within the taxable jurisdiction. Employees must notify you within 10 days if that percentage or their residency status changes, and hybrid schedules make that 10-day rule bite more often than it used to.
The Rest of the Map: A Quick Tour
A dozen more states have local payroll taxes worth knowing about before you hire across state lines. Michigan's 24 taxing cities charge residents 1% to 2.4% and nonresidents half that, with each city administering its own tax except Detroit, which the state handles. Indiana's county-level taxes run about 1.6% to 3%, set by the employee's county of residence (or principal workplace for nonresidents) as of January 1, and collected through state withholding driven by the employee's Form WH-4 county certificate. Wilmington, Delaware levies 1.25% on earned income with employer withholding. In New Jersey, Newark and Jersey City impose 1% employer-paid payroll taxes — the cost sits entirely with you and there is no employee return at all. Alabama's municipal and county occupational taxes range from 0.5% to 3% for residents and nonresidents alike, withheld and paid by the employer. Oregon layers transit district and payroll taxes over certain cities and counties on top of a statewide transit tax. And Kansas, blessedly, has only a local intangibles tax that involves no withholding whatsoever.
None of these is hard in isolation. The difficulty is that each one is a separate registration, a separate set of forms, and a separate calendar — and they multiply with every new hire in a new place.
W-2 Boxes 18–20: Where Local Tax Lives at Year-End
Everything above converges on three small boxes of the Form W-2: Box 18 (local wages), Box 19 (local tax withheld), and Box 20 (locality name). Each W-2 copy has room for only one locality, so an employee who lived in one Pennsylvania town, worked in another, and spent part of the year in Ohio will receive multiple W-2 pages — that is normal, not an error, and worth explaining to employees before January so your inbox survives tax season.
Box 20 entries can also look cryptic. Under Pennsylvania's Act 32, the box may show a collector code rather than a town name, while Philadelphia withholding still shows as Philadelphia. In Ohio, the locality should reflect where tax was actually withheld under the 20-day rule, which may differ from where the employee now lives. When an employee asks why their W-2 shows a city they barely remember working in, the answer is usually one of these mechanics — and having the per-pay-period work-location records to prove it is what separates a five-minute answer from a correspondence audit.
Five Mistakes That Generate Notices
First, never registering with the local collector. Payroll software cannot remit to RITA, Keystone, Berkheimer, or CCA on your behalf until you hold an employer account with each one — "the software handles taxes" covers federal and state, not the collectors it has never heard of. Second, withholding New York City tax for nonresident commuters who owe none of it; this is the single most common local withholding error in multistate payroll. Third, forgetting Yonkers' 0.5% nonresident earnings tax on wages earned in the city — small rate, real liability, and it applies to people who merely work there. Fourth, ignoring Ohio's 20-day rule for hybrid workers by withholding 100% to the office city all year; the employee's home city will notice the missing revenue and bill accordingly. Fifth, treating local compliance as the employee's problem and skipping annual reconciliations — withholding liability, penalties, and interest attach to the employer, and the February reconciliation is how every collector checks your work.
Keep Local Liabilities Visible in Your Books
The accounting discipline that prevents all of this is simple: track each local obligation as its own liability. Set up a separate payroll-tax payable account per collector — RITA withholding, Keystone EIT, Philadelphia wage tax, Yonkers nonresident tax — instead of lumping everything into one "payroll taxes payable" balance. Reconcile each account to the collector's statements every month the way you reconcile a bank account; a balance that drifts from the collector's records is an early warning of a misconfigured locality code or a missed registration. And keep the inputs — PSD codes, Ohio work-location day counts, IT-2104.1 allocation percentages — attached to the payroll records for each pay period. When a collector's notice arrives two years later asking why a quarter came up short, those records are your entire defense.
Keep Every Jurisdiction Straight From Payday One
Hiring across city and county lines should be a growth milestone, not the start of a compliance archaeology project. Maintaining clear, separate records for every local tax you withhold is what turns a scary notice into a routine lookup. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — every local liability visible, version-controlled, and ready for analysis. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
