QuickBooks Payroll, answered.

Choosing a payroll platform.

QuickBooks Payroll, Gusto, ADP, Paychex — the honest fit assessment without affiliate spin. Selection drives every other downstream decision.

QuickBooks Payroll vs Gusto vs ADP — which fits my business?

Three platforms with different fit profiles. QuickBooks Payroll wins for businesses already on QuickBooks Online or Desktop where deep accounting integration matters, accounting-fluent users, single-state or simple multi-state operations, and businesses whose CPA prefers QuickBooks-native workflows.

Gusto wins for businesses needing modern HR features (benefits administration, onboarding, employee self-service), significant contractor or 1099 volume, multi-state operations (Gusto’s multi-state handling is meaningfully cleaner), and non-accounting users running their own payroll. ADP wins for larger businesses (typically 50+ employees), complex multi-state operations with significant compliance overhead, businesses requiring deep HR + benefits + 401(k) integrated services, and PEO-style arrangements. Paychex fits similar to ADP at the mid-market level, often chosen for established relationships or specific industry depth.

TechBrot implements all four with zero affiliate commission — selection is based on business fit, not commission. See our QuickBooks Payroll vs Gusto breakdown for the detailed comparison.

What are the actual QuickBooks Payroll plan tiers?

Intuit offers QuickBooks Payroll in tiered subscriptions that integrate with QuickBooks Online and have separate Desktop versions. The current QBO Payroll tiers are Core, Premium, and Elite. Core handles basic payroll (federal and state tax calculation, direct deposit, basic W-2 filing). Premium adds same-day direct deposit, HR support, and workers’ comp administration. Elite adds tax penalty protection, expert setup review, and white-glove implementation support.

For Desktop payroll, the tiers differ: Enhanced Payroll (built into Desktop subscriptions) handles standard payroll within Desktop; Assisted Payroll historically offered Intuit-managed tax filing but has limited new-subscriber availability. Plan names, features, and pricing change — verify directly with Intuit or via the plan selection resource before committing. The right tier depends on employee count, multi-state complexity, HR integration needs, and CPA preferences. Discovery call sorts which tier actually fits.

When does QuickBooks Payroll stop being the right answer?

Several signals indicate it’s time to consider a different platform. Multi-state complexity beyond 3-4 states: QuickBooks Payroll handles multi-state, but Gusto’s multi-state workflow is meaningfully cleaner once the business operates across many states. Significant contractor volume: businesses with more 1099 contractors than W-2 employees often find Gusto’s contractor-first workflows (contractor-only pay runs, no full payroll seat cost for contractors, automatic 1099-NEC) better fit. Heavy HR integration needs: benefits enrollment, onboarding workflows, employee self-service, performance management — Gusto, Rippling, or BambooHR handle these natively where QuickBooks Payroll doesn’t.

Approaching 50+ employees with complex needs: at this scale, ADP or Paychex with dedicated account management often becomes the better fit. PEO arrangements: businesses considering PEO (Justworks, TriNet, Insperity) move outside the QuickBooks Payroll model entirely. The honest threshold: QuickBooks Payroll is excellent for accounting-integrated payroll at small-to-mid business scale; when other dimensions matter more than QuickBooks integration, other platforms typically win.

Should I use a PEO instead of standalone payroll?

A PEO (Professional Employer Organization) is a co-employment arrangement where the PEO becomes the employer of record for payroll, benefits, and HR compliance — the business retains operational control of employees but the PEO carries the employment relationship. Major PEOs: Justworks, TriNet, Insperity, Paychex PEO, ADP TotalSource. PEO advantages: access to large-group benefits (significantly better health insurance pricing), reduced HR administrative burden, consolidated compliance (the PEO handles multi-state registration, posters, mandated training), and risk pooling for workers’ comp.

PEO trade-offs: higher per-employee cost than standalone payroll (typically $100-$200+/employee/month), less control over benefits design (you get the PEO’s plans, not custom), data complexity for accounting (PEO summary entries vs detailed payroll posting), exit complexity (leaving a PEO requires re-establishing direct employer relationships, can take 60-120 days). PEO is the right answer for businesses with 10-100 employees where benefits and HR compliance are major pain points; less compelling for very small businesses or large businesses with dedicated HR teams. TechBrot configures the accounting side for PEO and non-PEO arrangements alike.

