FREE2026 AP Automation Software Comparison|Independent, data-backed — no sales callGet the PDF →

Spotsaas logo
Free PDF · AP Automation

Vendor Onboarding & W-9 Checklist

A controls-first checklist for onboarding new suppliers cleanly — collecting tax documentation, validating banking details against fraud, and setting up the vendor master so that downstream matching, payments, and 1099 reporting just work.

  • Tax & Legal Documentation
  • Required Fields by Vendor Type
  • Banking & Fraud Verification
  • Onboarding Decisions to Get Right
★★★★★Trusted by 3,000+ buyers· built from 38 AP automation software tools· independent
PDF · FreeVendor Onboarding & W-9 Checklist

Where should we send it? Free · arrives in seconds · no spam.

We email it to you — one-click unsubscribe anytime.

  1. 1Tell us where to send it

    Your name and work email — nothing more.

  2. 2Check your inbox

    Your checklist arrives in seconds, not days.

  3. 3Use it with your team

    Editable and ready to share — make it your own.

A peek inside

See exactly what you're getting

Free PDF
Spotsaas · 2026
Vendor Onboarding & W-9 Checklist
Tax & Legal Documentation
Required Fields by Vendor Type
Banking & Fraud Verification
Onboarding Decisions to Get Right
Get the checklist

What it is

The Vendor Onboarding & W-9 Checklist is a controls-first guide to bringing new suppliers into your vendor master cleanly — collecting the right tax documentation, validating banking details against fraud, and setting up the record so that downstream three-way matching, payments, and 1099 reporting just work. It covers the tax and legal documentation you collect before the first payment (W-9 for domestic vendors, W-8BEN or W-8BEN-E for foreign ones), the exact legal name and TIN as they appear on the IRS record, TIN matching to confirm name and TIN agree, tax entity classification to drive 1099 eligibility, and a required-fields table that differs for domestic versus foreign vendors.

Beyond tax setup, the checklist treats banking and fraud verification as a three-step workflow: collect bank details securely through a vendor portal (never over email), require a voided check or bank letter as evidence, then independently verify by calling the vendor back on a known number — not one from the request email — and confirming account ownership via micro-deposit or a validation service before the first ACH. Finally, it activates the vendor under segregation of duties, with vendor master and bank-detail changes routed through dual approval and every field change logged to an immutable audit trail. A short Q&A section answers the decisions teams most often get wrong.

The unifying idea is that the vendor master is the foundation every downstream control rests on. A clean legal name and validated TIN make year-end 1099s painless; verified banking stops payment fraud, particularly business email compromise; and de-duplication on normalized name, TIN, and bank account keeps three-way match honest and prevents duplicate payments. Five minutes of discipline at onboarding saves hours of cleanup at month-end and year-end, and the checklist is structured so a small team can apply it consistently whether onboarding manually or through a platform like Tipalti that automates W-9 collection and validation.

What it's used for

The checklist is used every time a new supplier needs to be set up to be paid, and whenever an organization tightens its vendor master controls after a fraud scare, a duplicate-payment incident, or a messy year-end 1099 scramble. It is built to make onboarding both fast and safe — collecting what year-end and matching will require, while closing the door on payment fraud at the point of entry.

  • Collecting a current W-9 (or W-8BEN / W-8BEN-E for foreign vendors) before the first payment, and capturing the exact legal name and TIN as they appear on the IRS record, separate from any DBA or trade name.
  • Running TIN matching against the IRS service to confirm name and TIN agree before activation, so a mismatch doesn't surface as a CP2100 B-notice at year-end.
  • Classifying the vendor's tax entity type and flagging 1099 reportability and the default box at onboarding, so December isn't a frantic data hunt.
  • Collecting bank details securely through a portal with a voided check or bank letter as evidence — never over email or an emailed attachment.
  • Independently verifying banking via call-back on a known number and confirming account ownership through micro-deposit or a validation service before the first ACH payment.
  • Applying segregation of duties and dual approval so the person entering a vendor cannot also approve and pay it, and bank-detail changes require a second approver.
  • De-duplicating on normalized name, TIN, and bank account so the same supplier can't be created twice and paid from two records.

Who uses it

The checklist is for the people who create and guard vendor records and for those who depend on those records being clean — AP, controllership, tax, and the auditors who test the controls. Because bank-detail changes are the top fraud vector, it deliberately separates the roles that request, verify, and approve a vendor.

AP Specialist / Vendor Master AnalystCreates and maintains vendor records and applies the documentation, TIN-match, and de-duplication steps so downstream matching and 1099s work.
ControllerOwns the control environment around the vendor master and enforces dual approval on bank-detail changes and segregation between setup and payment.
Tax / Compliance LeadCares that W-9s, entity classification, and 1099 reportability are captured correctly at onboarding so year-end filing is reconciliation, not a scramble.
ProcurementInitiates new supplier relationships and needs to route them through onboarding so a vendor isn't paid before tax and banking verification are complete.
Internal AuditorTests whether bank changes require independent verification and dual approval and whether every field change is logged — the checklist maps to that evidence.

Context & good to know

The vendor master is the quiet center of accounts payable risk. Almost every expensive AP failure traces back to a bad record: a duplicate vendor that enables a duplicate payment, a missing W-9 that forces backup withholding, or — most costly of all — a fraudulent bank-detail change that sends a payment to a criminal. Business email compromise, in which a spoofed email changes a vendor's banking, is consistently among the largest sources of AP loss, and the single highest-ROI defense is independent call-back verification on every bank-detail change. The checklist puts that control at onboarding and at every later change.

