Guide
How to Track Vendor Onboarding Status
By Keelstar Team · Updated July 11, 2026
The short answer
Track onboarding at the vendor-record level with statuses that mean something operationally: invited, in progress, waiting on vendor, in internal review, approved, or blocked. Each status should map to the next action and owner. Avoid binary done/not-done fields that hide whether you are waiting on a COI or a legal redline. Dashboard by age, tier, and blocker type so leadership sees bottlenecks — not just a count of open vendors. Integrate status with your ERP or P2P system so buyers cannot issue POs against vendors still in onboarding. Weekly standups review vendors past SLA with named escalation owners.
Define status semantics across teams
Procurement, AP, and legal must use the same status definitions. If 'in review' means different things in email vs the system, dashboards lie. Publish a one-page status glossary.
Blocker taxonomy
Tag blockers: missing W-9, COI limits insufficient, legal contract, banking verification, exclusion hit. Monthly review of blocker frequency drives process fixes — not blame.
Age-based escalation rules
Automate escalations at 7, 14, and 21 days idle. Idle means no vendor upload and no internal action. Reset timers when meaningful progress occurs.
Visibility for business sponsors
Sponsors who requested the vendor should see status without emailing procurement. Self-service visibility cuts status-check email volume significantly.
Close the loop at approval
When status moves to approved, notify sponsor, AP, and the vendor contact with payment/PO instructions. Silent approval creates first-invoice surprises.
Frequently asked questions
- What statuses should we use?
- Use a small set: Not started, Vendor action required, Internal review, Approved, Blocked, and Offboarding. Sub-status for document type (W-9 pending) is fine but keep executive rollups simple.
- How do we report onboarding cycle time?
- Measure from intake approval to ready-for-payment. Segment by tier and category. Spikes in 'vendor action required' usually mean unclear requirements or portal friction — not vendor bad faith.
- Should vendors see their own status?
- Yes, in the portal — show completed items, outstanding items, and who to contact. Transparency reduces 'where are we?' emails to buyers.
- Who gets alerted when onboarding stalls?
- Alert the assigned onboarding owner first, then the business sponsor at SLA breach, then procurement leadership for tier-one vendors past twice the SLA.
Related guides
Put this into a monitored workflow
Vendor Packet handles this continuously — with reminders and an audit trail.