In This Guide
Payroll Processing
& Compliance
Everything a Growing Business Needs to Know
What payroll processing actually involves, what "compliance" means beyond just running numbers on time, and how to know if your current setup can survive an audit — whether you're doing it in-house, through a PEO, or with a dedicated provider.
What is Payroll Processing?
Payroll processing is the full cycle of calculating what employees are owed, withholding what's legally required, and paying out the rest — done correctly, on a schedule, every single pay period.
At its simplest, payroll processing has three moving parts. First, gross pay: hours worked times rate, or a salaried amount, plus any overtime, bonuses, or commissions for that period. Second, deductions: taxes withheld on the employee's behalf, benefits contributions, garnishments, and anything else that reduces gross pay to net pay. Third, distribution: getting net pay to the employee, historically by check, almost universally now by direct deposit.
What makes this harder than it sounds is that none of those three steps happen in isolation. A new employee in a new state changes your withholding obligations. A missed overtime calculation on an hourly employee isn't just a math error — it's a wage-and-hour violation. A late direct deposit can trigger penalties in some states regardless of intent. Payroll processing is mechanical, but the margin for error is thin, and the consequences of getting it wrong land on the employer, not a vendor.
The core components of every payroll run
-
Time and attendance data — hours worked, overtime, PTO used. See our time & attendance page for how this typically feeds into a payroll run.
-
Gross-to-net calculation — applying the right tax tables, benefit deductions, and any garnishments for each individual employee.
-
Tax withholding and deposit — federal, state, and local, deposited on the schedule the relevant agency requires, not just calculated correctly.
-
Payment distribution — direct deposit, pay cards, or check, along with a compliant pay stub.
-
Recordkeeping — most jurisdictions require payroll records to be retained for several years; requirements vary by state and record type.
What "Payroll Compliance" Actually Covers
Payroll processing and payroll compliance get used interchangeably, but they're not the same thing — you can process payroll perfectly and still be out of compliance.
Processing is the mechanics: did everyone get paid the right amount, on time. Compliance is whether that process follows every law that applies to it — and those laws stack at three levels simultaneously. Federal law sets the floor: minimum wage, overtime rules under the Fair Labor Standards Act, and federal tax withholding and deposit requirements. State law adds its own layer on top — state income tax withholding (where applicable), state unemployment insurance, and often stricter wage-and-hour rules than the federal minimum. Local law can add a third layer in some cities and counties — local income taxes, paid sick leave ordinances, or predictive scheduling rules.
The practical problem is that these layers don't stay static. Rates change annually. New states pass new requirements — state-mandated retirement programs are a recent example. A business that was fully compliant last year can be out of compliance this year without changing anything about how it operates, simply because the law under it moved.
Payroll Tax Obligations, Step by Step
Every payroll run creates tax obligations at multiple levels, each with its own calculation, deposit schedule, and filing requirement.
Federal payroll taxes
Employers withhold federal income tax from employee wages based on each employee's W-4 elections, and separately owe and withhold FICA taxes (Social Security and Medicare), which are split between employer and employee. Federal unemployment tax (FUTA) is an employer-only obligation. Each of these has its own deposit schedule — some are due nearly immediately after payroll runs, others are quarterly — and missing a deposit deadline typically triggers penalties even if the amount owed was correct.
State and local payroll taxes
Most states with income tax require withholding parallel to the federal system, plus state unemployment insurance (SUTA), which is employer-funded and rate-based on the business's claims history. Some states and cities layer on additional local income taxes or specific-purpose payroll taxes (transit taxes, paid leave funds). Each of these requires its own registration before you can legally withhold or remit — you generally can't withhold a state's tax until you're registered with that state.
Filing versus depositing — a distinction that trips people up
Depositing tax withheld and filing the return reporting it are two different obligations on two different schedules. It's possible to deposit correctly every period and still fall out of compliance by filing quarterly or annual returns late or inaccurately. A compliant payroll process tracks both independently.
Multi-State Payroll Compliance
The moment you have one employee working from a state your business isn't already registered in — including a remote hire — you likely have new registration and withholding obligations in that state.
This catches growing businesses more than almost anything else in payroll, because it doesn't require opening an office. A single remote employee, a sales rep who relocates, or a contractor who converts to an employee in a new state can all trigger it. Multi-state compliance generally requires:
-
State withholding registration in every state where you have an employee performing work, not just where your business is headquartered.
-
State unemployment insurance registration, usually in the state where the employee's work is primarily localized.
-
Reciprocity agreement awareness — some neighboring states have agreements that change withholding obligations for cross-border commuters.
-
Local tax jurisdiction checks — some states have city- or county-level payroll taxes layered on top of state requirements.
None of this is optional or something that resolves itself. States actively cross-reference unemployment claims, wage filings, and business registration data, and a mismatch — an employee filing state taxes in a state where the employer never registered — is one of the more common ways multi-state gaps surface, usually well after the fact and with penalties attached.
Growing into new states faster than your payroll setup can track? That's exactly what a dedicated provider exists to catch before it becomes a filing.
Talk to a payroll specialist →Common Payroll Compliance Mistakes
Most payroll compliance failures aren't from ignoring the rules — they're from rules that were correct when they were set up and never got revisited.
-
Misclassifying employees as exempt. Exempt status depends on actual job duties, not job title — a title change or evolving responsibilities can quietly invalidate an exemption.
-
Missing new-state registration when a remote hire or relocation happens, as covered above.
-
Stale W-4 or state withholding elections that were never updated after a life change, leading to under- or over-withholding.
-
Manual overtime calculation errors, especially for employees with variable schedules or multiple pay rates.
-
Inconsistent recordkeeping that can't produce the documentation an audit or wage claim requests.
We wrote a full breakdown of what these mistakes actually cost in practice — worth reading if any of the above sound familiar: What Payroll Mistakes Are Really Costing Your Business.
In-House vs. PEO vs. Payroll Provider
The three most common ways businesses run payroll each trade off control, cost, and compliance responsibility differently — there's no universally correct answer, only the right fit for where the business is.
| Model | Who's the Employer of Record | Compliance Responsibility | Best Fit |
| In-House | Your business | Entirely yours — you own every registration, filing, and deadline | Very small teams, single-state, in-house expertise available |
| PEO | Co-employed with the PEO | Largely absorbed by the PEO, bundled with HR/benefits | Businesses wanting HR + benefits + payroll bundled under one relationship |
| Payroll Provider | Your business (you stay sole employer) | Processing and filing handled by the provider; you keep control of HR/benefits decisions | Businesses that want compliance support without giving up employer-of-record status |
The PEO-vs-provider distinction is the one we get asked about most, because the two are easy to confuse from the outside. The short version: a PEO takes on more (and asks for more control in return), a payroll provider takes on the processing and compliance layer while your business stays fully in charge of everything else.
How to Choose a Payroll Provider
Most payroll providers can run a basic biweekly cycle without issue. The differences show up in the situations outside that basic cycle — which is where compliance risk actually lives.
- Can they register you in a new state within the timeline you'd actually need, not just eventually?
- Do they review filings before submission, or just run them through automated validation?
- Is there a dedicated contact who knows your account, or a rotating support queue?
- Does their system integrate with your general ledger and accounting software, or does payroll data need manual re-entry?
- What happens if a filing is late or wrong — whose penalty is it contractually?
- Can they support off-cycle and bonus runs without extra lead time or fees that make it impractical?
That last question about penalty responsibility is worth pushing on directly in any sales conversation — it's usually the clearest signal of how seriously a provider treats compliance versus treating it as your problem with their software attached.
Staying Compliant Year-Round
Compliance isn't a setup task you finish once — it's a maintenance task that has to survive employee changes, state expansion, and annual rate updates.
- Reconcile every quarter, not just at year-end, so a discrepancy is caught while it's still small and explainable.
- Revisit exempt classifications whenever a role's responsibilities change materially, not just at hiring.
- Track every new work location the moment it happens — remote hire, relocation, or new office — and treat registration as part of onboarding, not a follow-up task.
- Watch for new state and local mandates that apply retroactively to your existing workforce, like state-run retirement programs.
We publish regular compliance updates as rules change — see Compliance Corner for the most recent one.
Frequently Asked Questions
Q. What is a PEO vs. a payroll provider?
A PEO co-employs your staff and bundles payroll with HR, benefits, and workers' comp under its own tax ID. A payroll provider processes payroll and handles compliance while you remain the sole employer of record — see Chapter 6 above for the full comparison.
Q. How often should payroll run?
Most businesses run weekly, biweekly, or semi-monthly, driven by state law minimums, cash flow, and workforce expectations — hourly teams often need weekly or biweekly, salaried teams are commonly semi-monthly.
Q. What triggers multi-state payroll compliance requirements?
Having even one employee working from a different state than your business is registered in — including remote employees — typically triggers state withholding and unemployment insurance registration requirements in that state.
Q. How do I switch payroll providers without disrupting a pay cycle?
Plan the transition to start at the beginning of a quarter when possible to keep tax filings clean, and migrate year-to-date payroll history before the first live cycle.
Q. What's the difference between payroll processing and payroll compliance?
Processing is the mechanical act of calculating pay and issuing it. Compliance is making sure that process follows every applicable federal, state, and local law — related, but distinct, and it's possible to be good at one without the other.
