W-9 Missing: What to Do When a Vendor Won't Respond to Your Request
A vendor who won't return a W-9 isn't just an administrative nuisance — it's an active compliance risk. Without certified taxpayer documentation, your organization faces incorrect 1099 filings, CP2100 mismatch notices, and potential backup withholding liability at 24%. The solution isn't to chase vendors indefinitely with informal emails — it's a structured outreach and escalation process that documents every step, applies real consequences for non-response, and validates the W-9 against IRS records once it finally arrives.
Why a Missing W-9 Is a Compliance Problem, Not Just an Admin Problem
Form W-9 is how a vendor certifies their legal name, tax classification, and TIN under penalty of perjury. That certification is the foundation of the 1099 filing for that vendor. Without it, your organization is filing based on unverified data — which means any mismatch between what's in your ERP and what the IRS has on file is your problem, not the vendor's.
- Missing TIN filing — the 1099 is incomplete and creates immediate IRS exposure
- CP2100 mismatch notice — if you file with unverified data that doesn't match IRS records
- B-Notice compliance requirements — triggered by the CP2100
- 972CG penalty assessment — if mismatches are unresolved at penalty assessment
- Backup withholding liability — if vendor refuses to provide valid taxpayer information
- Audit exposure — if documentation is absent during an IRS compliance review
The IRS doesn't accept "the vendor didn't respond" as a defense for incorrect or missing TIN filings. What it does accept is documented proof that you made a good-faith effort to obtain the information — which is exactly what a structured outreach process produces.
Why Vendors Don't Respond to W-9 Requests
Understanding the actual reasons for non-response makes outreach more effective. Most non-responding vendors aren't deliberately obstinate — they're one of these:
| Non-Response Reason | What Actually Helps |
|---|---|
| Request felt low-priority | Clear deadline and stated consequences in the initial request |
| Don't understand why it's required | Brief, plain-language explanation of the IRS requirement |
| Concerned about sharing SSN | Explanation that W-9 is not submitted to the IRS — it stays with the payer |
| Contact information is outdated | Verify through procurement or AP before sending any requests |
| Believe they're exempt | Ask them to confirm exemption code on a completed W-9 — not just claim verbal exemption |
| No longer actively engaged | Evaluate whether the vendor should be deactivated vs. pursued for documentation |
A W-9 request that explains why the form is needed, what the deadline is, and what happens if they don't respond gets a materially higher response rate than a generic request with a blank form attached.
Step-by-Step: What to Do When a Vendor Won't Respond
Step 1 — Confirm the Vendor Is Actually Reportable
Before escalating, confirm whether the vendor has a W-9 requirement. Review payment type (services vs. goods), total payment amount for the filing year, tax classification if known, and any potential exemptions.
Not every vendor requires a 1099 — but best practice is to maintain W-9 documentation for any vendor paid for services, regardless of threshold, because payment totals can change and a W-9 collected during onboarding is always easier than collecting one during year-end cleanup.
Step 2 — Verify Vendor Contact Information Before Sending More Requests
Before sending additional outreach, confirm the contact information in your system is current. Outdated email addresses, incorrect AP contacts, and old phone numbers are among the most common reasons W-9 requests go unanswered — the request simply never reached anyone.
Check with procurement, the vendor relationship owner, or use public EIN lookup tools to find current contact information before continuing the outreach cycle.
Step 3 — Send a Request With a Clear Deadline and Stated Consequences
A W-9 request that explains the requirement, sets a firm deadline, and states what happens if the deadline is missed gets results that a generic request does not.
- Why the W-9 is required (IRS information return reporting requirement)
- That the W-9 is kept on file by the payer — not submitted to the IRS
- The specific deadline for response
- That payment may be placed on hold pending receipt of the form
- That the IRS may require backup withholding (24%) on future payments if no valid TIN is provided
- Clear instructions for completing and returning the form
- A contact for questions
Vendors who understand the IRS requirement, know the deadline, and know a payment hold is coming respond significantly faster than vendors who receive a blank form with no context.
Step 4 — Follow a Structured Reminder and Escalation Cadence
A single request is not sufficient. The IRS expects documented, repeated outreach — not one email that went unanswered. The outreach cadence should be pre-defined, consistently applied, and logged automatically or manually with timestamps.
| Day | Action |
|---|---|
| Day 0 | Initial W-9 request — clear deadline, stated consequences, complete instructions |
| Day 7 | First reminder — reference original request, restate deadline |
| Day 14 | Second reminder — flag urgency, confirm payment hold is approaching |
| Day 21 | Final notice — deadline stated explicitly; payment hold or backup withholding will apply |
| Day 22+ | Payment hold applied and/or backup withholding initiated; procurement or management escalation triggered |
The documentation of this cadence — dates sent, what was communicated, vendor response status — is what supports reasonable-cause penalty abatement if a mismatch or missing TIN notice arrives despite good-faith outreach.
Step 5 — Log Every Outreach Attempt
Every contact attempt must be documented for IRS compliance purposes. Verbal conversations don't count. What counts is a retrievable record with timestamps.
Required log fields per outreach attempt:
- Vendor name and ID
- Date and time of outreach
- Contact method (email, phone, mail)
- Recipient name and address/email
- Summary or copy of the message sent
- Vendor response status
- Follow-up action scheduled
Step 6 — Apply a Payment Hold for Non-Responsive Vendors
If the outreach cadence completes without a response, a payment hold is the most effective next step. It communicates urgency in a way that reminder emails often don't, and it protects your organization from continuing to pay a vendor without required documentation.
Payment hold options:
- Block new invoice approvals until W-9 is received
- Hold pending payments pending W-9 receipt
- Require W-9 submission before the vendor record is reactivated
Coordinate with procurement or the vendor relationship owner when a payment hold is applied to a strategic vendor — the goal is W-9 collection, not relationship damage.
Step 7 — Apply Backup Withholding When Required
If a vendor fails to provide a valid TIN after documented outreach, IRS rules may require backup withholding at 24% on applicable payments. This is not optional — it is an IRS enforcement mechanism, and failure to apply it when required is its own compliance exposure.
Backup withholding documentation must include:
- The date withholding began and the triggering reason
- The vendor's non-response history
- Amounts withheld per payment
- IRS remittance records
- The date withholding ends (when valid TIN is finally confirmed)
Step 8 — Validate the W-9 When It Finally Arrives
When the vendor submits a W-9, don't file it and move on — validate it. A W-9 is the vendor's attestation that their information is correct, but vendors regularly submit incorrect TINs, DBAs instead of legal names, and outdated entity information in good faith.
Validation steps on receipt:
- Confirm the form is complete — all required fields, including signature and date
- Confirm the legal name is from Line 1 — not Line 2 (DBA)
- Confirm TIN type is consistent with entity structure
- Run IRS TIN matching on the name + TIN combination
- If matching confirms a match — update the vendor master and store the W-9
- If matching returns a mismatch — contact the vendor with specific correction detail and revalidate
A W-9 that arrives but still fails TIN matching is a problem — just a documented, correctable one.
Step 9 — Reassess the Vendor Relationship if Non-Response Persists
A vendor who repeatedly refuses to provide required IRS documentation despite documented outreach, payment holds, and backup withholding application presents risk beyond tax reporting. Consider:
- Formal vendor termination for non-compliance
- Transition to an alternative supplier
- Escalation to legal or procurement leadership
- Enhanced monitoring and controls if the relationship must continue
Vendors who won't provide a W-9 may also present fraud, sanctions, or identity verification risks worth examining separately.
Common Mistakes With Missing W-9 Vendors
| Mistake | Why It's a Problem |
|---|---|
| Paying without any taxpayer documentation | Direct backup withholding and penalty exposure |
| Assuming vendor is exempt without confirming | Unconfirmed exemptions offer no audit protection |
| Sending one email and stopping | IRS expects documented, repeated outreach |
| Filing 1099s with missing or placeholder TINs | Triggers CP2100 notices and penalty assessment |
| Waiting until January to collect W-9s | Vendor response time creates a filing deadline crisis |
| Not validating the W-9 after receipt | Vendors sometimes submit incorrect information in good faith |
| Storing outreach records in email inboxes | Not audit-ready — can't be retrieved under deadline |
Best Practices
- Require W-9 as a hard gate before vendor activation — no W-9, no vendor record
- Require W-9 before payment approval — no W-9, no payment
- Send W-9 requests with clear deadlines and stated consequences — not generic form requests
- Follow a structured reminder cadence and document every attempt
- Verify contact information before starting outreach for non-responsive vendors
- Apply payment holds for vendors who don't respond by Day 21
- Apply backup withholding when the IRS requirement applies — document it
- Validate every received W-9 via IRS TIN matching before updating the vendor master
- Store all W-9s and outreach records centrally, linked to the vendor record
- Run annual Q4 bulk W-9 validation — catch stale and missing documentation before filing season
Missing W-9 Response Checklist
- Vendor confirmed as 1099-reportable or W-9-required
- Vendor contact information verified and current
- Initial W-9 request sent with deadline and stated consequences
- Reminder sent at Day 7 — logged with date and content
- Reminder sent at Day 14 — urgency flagged; payment hold referenced
- Final notice sent at Day 21 — deadline explicit; payment hold imminent
- All outreach attempts logged: date, method, recipient, message, response status
- Payment hold applied for non-responsive vendors after Day 21
- Backup withholding applied and documented when IRS requirement is triggered
- W-9 validated via IRS TIN matching upon receipt
- Corrected W-9 requested if TIN matching returns a mismatch
- Confirmed-match W-9 stored centrally and linked to vendor record
- Vendor master updated and documentation retained for audit
Frequently Asked Questions
What if a vendor refuses to provide a W-9?
Document the refusal and follow your organization's escalation policy. IRS rules allow — and in many cases require — applying backup withholding (24%) on payments to vendors who refuse to provide valid taxpayer information. A payment hold is also appropriate. Document both the refusal and your organization's response at every step.
Can a 1099 be filed without a W-9?
A 1099 may still be required if payments were made — filing obligations don't disappear because documentation is missing. But filing without a valid TIN produces a missing-TIN return that increases mismatch and penalty exposure. The W-9 is what establishes the certified basis for what you file.
What is the IRS backup withholding rate?
The current rate is 24%. Backup withholding applies on applicable payments when a vendor fails to provide a valid TIN after required outreach.
Does one outreach email satisfy the IRS good-faith documentation requirement?
No. The IRS expects documented, repeated outreach. A single request that went unanswered is not sufficient to support reasonable-cause abatement. A structured, timestamped cadence — initial request, multiple reminders, final notice — is what constitutes good-faith documented effort.
How do I prove vendor outreach during an IRS audit?
With a centralized compliance log containing copies of all outreach emails, reminder timestamps, proof of mailing for any physical correspondence, and internal notes documenting dates, escalation steps, and vendor response status. Email inbox records alone are typically not sufficient — they're not organized by vendor, not easily retrievable under deadline, and not structured for audit presentation.
Conclusion
A missing W-9 is a solvable compliance problem when it's treated like one. Confirm the vendor is reportable, verify their contact information, send a request with a clear deadline and stated consequences, follow a documented reminder cadence, apply a payment hold when the deadline passes, apply backup withholding when the IRS requirement is triggered, and validate the W-9 against IRS records the moment it arrives. Every step documented. Every outreach timestamped. Every result stored centrally. That's the process that prevents a missing W-9 from becoming a CP2100 notice, a 972CG penalty, or an audit finding.
Automate W-9 Collection and Outreach with TIN Comply
Vendors receive a clean, structured W-9 request with a deadline. Reminders go out automatically on schedule. Completed W-9s are validated via IRS TIN matching before updating the vendor master. And every outreach attempt, validation result, and W-9 document is retained in a centralized, audit-ready record — so you're prepared for whatever comes next.
- Automated W-9 request workflows with deadline-driven reminder scheduling
- Real-time IRS TIN/Name matching on every received W-9
- Centralized outreach log with timestamps — audit-ready from day one
- Bulk W-9 status tracking across your full vendor list
- Sanctions screening across 250+ OFAC and global watchlists
- API integration with SAP, Oracle, Workday, NetSuite, and more