Multi-state payroll software: how to compare US options

Key takeaways

• Start with the worker relationship. US employee payroll applies to people classified as employees under the facts of the working relationship. Independent contractors and people employed abroad require different workflows, and state classification tests may differ from federal tax rules.
• “Multi-state” is broader than a tax calculation. Compare state and local withholding, unemployment insurance, employer registrations, wage rules, filings, deposits, year-end forms and corrections for the locations where employees actually work.
• Residence alone does not determine payroll treatment. Track physical workdays, assigned office, travel and effective dates separately. New York rules, for example, can depend on both the worker’s residence and the employer’s assigned office.
• A provider’s role must be explicit. The IRS distinguishes payroll service providers, reporting agents, section 3504 agents and CPEOs. Ask which arrangement applies, which authority and EIN are used, and who owns corrections and missed deposits.
• Verify the whole workflow. A realistic demonstration should include a remote hire, a move between states, a corrected payroll run, employee access, support escalation and independent federal deposit verification.
• Compare prices for the same scenario. Headcount, additional filing states, modules, implementation, registrations and the payroll period all affect cost. Public prices alone cannot produce a reliable first-year and renewal comparison for every candidate.
• Treat local coverage as a separate question. A provider’s all-state claim does not by itself establish every local registration, filing, calculation or wage rule in the buyer’s specific locations.
• Employee payroll and contractor administration serve different workers. Compare the payroll providers here for employees; assess contractor agreements, tasks, rights records, closing documents and engagement history separately.

Multi-state payroll options at a glance

The candidates below all support US employee payroll, but they divide by operating model, team size and service depth. The scope column records advertised coverage; it does not prove that a provider handles every locality, registration, correction or wage rule in a particular contract.

Provider	Suitable buyer	Advertised state or local scope	Tax-service boundary	Price basis
Gusto	Small businesses needing employee payroll with published multi-state tiers	Plus and Premium include payroll across all 50 states	Vendor advertises federal, state and local tax calculation, filing and payment	$80/month + $12/person for Plus; $180/month + $22/person for Premium
ADP RUN	Businesses with 1–49 employees	Multi-jurisdiction payroll for employees working in more than one state or locality in a pay period	Federal, state and local tax filing with proper authorization	Quote required
Paychex Flex	Buyers seeking payroll within a broader HR and employee-services platform	Advertises multi-state tax calculation, registration and filing in applicable states	Confirm actual states, localities and contracted responsibilities	Quote required for Flex packages
OnPay	Small employers wanting payroll plus optional HR and time modules	Payroll Essentials includes multi-state payroll and federal, state and local filings and payments	Registration and jurisdiction responsibilities require contract confirmation	$49/month + $6 per worker; add-ons priced separately
Rippling	Buyers testing an HR-to-payroll workflow or considering a separate PEO arrangement	Advertises registration, withholding and filing across all 50 states; local scope requires confirmation	Keep Rippling Payroll and the separate PEO co-employment arrangement distinct	Quote required
Paylocity	Organizations combining payroll with HR, time, employee experience and general-ledger functions	Supports employees across multiple states in one run	Verify local filings, registrations, support and correction ownership	Quote based on modules, services and employee count
QuickBooks Workforce Payroll	Buyers already using or evaluating QuickBooks accounting	Includes one state tax filing; each additional state costs $12/month	Does not include local tax payments or filings	Plan-dependent accounting bundle; request a current quote
Patriot Payroll	Buyers choosing between self-managed filings and full-service payroll	Basic and Full Service support all 50 states and DC; local account scope requires confirmation	Basic leaves filings and deposits to the customer; Full Service handles them	Full Service: $37/month + $5 per worker + $12/month per additional filing state
Square Payroll	Square-based businesses wanting full-service employee payroll	Supports locations across multiple states and localities; local filing scope requires confirmation	Advertises federal and state filings and payments	$35/month + $6 per person paid
Dayforce	Enterprises requiring configurable payroll rules and audit reporting	Supports multi-state tax-threshold configuration	Configuration does not establish automatic coverage of local filing tasks	Quote required
UKG Pro	Enterprises evaluating a broader HR and payroll platform	Advertises US federal, state and local filing services and multi-state rules	UKG One View is a separate international route; local registration terms require confirmation	Quote required

For each finalist, request a service matrix for your states and localities. It should identify who handles registration, withholding, unemployment insurance, wage rules, filings, deposits, corrections and escalation.

Define the payroll job before comparing platforms

Identify which workers are employees, who legally employs them and where they work before choosing payroll software. Independent contractors and employees abroad require separate operating paths.

Employees, contractors and workers abroad

For US federal employment-tax purposes, classification depends on the facts of the relationship, including behavioral control, financial control and the relationship between the parties. The IRS therefore does not treat the label assigned in a contract or software system as the conclusion. State tests may differ, so a federal classification does not resolve every state labor-law question.

Use this sequence before selecting a platform:

1. Classify the actual working relationship. Document who controls how the work is performed, who provides the tools and financial support, and the parties’ relationship. Do not classify someone from a product label, contract title or onboarding category.
2. Confirm the legal employer. If the company employs the person, determine which employer arrangements the payroll provider can support. If another organization is the legal employer, use that organization’s payroll arrangement rather than treating the relationship as ordinary direct employment.
3. Separate US employees from employees abroad. US state payroll addresses employees working in US states. It does not determine the employer, tax, social-insurance or payroll requirements for an employee based abroad. International employment needs its own country and employment-model analysis.
4. Keep contractors outside the employee-payroll table. A contractor workflow may record agreements, work, rights and supporting documents, but it does not replace employee withholding, state registrations or year-end employment tax filings.

