How to Run Payroll in QuickBooks Online

Before each run, confirm the company and employee setup, pay schedule, work locations, tax accounts, direct-deposit authorization, earnings, deductions, benefits, and year-to-date balances. Enter or import time, then review every employee’s gross pay, taxable wages, withholding, employer taxes, deductions, reimbursements, net pay, payment method, and pay date. QuickBooks menus and product features can change, so follow the current in-product prompts and official help for the subscribed payroll tier. After submission, save the payroll reports and verify bank funding, employee payment, tax activity, filings, and the general ledger.

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

Scheduled and off-cycle runs differ

Use the correct workflow for regular payroll, bonuses, commissions, final pay, corrections, or fringe-benefit reporting.

Pay date controls timing

Direct-deposit deadlines, payroll liabilities, quarter assignment, and employee wage statements depend on the actual pay date.

Employee setup drives calculations

Work state, resident state, filing status, W-4 data, local taxes, earnings, deductions, and benefits need current facts.

Hours need source approval

Reconcile imported time, overtime, leave, job coding, commissions, tips, and edits before payroll calculates.

Taxability needs review

A deduction or reimbursement label does not prove its federal, state, or local wage treatment.

Funding is separate from approval

Confirm the bank account, available cash, debit timing, direct-deposit deadline, and fallback checks.

Automation needs exception monitoring

Auto Payroll or recurring settings still require change, leave, termination, bonus, garnishment, and funding controls.

Submission is not the final status

Verify pay delivery, tax withdrawals, filings, rejects, corrections, and ledger posting.

Step-by-step workflow

1. Complete company setup. Verify EIN, legal name, addresses, tax accounts, deposit schedule, work locations, bank, accounting mapping, and payroll subscription.
2. Review employee profiles. Confirm identity, address, work and resident states, W-4, rate, schedule, earnings, deductions, benefits, leave, and payment method.
3. Set the payroll period. Choose the correct pay schedule, period dates, pay date, regular or off-cycle run, and direct-deposit deadline.
4. Load and approve inputs. Import or enter hours, overtime, leave, bonuses, commissions, tips, reimbursements, garnishments, and one-time changes.
5. Review gross-to-net. Inspect each employee and totals for wages, taxable bases, withholding, employer taxes, deductions, contributions, and net pay.
6. Check warnings and cash. Resolve missing data, negative checks, tax notices, bank issues, duplicate runs, and funding shortfalls before submission.
7. Submit payroll deliberately. Confirm authorization, payment method, debit timing, employee delivery, and final pay date in the current workflow.
8. Save payroll reports. Export the payroll summary, employee detail, tax liability, deduction, direct-deposit, and accounting reports.
9. Verify downstream status. Check employee deposits or checks, bank debits, tax payments, filings, agency acceptance, and benefit remittances.
10. Reconcile the ledger. Tie gross pay, taxes, deductions, employer costs, cash, liabilities, and journal entries to the payroll reports.

Worked example

A firm runs semimonthly payroll for 14 employees. Before submitting, the reviewer finds one new employee assigned to the company headquarters instead of the actual work state, a duplicate bonus import, and a terminated employee still receiving a benefit deduction. The team corrects the profiles and inputs, reruns the preview, approves the funding debit, and submits before the displayed direct-deposit cutoff. After payday, it ties reports to the bank and ledger and verifies tax status instead of treating the confirmation screen as the end of the process.

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

• Copying the prior run blindly. Review hires, terminations, leave, pay changes, bonuses, states, and one-time deductions.
• Using the wrong pay date. Pay date affects deadlines, periods, liabilities, and year-end reporting.
• Approving only net pay. Taxable wages, taxes, deductions, benefits, employer cost, and cash require review.
• Ignoring product warnings. Resolve setup, tax, bank, and employee exceptions before submitting.
• Missing the direct-deposit cutoff. Use the deadline shown for the current service and payment date.
• Editing payroll only in the ledger. Corrections should preserve payroll, filing, W-2, and audit-trail consistency.
• Assuming taxes were filed. Monitor the provider and agency status and resolve rejects.
• Keeping no run package. Export the source inputs, approval, reports, confirmation, bank proof, and reconciliation.

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.

Assign one owner and one reviewer to the calendar. The owner prepares the source schedule and resolves open items; the reviewer tests identities, totals, rule references, filing status, and evidence. Record the date of the official guidance used because form pages and software menus can change during the filing season. If a rule is uncertain, document the question and escalate it before the deadline rather than placing an unsupported assumption in the final file. This short control list protects both accuracy and continuity when another bookkeeper, payroll specialist, or tax preparer takes over the work. Save the checklist with the return so next year’s team can see which controls were completed and which exceptions required follow-up.

Practical implementation notes

Pre-submit checklist

Require employee changes, input approval, gross-to-net review, cash, warnings, direct-deposit deadline, and authorized submitter.

Exception report

List new hires, terminations, rate changes, unusual hours, negative checks, bonuses, new states, manual taxes, and large net-pay changes.

Run package

Archive inputs, preview, approval, final reports, confirmation, bank evidence, employee exceptions, and correction history.

Quarter tie-out

Reconcile payroll runs to deposits, Forms 941, state returns, benefits, W-2 accumulators, and the ledger before quarter close.

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.