State Payroll: The Complete Guide

A state payroll process begins by identifying where the employer, employees, and work are located. Register each required withholding, unemployment, paid-leave, disability, local, or other payroll account before the first applicable payroll. Then map employee residence and work locations, reciprocity, remote work, wage sourcing, taxable benefits, unemployment localization, deposit schedules, returns, wage statements, and account closure rules. Federal payroll setup does not automatically create or satisfy state obligations, and a payroll provider cannot determine jurisdictions from a mailing address alone.

This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Work location is operational data

Track where services are actually performed by date, not only the employee’s home address, manager location, or company headquarters.

Withholding and unemployment use different rules

Income-tax sourcing, reciprocity, convenience rules, unemployment localization, paid leave, and disability programs should be analyzed separately.

States without individual income tax still have payroll duties

Unemployment, wage reports, paid-leave programs, local taxes, new-hire reporting, workers’ compensation, and labor requirements can remain.

Local payroll can be a separate layer

Cities, counties, school districts, transit authorities, and occupational taxes may require registration, withholding, employer taxes, or returns.

Registrations control payment

A tax calculation is not complete when the agency account number, deposit method, rate, or portal access is missing.

State taxable wages can differ

Pretax benefits, fringe benefits, unemployment wage bases, supplemental wages, and state conformity can produce different wage amounts.

Remote work changes the footprint

A single employee moving or working temporarily elsewhere can create withholding, unemployment, registration, and business-tax questions.

Notices reveal system gaps

A notice can arise from a wrong account, rate, period, payment frequency, wage base, return, employee location, or closure date.

Step-by-step workflow

1. Create a jurisdiction census. List legal entities, work locations, employee residences, remote-work approvals, travel, project sites, hiring plans, and local jurisdictions.
2. Research each obligation. Use current official agency sources to identify withholding, unemployment, paid leave, disability, local tax, new-hire, wage-report, and closure requirements.
3. Register accounts. Obtain account numbers, rates, deposit frequencies, portal access, authorizations, and effective dates before payroll begins.
4. Configure employees. Record home and work addresses, reciprocal forms, exemptions, state withholding certificates, unemployment state, local codes, and effective dates.
5. Configure wage and deduction codes. Test regular wages, overtime, bonuses, commissions, tips, leave, taxable fringes, reimbursements, and pretax benefits by jurisdiction.
6. Calculate and approve payroll. Review gross-to-net results, state taxable wages, withholding, employer taxes, year-to-date limits, and location exceptions.
7. Deposit and file. Use each agency’s current schedule and portal, then save payment and filing acceptance separately.
8. Reconcile quarterly. Tie payroll registers to state returns, wage reports, deposits, agency balances, the general ledger, and federal totals where they should agree.
9. Manage employee moves. Use a dated workflow for address changes, work-location changes, reciprocity, registrations, rate changes, and year-end reporting.
10. Close accounts deliberately. File final returns, pay balances, answer notices, terminate authorizations, retain portal access, and confirm agency closure.

Worked example

A North Carolina consulting company hires an employee who lives in South Carolina, works mostly from home, and spends one week each month at client sites in Georgia. The company does not assign North Carolina withholding merely because headquarters is there. It documents the work pattern, researches each state’s current withholding and unemployment rules, registers required accounts, configures the employee with effective dates, and monitors travel. Payroll reports are reconciled to each state account and employee W-2 state fields at year-end.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Using headquarters for every employee. Payroll sourcing depends on employee residence, actual work, and jurisdiction-specific rules.
• Confusing reciprocity with no registration. A reciprocal withholding result may not answer unemployment, paid leave, local tax, or employer filing.
• Registering after wages are paid. Late accounts create rejected payments, notices, interest, and inaccurate returns.
• Using one state wage base. Taxable wages and annual limits can differ by program and jurisdiction.
• Ignoring temporary work. Travel and project work can create state or local obligations even when an employee does not move.
• Assuming the provider monitors moves. Create an employer-owned approval and notification workflow.
• Closing payroll but not agency accounts. Final returns and formal account closure help prevent future delinquency notices.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Practical implementation notes

State account register

Track legal entity, agency, program, account number, rate, frequency, effective date, portal, authorized users, filings, notices, and closure.