A company with US employees, independent contractors and employees abroad may need separate arrangements for each group.

Software, payroll service and employer arrangements

Once the worker is an employee, define which party will calculate, file and deposit payroll taxes. The IRS distinguishes several federal third-party payer arrangements: a payroll service provider, reporting agent, section 3504 agent and Certified Professional Employer Organization (CPEO). These arrangements have different authority and liability consequences.

The IRS explains that federal employment-tax liability depends on the arrangement and its facts. An employer may remain solely liable, share liability with the third party, or qualify for relief in certain circumstances. With an ordinary payroll service provider, the employer remains responsible for timely federal returns and deposits if the provider defaults; the IRS notes a CPEO exception in certain circumstances.

This distinction belongs in the contract and implementation plan. Before signing, identify:

• the exact legal arrangement and contracting entity;
• the authority under which federal returns are filed;
• the EIN used for each filing role;
• who calculates, files, funds and reconciles federal taxes;
• who owns state and local registrations and filings;
• who investigates and corrects an error;
• which party communicates a correction to the employee; and
• how missed deposits or late returns are escalated.

Software may provide workflow, data and automation, while a payroll service performs defined calculations, filings and deposits. A managed employer arrangement can also change who is the employer for covered workers. Those models should be compared by responsibility, control and documentation rather than grouped under a generic “compliance” claim.

Your request to each vendor should therefore be specific: identify the arrangement, list the taxes and filings included, state the remaining employer obligations, and name the correction owner for each jurisdiction. If the contract does not answer those questions, the advertised feature list is insufficient.

Map the state and local obligations a vendor must cover

A provider covers a multi-state payroll workflow when it can handle the obligations attached to the buyer’s actual locations. Create a state-by-state worksheet before comparing platforms. Each row should connect the employee’s facts to the required action, responsible party and evidence of completion. “All 50 states” does not answer whether a provider performs every local registration, filing, calculation, wage-rule update or correction for the worker in front of you.

Location data and a move between states

A residence field captures only part of the location question. Record physical workdays, assigned office, travel, effective dates and any employer office maintained at the remote location. A location change should trigger a documented payroll review, even when the employee stays with the same employer. An IZA study tracked residence changes among continuing employees in a sample drawn from Gusto clients; residence in that study does not establish where every workday occurred, and the sample does not represent all US employers.

New York illustrates why these facts must remain separate. Its guidance for a nonresident whose primary office is in New York treats telecommuting days outside the state as New York workdays unless the employer has established a bona fide employer office at the telecommuting location. For a nonresident who performs services partly inside and outside New York, the employer generally withholds on New York-source wages unless it receives Form IT-2104.1 or maintains adequate current records. Separate assigned-office and policy rules can change the analysis.

If you don’t know where employees are working, you’re not going to be able to administer the rules

— Stephen Kenney, associate at Ogletree Deakins at the time of the 2026 conference

Use a move as a controlled scenario during the demonstration:

1. Add a remote employee who has a different residence from the company’s assigned office.
2. Record physical workdays and travel before approving the payroll configuration.
3. Change the employee’s work location or assigned office with a documented effective date.
4. Show which tax, unemployment and wage-rule records change.
5. Identify who reviews ambiguous facts and approves the resulting configuration.
6. Produce the employee’s pay and tax records and the internal audit trail for the change.

A demonstration that only changes a state dropdown does not show how residence, workday allocation, travel and office records reach payroll. Ask the provider to explain the data flow and show who resolves exceptions.

Registration, withholding, unemployment and wage rules

Each obligation needs its own status because one “work state” setting cannot represent all of them. State income-tax withholding, unemployment insurance, employer registration, local tax accounts and wage rules have different sources, effective dates and owners.

Check	Buyer fact to establish	Vendor evidence to request
Employer registration	Is the company already registered, and does the arrangement require a new account?	The account owner, application evidence, effective date and whether service is included
State income-tax withholding	Where does the employee perform services, and what allocation records support that answer?	The calculation for the actual employee and the records used to produce it
Unemployment insurance	Which state or states apply under the worker’s facts?	A separate UI determination, account information and reporting treatment
Local taxes	Do state, county, city or special-district rules apply?	The applicable local calculation, filing, registration and payment scope
Wage and hour rules	Which minimum wage, overtime, leave, pay-frequency or pay-statement rules apply?	The configured rule, its effective date and the system that reports employee changes
New-hire reporting	Does the employee trigger reporting in the relevant jurisdiction?	Who files the report and where the filing is recorded

Pennsylvania’s remote-hire guidance shows why state and local setup must remain distinct. It calls for employer withholding and unemployment compensation accounts, new-hire reporting and separate Earned Income Tax and Local Services Tax setup for an employee working in Pennsylvania. Foreign-entity registration is conditional on the guide’s exclusions rather than automatic for every remote hire.

Registration timing can also be immediate. California requires a business hiring employees and paying more than $100 in wages in a calendar quarter to register as an employer within 15 days under the cited rule. That threshold and deadline are California-specific and apply to the specified business case; they are not a national registration standard.

Tax filings, deposits and correction ownership

