QuickBooks Payroll: The Complete Guide

QuickBooks Online Payroll is a payroll service connected to QuickBooks accounting. Current U.S. plans are generally identified as Core, Premium, or Elite. The exact features, pricing, funding timing, local-tax coverage, support, and protections can change, so confirm them in the company’s subscription and current Intuit materials. A sound implementation does more than activate payroll: it establishes company and agency identities, employee tax data, prior wages, pay policies, accounting mappings, approvals, tax authorizations, and a documented reconciliation.

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

Start with the active subscription

Confirm the company region, accounting plan, payroll plan, employee count, billing terms, direct-deposit timing, and included services in the live account. Do not use an old comparison chart as the contract.

Company identity must match agencies

Use the legal name, EIN, addresses, entity type, federal filing frequency, state account numbers, and local registrations that agencies recognize. A notice can result when software uses a trade name or wrong account.

Employee setup drives every calculation

Verify legal name, SSN, address, work and residence locations, hire date, pay type, rate, schedule, Form W-4 data, state forms, deductions, benefits, garnishments, and payment method.

Prior payroll is not optional midyear

If wages were paid before conversion, enter year-to-date employee and company totals by the required pay periods. Those figures affect wage bases, Forms 941, state returns, and W-2s.

Payroll settings encode policy

Define workweeks, pay periods, pay dates, overtime, paid time off, holiday pay, bonuses, commissions, tips, reimbursements, pretax deductions, employer contributions, and taxable benefits.

Tax automation requires authorization

Complete bank verification, principal-officer details, e-signatures, agency accounts, state third-party access, deposit schedules, and any tasks shown as incomplete.

A submitted payroll is a financial event

Review hours and pay, preview gross-to-net amounts, choose the funding account, approve the run, confirm direct-deposit status, and record paper checks or off-cycle payments.

Accounting mappings need design

Map wages, employer taxes, benefits, deductions, reimbursements, and liabilities to appropriate accounts, classes, locations, customers, or projects without duplicating entries.

Automated filing still needs oversight

Compare scheduled tax debits and filed forms with payroll liability reports and agency accounts. A software status does not replace acceptance or notice review.

Year-end begins during setup

Accurate employee identities, prior wages, taxable fringe benefits, voids, manual checks, and state allocations are prerequisites for reliable W-2s.

Step-by-step workflow

1. Document requirements. List states, localities, pay groups, worker types, benefits, deductions, time sources, projects, approvals, reports, tax forms, and record-retention needs.
2. Confirm registrations. Verify EIN and all state and local withholding and unemployment accounts before relying on automated filings.
3. Clean employee data. Compare payroll identities with onboarding records, current Forms W-4, state certificates, benefit elections, and bank authorizations.
4. Configure policies. Build earnings and deduction codes that reflect the employer’s written policies and tax treatment.
5. Load prior wages. Enter and reconcile every current-year payroll paid outside the new service, including quarter-to-date and employee-level tax details.
6. Authorize taxes and direct deposit. Complete the principal-officer, bank, e-signature, and state-agent tasks early enough to resolve rejections.
7. Run a parallel test. Calculate a representative payroll in the old records and QuickBooks, then explain every difference before going live.
8. Approve the first live run. Review pay period, pay date, employees, hours, earnings, deductions, taxes, net pay, funding, and accounting preview.
9. Verify settlement. Confirm employee payments, bank withdrawals, tax debits, rejected deposits, returned direct deposits, and manual checks.
10. Reconcile monthly and quarterly. Tie payroll registers to the general ledger, bank, Forms 941 or 944, state returns, and tax accounts.
11. Close year-end. Enter taxable benefits and adjustments, reconcile W-2 and W-3 totals to payroll returns, deliver statements, confirm SSA filing, and preserve corrections.

Worked example

A consulting business changes payroll systems in July after paying six monthly payrolls. The owner enters employee identities and pay settings, then loads each worker’s year-to-date wages and taxes plus company quarter totals. The reviewer compares a June payroll in both systems and finds that health deductions were set as after-tax instead of pretax. The configuration is corrected before the first live run. After July payroll, the business verifies employee deposits, the payroll bank withdrawal, tax liabilities, and general-ledger entries. At quarter-end, it ties the three July-through-September registers to Form 941 and the agency debit history.

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

