## 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

1. Collect business name, address, tax ID, contacts.
   Expected: A complete profile.
2. Validate tax ID and screen sanctions.
   Expected: Compliance gates.
3. Verify bank details via a known contact.
   Expected: Fraud prevention.
4. Create the vendor as pending approval.
   Expected: No active vendor yet.
5. 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