Federal filings, state filings and local filings are separate responsibilities. The vendor’s tax-service matrix should state who calculates each item, which authority and EIN are used, whether the filing is included, and whether the buyer must fund the account. “Taxes calculated” and “taxes filed” answer different parts of the decision.

The payer arrangement also affects control. ADP RUN, for example, says it can calculate and file federal, state and local payroll taxes with proper authorization. That statement does not establish who owns setup or corrections under a particular agreement. The buyer must obtain those terms for the contracted service.

For every tax type, require a written workflow:

• calculation and approval;
• filing authority and EIN;
• funding and deposit date;
• filing deadline and confirmation;
• employee and year-end forms;
• retained evidence;
• failed filing or missed deposit escalation;
• correction responsibility;
• communication after a correction; and
• access to the underlying records.

With an ordinary payroll service provider, the employer remains responsible for federal tax deposits and timely returns if the provider defaults. The IRS notes a CPEO exception in certain circumstances. The contract and actual payer arrangement determine which allocation applies; a blanket promise that the provider assumes every payroll-tax risk is not a substitute for the agreement.

You should also retain an independent control over federal deposits. The IRS advises employers to register for their own EFTPS PIN and periodically verify federal tax payments made by their payroll provider. EFTPS does not verify state deposits, employee pay accuracy or filing accuracy, so state reconciliations and employee-record checks remain separate controls.

This produces one practical test for the shortlist: choose the actual employee, tax and registration scenario and ask the vendor to show the complete chain from source data to calculation, filing, deposit, employee record and correction. Any missing link identifies work your team may still own.

Compare multi-state payroll software

These eleven candidates support US employee payroll through different service models. Some publish prices; others require a quote. Some combine payroll with HR, accounting or an optional PEO arrangement. Compare the contracted state and local work, registration, wage rules and correction responsibilities for your locations.

Gusto

Gusto is a practical candidate when a small business needs published multi-state pricing and a provider that advertises broad employee payroll tax support. Its Simple plan covers basic payroll in one state. Plus and Premium include multi-state payroll, and Gusto says those tiers calculate, file and pay federal, state and local employee payroll taxes in all 50 states.

Published prices:

• Plus: $80 per month plus $12 per person.
• Premium: $180 per month plus $22 per person.

These are base and per-person prices, not a complete first-year total. Confirm which registrations, implementation work and additional services fall outside the subscription.

Gusto supports import from specified QuickBooks, ADP RUN and Paychex reports, but Paychex payroll-history import is not available to every user. That makes Gusto worth examining for a small-business migration, provided the prospective team confirms its export format and import eligibility. Ask Gusto to demonstrate the actual employee locations and local obligations rather than relying on the all-state statement alone.

ADP RUN

ADP RUN targets businesses with 1–49 employees and offers multi-jurisdiction payroll for people working in more than one state or locality during the same pay period. Its package materials include tax filing, and RUN says it automatically calculates payroll taxes and can file federal, state and local payroll taxes with proper authorization.

RUN merits a closer look for a small business with employees working across jurisdictions in the same pay period. RUN prices the selected package by quote; request one that specifies the buyer’s service scope.

“Proper authorization” is a condition that belongs in the diligence process. Ask ADP to identify the contracting entity, authorization, EIN, account-setup owner and correction workflow for every required jurisdiction in the proposed agreement.

Paychex Flex

Paychex Flex combines employee payroll with records, hiring, benefits, time, reporting and employee self-service. That wider operating model makes it relevant to buyers consolidating payroll with HR administration rather than selecting a standalone payroll tool.

Paychex advertises multi-state payroll tax calculation, registration and filing in applicable states. The buyer still needs the actual locality matrix and the Flex contract terms to determine which tasks Paychex performs. Confirm local registrations and correction ownership in the Flex agreement.

Flex Select, Pro, Enterprise and HR Pro are quote-priced. A meaningful cost comparison therefore requires the same headcount, locations, modules, payroll frequency and service scope for Flex and every other candidate. It should also show which one-time implementation and year-end activities remain inside the company.

OnPay

OnPay Payroll Essentials advertises W-2 and 1099 payment, multi-state payroll, and federal, state and local tax filings and payments. Its published price is:

• $49 per month plus $6 per worker per month.

HR and time modules carry separate charges. Include the modules the buyer will actually use.

A small employer can evaluate the base payroll package and price the separate HR or time modules it needs. Confirm the jurisdiction matrix, registration ownership and correction process during the evaluation.

Employee self-service needs clarification before plan selection. OnPay’s pricing information and separate employee-self-service material conflict about whether employee self-service belongs in the base package or requires the HR module. Do not assign that feature to a plan based on either page. Ask OnPay to demonstrate the current package and its price for the proposed scenario.

Rippling

Rippling combines payroll with an HR platform and says work-location changes in its HR system flow into payroll. It also lists QuickBooks Online, Xero, Sage Intacct and NetSuite general-ledger integrations. That makes the HR-to-payroll handoff worth testing for a remote or mobile workforce.

Rippling’s current guide says Rippling Payroll handles tax registration, withholding calculations and filing automatically across all 50 states. Keep that payroll service separate from Rippling PEO, which is a co-employment product with a different legal model. A proposal that combines the two without labeling them clearly cannot be compared with ordinary payroll software.

Ask Rippling for a quote and written terms identifying the selected service, local registration and filing owners, work-location data flow and correction owner. Do not treat the PEO as evidence that the software route includes every payroll task.

