How to Create a 1099 in QuickBooks Online

In QuickBooks Online, review the current 1099 workflow from Expenses and Bills or use in-app search because menus can change. Confirm company legal information, invite or enter contractor W-9 data, identify the proper form and boxes, map expense accounts, and review the vendor and payment-detail reports. QuickBooks may exclude card and qualifying third-party network payments from payer Forms 1099, but the business should verify the actual payment channel and settlement record. For payments made in 2026, use the IRS’s current $2,000 general Form 1099-NEC threshold rather than relying on any software help text that still shows an earlier threshold. Preview forms, reconcile control totals, authorize filing, furnish recipients, and save acceptance and correction records.

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

Software does not classify workers

Confirm the factual employee-versus-contractor decision outside the 1099 wizard.

W-9 data should be authoritative

Use legal name, TIN, entity classification, address, and exemptions rather than a display name.

Account mapping controls inclusion

Review every expense and asset account that can contain reportable contractor payments.

Payment method controls exclusion

Card, ACH, check, direct deposit, and third-party network activity must be distinguished.

The IRS rule controls thresholds

Use payment-year official guidance when product screens or help pages lag.

A preview is not a filing

Track draft, submitted, accepted, rejected, recipient delivered, and corrected as distinct statuses.

Additional forms need separate review

Late vendors, corrected forms, and state copies should tie to the same control ledger.

Accounting remains the source

The final accepted totals must reconcile back to the closed books.

Step-by-step workflow

1. Close contractor transactions. Post invoices, payments, voids, credits, reimbursements, and year-end corrections.
2. Clean contractor profiles. Confirm Track 1099 status and match every identity field to a current Form W-9.
3. Review payment channels. Separate checks, ACH, direct deposit, cards, PayPal, and other settlement networks.
4. Map accounts. Include reportable service accounts and exclude unrelated payroll, inventory, owner, and personal accounts.
5. Run 1099 reports. Review vendor totals, account detail, excluded payments, missing TINs, and threshold exceptions.
6. Apply current form rules. Choose 1099-NEC or 1099-MISC, the correct boxes, tax year, threshold, and exemptions.
7. Preview every form. Verify payer, recipient, amounts, withholding, state fields, and control totals.
8. Authorize filing and delivery. Confirm fees, filing scope, recipient method, consent, addresses, and deadlines.
9. Resolve rejects and corrections. Fix source data where appropriate and use the current formal correction process.
10. Archive the package. Save reports, mapping, previews, acceptance, recipient evidence, states, and corrected copies.

Worked example

A consulting company maps subcontractor fees to Form 1099-NEC and runs the detail report. One vendor total includes $3,000 by ACH and $900 by card. Another vendor’s profile uses a nickname that differs from Form W-9. The reviewer separates the card payment, updates the legal identity from the W-9, applies the official 2026 threshold, previews the form, and ties the accepted total to the ledger. The company does not edit expenses merely to force the wizard total.

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 a display name as legal name. Match the current W-9.
• Selecting every expense account. Map only accounts containing potentially reportable payments.
• Counting card payments twice. Reconcile settlement methods.
• Following stale threshold text. Use current IRS instructions for the payment year.
• Filing before books close. Post corrections and reconcile first.
• Assuming preview means accepted. Save final filing status.
• Ignoring recipient delivery. Maintain consent, mailing, and replacement evidence.
• Editing transactions after filing silently. Use a controlled correction workflow.

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

Mapping workbook

List each general-ledger account, included boxes, excluded categories, reviewer, and approval date.

Vendor exception report

Track missing TINs, name mismatches, exemptions, card payments, negative totals, and withholding.

Filing control

Reconcile form count and dollars from QuickBooks to source ledger and accepted records.

Change log

Record post-close transaction edits, vendor corrections, additional forms, and agency responses.

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.