 |
The IOFM PodcastAuthor: IOFM
The IOFM Podcast is the leading on-the-go resource for the latest news, skill-sharpeners and strategies in the world of Accounts Payable and Procure-to-Pay. Tune in for interviews and insights from top AP professionals and thought leaders as they dig in to what's new in automation, tax and regulatory compliance, and industry benchmarks, plus hear case studies and listen in on Q&A with experts helping your peers in AP solve their toughest challenges. This podcast is presented by IOFM, the leading provider of training, education and certification programs specifically for Accounts Payable, Procure-to-Pay, Global and Shared Services professionals as well as Controllers and their F&A teams. Learn more at www.iofm.com Language: en Genres: Business Contact email: Get it Feed URL: Get it iTunes ID: Get it |
Listen Now...
W-9 Collection: Five Bad Habits Putting Your Vendor Data at Risk
Tuesday, 16 June, 2026
In this episode of The IOFM Podcast, Debra Richardson joins host Grace Berube to discuss the year-round importance of W-9 collection and what a new IRS draft form could mean for AP teams. The key change in the draft: sole proprietors, who previously could supply either a Social Security Number or an EIN, would now be required to provide only an SSN — potentially triggering a mass recollection effort from existing vendors. With sensitive data like SSNs on the line, Debra walks through five common but risky habits AP teams fall into when collecting W-9s, from using unsecured email to routing documents through internal team members, and explains why each one creates real exposure to fraud and data breaches. What you'll learn in this episode When and why you need to collect a new W-9 The key difference in the draft W-9: Why the IRS's new SSN requirement for sole proprietors is a bigger deal than a typical form revision Why collecting W-9s over standard email is risky — including identity spoofing, misdirected messages, and more How a mass email outreach can go badly wrong — specifically, the CC vs. BCC mistake Why routing vendor documents through internal team members is a security risk and what to do instead