Paylocity

Paylocity advertises payroll for employees across multiple states in one run and configurable payroll audits. Its small-business tiers—Express, Enrich and Elite—are available to eligible organizations with 1–50 employees, depending on the selected modules and services.

Paylocity may suit buyers connecting payroll with employee experience, HR, time and general-ledger workflows. Request a configured run and audit report for your states.

Optional Elevate implementation services advertise pay-data audit, dual maintenance, pay and tax validation, test payroll runs and a dedicated implementation contact. These services are not established as part of every contract. Ask whether implementation is included, what it costs and which tasks the customer must perform.

Paylocity’s public pricing depends on selected modules, services and employee count, so the comparison requires a current quote. Include implementation, extra locations, support and year-end work in that quote rather than comparing the platform with a fixed-price payroll package.

QuickBooks Payroll

Intuit now presents QuickBooks Workforce plans with payroll included alongside accounting bundles. That makes QuickBooks Payroll relevant to buyers already using QuickBooks or evaluating a combined accounting and payroll workflow.

The current terms define an important limit. Workforce Payroll and Workforce Premium include one state tax filing and charge $12 per month for each additional state filing. Intuit also states that QuickBooks Workforce Payroll does not offer local tax payments or filings. A buyer with local obligations must establish who performs that work and how it fits the first-year budget.

Public prices are presented through plan-dependent accounting bundles. Request a same-scope quote that separates payroll from the accounting package where necessary. Older Core, Premium and Elite figures no longer describe the current offer and should not enter the comparison.

Patriot Payroll

Patriot provides two distinct service levels. Basic Payroll leaves tax filings and deposits to the customer. Full Service handles federal, state and local filings and deposits. Patriot says both support employees in all 50 states and DC, but Basic gives the buyer a materially different operating model from Full Service.

Full Service pricing before promotions:

• $37 per month plus $5 per worker paid.
• $12 per month for each filing state beyond the first.

The additional-state charge applies to Full Service, not Basic. Compare Basic only with offers that leave comparable filing and deposit work with the buyer.

The all-state statement does not establish that every local account or registration is included. Confirm which tax accounts Patriot opens, who funds each account, how local work is handled and who owns correction and year-end tasks under the selected package.

Square Payroll

Square Payroll advertises full-service employee payroll and supports businesses setting up locations across multiple states and localities. It automates federal and state tax filings and payments. Published employee-payroll price:

• $35 per month plus $6 per person paid monthly.

This makes it a candidate for Square-based businesses already using Square products. Test whether the time and location records feed payroll cleanly and whether the service handles the buyer’s actual local obligations. Confirm local registrations and filings in the proposed contract.

Square also has a separate contractor-only tier at $6 per person paid monthly. That price applies to a different worker category and must not be used as the employee-payroll price in this comparison.

Dayforce

Dayforce is suited to enterprise buyers that need configurable payroll rules and audit reporting. Its documentation describes employee-level multi-state tax-threshold configuration and a payroll audit report that tracks how close employees are to applicable state thresholds.

Those controls matter for larger or geographically complex workforces where a single static tax setup would be difficult to administer. A demonstration should use the buyer’s actual threshold scenarios and show how exceptions, amendments and audit output work.

Dayforce also describes global payroll, configurable rules, reporting and employee self-service. Request a quote: configuration capability alone does not establish which state or local filing tasks Dayforce performs. Ask for a written US scope, a quote for the selected configuration and a demonstration of account setup and correction ownership.

UKG Pro

UKG Pro supports US and Canadian payroll and advertises US federal, state and local filing services. Its compliance profile describes multi-state taxing rules and reciprocity calculations. This makes it relevant to enterprise buyers already evaluating UKG’s broader workforce platform.

UKG One View is a separate international management route. Keep it separate from UKG Pro when requesting a US proposal, particularly for a workforce that includes employees based abroad.

UKG should demonstrate the buyer’s state and locality scenario, specify local registration and correction responsibilities in the proposed agreement, and provide a comparable quote.

Test the workflows behind a coverage claim

Run the same employee scenario with each candidate. Trace source data through tax calculation, filing, deposit and correction, and record the outputs, exceptions and tasks your team retains.

A remote hire and a location change

Use a remote employee whose residence, assigned office and physical workdays differ. Then change one of those facts and ask the provider to demonstrate the resulting payroll changes. This exposes whether the system treats location as one configurable field or captures the facts required for state and local decisions.

The test should include these steps:

1. Enter the worker record. Record residence, assigned office, physical workdays and the effective date of each fact.
2. Show the review point. Identify the person or team that resolves ambiguous travel or office information before payroll is approved.
3. Display the configuration. Show the state withholding, unemployment insurance, registration, local tax and wage-rule records created or updated.
4. Produce the employee records. Open the pay statement and the tax records available to the employee.
5. Explain the sources. Identify which fields fed each calculation and which records support the result.
6. Move the worker. Change the relevant location fact with a new effective date and repeat the demonstration.
7. Trace the change. Show the audit trail, approval history and any tasks that remain outside the vendor’s service.

New York provides a useful reference scenario because assigned-office and workday records can affect the outcome. Its guidance treats telecommuting days outside New York as New York workdays for certain nonresidents whose primary office is in New York, unless the employer has established a bona fide employer office at the telecommuting location. The employer’s withholding guide also requires adequate current records or the prescribed form for certain employees who work partly inside and outside the state.

