How to Create a 1099 Form for a Contractor

A business generally prepares Form 1099-NEC for covered nonemployee service payments after confirming the worker is not an employee, obtaining a valid Form W-9, reviewing the current reporting threshold and exceptions, and removing payment-card or qualifying third-party-network transactions that are generally reported on Form 1099-K. For payments made in 2026, the IRS states a $2,000 threshold for covered Form 1099-NEC payments, while backup withholding can require reporting regardless of amount.

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

Worker status comes first

Form 1099-NEC does not turn an employee into a contractor.

Form W-9 controls identity

Use the legal name, business name, tax classification, address, and TIN in the manner required by the form.

Payment category selects the form

Nonemployee compensation generally uses Form 1099-NEC, while rent and other specified categories use Form 1099-MISC.

Payment method affects the total

Card and qualifying third-party-network payments are generally handled by the payment settlement entity.

Current-year rules matter

Thresholds, form boxes, e-file rules, deadlines, and state requirements can change.

Step-by-step workflow

1. Collect Form W-9 during onboarding. Resolve a missing or inconsistent name and TIN before the first reportable payment.
2. Confirm contractor status. Document behavioral control, financial control, relationship facts, and applicable state tests.
3. Export vendor payments. Include checks, ACH, cash, direct deposits, credits, voids, reimbursements, and payment channels.
4. Reconcile and classify. Remove transfers and applicable card transactions, separate nonemployee compensation from other categories, and document exceptions.
5. Apply the current rules. Review threshold, corporate exemption, legal or medical exceptions, and backup withholding.
6. Prepare the form. Enter payer and recipient data, box 1a compensation, federal withholding, and state information.
7. Review and file. Have a second person verify identity and dollars, then transmit through the approved channel.
8. Furnish and retain. Deliver the recipient statement and keep acceptance, delivery evidence, and the source workpaper.

Worked example

A consulting firm pays a designer $9,500 by ACH and $3,000 by credit card during 2026. The designer is a true nonemployee and provided Form W-9. The payer’s workpaper starts with $12,500, identifies the card portion that the payment settlement entity generally reports on Form 1099-K, and reviews $9,500 for Form 1099-NEC. The firm prepares the current form, files through its approved electronic system, verifies acceptance, and furnishes the contractor copy.

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

• Waiting until January for Form W-9. Missing TINs can create backup-withholding and filing problems.
• Reporting an employee as a contractor. Worker status follows the facts, not the payment method.
• Using gross vendor spend without reconciliation. Loans, reimbursements, voids, and card payments can distort the amount.
• Using an old $600 threshold for 2026. The IRS states $2,000 for covered payments made in 2026.
• Treating every corporation as exempt. Review current exceptions and the payment category.
• Assuming transmission equals acceptance. Monitor the filing status and resolve rejections.
• Ignoring the recipient copy. Filing and furnishing are separate obligations.

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

Monthly control

Code contractor payment methods consistently and reconcile them monthly so the year-end report does not double count card transactions.

Approval control

Separate preparation from review. The reviewer should recheck names, TIN format, payment channels, amount, form type, state fields, and year.

Correction control

Preserve the original filing, reason for correction, corrected acceptance, and corrected recipient-delivery evidence.

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.