• Activating payroll before registrations. Software cannot repair a missing state account number or decide where an employee creates nexus.
• Skipping prior pay history. Wage bases, withholding, returns, and W-2s can be wrong even when the first new paycheck looks reasonable.
• Copying deduction tax settings. Confirm each benefit’s federal, state, and local treatment from plan facts and current guidance.
• Letting employees approve themselves. Separate time approval, payroll preparation, release, and bank reconciliation where staffing allows.
• Posting net pay only. The books should capture gross wages, employee deductions, employer taxes, liabilities, and payments.
• Assuming every locality is covered. Confirm local withholding and filing support for each work location and plan.
• Ignoring alerts after payday. A payroll can pay employees while a tax authorization, direct deposit, or filing remains rejected.
• Canceling the old system too early. Preserve reports, forms, audit logs, notices, and access before ending the prior service.

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

Implementation file

Save subscription terms, setup checklist, agency accounts, authorizations, bank confirmation, policy decisions, employee import, prior-payroll tie-out, and test results.

Payroll approval packet

Retain approved time, change log, payroll preview, reviewer sign-off, final register, payment status, tax liability report, and accounting export.

Quarterly control

Reconcile wages, withholding, Social Security wages and taxes, Medicare wages and taxes, deposits, returns, state reports, and general-ledger liabilities.

Access control

Use named users, appropriate roles, multifactor authentication, prompt termination of access, and periodic review of administrators and bank permissions.

Deeper planning points

Plan and price research

Record what was true on the decision date. Save current official plan pages and the in-account quote, including per-employee charges, promotions, renewal terms, direct-deposit timing, add-ons, exclusions, and cancellation access. Recheck before renewal because product terms change.

Employee and contractor separation

Keep payroll and 1099 workflows distinct. Employees belong in payroll with withholding and wage reporting. Contractors require a documented classification, Form W-9, vendor payments, and information-return review. A menu labeled Contractors does not decide worker status.

Multistate payroll

Work location often matters more than headquarters. Track where each employee works, residence, reciprocity, temporary assignments, local taxes, unemployment state, registrations, and effective dates. Obtain advice before the first paycheck in a new jurisdiction.

Off-cycle payroll

Manual checks, bonuses, corrections, and voids must enter the same control system. Use the correct pay date and tax treatment, approve the entry, confirm funding, reconcile the employee record and bank, and test its effect on the quarterly and annual forms.

Tax notices

Keep agency mail with the payroll close. Record the agency, account, period, issue, amount, response deadline, owner, provider case, documents sent, and final resolution. Verify changes in both the agency account and payroll configuration.

Year-end continuity

Preserve access and source reports beyond December. Download payroll registers, employee details, tax forms, payment confirmations, audit logs, benefit reports, and correction records before changing services or subscriptions.

Disaster recovery

Plan how payroll will run if the primary administrator or bank connection is unavailable. Maintain a backup authorized user, secure contact list, funding deadline calendar, manual-check process, agency access, and a documented way to obtain employee pay information.

Service-provider responsibility

A provider can perform tasks, but the employer remains responsible for accurate and timely filings. Review submitted forms, keep acceptance evidence, monitor agency accounts, respond to notices, and do not assume a support case pauses a statutory deadline.

Time integrations

Imported time still needs payroll approval. Map regular, overtime, leave, project, location, and job codes before the first import. Test rounding, time zones, edited punches, approvals, and duplicate imports, then compare source totals with the payroll preview every period.

Benefits and deductions

Build each code from plan documents and legal orders. Document pretax or after-tax treatment, employee and employer portions, limits, effective dates, arrears, refunds, and W-2 reporting. Reconcile payroll deductions to carrier invoices, retirement funding, garnishment remittances, and employee elections.

Bank funding

Payroll approval and cash availability must share a calendar. Record direct-deposit lead times, tax withdrawal timing, bank holidays, funding limits, returned deposits, fraud controls, and backup payment procedures. Confirm the correct account before every submission and review unexpected debits promptly. Reconcile cleared payroll and tax transactions to the final register, liability reports, and provider status before closing the bank month and approving the reconciliation.

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.