Payroll & 1099
How to Report 1099 Payments
Reporting 1099 payments is a payer workflow, not a year-end export. The correct result depends on worker status, W-9 identity, payment purpose and method, current thresholds, form boxes, states, recipient delivery, and IRS acceptance.
For payments made in 2026, covered nonemployee compensation generally uses a $2,000 Form 1099-NEC threshold, while backup withholding can trigger reporting regardless of the payment total. Report business payments, not personal payments. Confirm that the recipient is not an employee, validate the signed W-9, review corporation exemptions and exceptions, separate card and qualifying third-party network transactions, and map each included amount to the correct form and box. The aggregate electronic-filing threshold is 10 information returns. Reconcile the form population to the ledger, review state duties separately, furnish recipients, transmit through IRIS or another approved method, and resolve every reject.
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
Status controls the form
Employee wages belong on Form W-2, not Form 1099-NEC.
The payment year controls
Use the form revision and reporting threshold for the year paid.
W-9 controls identity
Match legal name, TIN, classification, address, and exemptions.
Purpose controls the box
Services, rent, medical payments, and attorney payments can follow different rules.
Method controls inclusion
Qualifying card and settlement-network payments are generally reported by the settlement entity.
Corporation exceptions matter
Medical and legal payments can remain reportable.
States are separate
Federal acceptance does not prove state compliance.
Acceptance closes the filing
A submitted return can still be rejected.
Step-by-step workflow
- Classify workers and vendors. Document employee versus contractor status and vendor entity type.
- Collect valid W-9s. Resolve missing names, TINs, classifications, and exemptions.
- Close payment activity. Post invoices, checks, ACH, cards, voids, refunds, and reimbursements.
- Build the reportable population. Review service, rent, medical, legal, and other accounts.
- Separate payment channels. Remove qualifying card and third-party settlement activity from payer-reported totals.
- Apply current rules. Use 2026 forms, thresholds, boxes, withholding, and exceptions.
- Reconcile totals. Tie recipients, forms, boxes, withholding, and states to the ledger.
- Review and transmit. Use IRIS or an approved provider and save transmission records.
- Furnish and file states. Deliver recipient statements securely and complete each jurisdiction.
- Resolve and retain. Correct rejects and archive source, approval, acceptance, delivery, and corrections.
Worked example
A consulting firm pays an independent designer $11,000 by ACH and $3,400 by company card in 2026. The firm validates classification and the W-9, reconciles both payment channels, and reports the covered ACH amount on Form 1099-NEC. It excludes the qualifying card settlement from its payer total because the settlement entity handles Form 1099-K reporting. The firm saves IRIS acceptance, recipient delivery, and its state review.
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
- Reporting vendor balances. Use payment transactions, not ending payables.
- Applying the old $600 threshold. Use the 2026 $2,000 threshold and current exceptions.
- Including card payments twice. Reconcile payment settlement channels.
- Using a trade name as identity. Follow the signed W-9.
- Treating all corporations as exempt. Review legal, medical, and other exceptions.
- Filing before the books close. Post voids, corrections, and late activity.
- Ignoring state reporting. Confirm every jurisdiction.
- Treating submission as acceptance. Resolve all rejected records.
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 readiness list
Track W-9, classification, payment channels, exceptions, states, owner, and resolution.
Box mapping
Document form, box, threshold, method exclusion, corporation rule, and source.
Control totals
Reconcile ledger payments to forms, exclusions, withholding, and accepted totals.
Correction register
Link the original record, error, source fix, correction, delivery, and acceptance.
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.
Frequently asked questions
What is the 2026 Form 1099-NEC threshold?
Covered nonemployee compensation generally uses a $2,000 threshold, with exceptions such as backup withholding.
Do I report card payments?
Generally not when a payment settlement entity reports qualifying transactions under Form 1099-K rules.
Do payments to corporations require a 1099?
Many do not, but legal, medical, and other specific payments can remain reportable.
Can I file Forms 1099 free?
The IRS IRIS Taxpayer Portal provides a no-cost electronic filing option.
Do I file state copies too?
Possibly. State filing, withholding, and recipient-copy rules need a separate review.
What evidence should I keep?
Keep W-9s, payment detail, mapping, forms, acceptance, recipient delivery, states, and corrections.
Turn this guide into action