Checklist
Vendor onboarding checklist: 10 steps for small and mid-size companies
Vendor onboarding is everything between "we chose this supplier" and "they are delivering and getting paid correctly": approve the request, check the vendor, sign the contract, set up tax and bank details with call-back verification, grant access, kick off, check the first invoice and review at 30 and 90 days. Below is the full checklist with an owner for each step, typical timelines and a CSV you can copy into Excel or Google Sheets.
Updated November 17, 2026 ยท 11 min read
Download the checklist (CSV) 30 tasks with owners and timing, opens in Excel and Google Sheets
Key takeaways
- Scale the effort to the risk. A caterer needs a tax form and verified bank details; a payroll provider or anyone touching customer data needs the full list.
- The single most important control is the call-back: confirm bank details by phone on a number you found yourself, and repeat it for every bank change.
- Split duties even in a small team: the person who enters bank details should not be the one who releases payments.
- Typical timing: 1 to 3 days for a low-risk vendor, 1 to 2 weeks for medium risk, 3 to 6 weeks when security review and legal negotiation are involved.
- Onboarding is not finished at the first payment. The first-invoice check and the 30- and 90-day reviews catch most problems early.
The vendor onboarding process at a glance
Most vendor onboarding guides are written for enterprise procurement teams with a supplier portal and a dedicated compliance function. If you are a 10- to 500-person company, the same risks apply (fake vendors, diverted payments, data leaks, invoices that do not match the quote) but one person may own three steps. This checklist assumes exactly that.
| # | Step | Owner | Output |
|---|---|---|---|
| 1 | Request and approval | Requester, budget owner | Approved need with budget |
| 2 | Risk tier | Procurement or ops lead | Low, medium or high |
| 3 | Due diligence | Ops lead, IT for security | Verified, screened vendor |
| 4 | Contract, NDA, DPA | Founder or legal | Signed agreement, insurance certificates |
| 5 | Tax and bank setup with call-back | Finance / accounts payable, second approver | Verified tax ID and bank details |
| 6 | Vendor record and approved list | Finance, ops lead | Vendor live in accounting and on the AVL |
| 7 | System access | IT | Named, least-privilege accounts |
| 8 | Kickoff | Business owner | Shared scope, contacts, invoicing rules |
| 9 | First-invoice check | Finance, business owner | Invoice matched to contract |
| 10 | 30- and 90-day review | Business owner | Keep, improve or replace decision |
Step 1: Request and approve the purchase
Onboarding starts before you talk to the vendor. The person who needs the service writes down, in a few lines, what problem it solves, the scope, the budget and the deadline, and the budget owner approves it.
- Check whether you already pay a vendor who does this. Duplicate vendors for the same service are a common source of wasted spend.
- Check the offers you already have. If your team files cold pitches somewhere shared (for example by forwarding them to save@pitchbin.com, which files the vendor, service and quoted price in your company catalog), you may already hold three priced options.
- If you are still choosing between vendors, finish that first: see the vendor selection process and vendor evaluation criteria.
Step 2: Assign a risk tier
A risk tier decides how much of the rest of the checklist applies. Three tiers are enough for most small and mid-size companies.
| Tier | Typical vendors | Required checks |
|---|---|---|
| Low | Catering, printing, one-off small purchases; no data, no site access | Registry check, tax form, verified bank details, simple order or invoice terms |
| Medium | Agencies, consultants, recruiters, on-site contractors | Low tier plus references, sanctions screening, written contract, NDA, insurance certificates |
| High | Software holding your data, payroll, IT providers with admin access, critical single-source suppliers | Medium tier plus security review (SOC 2 or ISO 27001), data processing agreement, financial stability check, exit plan |
Step 3: Due diligence
Confirm the vendor is who they say they are, and that nothing in their background should stop you.
- Legal entity: look the company up in the official registry (in the UK, Companies House; in the US, the state's business entity search) and confirm it is active and the name matches exactly.
- Consistency: website, email domain, address and phone number should all point to the same company.
- Sanctions: screen the company and, for medium and high tiers, its owners.
- References: call one, and ask what went wrong, not just whether they were happy.
- Security (high tier): review a SOC 2 Type II report or ISO 27001 certificate with scope, or a short security questionnaire.
- Financial stability (critical suppliers): recent accounts or a credit check, so you are not dependent on a supplier about to fail.
The full set of checks, with what to do for each red flag, is in the vendor due diligence checklist. For a quick read on whether a company or cold email is genuine, see how to verify a vendor.
Step 4: Contract, NDA and data processing agreement
- Contract: a master services agreement plus a statement of work, or the vendor's order form after you have read it. At minimum, put price, scope, deliverables, payment terms, renewal and termination in writing. Watch for auto-renewal clauses and notice periods.
- NDA: sign before you share anything confidential, which for many vendors means before the kickoff call.
- Data processing agreement (DPA): if the vendor will process personal data on your behalf (customer lists, employee data, CVs), a written contract with specific terms is required under Article 28 of the GDPR in the EU, and the same rule applies under the UK GDPR. Many software vendors publish a standard DPA you can sign.
- Insurance: request certificates of insurance that match the contract (professional liability for advisors, general liability and workers' compensation or employer's liability for on-site work, cyber cover for data handlers) and note expiry dates.
This is general guidance, not legal advice. Have a lawyer review high-value or high-risk contracts.
Step 5: Tax and bank setup with call-back verification
This is where onboarding goes wrong most expensively. Payment diversion scams (a criminal sends "updated bank details" that look like they come from your vendor) target exactly this step, and a company that pays to the wrong account rarely gets the money back.
Tax
- US vendors: collect a signed Form W-9 before the first payment. You need the vendor's correct TIN to file information returns such as Form 1099-NEC, and without one you may have to apply backup withholding. The IRS Form W-9 page has the current form and instructions.
- Non-US vendors paid by a US company: Form W-8BEN-E (entities) or W-8BEN (individuals).
- UK and EU vendors: the VAT number if they charge VAT, validated with HMRC's VAT number check or the EU's VIES service before you reclaim VAT or apply the reverse charge.
Bank details
- Collect bank details through a secure upload or your accounting system's vendor portal, never typed into an email.
- Check the account holder name matches the vendor's legal name.
- Call back on a phone number from an independent source (the vendor's website, your signed contract, a previous invoice), never the number in the email or form that sent the details. Confirm the account details verbally.
- Record the call: who called, which number, where it came from, the date and the result.
- A second person approves the vendor record before the first payment.
- Use your bank's payee name check where available (Confirmation of Payee in the UK, Verification of Payee for euro transfers in the EU).
The full list of fields to collect, and which to skip for low-risk vendors, is in the vendor registration form template.
Step 6: Create the vendor record and add it to your approved vendor list
- Create the vendor in your accounting system with the legal name, category, payment terms and default expense account.
- Add them to your approved vendor list with the relationship owner, risk tier, contract end date and next review date.
- Delete stray copies of tax forms and bank letters from inboxes and download folders once the data is in the system.
Step 7: System access
- Give each vendor person a named account, never a shared login.
- Grant the least access that lets them do the job, with multi-factor authentication on.
- Set an end date that matches the contract, and record what was granted so you can remove it at offboarding.
- Share files through your own workspace with expiring links, rather than sending documents to personal addresses.
Step 8: Kickoff
A 30-minute kickoff prevents most first-month friction. Cover:
- Who is who on both sides, and who can approve changes to scope.
- The scope and how you will measure success at 30 and 90 days.
- Meeting and reporting cadence.
- Invoicing rules: PO number on every invoice, billing email, required fields, payment terms, and the bank change policy above.
Step 9: First-invoice check
The first invoice is your chance to catch setup errors before they repeat every month. Finance checks:
- Price, quantity and tax match the contract or purchase order, and the price matches what the vendor originally quoted.
- The bank details on the invoice are identical to the verified record. If they differ, stop and run the call-back.
- The legal name and tax ID match the vendor record.
- The business owner confirms the work was delivered.
Step 10: 30-day and 90-day review
At 30 days, the business owner answers three questions: is the vendor delivering what was agreed, are they responsive, and are there issues that need a conversation now? At 90 days, score the vendor on quality, price, communication and reliability, decide to keep, improve or replace, and set the next review date. For medium and high tiers, check insurance and certificate expiry dates at the same time.
Who owns each step in a small company
Few small companies have a procurement department. Here is how the roles usually map:
| Role in the checklist | 10 to 50 people | 50 to 500 people |
|---|---|---|
| Requester / business owner | Team lead who needs the service | Department head or manager |
| Budget owner | Founder or CEO | Department head, with finance above a threshold |
| Procurement / ops lead | Office or operations manager | Operations or procurement manager |
| Legal | Founder, plus outside counsel for big contracts | In-house counsel or outside counsel |
| Finance / accounts payable | Bookkeeper or outsourced accountant | AP specialist or finance team |
| Second approver | Founder (if the bookkeeper enters details) | Finance manager or controller |
| IT / security | Whoever administers Google Workspace or Microsoft 365, or the managed IT provider | IT team |
The one rule that should not bend with company size: the person who adds or changes bank details is not the person who approves payments.
How long does vendor onboarding take?
Timing depends almost entirely on the risk tier and on how fast the vendor returns documents. Typical ranges for a small or mid-size company:
| Tier | Typical time to first payment | What usually slows it down |
|---|---|---|
| Low | 1 to 3 business days | Missing tax form, unreachable for the call-back |
| Medium | 1 to 2 weeks | Contract redlines, insurance certificates |
| High | 3 to 6 weeks | Security review, DPA negotiation, internal approvals |
Two things speed it up more than anything else: sending the vendor one complete request (all documents, one secure link) instead of asking piece by piece, and starting the contract and security review in parallel rather than one after the other.
Common vendor onboarding mistakes
- Accepting bank details by email. Or worse, accepting a bank change by email. Always call back on a known number.
- One person doing everything. Entering bank details and releasing payments should be two people, even if one of them is the founder.
- Work starting before the contract. The vendor starts "to save time", and the price and scope are never written down.
- Sharing personal data before the DPA. Sending a customer list for a "quick test" is still processing.
- Same process for every vendor. A 40-question security review for a caterer wastes everyone's time; skipping it for your payroll provider is worse. Tier first.
- Collecting the W-9 at year end. By then the vendor may be slow to respond and you may already owe backup withholding.
- Forgetting access at the end. Vendor accounts that outlive the contract are an open door. Record every grant so offboarding can remove it.
- No first-invoice check. A wrong rate or tax code on invoice one repeats on every invoice after it.
- Never reviewing. Without a 90-day review, an underperforming vendor simply renews.
And when the relationship ends
Offboarding is onboarding in reverse: remove system access, collect or confirm deletion of your data (the DPA should say how), pay the final invoice, mark the vendor inactive in the accounting system so nobody pays them by mistake, and update the approved vendor list with the reason, so the next person searching for that service knows the history.
Frequently asked questions
What are the steps in the vendor onboarding process?
Request and approval, risk tiering, due diligence, contract with NDA and DPA, tax and bank setup with call-back verification, creating the vendor record, system access, kickoff, first-invoice check, and 30- and 90-day reviews.
What documents do you need to onboard a new vendor?
At minimum a tax form (W-9 for US vendors, W-8BEN-E for foreign vendors paid by a US company, or a VAT number in the UK and EU), verified bank details and a signed agreement. Depending on risk, add certificates of insurance, an NDA, a data processing agreement and security reports such as SOC 2.
Who should own vendor onboarding in a small company?
The person who needs the vendor owns the relationship, an operations lead runs the checklist, and finance owns tax and bank setup. A second person, often the founder, approves bank details so no single person can add and pay a vendor.
How long does vendor onboarding take?
Typically 1 to 3 business days for a low-risk vendor, 1 to 2 weeks for agencies and contractors, and 3 to 6 weeks when a security review and data processing agreement are needed.
What is the difference between vendor onboarding and supplier onboarding?
None in practice. Supplier is more common in manufacturing and procurement, vendor in services and software, but both mean setting up a new company you buy from so it can deliver and be paid.
How do you prevent vendor payment fraud during onboarding?
Collect bank details through a secure channel, confirm them by calling the vendor on an independently sourced number, require a second approver, and apply the same checks to every bank change request.
Keep reading
Start onboarding with offers you already have.
Forward vendor emails to save@pitchbin.com and every offer is filed with company, service and quoted price, so the next time you need a supplier your shortlist is already there. Free for buyers.