Disclosure: I'm a DM at ADP, so I'll note my bias. With that out of the way — multi-state at 12+ states stops being a 'platform feature' and becomes its own operational discipline, regardless of which platform you're on.
Specific failure modes I've watched companies hit in the 5-15 state band:
1. State UI registrations falling behind. Every new state hire triggers a SUTA registration. Some states take 4-6 weeks; some take 2 days. If your platform doesn't track which registrations are pending vs. complete vs. needs-renewal, you'll find yourself processing wages in a state where you're not actually registered. Penalty exposure is real (and varies by state — CA, NY, WA are aggressive).
2. Local taxes. OH, PA, KY, IN, MI all have local-tax overlays on top of state withholding. PA has 2,500+ school district + municipal codes. Your platform either has the local-tax tables loaded (and tested for the specific cities your people live in) or you're hand-coding withholdings. Test this before signing.
3. Wage notices. Most states require a wage-rate notice at hire AND when pay changes. The triggering events and the format are state-specific. NY's WTPA notice is its own genre of compliance paperwork. CA requires Spanish translations in certain counties.
4. State-specific paid leave. WA PFML, CA CFRA + PFL, CO FAMLI, NY PFL, NJ TDI, OR PFML, MA PFML. Each has its own funding mechanism, employee contribution rate, and claims process. Your payroll platform needs to handle the deductions; your HRIS or a separate leave-admin vendor needs to handle the claims workflow.
5. Reciprocity agreements. If you have someone living in MD working in DC, or living in NJ working in NY, you need to apply the right state's withholding. Some platforms auto-handle this if you set the work and resident states correctly; some don't.
6. Year-end reporting fragmentation. W-2s file separately in each state. State magnetic media specs vary. ACA filing has state-level filings in CA, DC, MA, NJ, RI in addition to federal.
Where platforms genuinely differentiate at 12+ states:
- Tax filing as a service vs. tax calculation as a service. ADP files in all 50 states + DC ourselves. Some competitors file in 30-35 states and partner for the rest. Ask explicitly — 'do you file the return, or do you give me the calculation?'
- Pre-flight checks. Does the platform flag a new-state hire and surface the registration TODO before you process the first paycheck? Some do (Workday, ADP WFN, Paylocity); some bury it in a report you have to know to run.
- Audit trail by jurisdiction. When you get a state tax notice, can you pull the exact wages + withholdings + filing history for that state in one report? At 12 states, this matters.
For someone at 12 states specifically: I'd evaluate Rippling, ADP Workforce Now, and Paylocity as the realistic mid-market contenders. Each does multi-state credibly. Avoid generalist platforms that 'support' multi-state but treat states as a configuration checkbox.
The one thing every multi-state operator I talk to wishes they'd done sooner: hire or contract a payroll tax specialist. At 12 states you're looking at 30-50 tax accounts to maintain. That's a job, not a side task.
— AJ