How to Fill Out a 1099 for Contractors

For covered payments made in 2026, the federal Form 1099-NEC threshold is generally $2,000. Backup withholding can require reporting regardless of amount. Begin with the contractor’s legal name, business name, tax classification, address, and TIN from Form W-9. Reconcile checks and ACH while separately reviewing card and qualifying third-party-network payments generally reported by settlement entities. Use the December 2026 Form 1099-NEC revision and its current box layout rather than copying an older tutorial. Filing the form does not decide worker status or correct prior payroll misclassification.

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

An employee generally receives Form W-2; a contract label or lack of withholding does not create contractor status.

Payer identity must be consistent

Use the legal payer name, address, TIN, and contact information tied to the reporting business.

Recipient data comes from Form W-9

Use the supported name and TIN format rather than a nickname, invoice header, or vendor display name.

Box 1a reports covered compensation

Reconcile qualifying service payments, including applicable parts and materials, under the current instructions.

Payment method matters

Do not duplicate eligible card and network payments generally handled through Form 1099-K.

Backup withholding has its own rule

Report federal income tax withheld in the applicable box and file regardless of the normal payment amount.

Corporate exemptions have exceptions

Legal services and specified medical or health-care payments require separate review.

States need separate decisions

State boxes on the federal form do not necessarily complete direct state filing, withholding, or recipient duties.

Step-by-step workflow

1. Confirm contractor classification. Document behavioral control, financial control, relationship, state tests, and any classification review.
2. Collect and validate Form W-9. Review legal name, business name, classification, address, TIN, exemptions, signature, and date.
3. Reconcile payments. Tie vendor ledger to invoices, checks, ACH, cards, networks, credits, voids, reimbursements, and backup withholding.
4. Apply the 2026 threshold. Use $2,000 for covered payments and test backup-withholding reporting regardless of amount.
5. Review exemptions and exceptions. Apply the corporate rule, legal and medical exceptions, and payment-specific instructions.
6. Complete payer fields. Enter the payer identity and contact details consistently with federal records.
7. Complete recipient and amount fields. Use Form W-9 data, box 1a compensation, backup withholding, and applicable state fields.
8. Run identity and amount review. Compare TIN format, name, address, year, form revision, dollars, state data, and source reconciliation.
9. File and furnish. Use the required electronic or permitted paper channel, meet recipient and agency dates, and save acceptance and delivery evidence.
10. Correct errors formally. Preserve the original, follow the current correction procedure, update the recipient, and fix vendor-master data.

Worked example

A contractor receives $12,600 in 2026: $8,000 by ACH, $3,600 by company credit card, and $1,000 as a reimbursed cost supported under the payment agreement. The payer does not copy $12,600 blindly to Form 1099-NEC. It verifies worker status and Form W-9, reconciles the card portion under payment-settlement rules, evaluates the reimbursement, applies the current threshold, and reports the supported box 1a amount. A reviewer then compares the form, vendor ledger, and filing payload before transmission.

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 an old $600 threshold for 2026. Covered 2026 payments generally use $2,000.
• Choosing 1099 because payroll was skipped. Classification is based on the relationship and applicable tests.
• Copying the vendor display name. Use Form W-9 identity data.
• Counting card payments twice. Separate eligible payment-settlement transactions.
• Suppressing every corporation. Review legal, medical, and other current exceptions.
• Ignoring backup withholding. It can require filing regardless of payment amount.
• Using the prior-year form layout. Use the December 2026 revision and current instructions.
• Treating prepared as filed. Keep transmission, acceptance, recipient delivery, and correction evidence.

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

Vendor control sheet

Track Form W-9, classification, payment category, method, gross total, exclusions, threshold, form, box, state, and reviewer.

TIN review

Resolve missing, invalid, inconsistent, or notice-related identity data before the filing deadline.

Filing status board

Separate drafted, reviewed, approved, transmitted, accepted, recipient delivered, state filed, and corrected.

Next-year cleanup

Update onboarding, payment-method coding, vendor classifications, backup-withholding procedures, and state mapping from current exceptions.

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.