Can I switch payroll providers mid-year?

Yes, but timing matters significantly. Mid-year switches require migrating year-to-date payroll history from the prior provider to the new one — cumulative wages, withholding, employer tax accumulations all transfer so the new provider can correctly calculate Social Security wage base limits, year-end W-2 figures, and 940/941 filings. Most providers support YTD data import but accuracy depends on prior provider data quality.

Best switch timing: January 1 (new year, clean start, no YTD transfer needed) — the ideal but requires planning. Second-best: end of any quarter (April 1, July 1, October 1) — aligns with quarterly 941 filings and reduces mid-quarter complexity. Mid-quarter switches: workable but adds reconciliation complexity for the partial quarters. Switches require coordinating final pay-runs at the prior provider, YTD data export, new provider setup and testing, parallel run verification (highly recommended for the first pay-run at the new provider), and clean handoff timing so no pay-runs fall in a gap. Switch engagements scope at $2,500-$6,000+ depending on employee count, state count, and timing.

QuickBooks Payroll setup.

Setup scope, tax-account registration sequencing, employee onboarding, benefits integration, and what goes wrong when setup is rushed.

What does QuickBooks Payroll setup actually involve?

Complete QuickBooks Payroll setup covers seven core areas: (1) Federal tax registration verification — EIN active, federal payroll tax accounts in good standing. (2) State tax registration in every state where employees physically work — state withholding accounts and state unemployment insurance (SUI) accounts, which can take 2-6 weeks per state to establish. (3) Employee setup — W-4 collection, direct deposit setup, benefits elections, garnishments if applicable, pay rate and schedule configuration. (4) Tax setting configuration — federal and state withholding tables, SUI rates per state, local tax setup where applicable. (5) Chart of accounts mapping — payroll posting accounts aligned with the QuickBooks CoA so monthly bookkeeping flows correctly (see chart-of-accounts setup). (6) Benefits integration — health insurance, 401(k), HSA, FSA contributions correctly configured for pre-tax vs post-tax treatment. (7) First pay-run verification — test run reviewed against expected calculations before going live.

Setup pricing: typically $1,500-$6,000 fixed-fee depending on employee count, state count, and benefits complexity.

How long does state tax account registration actually take?

State tax account registration is the most common bottleneck in payroll setup. Timelines vary significantly: fastest states (online registration, instant or same-day approval): California (with EDD account), Florida (no income tax but SUI required), Texas (no income tax but SUI). Moderate timeline (1-3 weeks for online registration to process): most states with electronic systems. Slow timeline (3-8 weeks, sometimes requiring paper applications or mail-in employer registration forms): some legacy state systems still rely on paper processing for new employer registration.

The honest planning rule: start state registration 6-8 weeks before the first payroll run in that state. Trying to run payroll before state accounts are established creates compliance gaps that take significant work to clean up — SUI returns get filed without account numbers, withholding gets remitted to wrong accounts, and the state takes months to reconcile. We coordinate state registration timing during setup engagement scoping; for businesses adding new states, we plan the registration sequence before any employee starts work in that state.

How are benefits (health insurance, 401(k), HSA) configured in QuickBooks Payroll?

Benefits configuration in QuickBooks Payroll requires correct tax treatment for each benefit type. Pre-tax health insurance (Section 125 cafeteria plan): employee contributions reduce wages subject to federal income tax, Social Security, Medicare, and most state income taxes. HSA contributions: employee pre-tax HSA contributions reduce wages subject to FICA, Medicare, federal income tax, and most state income tax. 401(k) traditional contributions: reduce wages subject to federal income tax but NOT FICA/Medicare (this is a common error in setup — 401(k) does not save Social Security or Medicare tax). 401(k) Roth contributions: not pre-tax at all — included in all wage bases.

HSA employer contributions: excluded from employee wages (federal income tax, FICA, Medicare, most state income tax). Dependent care FSA: pre-tax up to $5,000 annual limit ($2,500 if married filing separately). Health FSA: pre-tax up to the annual IRS limit (verify current year). Incorrect benefits configuration creates W-2 errors that surface in employee tax returns the following spring — we configure correctly at setup to avoid year-end W-2c work.

What about S-corp owner-employee compensation in QuickBooks Payroll?