Year-end 1099 pain is almost always created during onboarding, not in January. A vendor paid without a W-9, or with a legal name and TIN that don't match the IRS record, becomes a CP2100 B-notice and potential 24% backup withholding months later. By collecting and TIN-matching the W-9 before the first payment, classifying the entity type, and flagging 1099 reportability and the default box up front, the checklist turns year-end into a reconciliation exercise. This is why onboarding discipline and the separate 1099 prep checklist are two halves of the same control.

De-duplication is the unglamorous step that protects everything downstream. When the same supplier exists under two records — 'Acme Inc.' and 'Acme, Inc.' with different vendor IDs — spend is split, three-way match breaks, and duplicate payments slip through. Matching on normalized name, TIN, and bank account before creating a new record keeps the master clean and the matching control honest. Many AP automation platforms, including Tipalti and AvidXchange, surface potential duplicates and automate W-9 collection and TIN matching, but the policy for what to verify and who can approve still has to be designed.

For teams evaluating AP software, vendor onboarding is a revealing lens, because it exposes whether a platform treats the vendor master as a controlled, auditable asset. Buyers asking 'what is the most reliable AP software?' should test whether a tool offers a secure vendor portal, automated W-9 and W-8 collection, IRS TIN matching, OFAC sanctions screening, duplicate detection, and dual-approval workflows on bank-detail changes. A platform like Tipalti markets supplier onboarding and tax-form collection as a core capability precisely because clean onboarding is what makes everything downstream — matching, payments, and 1099s — reliable.

✓ Independent · vendors can't pay to rank

Built on verified data, not vendor spin

Every Spotsaas resource draws on the Spotsaas Score — a blend of verified review ratings, review volume, and feature depth across 38 AP automation software tools. Refreshed regularly; data as of June 2026.

FAQ

Questions, answered

Why do I need a W-9 before paying a new vendor?

Because a missing or mismatched TIN at year-end can force backup withholding at 24% and trigger IRS penalties. Collecting a signed W-9 (or W-8BEN/W-8BEN-E for foreign payees) before the first payment lets you capture the exact legal name and TIN, run TIN matching, and flag 1099 reportability up front. Paying first and chasing the form later is how teams end up with a frantic, error-prone year-end.

What is TIN matching and why does it matter?

TIN matching checks the vendor's legal name and taxpayer identification number against the IRS TIN Matching service to confirm they agree before you activate the vendor. A mismatch that isn't caught at onboarding resurfaces as a CP2100 B-notice and possible backup withholding at year-end. Resolving mismatches with a fresh W-9 and re-running the match before the first payment is far cheaper than fixing it after 1099s are issued.

How do I verify a vendor's bank details safely?

Collect them through a secure vendor portal, never over email, and require a voided check or bank letter as evidence. Then independently verify: call the vendor back on a phone number you sourced yourself — not one from the request email — and confirm account ownership via micro-deposit or a validation service before the first ACH. Treat every later bank-change request as a fresh, high-risk verification event.

What's the difference between onboarding a domestic and a foreign vendor?

Domestic vendors provide a W-9 with an EIN or SSN validated via TIN match, are paid by ACH or check, and may be 1099-reportable. Foreign vendors provide a W-8BEN or W-8BEN-E, generally have no US TIN, are usually reported on 1042-S rather than 1099, are paid by SWIFT/IBAN in the relevant currency, and are subject to treaty withholding rates or a 30% default. Both require OFAC sanctions screening.

How do I prevent duplicate vendor records?

De-duplicate on normalized name, TIN, and bank account before creating any new master record. Duplicates split spend, break three-way match, and enable duplicate payments — for example, the same supplier set up as 'Acme Inc.' and 'Acme, Inc.' Many AP platforms flag potential duplicates automatically, but you still need a rule that the system checks those keys before a new vendor goes live.

Who should be allowed to change vendor bank details?

Edit rights should be restricted to a small, named group, every change should require independent call-back verification, and a second approver should release the change before it goes live. Bank-detail changes are the number-one vector for business email compromise, so dual approval plus independent verification is the control that stops the most expensive fraud. Every change should be logged with requestor, verifier, and approver.

What is OFAC screening and do I need it?

OFAC screening checks a vendor against the US Treasury's Specially Designated Nationals (SDN) list and other denied-party lists to ensure you're not paying a sanctioned entity. It's required for both domestic and foreign vendors at onboarding, with foreign vendors also checked against broader denied-party lists. Many AP automation platforms run this screen automatically; if you onboard manually, it needs to be an explicit step before activation.

How does clean onboarding help month-end and year-end?

A clean legal name and validated TIN make 1099 filing a reconciliation rather than a data hunt; verified banking prevents fraudulent payments that would have to be investigated; and a de-duplicated master keeps three-way match and the AP subledger accurate. The discipline you apply in five minutes at onboarding removes hours of cleanup at month-end close and year-end 1099 prep.

Should procurement or AP own vendor onboarding?

Procurement typically initiates the relationship, but AP or a dedicated vendor master function should own the controlled setup — tax documentation, TIN match, banking verification, and de-duplication — under segregation of duties. The key rule is that the person entering a vendor cannot also approve and pay it. Many organizations route new vendors through a portal so procurement initiates and AP verifies, keeping the roles separate.

Can AP automation software handle vendor onboarding?

Yes. Platforms like Tipalti and AvidXchange offer secure supplier portals that collect W-9/W-8 forms, run IRS TIN matching, screen against OFAC lists, detect duplicate records, and enforce dual approval on bank-detail changes. They automate much of the manual work, but you still design the policy — what to verify, who can approve, and what blocks a payment. The checklist is the requirements spec the platform should be configured to enforce.

Grow your pipeline with buyers who are already looking for you

254,000+ buyers use Spotsaas every month to evaluate and shortlist software. Get in front of them — for free, or with a managed growth plan built around your category.