W-9 collection pillar

W-9 vendor readiness checklist: make every record 1099-ready

A vendor record is 1099-ready when five controls are in place: a valid W-9 is on file, the certified federal tax classification is captured, the contact path works, payment context is documented, and every exception has an owner. A valid W-9 or substitute contains the payee's name and TIN and, where certification is required, is signed under penalties of perjury (IRS About Form W-9, IRS Instructions for the Requester of Form W-9). This checklist defines the firm-side record standard and audit workflow. This page explains the rules for firm review workflows. It is not tax or legal advice.

Who this page is for

This is the W-9 collection pillar for bookkeeping firms and accounting teams that manage vendor records across clients. It provides one repeatable definition of readiness and one audit workflow for applying that definition across a vendor list.

The related guides cover individual collection steps, including requesting a W-9, handling a vendor who does not provide one, and determining when a contractor should be routed into the W-9 workflow. This page defines the record standard those steps support.

The record standard: what ready means

1. A valid W-9 is on file.

The IRS describes Form W-9 as the form a payee uses to provide the correct taxpayer identification number to a person required to file an information return (IRS About Form W-9). A valid W-9 or substitute contains the payee's name and TIN and, where certification is required, is signed under penalties of perjury (IRS Instructions for the Requester of Form W-9).

A blank TIN or a missing required certification leaves the request unresolved.

2. The name follows the IRS name rules.

For a sole proprietor, the individual's name appears first and a business or trade name may appear second. A business name alone is insufficient. For a single-member LLC disregarded from its owner, the owner's name appears first, the LLC name appears second, and the record uses the owner's TIN. An LLC treated as a corporation or partnership uses the entity's name and EIN (IRS General Instructions for Certain Information Returns).

Capture these distinctions when the W-9 is reviewed so the vendor record matches the certified payee information.

3. The certified federal tax classification is captured.

The current Instructions for Forms 1099-MISC and 1099-NEC generally exempt payments to corporations, including LLCs treated as C or S corporations, while retaining exceptions for categories such as legal services and medical and health care payments (IRS Instructions for Forms 1099-MISC and 1099-NEC).

The reviewer applies those rules to the federal tax classification certified on the W-9 rather than a suffix in the vendor's display name. A blank classification prevents the record from being mapped to the applicable review rules, so missing classification is a readiness flag.

This checklist captures the classification for qualified review. It does not decide a vendor's filing treatment.

4. The payee is routed to the appropriate tax-document workflow.

Form W-9 is used to request the TIN and certifications of a U.S. person, including a resident alien. The requester instructions direct foreign persons to the appropriate Form W-8 or Form 8233, depending on the circumstances (IRS Instructions for the Requester of Form W-9).

Route foreign payees to the appropriate foreign-payee documentation workflow rather than continuing a W-9 request.

5. The contact path works.

Every record should have a usable contact path for request outreach and follow-up. Documents containing TINs should move through a private upload workflow rather than ordinary email attachments.

Record bounced requests and invalid contact information as open exceptions requiring follow-up.

6. The payment context is documented.

For affected payments made in 2025 and reported in early 2026, the applicable common threshold is $600 under the IRS 2025 Instructions for Forms 1099-MISC and 1099-NEC. For affected payments made in 2026 and reported in early 2027, the Rev. December 2026 IRS instructions, with Public Law 119-21, section 70433 as the statutory basis, set the threshold at $2,000. Separate categories retain their own amounts and rules. The payment year controls.

Payments made by credit card, payment card, or through third-party payment networks are reported by the payment settlement entity rather than the payer on Forms 1099-MISC or 1099-NEC (IRS Instructions for Forms 1099-MISC and 1099-NEC).

The readiness record should preserve payment-year totals and payment methods for qualified review. This checklist does not issue a reportability verdict. The full year-by-year analysis belongs on the 1099 reporting threshold page.

7. Exposure and classification-review flags are visible.

Backup withholding can apply when a payee fails to provide a correct TIN (IRS Backup Withholding). Keep missing-TIN exposure visible for qualified review without stating a withholding rate on this page.