S-corp owner-employees (>2% shareholders) have distinctive payroll treatment that QuickBooks Payroll must be configured for correctly. Reasonable salary requirement: S-corp owners performing services must take a reasonable salary subject to FICA/Medicare — the IRS scrutinizes “reasonable” based on industry, role, and comparable compensation. Pure distributions without salary are a common audit trigger.

Health insurance treatment: S-corp >2% shareholder health insurance premiums paid by the S-corp must be added to the shareholder’s W-2 box 1 (taxable wages) but are NOT subject to FICA/Medicare. The shareholder then deducts the health insurance as an above-the-line deduction on their personal return. This treatment is one of the most commonly mishandled items in S-corp payroll — missing it creates a W-2c at year-end. HSA contributions by the S-corp for >2% shareholders are also added to W-2 box 1. 401(k) contributions: S-corp owner-employees can participate in 401(k) like other employees, but contribution limits are based on the W-2 salary, not distributions. Setup configuration requires getting all of these right from the first payroll; year-end cleanup catches what setup missed.

What goes wrong when payroll setup is rushed?

Rushed payroll setup creates predictable problems that compound. Common setup errors: wrong state SUI rate (results in months of under- or over-payment to state UI), incorrect chart-of-accounts mapping (every payroll posts to wrong general ledger accounts, requiring monthly journal entries to fix), benefit configuration errors (pre-tax treatment wrong, leading to W-2c at year-end), missing employee tax forms (W-4 not collected, defaulting to maximum withholding), local tax setup omitted (PSD codes for PA, RITA for OH, etc. missed entirely), direct deposit setup errors (employee pay rejected by bank, creating manual check issuance).

Time cost of fixing rushed setup: 5-10x the cost of doing it right initially. A $3,000 setup engagement done correctly is far cheaper than $1,500 setup plus $8,000-$15,000 of cleanup work over the following year. The discovery call assesses what’s actually involved — new entities, new state expansion, complex benefits, multi-entity coordination — and scopes setup to cover the actual scope rather than the minimum.

Multi-state payroll mechanics.

The convenience-of-the-employer rule, reciprocity agreements, local taxes across dozens of municipalities, and remote-employee complexity.

How does multi-state payroll actually work?

Multi-state payroll requires registering for state income tax withholding and state unemployment insurance (SUI) accounts in every state where employees physically work — not just the state where the business is headquartered. Six states (NY, CT, PA, NJ, DE, NE) have variations of the convenience-of-the-employer rule that override normal state-of-work logic — a remote employee working from home in a different state may still owe taxes to the employer’s state under these rules.

Some state pairs have reciprocity agreements (PA-IN, PA-MD, PA-NJ, OH-IN, etc.) that simplify cross-border employee withholding. Local taxes apply in dozens of municipalities: Pennsylvania PSD codes (every employee taxed to their work and home PSD), Ohio RITA and CCA municipal income taxes, Kentucky local occupational taxes, NYC city tax, San Francisco payroll expense tax, Detroit city income tax plus 23 other Michigan cities. Multi-state payroll setup pricing: typically $3,000-$10,000+ depending on state count and complexity. We handle the operational configuration and coordinate with the client’s CPA on nexus opinions.

What is the convenience-of-the-employer rule and which states have it?

The convenience-of-the-employer rule (often called the COE rule or convenience rule) is a state tax doctrine applied by six states: New York, Connecticut, Pennsylvania, New Jersey, Delaware, Nebraska. Under this rule, when an employee of an employer in one of these states works remotely from another state for the employee’s own convenience (not because the employer requires the work to be done out-of-state), the work is treated as if performed in the employer’s state — meaning the employer’s state taxes the wages.

Practical impact: a New York-based employer with an employee working remotely from Florida (where there’s no income tax) will typically be required to withhold New York income tax on that employee’s wages, even though the employee never works from New York. The employee may then face state tax returns in both states — one to claim the credit for taxes paid to the other. The COE rule has become significantly more contested post-2020 with widespread remote work; some states have aggressive enforcement, some have modified rules during COVID-era exceptions. We configure payroll for COE compliance where employers fall under these rules; we coordinate with the client’s CPA on the employee’s personal-side tax implications.

How do state reciprocity agreements work?