Pennsylvania offers a different test. Its remote-employee guide separates employer withholding and unemployment accounts from Earned Income Tax and Local Services Tax setup and new-hire reporting. A demonstration should identify who performs each step and where the buyer receives evidence that it is complete.

Then ask for an exception. For example, request a change in travel days, assigned office or residence that leaves the correct answer uncertain. A provider that relies on a single address field may still reach a state configuration; a provider with a controlled workflow should preserve the missing fact, route it to an owner and prevent approval until the decision is documented.

Employee records, corrections and support

Test what employees and your team can see after a successful run, a rejected transaction and a corrected payroll. A provider may produce accurate calculations while still requiring manual work to explain an exception or assemble replacement records.

For the employee side, verify:

• when the pay statement and tax records become available;
• which work-location and pay details appear;
• how an employee reports a missing or disputed record;
• whether corrections create a new document or replace the earlier record;
• which notice explains a changed withholding amount or payment; and
• where the employee retains access to both the original and corrected history.

For the internal support path, create a controlled correction and ask the vendor to show:

1. the employee or transaction that triggered it;
2. the owner of the initial review;
3. the tax or payroll record affected;
4. the approval required before reprocessing;
5. whether wages, withholding, deposits and year-end forms change;
6. the employee communication generated;
7. the evidence retained for audit; and
8. the escalation path if the first reviewer cannot resolve the issue.

The contract must identify the correction owner for federal, state and local obligations. A provider that calculates tax may not own every filing or deposit. “Full service” has little decision value until the buyer can point to the clause or service matrix that defines the task.

Use the IRS third-party payer framework to test the boundary between vendor responsibility and employer control. The arrangement affects federal employment-tax liability, while an ordinary payroll service provider’s default does not remove the employer’s responsibility for timely federal returns and deposits. The vendor should state which entity acts as payer, which authority and EIN it uses, and how a correction travels between the provider and the employer.

Keep an independent federal deposit control. The IRS advises employers to obtain their own EFTPS PIN and periodically verify payments made by a payroll provider. This check covers federal deposits only. State deposit records and employee pay accuracy need separate reconciliation.

Integrations, access controls and audit trails

Multi-state payroll depends on data arriving from other systems and moving onward to finance, benefits, accounting and employees. Test the handoff instead of counting named integrations. A connector claim needs a field-level test: which value changed, who approved it and what the receiving system recorded.

For each relevant system, request a trace of one employee through the complete flow:

• the originating system and field;
• validation and mapping rules;
• the payroll record affected;
• the approval before submission;
• the output sent downstream;
• the treatment of a rejected or corrected value; and
• the audit trail available to the buyer.

Rippling is a useful case because it says work-location changes flow from HR into payroll and lists general-ledger integrations. The test should still show the actual work-location field, its effective date, the resulting payroll change and the ledger output. A connected diagram is less informative than a trace of one changed value.

Apply role-based access controls to the same scenario. The NIST voluntary payroll cybersecurity profile recommends defining permissions by user type, applying least privilege and reviewing privileged access. It also recommends establishing expected data flows and assessing external service providers against agreed security obligations. These are buyer controls, not certifications of any named platform.

Ask the vendor to demonstrate:

• who can enter or change an employee’s work location;
• who can approve a tax configuration;
• who can view pay statements and tax records;
• who can initiate a payment or deposit;
• who can run a report containing sensitive payroll data;
• how shared and departing users lose access;
• whether privileged actions produce retained logs; and
• how support personnel receive and limit access for an investigation.

The audit trail should answer more than “the platform logs activity.” Open the record behind a location change, correction and access decision. It should identify the actor, time, old and new values, approval, downstream action and linked supporting record where the system records those elements.

Finally, test the failure path. Revoke access to one upstream system, introduce a duplicate employee record or reject a ledger export. The provider should explain what blocks the payroll, what creates an alert, who owns the resolution and which downstream systems remain unchanged. This path reveals whether the integration is a controlled workflow or a sequence of unattended copies.

Record the facts, decisions and evidence from the remote hire, move, correction and access-control test. Assign an owner and implementation cost to any task outside the demonstrated workflow.

Compare the full cost of the same scenario

A comparable payroll quote needs one scenario, one scope and one calculation method. Public subscription prices identify part of the cost, but they cannot produce a valid first-year or renewal comparison across every vendor. Obtain a quote for the same headcount, work locations, pay frequency, filing states, tax accounts, implementation work, modules and contract term.

Use this scenario for every candidate:

• a defined number of US employees;
• a defined number of states and localities, including at least one remote employee;
• the same payroll frequency and pay date;
• the required federal, state and local filing services;
• the same employee access and support scope;
• the same accounting, HR, time and benefits connections;
• the same implementation and migration tasks; and
• the same year-end reporting and correction responsibilities.

Then ask each vendor to price these components separately:

Cost component	What the quote must show
Base platform	Subscription amount and billing period
Employees	Per-employee or per-person-paid charge and its definition
States	Number included and charges for additional filing states
Local scope	Included local tasks, excluded local tasks and cost of customer-managed work
Tax services	Included federal, state and local filings, deposits and year-end forms
Registration and setup	Included services and customer-performed tasks
HR, time and benefits	Required modules and their charges
Accounting and other integrations	Setup, subscription and per-transaction charges
Implementation	Data migration, configuration, training and parallel-run services
Support	Included channels and any premium support charge
Corrections and year-end work	Included services and any manual work retained by the customer
Renewal	Recurring charges and the price change at renewal

