Supplier Onboarding: A Practical Guide to a Faster Process
A supplier onboarding process has one job. Get a new supplier to the point where you can raise a purchase order and pay them, with nobody guessing what happens next.
When it takes three weeks, the department that needs the supplier usually starts the work anyway. The order goes out by email or on someone’s card. The invoice arrives with no purchase order to match it, and finance learns about the commitment after the money is owed. Onboarding sits early in the procurement process, and a slow stage there pushes spend outside the controls built for everything downstream.
This article covers the onboarding stage in operational depth: who owns it, how long it should take, what to collect, what to do when a supplier stalls, how to run it at volume, and how to tell whether it is working. The work of managing a vendor across the whole relationship, including the record you keep and how to review performance over time, is a separate discipline that starts where this one ends.
What supplier onboarding is, and where it starts and ends
Supplier onboarding is the process of collecting and verifying the information you need to trade with a new supplier, then setting them up in your systems so they can receive orders and get paid.
It starts when someone decides to buy from a supplier you have not set up. It ends when that supplier can receive a purchase order and be paid against it. Everything before that point is selection. Everything after it is vendor management, the stage that vendor management software is built to handle.
Write down what that end point means in your organization. Without a stated finish line, each team assumes a different one. Procurement treats onboarding as finished when the contract is signed. AP treats it as finished when banking details are verified. The requester treats it as finished when they got a yes. A supplier can sit in that gap for a week while three people believe someone else has it.
Supplier or vendor?
The two terms are used interchangeably. “Supplier” usually describes a business providing goods. “Vendor” is broader and takes in service providers. The process is the same for both. Where teams apply a heavier process to one, the reason is normally risk rather than the label.
Who owns supplier onboarding
Onboarding touches procurement, finance, legal, IT and the person who wants to buy something. Shared work with no single owner is the most common reason it stalls. Name one person accountable for a supplier reaching the ready state, then name who decides each gate along the way.
| Step | Who does it | What they decide | What blocks it |
|---|---|---|---|
| Request a new supplier | The requester | Whether an existing supplier already covers this need | Requests that arrive by email instead of through the process |
| Check for an existing record | Procurement | Whether this is a new supplier or a duplicate | Name variations and trading names |
| Terms and contract | Procurement, with legal where the category warrants it | Price, payment terms, notice and renewal | Legal review with no agreed scope or turnaround |
| Risk and compliance review | Legal, IT security or the category owner | Whether the supplier meets the requirements for this category | Reviews run in sequence that could run in parallel |
| Tax and payment setup | Finance or AP | Whether the supplier can be paid correctly | Bank verification, which is slow for good reason |
| Create the record and activate | Procurement or AP, wherever the master record lives | Whether the supplier is ready to receive a purchase order | A final step nobody has been given |
You can run all of this across existing roles, and most organizations should. What matters is that every gate has a named decision maker and a turnaround time, and that the gates capable of running in parallel actually do. The same thinking that shapes purchase approval workflows applies here: a review step with no owner and no deadline becomes a queue.
Before you redesign any of it, map what happens today, from the person placing the order through approval, the purchase order, the purchase itself and the invoice, all the way to the payment leaving the bank. Get input from everyone in that chain first. Teams that skip this step automate a process nobody had agreed on. The map shows you which steps carry weight and which exist because somebody added them once and never removed them.
How long it should take, and what makes it take longer
Onboarding time depends on how much review a supplier needs, and that is a decision you control. Set a target for each level of review and measure against it. Benchmark figures from elsewhere describe other organizations, other categories and other risk appetites.
A straightforward supplier, with modest spend, no access to your systems and no regulated data, should move in days. A supplier that needs legal review, a security assessment and insurance verification will take weeks, and should. The problem sits between those two: suppliers that need nothing unusual and take three weeks anyway.
Measure dead time, not work time
Add up the actual work in a typical onboarding. Reading a tax form, checking a certificate, keying a record, verifying an account. For most suppliers it comes to under an hour. The rest is waiting, and waiting is where the time goes.
- The request sits with someone who does not know it is theirs.
- Documents arrive one at a time, each one triggering another email.
- Legal review has no turnaround time attached to it.
- Two reviews run one after the other when they could have run together.
- The supplier has not replied and nobody has been given the job of chasing.
- The record is complete and waiting for someone to press activate.
This is the same pattern that drives purchase order cycle time, and it responds to the same fix. Time each handoff, find the longest queue, and work on that one rather than asking people to move faster.
Decide how much onboarding each supplier needs
Run every supplier through the same process and you get one of two outcomes. Either the risky ones receive too little scrutiny, or the simple ones receive too much and your team spends its week on paperwork for a one-off purchase. Tiering solves both. Define the tiers once and apply them at intake.
| Tier | Typical supplier | What you collect | Who reviews | Target |
|---|---|---|---|---|
| Light | One-off or low-spend purchase, no system access, no sensitive data | Legal name, address, contact, tax form, payment details | Procurement and AP | Days |
| Standard | Recurring supplier with ongoing spend and a contract | The above, plus the agreement, insurance certificate, agreed pricing and payment terms | Procurement, AP, category owner | One to two weeks |
| Enhanced | Access to your systems or data, regulated category, critical to operations, or high spend | The above, plus security review, compliance certifications, financial checks, named escalation contacts | Add legal, IT security, compliance | Scoped per supplier |
Put the tiering rule in writing and apply it when the request comes in, so the supplier receives one list of requirements rather than a list that grows each week.
Regulated categories pull a supplier up a tier regardless of spend. Anything touching patient data, clinical supply, food safety, or a grant with reporting conditions carries requirements set outside your organization. Those are checks you perform, rather than preferences you balance.
What to collect, and what can wait
Order the list by what each item unblocks. That turns one long form into three short ones, and stops the first purchase order waiting on a document it never needed.
Needed before you can raise a purchase order
- Legal entity name and trading name
- Address and primary contact
- Agreed pricing, or the quote it comes from
- Payment terms and currency
- The signed agreement, filed where you can find it again, which is the job contract management software exists to do
- Your internal supplier ID and the named relationship owner
Needed before you can pay an invoice
- The tax form: a W-9 for US suppliers, the W-8 series for foreign ones, local equivalents elsewhere
- Verified bank details
- A remittance contact
- Invoicing instructions issued to the supplier, which is a step rather than a document
Needed on a schedule, rather than on day one
Insurance certificates, licenses, certifications and annual compliance attestations all expire. Record every expiry date alongside the document and give one person the job of working that list each month. The alternative is discovering the lapse during an audit, or after an incident, when the gap is no longer administrative.
Those fields belong on a single record rather than spread across a finance system, a shared drive and somebody’s inbox. Deciding where the master vendor record lives, and who maintains it, is worth settling before you onboard anyone new.
Treat a bank detail change as a separate request
Collecting bank details during onboarding is routine. A request to change them later is a different kind of request, and payment fraud works precisely because teams handle both the same way. Verify any change by calling a number you already hold, rather than one supplied in the request, and record who verified it and who authorized it.
Let the supplier enter their own information
The fastest improvement available to most teams is to stop retyping information the supplier already has. Send a request, let them complete it, and have it land in your system as a record rather than as an email attachment.
What changes when the supplier does the entry:
- The data comes from the party that holds it. Transcription errors disappear, and the supplier carries the accuracy of their own legal name and account number.
- Status becomes visible on both sides. You can see what is outstanding without asking, and so can they.
- Updates keep working after onboarding. A supplier who moves office updates it once, instead of you finding out when a remittance bounces.
- Your team’s job moves from collecting to reviewing, which is the part that needs judgment.
What it asks of you in return:
- One request that covers everything at once. A second request a week later is how two weeks disappear.
- A stated deadline, tied to something the supplier cares about.
- A reason attached to each item. Suppliers hesitate over bank details, and they are right to.
- Somewhere for them to check progress without emailing your AP team.
- No account they cannot create. If completing the request depends on software their bookkeeper cannot access, the process stops there.
You have moved work onto the supplier, so keep it short. Ask for what their tier requires and leave the rest.
What to do when a supplier stalls
Suppliers stall for ordinary reasons. The request reached a salesperson rather than their finance team. No order exists yet, so there is no commercial pull. The email asking for banking information looks like a phishing attempt, which is a sensible thing to suspect.
- Tie the deadline to the first order. “We can raise the purchase order once this is complete” moves faster than “please complete at your convenience”.
- Give the chase to the requester. They hold the relationship and have a reason to care. An AP clerk chasing a stranger gets ignored.
- Check you have the right person. Ask your sales contact who handles their tax and banking paperwork, then address that person directly.
- Make the request verifiable. Tell the supplier on a call that a request is coming, and from which address. That removes the phishing question for both of you.
- Set an abandonment point. After a stated number of days with no response, escalate commercially or take the purchase elsewhere. For a genuine one-off, a one-time payee route with its own approval saves you onboarding a supplier you will never use again.
Track how often you use that last route. Frequent use is a signal that the request is too heavy for the tier it sits in.
Onboarding at volume
Onboarding one supplier is a different job from onboarding forty. At volume the bottleneck moves from the individual steps to the way work arrives.
- Batch the invites. Send requests to a group at once rather than one at a time as they occur.
- Hold a standing review slot. One session a week to review everything that came back beats switching context four times a day.
- Dedupe before you start. Check the list against suppliers you already hold under a different name or a trading name. Duplicate records split your spend data and make duplicate invoices harder to spot.
- Keep one front door. Every new supplier request uses the same route. A second route, usually an email straight to AP, is where unapproved suppliers come from.
- Template by tier. Each tier gets a standard request, a standard reviewer set and a standard turnaround, so nobody designs the process again each time.
Moving your existing supplier base into a new system is its own project and should be sequenced by spend. Onboard the suppliers you transact with weekly first, leave the long tail until later, and use the exercise to retire records you have not touched in two years.
For suppliers you buy from repeatedly, a punchout catalog connects their catalog to your purchasing process, so requesters order against agreed pricing instead of raising a request for a new supplier each time.
Connecting onboarding to the first purchase order and the first invoice
Onboarding gets tested at the handoff. A supplier can be fully set up in your system and still send their first invoice to the wrong address, with no reference on it, for a price nobody agreed.
Before the first order, tell the supplier five things in writing: that a purchase order is required before work starts, that every invoice must quote the purchase order number, where invoices should be sent, what the payment terms are, and who to contact about a payment. Sending that once, at the end of onboarding, prevents most first invoice problems. The work of teaching a supplier how to transact with you has a name, supplier enablement, and it is the step most often skipped.
On your side, the first invoice is where you find out whether the record is right. Three-way matching checks the invoice against the purchase order and what was actually received. An alert when the invoice price does not match the purchase order is the single most useful control to configure, because it catches pricing errors, quantity errors and record errors in one check.
It is also what makes a team trust the process they have built.
A lot of it is developing that confidence in your system. Once you have those processes in place, once you’re confident in your process and the system flows together, being able to set up those guardrails, whether for approvals, or if prices don’t match the PO when the invoice comes in, having those things that can alert you, is helpful in giving you that confidence.
Kayla Livingston, Accountant at Vance Thompson Vision, speaking about building confidence in a process before trusting a system to run it.
How to tell if it is working
Most teams know their onboarding is slow and cannot say by how much. Six measures are enough to change that.
| Measure | How to calculate it | What it tells you |
|---|---|---|
| Cycle time | Median days from request to ready, reported alongside the slowest 10 percent | Whether the process works, and where it breaks |
| Dead time share | Median hours of actual work divided by median elapsed time | Whether to fix the work or fix the queue |
| First-time-complete rate | Suppliers accepted without a follow-up request, divided by all suppliers onboarded | Whether you are asking clearly |
| Touches per supplier | Count of emails and handoffs per completed onboarding | Where the manual effort is going |
| Onboarded before the first order | Suppliers fully onboarded before the first purchase order, divided by all new suppliers | Whether the process is being bypassed |
| Invoices with no purchase order reference | Invoices received without a valid reference, divided by all invoices received | Whether your invoicing instructions are landing |
Report medians with the tail rather than averages. One supplier stuck for ninety days drags an average somewhere unhelpful and hides the fact that most finish in four. At low volume, read the worst cases one by one. Five bad onboardings will tell you more about your process than a percentage will.
The last measure is worth watching closely, because a rising rate of non-PO invoices usually means people are buying first and onboarding afterward. Where you already track procurement KPIs, onboarding cycle time belongs in the same set.
How Procurify handles supplier onboarding
Procurify’s Vendor Portal applies most of this in one workflow. You invite vendors in batches of up to 10, choose what each one needs to provide, and watch their status without opening a spreadsheet.
The vendor creates their own profile and enters their own details. When they upload a W-9 or W-8, Procurify reads the Tax ID and legal name from the form and flags a name that does not match the vendor record. Insurance certificates and contracts stay on that record. The profile is free for vendors, and one profile works across every Procurify customer they deal with, which is the difference between a supplier completing your request and ignoring it.
After onboarding, vendors see their purchase orders and invoices with live status, and message your team about a specific document, so the conversation sits on the record. They can also invoice against the purchase order directly, adjusting quantities for what actually shipped. That arrives as a draft bill with the order already matched, ready for AP automation to process rather than for someone to rekey.
Frequently asked questions
Who should own supplier onboarding?
One named person should be accountable for a supplier reaching the point where they can be ordered from and paid. That person is usually in procurement or AP, depending on where your master vendor record lives. Each gate along the way keeps its own decision maker, with a turnaround time attached.
How long should supplier onboarding take?
Days for a low-risk supplier, one to two weeks for a recurring supplier with a contract, and longer where a security or compliance review applies. Set the target yourself by tier and measure against it. Most of the elapsed time in a slow process is queueing rather than work.
What documents do you need to onboard a supplier?
At minimum: a tax form, verified bank details, the agreement where one exists, and agreed pricing and payment terms. Regulated categories add insurance certificates, licenses and compliance attestations. Sort them by what each one unblocks, so the first purchase order is not held up by a document only needed before the first payment.
Should suppliers enter their own information?
Yes, in almost every case. The data comes from the party that holds it, status becomes visible to both sides, and updates keep working after onboarding ends. In exchange, ask for everything in one request, explain why each item is needed, and give the supplier somewhere to check progress.
Do you need software to onboard suppliers?
A small team onboarding a handful of suppliers a year can run this on a checklist. Volume, tiering and audit requirements are what make software worth it, because those are the three things a manual process handles worst. Our guide to vendor management software covers what to compare, and a vendor management system shows how supplier records connect to day-to-day purchasing.

$30B+ in real spend data you won’t get anywhere else
Find out what it takes to move from reactive to AI-driven operations.