Reciprocity agreements between state pairs allow employees who live in one state and work in another to be taxed only by their state of residence — the employer withholds the home-state tax, not the work-state tax. Reciprocity simplifies payroll for cross-border employees. Major reciprocity agreements: Pennsylvania has reciprocity with Indiana, Maryland, New Jersey, Ohio, Virginia, West Virginia; Ohio with Indiana, Kentucky, Michigan, Pennsylvania, West Virginia; Indiana with Kentucky, Michigan, Ohio, Pennsylvania, Wisconsin; Michigan with Illinois, Indiana, Kentucky, Minnesota, Ohio, Wisconsin; Kentucky with Illinois, Indiana, Michigan, Ohio, Virginia, West Virginia, Wisconsin; Maryland with DC, Pennsylvania, Virginia, West Virginia; DC with Maryland, Virginia; Virginia with DC, Kentucky, Maryland, Pennsylvania, West Virginia.

Reciprocity requires the employee to file a reciprocity certificate with the employer (form varies by state pair) declaring their residence state. Without the certificate, the employer withholds work-state tax by default. We collect reciprocity certificates at employee onboarding for employees in reciprocity states and configure QuickBooks Payroll to withhold the correct state. Reciprocity does NOT typically extend to local taxes or SUI — local and unemployment taxes still follow normal rules.

How are remote employees handled across states?

Remote employees create the most multi-state payroll complexity of any employee category. Core rule: payroll taxes (state withholding, SUI) generally follow the state where the employee physically performs the work. A remote employee working from Texas for a California employer is generally a Texas payroll employee — the California employer must register for Texas SUI, withhold any applicable Texas taxes (none for state income, since TX has no state income tax), and report wages to Texas. Exceptions: convenience-of-the-employer rule states flip this for some remote arrangements; reciprocity agreements modify it for some state pairs.

Practical challenges: remote employees who move mid-year (employee relocates from CA to FL in July) require mid-year state registration in the new state and ongoing reporting through year-end in both states. Employees who travel for work present nexus questions (a NY employee traveling to other states for client work may trigger short-term withholding obligations in those states). Employees in multiple states simultaneously (truly remote with no single fixed work location) create allocation challenges. We handle the operational side; nexus opinions on income tax obligations stay with the client’s CPA.

What local taxes does multi-state payroll need to handle?

Beyond state income tax and SUI, dozens of municipalities impose local payroll taxes that QuickBooks Payroll must be configured for. Major local tax jurisdictions include Pennsylvania PSD codes (Political Subdivision codes assigned to every PA municipality — every PA employee’s work location AND residence location both have PSD codes, and the local Earned Income Tax is withheld at the higher of the two rates; major payroll complexity unique to PA); Ohio RITA and CCA (Regional Income Tax Agency and Central Collection Agency handle municipal income tax filing for ~300 Ohio municipalities; different cities use different agencies, some collect directly); Kentucky local occupational taxes (cities and counties impose occupational license taxes ranging 0.5%-2.5% on wages); NYC city tax (New York City imposes city income tax on NYC residents, different from NY State tax); San Francisco payroll expense tax (applies to businesses with significant SF payroll); Detroit city income tax (Detroit plus 23 other Michigan cities impose city income tax); Indiana CAGIT/COIT (County Adjusted Gross Income Tax / County Option Income Tax for residents); and Maryland county taxes (each county adds local tax to state income tax).

Missing local tax setup creates compliance gaps that surface in employee tax returns months or years later. We configure local taxes correctly during initial setup and ongoing as employees move.

What happens if I had employees in a state and never registered for payroll there?

This is a common discovery during cleanup engagements — the business had remote employees in a state for months or years, never registered, never withheld, never reported. Exposure dimensions: unpaid state withholding tax (employer is liable for under-withheld amounts plus penalties), unpaid SUI (employer must pay back-SUI from the date the first employee started in that state), penalties for failure to file (varies by state; can reach 5-25% of unpaid amounts), interest accumulating on unpaid balances, and potential state notices triggering audits or expanded scrutiny.

Remediation path: register retroactively in each affected state, file back returns (state withholding returns and SUI returns for each affected quarter), pay back amounts plus penalties and interest, and establish ongoing compliance going forward. Many states have voluntary disclosure programs that reduce penalties for employers who proactively come forward before being identified by the state. We handle the operational remediation (back returns, registration, payment coordination); the CPA handles any income-tax nexus questions and penalty negotiation. Engagement scope for back-state remediation: typically $5,000-$25,000+ depending on number of states, time period, and employee count. The cost of waiting is significantly higher than the cost of remediation — states catch up eventually.