Published prices provide useful anchors for the first quote request:

• Gusto: Plus is $80 per month plus $12 per person; Premium is $180 per month plus $22 per person. Multi-state payroll is available on those tiers rather than Simple.
• OnPay: Payroll Essentials is $49 per month plus $6 per worker per month. HR and time modules are separate.
• Patriot Payroll: Full Service is $37 per month plus $5 per worker paid before promotions, plus $12 per month for each additional filing state. Basic leaves filings and deposits with the customer.
• Square Payroll: Full-service employee payroll is $35 per month plus $6 per person paid monthly. Square’s separate contractor-only tier does not price the same service.
• QuickBooks Workforce Payroll: Each additional state filing costs $12 per month on Workforce Payroll and Workforce Premium. Local tax payments and filings are excluded, so the buyer must price the work needed to cover them.

ADP RUN, Paychex Flex, Rippling, Paylocity, Dayforce and UKG Pro require scoped quotes. Request the selected package and service scope rather than a quote for a different scale, region or service model.

For each quote, calculate two totals:

1. First-year total: recurring charges for the agreed period plus implementation, setup, registrations, integrations, training and other one-time services.
2. Recurring total: the monthly or annual amount that continues after implementation, including per-person, per-state, module and support charges.

Keep internal labor visible as a separate line. If the customer must open tax accounts, handle local filings, maintain exceptions, correct payroll or complete year-end work, assign an estimated internal effort and identify its owner. Do not convert that estimate into a vendor charge, but do not treat the work as free either.

Exclude contractor payments from the employee-payroll comparison. Square’s contractor-only price, for example, serves a different worker category and would distort the total. The employee scenario should also exclude foreign employees whose payroll requires a separate country arrangement.

Finally, ask what triggers a price change: additional employees, a second filing state, a new locality, added modules, a payroll-data migration or support outside the selected plan. A low subscription price can be offset by state, implementation and customer-side obligations, while an enterprise quote can be harder to interpret without a precise scope. Compare the scenario totals alongside the work each vendor performs and the work your team retains.

Plan a switch without losing payroll continuity

A payroll switch is a controlled transfer of ongoing obligations, not a software activation. Preserve the employer’s tax accounts, employee records, year-to-date balances, filing authority and deposit access before the first run under a new provider. The provider should own a written cutover plan because state setup, data formats and implementation tasks vary by product and contract.

Before agreeing to a cutover date, assign an owner for each item:

Workstream	Records or decisions to confirm	Evidence required
Employee data	Name, address, work location, pay rate, earnings, deductions, benefits and payment details	Source-to-target reconciliation and exception list
Payroll history	Prior payroll registers, pay statements, corrections and year-to-date wage and tax balances	Sample comparison for each pay group and employee population
Tax accounts	Federal, state and local registrations, account identifiers and standing orders	Account list, authorized users and effective status
Filing authority	Which filing entity, authority and EIN each provider will use	Written authority schedule and confirmation of filings
Transition filings	Which provider files for each period and tax type	Cutover calendar naming the responsible party
Deposits	Funding workflow, due dates, account balances and access to payment records	Funding confirmation and reconciliation checklist
Historical forms	Who prepares and delivers W-2s and other year-end forms	Delivery plan with data and review responsibilities
Authorizations	Existing client approvals and the authorizations required by the new provider	Approval register and completed forms
Parallel controls	Test runs, variance thresholds and approval to proceed	Signed test results and escalation log
Employees	Change notices, support channels and escalation for missing pay	Communication record and support plan

Paylocity’s published switching guidance supports a concrete records request: prior employee data, payroll registers, payroll tax returns and pay stubs; assignment of transition-period filing responsibility; and review of the first new payroll journal for discrepancies. Treat that as a checklist to adapt, not as a guaranteed implementation timetable or a promise that every provider follows the same process.

Define the parallel run around the actual population. Include employees with multiple work locations, different pay schedules, deductions, benefits, leave, bonuses and prior corrections. Compare gross pay, taxes, deductions, net pay and year-to-date balances against the approved source records. A clean total can conceal an error in one employee or one jurisdiction.

Paylocity’s optional Elevate implementation services advertise pay-data audit, dual maintenance, pay and tax validation and test payroll runs. They are not included in every contract. Establish whether the new provider offers comparable work, who performs it and how it affects the implementation fee.

The cutover calendar should name one responsible party for each tax and period. It must also identify gaps. A provider may calculate federal taxes but leave state registration to the customer; another may file in states while requiring the customer to fund an account. If the calendar contains two owners for a filing or none, resolve that before approving the switch.

Preserve independent federal deposit access. The IRS advises employers to enroll in EFTPS, obtain their own PIN and periodically verify federal tax payments made by their payroll provider. Ensure that access survives the transition and that the first post-cutover verification is performed by the employer. EFTPS does not verify state deposits, so add state reconciliation to the calendar.

Gusto supports payroll-history import from specified QuickBooks, ADP RUN and Paychex reports, but Paychex history import is not available to every user. Confirm the export fields, file format, employee population and import eligibility before relying on automated transfer.

After the first new payroll, do not close the migration at payroll approval. Reconcile:

