QuickBooks Payroll automates filing — but only based on how it’s configured. The software files exactly what you tell it to, which means a configuration error becomes a filing error becomes a state notice. The failures cluster in predictable places:
Work state vs. residence state. An employee living in one state and working in another needs both configured, with the correct withholding for each. QuickBooks doesn’t infer this — if it’s set wrong, withholding is wrong from day one.
Reciprocity agreements. Many neighboring states have reciprocity (the employee pays tax only to their residence state). If reciprocity exists and isn’t applied, the employee is double-withheld; if it doesn’t exist and is wrongly assumed, the employer under-withholds.
Local jurisdiction tax. This is the deepest trap. Indiana has county income tax (CAGIT/COIT) tied to the employee’s January 1 county of residence. Ohio has municipal tax administered through RITA and CCA. Pennsylvania has local earned-income tax keyed to PSD codes. New York City and Yonkers have resident taxes. QuickBooks Payroll supports these — but only if a human configures them correctly. They’re the single most common thing left unconfigured.
A Certified Payroll ProAdvisor sets these against the actual state and local requirements and verifies them — the difference between payroll that’s quietly correct and payroll that surfaces as a notice 12 months later. See ongoing payroll management →