Year-end payroll work.

The November-through-April year-end cycle, the deadlines, the fringe benefit adjustments, S-corp owner items, and W-2c corrections.

When should I start year-end payroll work?

Year-end payroll is a six-month cycle, not a January event. Ideal engagement timing: late November or early December, before the final payroll of the year. The pre-year-end reconciliation phase verifies year-to-date wage and tax accumulations match QuickBooks general ledger before W-2 generation locks the figures. Year-end adjustments happen before December’s final payroll: bonuses, fringe benefits, group-term life insurance over $50,000 (imputed income), third-party sick pay reporting, S-corp owner health insurance (added to W-2 box 1 but not subject to FICA).

January is the deadline crunch — W-2s, 1099-NECs, Form 940, Q4 941 all due by January 31. February through April handles W-2c amendments as employees file personal returns. Engage by mid-December for full cycle coverage; January engagement works under tighter deadlines but adjustment options narrow significantly once payroll is closed.

What are the actual year-end payroll deadlines?

The critical year-end deadlines, in order: December final payroll must include all year-end fringe benefit additions (group-term life, S-corp owner health, other taxable benefits) before the year closes. January 31: W-2s to employees, 1099-NECs to contractors and the IRS, Form 940 (annual FUTA), Form 941 for Q4 (or Form 944 for small employers), and state W-2 transmittals in most states. February 15: deadline to claim exemption from withholding on W-4 (employees who claimed exempt in the prior year must file a new W-4 by this date to continue exemption). February 28: paper 1099s filed with the IRS (versus January 31 if filed electronically). March 31: electronic 1099 filing deadline for some 1099 types (the NEC deadline is January 31 regardless of paper/electronic). April 15: by this date employees file personal tax returns, and W-2c corrections most often surface here.

State deadlines vary; most align with federal but some states have earlier filing dates or additional state-specific transmittal forms. We track all federal and state deadlines per client and schedule work to hit them.

What fringe benefits need year-end treatment?

Several fringe benefits require specific year-end W-2 treatment that QuickBooks Payroll must be configured for before the final payroll closes. Common year-end fringe items: group-term life insurance over $50,000 (the cost of coverage exceeding $50,000 is imputed income subject to FICA/Medicare but not federal income tax withholding; added to W-2 box 1 and box 12 code C); personal use of company vehicles (imputed income for the personal-use portion, via annual lease value or cents-per-mile method); educational assistance over $5,250 (amounts above the IRS limit are taxable wages); awards and gifts over $25 ($400 for length-of-service awards) are taxable wages; gym memberships and most wellness incentives (taxable wages unless meeting specific exclusion requirements); spousal travel (when an employee’s spouse travels with them on business at company expense, the spousal travel cost is generally imputed income); and domestic partner benefits (the cost of health coverage for non-tax-dependent domestic partners is imputed income).

Missing fringe benefit additions creates W-2c work in spring when items surface. We coordinate fringe benefit tracking through the year and add adjustments to the December payroll before year-end close.

How is S-corp owner health insurance handled at year-end?

S-corp >2% shareholder health insurance is one of the most commonly mishandled year-end items. The required treatment: health insurance premiums paid by the S-corp for the >2% shareholder must be added to the shareholder’s W-2 box 1 (federal taxable wages) but are NOT subject to FICA or Medicare withholding. The premiums are also not subject to federal income tax withholding (the employee picks them up on their personal return).

Practically, this means configuring a year-end payroll adjustment that: (a) adds the annual premium amount to gross taxable wages, (b) increases box 1 of the W-2, (c) is reported in box 14 with code “S CORP HEALTH” or similar for IRS reporting, (d) doesn’t affect FICA/Medicare boxes, (e) doesn’t generate withholding. The shareholder then deducts the premium as a self-employed health insurance deduction on their personal return (above-the-line deduction). HSA contributions by the S-corp for >2% shareholders are handled similarly. Missing this treatment creates a W-2c in spring when the shareholder’s CPA flags it. We configure the December payroll to include these adjustments before year-end close.