• employee and payment details against the source file;
• gross pay, taxes, deductions and net pay against the approved calculation;
• year-to-date balances used for withholding and year-end forms;
• federal and state deposit records;
• filed returns and their confirmation;
• downstream accounting exports;
• employee access to pay statements and tax records;
• unresolved exceptions and manual adjustments; and
• corrections needed before the next payroll.

Keep the former provider available through the agreed reconciliation point. Record who owns each correction and preserve the source data, approvals and final payroll journal. The provider-specific cutover plan should state its dates, responsibilities and prerequisites; without those terms, a generic migration checklist cannot show when the buyer is ready to switch.

Where contractor operations fit

Contractor operations become a separate requirement when the work is performed by independent contractors rather than the company’s employees. US employee payroll handles employment-tax withholding, unemployment insurance, employer registrations, year-end forms and other obligations attached to the employer–employee relationship. Contractor administration handles the agreement, work, rights, supporting records and engagement history between a company and its contractors.

The worker relationship determines the workflow. For US federal employment-tax purposes, the IRS considers behavioral control, financial control and the relationship between the parties. A contract label or the choice of software does not decide whether someone is an employee or an independent contractor. State tests may differ, so classify the actual relationship before combining records from different workforces in one system.

4dev.com fits the contractor side of that distinction. It is a global platform for working with contractors, with Contractor Platform as the product. After a contractor has been selected, the platform administers post-selection work through one agreement with 4dev.com. Its register brings together:

• tasks and their statuses;
• the agreement with each contractor;
• rights records for the work;
• closing documents;
• document and status checks; and
• the history of the engagement.

For teams with several contractors, those records sit in one register. Employee payroll still requires its own service and worker-classification review.

A mixed workforce can therefore require two connected processes with different owners. Depending on the contract, the employee payroll provider may handle tax calculations, filings, deposits, benefits administration and employee records. The contractor platform manages contractor agreements, task documentation, rights, closing documents and engagement history. Finance may still need a unified reporting view, but combining the source records does not make the underlying employment arrangements interchangeable.

Before deciding whether contractor administration belongs in a payroll platform, ask:

1. Does the system manage work with contractors, employees or both?
2. Which worker classifications does the vendor support?
3. Does the contract identify the legal employer or contracting counterparty?
4. Can each agreement, task and set of rights be connected to the right contractor?
5. Are closing documents and engagement history retained in one register?
6. Can finance distinguish contractor records from employee payroll records?

For US employees in several states, use the payroll criteria above. If the company also engages independent contractors, assess their agreement and documentation workflow separately.

Frequently asked questions

What does multi-state payroll mean?

Multi-state payroll means calculating and administering payroll for US employees whose work creates obligations in more than one state or locality. The scope can include state income-tax withholding, unemployment insurance, employer registrations, local taxes, wage rules, tax filings, deposits, year-end forms and corrections.

The number of employee addresses is not the whole test. A remote employee may work in one state, another state and a locality with its own tax rules. Residence, physical workdays, assigned office and travel can affect which obligations apply. New York guidance, for example, distinguishes residence from assigned-office and workday facts for certain nonresidents.

Your comparison should therefore name every employee’s work location and the resulting obligations. A general “multi-state payroll” label does not establish local coverage, registration ownership or correction responsibility for your specific workforce.

Who is responsible if a payroll provider misses a tax deposit?

Responsibility depends on the legal arrangement and the affected tax. The IRS distinguishes payroll service providers, reporting agents, section 3504 agents and CPEOs because their federal authority and liability differ.

Under an ordinary payroll service provider arrangement, the employer remains responsible for federal tax deposits and timely returns if the provider defaults. The IRS notes a CPEO exception in certain circumstances. Federal employment-tax liability can otherwise remain with the employer, be shared under the applicable arrangement, or qualify for relief.

State and local obligations require their own contract terms. Ask who funds each account, makes the deposit, monitors the deadline, detects a failure and owns the correction. The employer should also retain its own EFTPS access and periodically verify federal payments made by its payroll provider, as the IRS advises. EFTPS does not verify state deposits.

Does “all 50 states” include local taxes and registrations?

It depends on the product and the contract. An all-state statement may refer to state-level availability, withholding and filing. It does not automatically establish every county, city, municipal or special-district registration, calculation, filing and payment.

Local work must be checked task by task. Pennsylvania, for example, separates employer withholding and unemployment accounts from Earned Income Tax and Local Services Tax setup. Intuit states that QuickBooks Workforce Payroll does not include local tax payments or filings. Other vendors advertise broader local support, but the buyer still needs the actual locality matrix and service terms.

Ask the provider to identify:

• which local taxes it calculates;
• which registrations it completes;
• which filings and payments it makes;
• which tasks remain with the customer;
• how local accounts are funded; and
• who handles local corrections.

State availability and full local service are different claims.

Do I need employee payroll if I only work with contractors?

You need a contractor workflow, but you do not need employee payroll merely because the company pays people for work. If the people are genuinely independent contractors, employee payroll creates the wrong operating model for those engagements.

First assess the actual relationship. For US federal employment-tax purposes, the IRS considers behavioral control, financial control and the relationship between the parties. State tests may differ. Do not determine status from a contract title, payment method or software category.

Contractor administration needs agreements, task and status records, rights documentation, closing documents and engagement history. Assess it separately from employee payroll.

If the company has both employees and contractors, keep the operating models and records distinct. An employee payroll service handles employment-tax withholding, filings, deposits and year-end forms. The contractor workflow handles the agreement and service documentation for each contractor.