Location change form

Capture old and new residence, actual work locations, effective date, manager approval, expected travel, and required payroll review.

Quarterly matrix

Compare employees, wages, taxable wages, tax, deposits, returns, agency balances, general ledger, and year-to-date continuity by jurisdiction.

Notice log

Record agency, date, period, issue, amount, response deadline, owner, evidence, submission, resolution, and system correction.

Deeper planning points

Employee residence

Use a verified residential address and current withholding certificate. Residence can affect withholding and reciprocal treatment, but it does not replace actual work-location tracking or unemployment analysis.

Remote work

Require approval before an employee begins working in a new jurisdiction. The review should reach payroll, tax, HR, legal, insurance, benefits, security, and business licensing as appropriate.

Travel

Define materiality and monitoring procedures before employees cross state lines. A calendar, expense report, time system, and project data should agree on dates and locations.

Local tax

Geocode addresses carefully and test jurisdiction boundaries. Postal city names and ZIP codes do not always identify the correct local tax authority or school district.

Provider coordination

Document what the provider will and will not register, calculate, deposit, file, amend, and close. Retain employer access and confirm every acceptance rather than relying only on a service summary.

Year-end

Reconcile state and local W-2 boxes before furnishing statements. Confirm state IDs, locality codes, wage sourcing, withholding, unemployment totals, and corrections while source records are available.

Reciprocity

Collect the required employee certificate and verify that the agreement applies to the states and wage type. Reciprocity may change resident and work-state withholding, but it generally does not eliminate every employer registration, unemployment, local, or return obligation.

Convenience rules

Identify states that source certain remote wages to an employer location under their current rules. Do not generalize one state’s rule to another. Document the employer office, assigned work location, remote-work reason, dates, and official guidance.

Unemployment rates

Load the correct employer-specific rate, taxable wage base, and effective date. New-employer rates, experience rates, successor rules, voluntary contributions, and rate notices can change the calculation even when employee withholding is unchanged.

Paid leave and disability

Treat state programs as distinct payroll components. Confirm employee and employer rates, wage bases, exemptions, private-plan approvals, returns, employee notices, and year-end reporting for each applicable program.

Acquisitions and entity changes

Review predecessor and successor payroll facts before carrying balances forward. EIN changes, common-paymaster questions, unemployment experience, wage bases, registrations, and W-2 reporting require coordinated legal and payroll analysis.

Reconciliations

Explain differences between federal and state wages instead of forcing them to match. A valid difference can arise from benefit conformity, state additions, work sourcing, unemployment limits, or timing. Record the reason by employee and code.

Supplemental wages

Test each state’s current bonus and supplemental-wage method. A federal flat withholding method does not automatically produce the correct state result, and local taxes may use another rule.

Final pay

Build state-specific termination and final-pay procedures. Pay timing, accrued leave, permissible deductions, wage statements, and delivery can change based on the separation facts and jurisdiction.

New-hire reporting

Track employee and independent-contractor reporting rules separately from tax registration. Submit required identity and employment data through the current state channel and retain confirmation without placing sensitive data in general files.

Agency mergers and portal changes

Verify official sites and account numbers each year. States can change tax departments, unemployment portals, login systems, file formats, and payment vendors. Preserve the guidance date and test access before a deadline.

Locality boundaries

Use authoritative address tools where available. A city label in payroll may not equal the legal taxing jurisdiction, and an employee can work across multiple localities in one pay period.

Account closure

Confirm the final return and agency closure status in writing or portal evidence. Stopping payroll, withdrawing authorization, or filing a zero return does not always close the account or eliminate future filing expectations.

Employee certificates

Collect the correct current state and local forms before applying exemptions or special withholding. Retain effective dates, employee signatures, supporting residency facts, and replacement forms when circumstances change; do not translate a federal Form W-4 election automatically.

Wage-report identity

Validate names and Social Security numbers consistently across payroll and state portals. Resolve rejected records, duplicate accounts, entity-name differences, and predecessor data before the quarterly or annual report becomes a notice.

Cash forecasting

Project state payroll liabilities separately by agency and due date. Withholding, unemployment, paid leave, disability, local tax, assessments, and prior notices may settle on different schedules even when a provider makes one combined bank withdrawal.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.