What if W-2s have errors after they’re filed?

W-2 errors discovered after initial filing are corrected through Form W-2c (Corrected Wage and Tax Statement) filed with the Social Security Administration along with Form W-3c transmittal. Common scenarios triggering W-2c work: employee finds a discrepancy when preparing a personal tax return, employer realizes a fringe benefit was missed, incorrect Social Security number, wrong wage amounts, missing pre-tax benefit treatment, group-term life insurance not added, S-corp owner health insurance not added to box 1.

W-2c filing has no specific statutory deadline but should be filed promptly when errors are identified. The corrected W-2c is furnished to the employee, who may need to file an amended personal tax return depending on the magnitude of the correction. Multi-employee W-2c batches are common in year-end cleanup engagements when prior bookkeeping missed multiple adjustments. W-2c engagement scope: typically $500-$2,500 for individual corrections; multi-employee batches scope as cleanup projects at $2,500-$10,000+ depending on volume.

Are bonuses taxed differently than regular wages?

Bonuses are supplemental wages with specific federal withholding treatment under IRS rules. Two acceptable methods: (1) flat 22% federal supplemental rate on bonus amounts up to $1,000,000 ($1M+ uses 37% flat rate) — the simplest method, often used for year-end and one-time bonuses; (2) aggregate method, treating the bonus as if added to regular wages and applying normal withholding tables — more accurate for employees whose effective rate is below 22% but more complex to calculate.

FICA/Medicare: bonuses are fully subject to FICA (up to the annual wage base) and Medicare (no cap) regardless of withholding method. State supplemental rates: many states have their own supplemental withholding rates (CA 10.23%, NY varies, etc.) that apply to bonuses separately from federal. 401(k) treatment: bonuses are eligible for 401(k) elective deferrals unless the plan document excludes them. HSA treatment: bonuses can include HSA contributions if elected. We configure bonus runs in QuickBooks Payroll with correct treatment for federal supplemental, state supplemental, FICA, and benefit deductions before processing.

Contractor classification.

The 1099 vs W-2 distinction, California AB5, the ABC test, state variations, and the substantial liability of misclassification.

What is California AB5 and which states have similar rules?

California AB5 (Assembly Bill 5, effective January 2020) codified the ABC test for distinguishing employees from independent contractors. Under the ABC test, a worker is presumed to be an employee unless the hiring entity proves all three: (A) the worker is free from control and direction of the hiring entity, (B) the worker performs work outside the usual course of the hiring entity’s business, and (C) the worker is customarily engaged in an independently established trade or business.

Failing prong B is especially common — a marketing agency hiring marketing contractors typically fails B because the work is within the usual course of the business. Other states with ABC test or similar strict classification standards: Massachusetts (long-standing strict three-prong test), New Jersey (ABC test), Connecticut (ABC test), Illinois (ABC test for unemployment purposes), and a growing list of states adopting or proposing similar standards. Misclassification creates back-tax liability (employer-side payroll taxes that should have been paid), unemployment insurance and workers’ comp exposure, and state-specific penalties. We coordinate with the client’s CPA on classification questions but handle the operational tracking and year-end filings.

What’s the federal standard for contractor classification (IRS)?

The federal standard uses the IRS common law test, evaluating three categories: behavioral control (does the company control or have the right to control what the worker does and how the worker does the job?), financial control (does the company control the business aspects of the worker’s job — how the worker is paid, whether expenses are reimbursed, who provides tools?), and type of relationship (are there written contracts or employee-type benefits, will the relationship continue, is the work a key aspect of the business?).

The IRS does not have a fixed checklist; the test is multi-factor with no single deciding factor. The IRS also publishes Form SS-8 — either the worker or the company can request an IRS determination on classification, though processing takes 6+ months and the determination is binding only for the specific facts. Federal vs state divergence: a worker may be properly classified as a contractor under federal IRS standards but be an employee under California ABC or Massachusetts standards. Multi-state businesses must comply with the strictest applicable standard, not just federal. Misclassification penalties at the federal level: back employment taxes (Social Security, Medicare, FUTA), failure-to-deposit penalties, failure-to-file penalties, interest. Coordinated with the client’s CPA on classification opinions.

Does QuickBooks Payroll handle 1099 contractors well?