What should I test before changing payroll software?

Test one realistic remote employee, one move between states and one corrected payroll. Use the same records, locations and questions for every candidate.

The demonstration should cover:

1. Location capture: residence, physical workdays, assigned office, travel and effective dates.
2. Configuration: state withholding, unemployment insurance, registrations, local tax and wage-rule treatment.
3. Responsibility: calculation, filing, deposit, funding, correction and escalation owners.
4. Employee records: pay statements, tax records, notices and access after a correction.
5. Integrations: the originating field, validation, approval, payroll result and downstream accounting output.
6. Controls: role permissions, privileged access, retained activity and independent federal deposit verification through the employer’s EFTPS access.
7. Migration: employee data, year-to-date balances, tax accounts, filing authority, authorizations and parallel-run reconciliation.
8. Cost: first-year and recurring charges for the same headcount, states, modules, implementation and service scope.

A clean demonstration with a state dropdown does not establish local coverage. Ask for a jurisdiction-specific service matrix and evidence from the complete workflow. The provider should be able to name every manual task it leaves with your team.

How to choose for your workforce

Choose the payroll provider that fits the employee population, jurisdictions and operating model you actually have. The closest product feature set will not compensate for missing state registrations, unclear correction ownership, data that never reaches payroll or a migration plan that leaves employees exposed.

Start with a shortlist based on five decisions:

1. Which workers are employees? Multi-state employee payroll is relevant when the working relationship meets the applicable employee tests. Independent contractors need a separate workflow, and employees based abroad require country-specific analysis.
2. Where do employees work? List physical workdays, assigned offices, remote locations and localities. This determines which tax, unemployment, registration and wage-rule checks enter the evaluation.
3. Which service model do you need? Decide whether you require software alone, managed payroll calculations and filings, or a broader employer arrangement. Each changes liability, control and documentation.
4. Which systems must connect? List HRIS, time and attendance, accounting, benefits and employee-access requirements. Test the actual data flow for each connection.
5. What can your team administer? Decide whether internal staff can own registrations, local tasks, corrections, year-end work and exception handling.

Then apply the same scenario to each finalist. Require a written service matrix covering:

• employee classification and the legal employer;
• federal, state and local registrations;
• state and local withholding;
• unemployment insurance;
• wage, leave, pay-frequency and pay-statement rules;
• tax filings, deposits and year-end forms;
• employee records and self-service;
• failed filings, missing deposits and corrections;
• implementation, migration and support;
• price, renewal and additional-state or module charges.

Use the provider’s coverage statement to decide what to test, not to close the evaluation. For example, an all-state claim should lead to a locality-by-locality question. A published price should lead to a complete first-year and recurring cost. A connector should lead to a trace of one changed employee field. Each claim becomes useful when the provider demonstrates the underlying task.

Pay attention to the work that remains with your company. A managed service may calculate and file taxes while requiring you to register the employer, fund accounts, maintain work-location records or resolve ambiguous facts. An enterprise platform may offer configurable rules while requiring your team to configure and validate them. Quantify that work and assign an owner before signing.

Set rejection conditions before the demonstrations:

• the provider cannot support a required employee location or service;
• the proposal mixes software, managed payroll and a co-employment arrangement without stating the legal model;
• local tasks remain undefined;
• the contract does not identify filing authority, deposit responsibility or correction ownership;
• the employee workflow cannot retain the records needed after a move or correction;
• a required integration fails the scenario test;
• migration support excludes your actual data or account setup;
• the first-year and renewal quote excludes material services; or
• the provider cannot demonstrate independent deposit verification and escalation.

Pay particular attention to the transition. Obtain a provider-specific cutover plan that covers employee data, payroll history, year-to-date balances, state accounts, filing authority, authorizations, parallel testing and the first payroll reconciliation. The plan should name who will find and correct missing fields before employees are paid.

For a small business seeking published pricing and direct multi-state employee payroll, Gusto, OnPay, Patriot Full Service, Square Payroll and QuickBooks Workforce Payroll provide different starting points. A small team that needs a broader service or platform may also need a quote from ADP RUN or Paychex Flex. A buyer prioritizing HR-to-payroll integration may examine Rippling; Paylocity, Dayforce and UKG Pro fit buyers whose evaluation includes broader HR, configuration or enterprise workflows.

These are starting points for different buyers. Make the final selection from the demonstrated scenario, written service allocation and complete cost. Ask the finalist to reproduce the remote hire, move, correction, deposit check and cutover records with your workforce data.

Sources

• Topic no. 762: Independent contractor or employee — Internal Revenue Service.
• Outsourcing payroll and third-party payers — Internal Revenue Service.
• Outsourcing payroll duties — Internal Revenue Service.
• Hire remote employees in Pennsylvania — Pennsylvania Business Hub.
• Frequently asked questions about filing requirements, residency and telecommuting for New York State personal income tax — New York State Department of Taxation and Finance.
• New York State employer’s guide to wage reporting and withholding — New York State Department of Taxation and Finance.
• Register as an employer in California — California Employment Development Department.
• CSF Payroll Profile — National Institute of Standards and Technology and Internal Revenue Service.
• The new geography of labor markets — IZA Institute of Labor Economics.
• Capital Summit session warns multi-state payroll compliance risks are growing with remote work — Thomson Reuters Tax.