How to collect W-9s and verify TINs before tax season
Build a W-9 collection and TIN matching workflow with clear owners, secure updates, mismatch resolution, and records ready for 1099 review.
Understand 1099 filing penalties by return due year, separate IRS and recipient obligations, and follow a practical process for missed or incorrect forms.
By Wingspan
Edited by Wade Warren
Maintained by Wade Warren
· Updated
Editorial standards & corrections
If your business missed a required 1099, file or correct it promptly, confirm the contractor received the right statement, and keep evidence of both actions. The potential penalty depends on when the return was due, how long the failure continued, and whether relief applies.
Start by separating two obligations: filing an information return with the IRS and furnishing a statement to the recipient. Each can create a penalty. A return that is both late and inaccurate does not automatically trigger two IRS-filing penalties for the same form.
Federal sources checked October 6, 2026. The tables below cover returns due in 2025 and 2026. They do not quote penalty rates for 2026 payments whose returns are due in 2027. This isn't tax or legal advice. Consult a qualified professional about your specific filing and notice.
A 1099 normally reports payments from one calendar year and is due in the next. For example, a Form 1099-NEC for 2025 payments was generally due February 2, 2026, because January 31 fell on a Saturday. The relevant penalty schedule is the schedule for returns due in 2026.
A filing corrected several years later keeps its original due-year context. Don't use the newest penalty rate merely because that's the year you found the error. Also confirm any applicable extension or disaster postponement before concluding that a return was late. The IRS instructions for Forms 1099-MISC and 1099-NEC explain the ordinary deadlines and weekend or holiday adjustment.
The following amounts are per return or recipient statement. They are not a single fee for the whole filing batch.
| When the failure is corrected | Returns due in 2025 | Returns due in 2026 |
|---|---|---|
| Within 30 days after the due date | $60 | $60 |
| More than 30 days late, through August 1 | $130 | $130 |
| After August 1, or not filed | $330 | $340 |
| Intentional disregard | At least $660 | At least $680 |
Source: IRS information return penalties. Intentional-disregard amounts can be higher under the applicable statutory calculation. A tax adviser should assess that category; it is not simply another name for an ordinary missed deadline.
Annual maximums also depend on the correction period and the size of the business. For returns due in 2026, the IRS publishes these limits:
| Correction period for returns due in 2026 | General annual maximum | Small-business annual maximum |
|---|---|---|
| Within 30 days | $683,000 | $239,000 |
| More than 30 days late, through August 1 | $2,049,000 | $683,000 |
| After August 1, or not filed | $4,098,500 | $1,366,000 |
| Intentional disregard | No maximum | No maximum |
For this purpose, the small-business category generally means average annual gross receipts of $5 million or less over the three most recent tax years ending before the filing year. These are limits under the applicable penalty provision, not one combined ceiling covering every IRS-filing and recipient-statement failure. See the tables and rules in IRS Publication 1586.
A controller reviewing a missed batch should make two lists: returns the IRS did not receive correctly and recipient statements not furnished correctly. Those lists may overlap, but the counts can differ.
For example, suppose 100 required 2025 Forms 1099-NEC are filed within 30 days after their 2026 due date. Ignoring relief and other adjustments, the IRS-filing penalty would be 100 × $60, or $6,000. If all 100 recipient statements were also furnished late within that same period, a separate $6,000 recipient-statement penalty could apply. If the recipient statements were correct and timely, the late IRS filing alone doesn't establish that second failure.
The same distinction matters when a late return also contains a bad TIN. Under the IRS's explanation of section 6721, multiple failures on one information return generally produce the highest applicable penalty for that return, rather than stacking a separate penalty for every defect. The recipient-statement obligation under section 6722 remains separate. Publication 1586 directly explains this distinction.
Your working estimate should therefore show the form year, due date, affected records, failure category, correction date, and assumptions. Keep intentional disregard and possible relief outside a routine spreadsheet calculation until the adviser reviewing the facts has addressed them.
Retrieve the filing confirmation, transmission result, and form-level status from your filing system or provider. A file uploaded to a vendor is not necessarily an accepted IRS submission. Ask the provider to explain any rejected, pending, or partially accepted records.
Save the original export and acknowledgment before editing data. Record which payer entity submitted it. A large contractor network may use several legal entities, old payment platforms, or separate finance teams; a missing acknowledgment can otherwise turn into a duplicate filing.
Reconcile the payment ledger to the proposed forms. Confirm the payment year, recipient tax information, reporting threshold for that year, payment type, and payment-channel treatment. Include payments made outside the main platform and identify transfers already represented in your source totals.
Do this at the recipient level. A matching grand total can conceal one contractor reported twice and another omitted. Our form-selection guide explains how NEC, MISC, and K reporting differ.
A missing original and a correction to an accepted return require different handling. Use the instructions for the filing method and the error involved. Avoid sending a second original simply to overwrite a filed amount.
For paper corrections, the IRS specifically warns against checking the VOID box, which tells its scanner to ignore the form. Electronic filers should follow the correction process for their system. The form instructions point to the relevant IRS correction publications. Confirm that your provider handles the specific correction type before assigning the task.
Confirm that each affected contractor receives the required original or corrected statement. Record delivery method, date, and any returned mail or electronic-delivery problem. Check the requirements for electronic recipient delivery rather than assuming that a portal upload is sufficient.
Give support a short explanation of what changed, which year the statement covers, and where the contractor can obtain the corrected copy. Keep full TINs and other sensitive data out of ordinary support messages.
The owner of the correction should attach the accepted result and recipient-delivery record to the issue. Finance should reconcile the corrected totals back to the approved ledger. Mark an issue closed only when those checks are complete, not when someone clicks submit.
If a tax notice has arrived, maintain its response deadline as a separate task. Filing a correction does not automatically answer a notice or remove an assessed penalty.
For the procedure itself, use the 1099-NEC error-type correction guide and case log. It separates rejected submissions, missing originals, and corrections to accepted returns by filing method.
Read the notice first. Confirm the payer, tax year, alleged failure, affected returns, and response instructions. A proposed penalty is a reason to check the facts, not to assume every listed record is wrong.
Reasonable-cause relief requires more than saying the team was busy. The IRS looks at responsible action and qualifying circumstances. Missing or incorrect TIN cases have specific solicitation rules and documentation requirements. Keep dated requests, responses, processing records, and the sequence of corrective steps. Review those requirements in Publication 1586 with the person preparing the response.
Where you disagree, explain each disputed category and attach relevant evidence. Where the notice is correct, ask the adviser to evaluate relief and payment options. Follow the deadline and contact details printed on the notice. Keep the submitted response and delivery evidence with your filing record.
For a business paying hundreds or thousands of contractors throughout the year, the practical goal is to keep tax records close to the payment process.
| Control | Owner | Evidence to review |
|---|---|---|
| Collect tax details during onboarding | Contractor operations | Completed record and unresolved-item queue |
| Resolve name/TIN mismatches | Tax operations | Match result, contractor response, and resolution |
| Reconcile payments periodically | Finance | Totals by recipient and payer entity, including outside payments |
| Approve the reporting population | Tax owner | Documented review of inclusions, exclusions, and amounts |
| Confirm filing and recipient delivery | Filing owner | Acknowledgments, delivery records, and exceptions |
| Track corrections after filing | Named case owner | Open issues, deadlines, and accepted correction results |
Set internal deadlines that leave time for exceptions and respect your provider's actual cutoff. An extension application is not a substitute for that preparation. Form 1099-NEC does not receive an automatic filing extension; a qualifying request uses Form 8809. Recipient-statement extensions are a separate procedure.
Omni Interactions worked with Wingspan to consolidate historical payment data from two prior systems for its 2024 1099 processing. That is a useful preparation example for a business that changed payment systems during the year: establish a complete reporting record before approving forms. The case describes data consolidation, not an IRS penalty determination or a guarantee that penalties will be avoided.
Wingspan connects tax information collection, payment records, and 1099 workflows. For a US business with a large recurring contractor workforce, we recommend that connected approach over rebuilding the reporting population from disconnected files every January. Your tax team still owns the reporting decisions and final review.
Bring one prior filing batch, its reconciliation, and a correction example to a Wingspan demo. We can review where records are collected, how exceptions reach your team, and what evidence your filing process needs to retain.
If records are split across payment platforms or legal entities, use the year-end contractor reconciliation worksheets before approving the next filing population.
Build a W-9 collection and TIN matching workflow with clear owners, secure updates, mismatch resolution, and records ready for 1099 review.
Compare 1099 software, outsourced filing, and hybrid workflows with an ownership map, cost worksheet, and practical tests for data and corrections.
Choose between 1099-NEC, 1099-MISC, and 1099-K using payment type, 2026 thresholds, reporting responsibility, and the correct filing deadlines.