QuickBooks Payroll handles contractor payments and 1099-NEC generation, but the workflows are less polished than dedicated contractor platforms like Gusto. For businesses with significant contractor volume relative to W-2 employees, we typically recommend evaluating Gusto first — Gusto treats 1099 contractors as first-class entities with separate onboarding workflows, contractor-only payment runs (no full payroll seat cost), and automatic 1099-NEC filing.

For businesses where contractors are a small share of payments alongside W-2 employees, QuickBooks Payroll’s contractor handling is adequate. Workflow specifics: contractors are set up separately from employees, payments are tracked as expenses to 1099-eligible categories, year-end generates 1099-NEC forms from the accumulated payments, and electronic 1099 filing is available. Common issues: W-9 collection at contractor onboarding is critical (without TIN, year-end backup withholding rules apply), tracking payments by contractor across the year requires discipline in QuickBooks expense categorization, and state-specific 1099 filings (CA, NY, several others require separate state filings) add complexity. See our QuickBooks Payroll vs Gusto comparison for the detailed contractor-handling breakdown.

What are the actual penalties for contractor misclassification?

Misclassification penalties layer across federal, state, and operational categories. Federal penalties (IRS): back employment taxes (Social Security, Medicare, FUTA) on misclassified wages, failure-to-deposit penalties (typically 1.5% of employee’s wages, 40% of Social Security/Medicare not withheld plus 100% of employer share), failure-to-file penalties on missing Form 941s, interest on unpaid amounts. The IRS offers a Voluntary Classification Settlement Program (VCSP) that significantly reduces penalties for employers proactively reclassifying contractors as employees going forward.

State penalties: vary widely. California penalties under AB5 can include $5,000-$25,000 per violation under Labor Code 226.8 for willful misclassification. State unemployment insurance back-payment plus penalties. State workers’ compensation premiums retroactively owed. Civil liability: misclassified workers can sue for back wages, overtime, benefits, and statutory damages. Operational impact: state audits often expand once one classification issue is found, scrutinizing payroll practices broadly. The cost of getting classification wrong is significantly higher than the cost of getting it right at hiring — the discovery call and engagement scope addresses classification questions before they compound.

Common errors & restoration.

Year-to-date posting drift, missing tax filings, payroll history loss, and the cleanup engagements that restore payroll accuracy.

What is payroll posting drift and how do I detect it?

Payroll posting drift is the accumulating divergence between QuickBooks general ledger payroll figures and the payroll service’s actual payroll reports. Common causes: chart-of-accounts mapping errors at setup (payroll posts to wrong GL accounts), benefit deductions configured with wrong GL accounts (HSA deductions hit the wrong liability account), manual journal entries adjusting payroll-related accounts incorrectly, partial posting of payroll runs (the gross posts but the deductions don’t), and bank reconciliation not catching net payroll discrepancies.

Detection signals: payroll liability accounts that don’t reconcile to expected balances (the balance keeps growing because deductions post but remittances don’t), wage expense in QuickBooks not matching the payroll service’s YTD wage report, employer tax expense in QuickBooks not matching expected calculations, and W-2 generation showing differences between QuickBooks data and payroll service data. Fix: monthly bookkeeping discipline that reconciles QuickBooks payroll figures to payroll service reports as part of month-end close. We catch drift early and fix it before it compounds across months and surfaces at year-end with significant cleanup cost.

What if I missed quarterly 941 filings or state payroll tax returns?

Missing payroll tax returns triggers escalating penalties. Federal Form 941 (quarterly): failure-to-file penalty starts at 5% per month of the unpaid tax, up to 25%. Failure-to-deposit penalty applies separately on unpaid deposits. Interest accumulates on unpaid amounts. After IRS notices, the matter escalates to collections. State withholding and SUI returns: vary by state. Most states impose 5-25% failure-to-file penalties plus interest. SUI penalties can include increased SUI rates in future years. Some states impose flat-dollar penalties per missing return.

Remediation: file back returns as soon as identified (don’t wait for IRS or state notices — proactive filing reduces some penalty categories), pay unpaid amounts plus penalties and interest, set up installment agreements if cash flow doesn’t allow lump-sum payment. The IRS’s First-Time Abate program may eliminate some penalties for employers with clean prior compliance history. State voluntary disclosure programs apply in some cases. We handle the operational back-filing; a CPA or EA handles IRS representation and penalty abatement requests. Back-payroll-tax cleanup engagements scope at $2,500-$15,000+ depending on number of missed returns, jurisdictions, and back-tax amounts.