If the account later appears on an IRS name and TIN mismatch notice, use the CP2100 and B-notice guide for the response sequence.

A worker whose classification remains unsettled should move to the firm's worker-classification review before the vendor collection workflow is completed.

8. Every exception has an owner and status.

Bounced requests, incomplete forms, name and TIN mismatches, likely duplicate records, and unclear classifications should each have an owner and a current status. This is an operational control for the firm, not a W9Finder capability claim.

The audit workflow

  1. Import or pull the vendor list for one client. Resolve likely duplicate records first so the audit counts distinct vendors.
  2. Review each record for W-9 status, applicable name rules, federal tax classification, U.S.-person routing, contact path, payment context, and exposure flags.
  3. Send private W-9 requests for missing records and track delivered, bounced, submitted, canceled, and needs-review states. Record request dates.
  4. Review each submission against the full record standard. Return incomplete or inconsistent submissions for correction while the vendor is still reachable.
  5. Separate approved records from open exceptions. Send the approved set to the firm's year-end workflow and retain the exception list with owners and statuses until resolved.

When to run the checklist

Run the checklist at four points:

  • during vendor onboarding
  • after a vendor import or client handoff
  • at a mid-year checkpoint
  • before the filing-season handoff

These checkpoints surface missing records while the firm still has time to complete outreach and review.

Readiness at a glance

Area Ready state Why it matters
W-9 on file Name and TIN are present, with certification signed where required Establishes the IRS-defined record foundation
Name rules Sole proprietor and LLC names follow the applicable IRS instructions Keeps the record aligned with the certified payee identity
Federal tax classification Classification is captured from the W-9 Gives qualified reviewers the classification needed to apply reporting rules
Payee routing U.S. persons use the W-9 workflow and foreign payees are routed appropriately Keeps the request in the correct tax-document workflow
Contact path A usable request path exists and documents move through private upload Supports secure collection and follow-up
Payment context Payment year, totals, and payment methods are documented Preserves the facts needed for year-specific review
Exposure flags Missing-TIN and worker-classification questions remain visible Routes unresolved issues to qualified review
Exceptions Every open item has an owner and status Prevents unresolved records from entering the approved handoff

This checklist, as software

W9Finder applies this workflow across client vendor lists: import a CSV per client; flag missing W-9s, missing email, incomplete legal names or addresses, missing TINs, missing tax classifications, and likely duplicates; send private upload links with reminders tracked in-app; review and approve submissions; and export a reviewed, 1099-ready vendor file while unresolved exceptions remain visible for review.

W9Finder does not file information returns, perform IRS TIN Matching, collect W-8 forms, connect directly to QuickBooks or Xero, or decide reportability.

Explore W9Finder

Free QA tool

Scan your vendor list for W-9 gaps

Run a vendor CSV through the scanner to surface missing W-9 status, missing tax classifications, and likely duplicates. TIN-like values are reduced to last4 in scanner output.

Scanner output

Missing W-9s Flagged
Missing tax classifications Flagged
Duplicate vendors Checked
TIN-like values Masked

FAQ

What makes a W-9 valid?

A valid W-9 or substitute contains the payee's name and TIN and, where certification is required, is signed under penalties of perjury (https://www.irs.gov/pub/irs-pdf/iw9.pdf). The name also follows the applicable IRS rules for sole proprietors and LLCs (https://www.irs.gov/instructions/i1099gi).

Should vendors send W-9s by email?

Use a private request-and-upload workflow for documents that may contain SSNs or EINs. Ordinary email attachments place full TINs in working inboxes and make access harder to control.

Does this checklist decide 1099 filing treatment?

No. The checklist prepares the records that qualified reviewers use when applying the payment year's rules and the payee's certified federal tax classification. The who-gets-a-1099 guide and reporting-threshold page provide the related rule framework.

How often should firms run the checklist?

Run it during vendor onboarding, after vendor imports or client handoffs, at a mid-year checkpoint, and before the filing-season handoff.

Related W9Finder resources

Sources