Vendor Intake Flow

Problem Statement

Vendor intake repeats across procurement, finance, security, and legal. Teams ask for the same documents more than once and lack a reliable owner for the next approval.

Proposed Workflow

• Start one vendor intake with the documents and owners you need.
• Route tax, insurance, finance, and security checks by sensitivity.
• Chase whatever’s missing automatically in Slack, with a clear owner and due date.
• Let each team see only the vendors and documents their role allows.

Access and Governance

Vendor Intake Flow separates vendor status from sensitive documents. Procurement can see the full intake, Finance can review payment and tax fields, Security can review risk material, and business owners can track whether their vendor is blocked without seeing restricted attachments.

What It Connects To

• Slack, for missing-document reminders and owner follow-up.
• Procurement records, for vendor status, owners, and approval history.
• Security review, for sensitivity triage and required control checks.

Acceptance Criteria

• Everyone who should see a vendor’s status can, and no one else.
• Every missing document has an owner and a due date.
• Security review can’t be skipped for high-sensitivity vendors.
• Status stays honest, it only shows what’s actually done.