Can payroll history be restored if data is lost?

Yes, in most cases — though the work varies by scenario. Scenario 1: QuickBooks file corruption or loss. Payroll data can be reconstructed from the payroll service (QuickBooks Payroll, Gusto, ADP) reports, which maintain independent records. Year-to-date wage reports, tax filings (941s, W-2s), and detailed pay-run reports allow rebuilding the QuickBooks payroll postings. Cost: a few hours of reconstruction work to a multi-day project depending on the period covered.

Scenario 2: Payroll service data loss or platform switch with incomplete data export. Reconstruction uses bank statements (employee net deposits), tax filings (941s, state returns) for gross-to-net reconciliation, W-2s if any have been issued, and employee records. This is more complex than Scenario 1 but workable. Scenario 3: Both QuickBooks and payroll service data lost (rare but happens). Reconstruction from bank statements, employee records, prior W-2s, and tax filings on file with the IRS and states. The most labor-intensive scenario, but the IRS and states maintain records of filed returns that anchor the reconstruction. We handle all three scenarios; engagement scope depends on the period covered and the data sources available.

What if my payroll service made an error?

Payroll service errors do happen — missed tax deposits, incorrect tax filings, employee setup errors, year-end W-2 issues. Resolution path: (1) document the error specifically (which return, which amount, which deadline missed), (2) work directly with the payroll service’s support to acknowledge the error and request remediation, (3) if the service caused penalty exposure, request the service cover penalties (most major payroll services have tax-penalty protection on premium tiers), (4) file corrected returns if needed, (5) follow up to ensure the fix is documented and verifiable in future filings.

QuickBooks Payroll Elite tier and some Premium configurations include tax penalty protection — Intuit covers penalties resulting from their errors in tax calculation or filing. ADP, Paychex, and other major providers offer similar protection at their higher tiers. Gusto includes tax accuracy guarantees on standard plans. The protection has conditions (timely setup, accurate employee data, no employer-side mistakes), but legitimate platform errors are typically covered. For businesses without protection tiers, the platform error remediation comes out of the business’s pocket. We handle the operational cleanup; the platform’s support team handles the protection claim if applicable.

Engagement & pricing.

What we deliver, what we don’t, and how engagements actually start.

What payroll services does TechBrot deliver?

Five core engagement types across the payroll silo: QuickBooks Payroll setup ($1,500-$6,000+) — one-time setup covering tax registration coordination, employee setup, benefits configuration, CoA mapping, first pay-run verification; multi-state payroll setup ($3,000-$10,000+) — setup or expansion to multi-state operations, including state registration, convenience-of-employer configuration, reciprocity handling, local taxes; ongoing payroll management ($150-$800+/mo) — recurring payroll engagement covering pay-run processing, employee changes, quarterly tax filings, monthly bookkeeping integration; year-end payroll ($1,500-$7,500+) — the November-through-January year-end cycle: pre-year-end reconciliation, fringe benefit adjustments, W-2/1099 generation, Q4 941 and Form 940 filing; and payroll cleanup and restoration ($2,500-$25,000+) — remediation engagements for posting drift, missed filings, multi-state catch-up, data restoration, W-2c corrections.

What we don’t do: income tax filing (CPA/EA work), IRS representation in audits or controversy (CPA/EA work), legal opinions on classification questions (attorney work). See the payroll hub for the engagement universe.

How do I get started with payroll services?

Book a 30-minute discovery call. The call covers your current payroll state (which platform if any, employee count, state count, contractor mix), your specific situation (industry, growth stage, recent changes, current pain points), the engagement type that fits (one-time setup, ongoing management, multi-state expansion project, year-end cleanup), and any questions about how we work. Within 3 business days of the call, we deliver a written scope with fixed-fee pricing — no surprises, no hourly billing.

If the engagement fits, work begins on the scheduled start date. If a different scope is needed (cleanup before setup, CPA coordination before resolution, attorney input on classification), we’ll say so and route accordingly. The discovery call is complimentary; the scope is non-binding; engagement starts only when you commit in writing.

Book the discovery call →