Vendor onboarding
Vendor re-onboarding workflow after changes
When vendors merge, rename, or lapse on compliance, Keelstar relaunches the right packet and preserves history from the prior relationship.
Last updated:
Related: Vendor Packet · Vendor onboarding · Supplier onboarding workflow · Vendor onboarding checklist · Vendor compliance dashboard · All solutions
The common problem
Acquired vendors keep old tax IDs and COIs on file. Name changes break TIN matching. Nobody runs a formal re-onboarding when relationships change.
- Merged entities pay under outdated vendor records
- Name changes do not trigger W-9 re-collection
- Lapsed compliance resumes without fresh documentation
- Prior vendor history is lost when records are duplicated
How vendor onboarding works
Define
Set the documents and attestations each vendor type must complete before they are approved to work or get paid.
Collect
Send a single portal link so vendors upload W-9s, insurance, contracts, and questionnaires in one place.
Approve
Review completeness, assign owners, and release vendors to AP and operations with a dated audit record.
Benefits
- One portal instead of scattered email threads
- Checklists tied to vendor type and spend tier
- Status visibility for procurement, AP, and risk
- Evidence packet for internal and external audits
Workflow
Relaunch onboarding without losing history
Trigger re-onboarding from the existing vendor record so prior W-9s, COIs, and screening results remain linked.
Entity changes
Handle mergers and name changes cleanly
Collect updated W-9s, COIs, and screening for the new entity while documenting the transition for audit.
- Re-onboarding triggers by event type
- Updated legal name and TIN validation
- Prior record version history preserved
Controls
Block payment until re-onboarding completes
Payment holds stay active until the re-onboarding packet clears so AP does not pay the wrong entity.
Who it's for
- Vendor master data teams managing entity changes
- AP groups updating records after mergers
- Procurement re-qualifying lapsed vendors
- Healthcare organizations re-screening after gaps
What good looks like
- Re-onboarding triggered by defined events
- Updated documents collected before payment resumes
- Prior vendor history remains linked
- Entity changes documented with timestamps
- Re-onboarding status visible on dashboard
Need a tracked version? Set up a vendor portal, vendor onboarding workflow, or browse all solution guides.
FAQ
You define triggers—merger, name change, compliance lapse, or manual request.
Yes. Prior versions stay on the record for audit while new documents become current.
Yes. Include LEIE screening in the re-onboarding packet.
Keelstar tracks compliance on the vendor record your team links to ERP identifiers.
Keelstar covers W-9, COI, OIG screening, contracts, invoices, and policies on shared vendor records.