Supplier onboarding: what’s holding up the new supplier?

Problem

“Can we use this supplier yet?”

Someone needs to place an order. The supplier has sent its paperwork. Finance has received a request to create the account. Then comes the question: “Can we use this supplier yet?”

Answering it takes another round of messages. Someone checks the attachments. Someone asks whether the review is finished. Someone discovers that a missing detail was requested last week, but nobody followed up.

Supplier onboarding can involve several legitimate checks. When those checks happen across separate email conversations, finding out where things stand becomes a recurring task of its own. The person chasing the answer may work in purchasing, operations, finance, or simply be the person everyone asks.

Examples

One supplier. Several versions of what happens next.

Consider a fictional business bringing on a new materials supplier. Purchasing sends a setup form. The supplier returns it with one required field blank. Finance asks for the missing information. Meanwhile, the person requesting the purchase forwards the original form to operations and asks whether everything is ready.

There are now several conversations about the same supplier. Each contains part of the answer. The supplier may receive a reminder for something it already submitted. A reviewer may receive an incomplete packet. The requester keeps asking for updates because there is nowhere else to check.

Graphite Connect’s May 2026 research, covering nearly 70 organizations in North America and Europe, reported averages of 8.14 hours weekly on onboarding tasks and 8.89 hours fielding redundant supplier questions. These vendor-sponsored findings describe that sample. They do not establish how much time a particular business could save. The example here is fictional, not a client result.

Make the next action visible

“Pending approval” tells the requester very little. “Waiting for the supplier’s missing address; purchasing will follow up Thursday” explains what is happening. An onboarding record should make that answer available without another search through messages.

What information is required for this purchase?
What has arrived, and what is still missing?
Which reviews are required, and who owns each one?
What prevents the next step?
When will someone follow up?

Solutions

Give supplier onboarding a process people can follow

Start by agreeing on the requirements and the people responsible for reviewing them. A local materials supplier and a software provider receiving access to business data may need different reviews. Define those paths before asking software to route the requests.

Check what your existing purchasing or accounting software supports. Forms, review steps, reminders, and status views may already be available. A separate automation becomes worth considering when a recurring gap remains between those tools.

What automation could handle between handoffs

A submitted request could create one onboarding record. Required fields could be checked before the packet reaches a reviewer. Missing information could generate a specific request to the supplier. Completed submissions could move to the appropriate person with the supporting documents attached.

Reminders should follow the actual state of the work. If the supplier has responded, the request for that information stops. If the packet is complete but awaiting an internal review, the follow-up goes to the reviewer. Record a backup owner for absences and an agreed route for overdue work.

The requester could see whether information is outstanding, a review is underway, a correction is needed, or the responsible person has approved the supplier. Keep a record of who changed the status and why, and show when information was last updated. A failed update needs a visible owner and a manual fallback.

Receiving a document does not complete the review

Software can check whether a field is present. The appropriate person still needs to decide whether the information is acceptable. Record the required approvals explicitly; a complete packet must not silently become an approved supplier.

Supplier acceptance, exceptions, and sensitive changes such as banking details stay with authorized people under the business’s verification process. Give each participant access to the information their role needs. A requester checking progress does not need access to every financial document.

A short worksheet for one recent supplier

Choose one recently approved supplier and walk through the request with the people who handled it. Use these prompts to record the purchase, requirements, waits, owners, and repeated follow-ups. The answers give you a concrete starting point for deciding what to change.

Purchase: What triggered the request, and when was the supplier needed?
Requirements: What information and reviews were needed, and where were those requirements recorded?
Waiting: What caused each delay—missing information, an internal review, or a correction?
Ownership: Who had the next action, and could the requester see that?
Follow-ups: Which messages repeated a request or asked for a status someone already knew?
Existing tools: Which of those steps could your current software already support?

Check whether the chasing actually decreases

Before changing the workflow, record manual follow-ups per supplier, time spent finding the current status, and incomplete submissions reaching reviewers. Separate time spent actively reviewing from time waiting for information or a decision.

After a limited rollout, compare similar supplier requests using the same measures. Include the work needed to correct mistakes, review exceptions, and maintain the process. Look for repeated requests that stopped and handoffs that became clearer, while checking that required reviews still happened.

How Zoevin helps

Bring one supplier request that took too much chasing

At Zoevin, I build scoped automations in your business’s own environment and hand them over on an agreed date. If supplier setup repeatedly turns into a search through messages, tell me where the request starts, who reviews it, and what someone has to chase by hand.

Discuss one recent supplier request and the work repeated between reviews.
Identify a possible automation scope and the decisions your team retains.

Zoevin has no delivered automation projects yet. Discovery names the seam. If I build, I hand it over on a written date. You get the workflow, the logins, and the write-up. I don't stay on to run it. You buy the software.

Talk through your supplier onboarding process

Evidence

Sources

Primary reporting first. Open the sources yourself rather than taking this account alone.

primary source
Graphite Connect — 2026 Supplier Data Benchmark Report announcement
Published May 20, 2026; reviewed September 23, 2026. Vendor-sponsored research covering nearly 70 organizations in North America and Europe. The public announcement reports weekly averages of 8.14 hours on onboarding tasks and 8.89 hours fielding redundant supplier questions. These are sample findings, not small-business benchmarks or potential savings. The supplier example and worksheet are Zoevin’s illustrative design.