Vendor Onboarding Checklist Template

What this template is for

A vendor onboarding checklist is the difference between a supplier who can be paid and granted access on day one, and one who sits half-finished for weeks because someone forgot a document. It turns "have we reviewed the contract?" into a grid you walk through function by function, so procurement, legal, finance, and IT each know exactly what they own. The trick is structure: separate the four swimlanes that actually touch a new vendor, and lay the stages across the top — collect documents, review and approve, sign, set up records, and go live. This template gives you three scenes to adapt. The standard-vendor scene is the full matrix: four lanes by five stages, so nothing between the first quote and the first invoice gets missed. The one-time-vendor scene collapses the flow to four stages and ends at pay and close, because a temporary supplier has no long-term record to build. The SaaS-vendor scene keeps all five stages but shifts the actions toward security — legal signs the DPA, IT runs the security review, and finance wires up subscription billing. Every cell is a replaceable, checkable action, and each lane carries its own color so the matrix reads at a glance. This template structures the handoff between teams; it does not give tax, contract-compliance, or legal conclusions. Build the checklist around your real vendor base: which vendor types you onboard, which team owns each stage, and what must be complete before you sign.

When to use this template

• Onboard a standard supplier across procurement, legal, finance, and IT in five stages.
• Run a condensed four-stage flow for a one-time vendor that ends at pay and close.
• Onboard a SaaS vendor with security review, DPA signing, SSO, and subscription billing.
• Give each team its own lane so procurement, legal, finance, and IT check off their own work.
• Track what must be complete before signing — DPA, bank details, and data access scope.
• Reuse the same grid for the next vendor and update the stages and actions.

How to use it

1. 1List your vendor types and whether each needs the full flow or the one-time flow.
2. 2Assign one owner per lane — procurement leads, legal, finance, and IT each hold their lane.
3. 3Collect documents first: license, certifications, bank details, and system contacts.
4. 4Review and approve before signing — contract terms, payment terms, and access scope.
5. 5Set up records and accounts only after signing, then run a first-invoice and access test.
6. 6Mark the vendor go-live only when every lane has checked off its final cell.

Quick example

Related resources

How it compares to similar tools

Common mistakes to avoid

• No legal lane until it is too late

  Contract review and DPA signing are often added at the end, after finance has already set up payment. Put legal in the flow from the collect-documents stage.

• Finance sets up payment before signing

  Bank accounts and auto-billing should be created only after the contract is signed, so you are not paying a vendor you have not committed to.

• IT grants access before the security review

  For SaaS vendors, granting access before the security and pen-test review means the risk is already live. Confirm access scope and finish the review first.

• One flow for every vendor

  A one-time vendor does not need records and go-live stages. Forcing the full matrix adds noise and slows a simple purchase.

• No go-live checkpoint

  Without a final "all lanes checked" gate, the vendor is half-enabled — buyers can order but IT has not granted access, or the reverse.

Frequently asked questions