how to onboard a new vendor through an agent safely
Onboards new vendors via an agent with verification and controls. Use for vendor master additions. Not for bank-detail changes on existing vendors.
TL;DR
Agent-led onboarding must verify before it creates: collect business details, validate tax ID, screen sanctions, verify bank details out-of-band, and create the vendor as pending-approval. A human approves the vendor before the first PO or payment. Speed comes from the agent doing the legwork, not from skipping checks.
Steps
- Collect business name, address, tax ID, contacts.
Expected: A complete profile.
- Validate tax ID and screen sanctions.
Expected: Compliance gates.
- Verify bank details via a known contact.
Expected: Fraud prevention.
- Create the vendor as pending approval.
Expected: No active vendor yet.
- Human approves; then activate.
Expected: Controlled go-live.
When to use
- Vendor onboarding
- Vendor master growth
- Procurement automation
When not to use
- Bank changes on existing vendors
- Employee vendors
- One-time vendors (simplified flow)
Compatibility
ERP-agnostic.
Variant phrasings
agent vendor onboarding
new supplier setup automation
vendor master creation controls
Root cause
The vendor master is the payment directory; a bad entry means paying the wrong party. Verification at creation is the control point.
Edge cases
- Sole proprietors need adapted verification
- International vendors need local registry checks
- Emergency onboarding expedites but does not skip
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_njaDOuOVaV0F-XW4Z4zR5A
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.