Vendor onboarding

Move every vendor from intake to approved record on one governed path.

Build a vendor onboarding tool for structured intake, document status, departmental review, approvals, and activation. Keep the workflow in real code with scoped actions and an attributable audit history.

Build the workflow Inspect the operating model
data · audit PROD
Data audit append-only
  1. UPDATE assignments 26.06.2026 · 14:02:11
    allocation_percent: 40 → 55 m.alvarez@acme-inc.io
  2. INSERT time_entries 26.06.2026 · 13:47:36
    logged_hours: ∅ → 6.5 j.kim@acme-inc.io
  3. UPDATE projects 26.06.2026 · 11:20:58
    status: planned → active p.nwosu@acme-inc.io

tenant roles hold SELECT + INSERT only · captured by AFTER triggers

The onboarding problem

Email threads do not show which evidence is missing or who owns the next decision.

Vendor onboarding crosses procurement, finance, security, legal, and operations. Shared spreadsheets can record a status, but they rarely enforce required fields, decision rights, or a durable history of each handoff.

Onboarding controls

Model the process your organization actually uses.

Relpin provides the governed app, data, workflow, and audit primitives; your team defines the vendor policy in code.

01

Structured intake

Capture vendor identity, category, risk fields, document state, and responsible owners in typed tables and forms.

02

Role-scoped reviews

Expose finance, security, legal, and procurement decisions only to the roles or app permissions responsible for them.

03

Audited activation

Keep approval decisions and final vendor activation attributable through row-level changes and workflow execution history.

Workflow model

Collect, review, decide, and activate without losing the record.

The workflow can stay simple for low-risk vendors or branch into additional review paths when policy requires it.

  1. 01

    Open the vendor record

    Create a typed intake record with the required ownership, evidence checklist, and current onboarding state.

  2. 02

    Route departmental reviews

    Run code-defined checks and durable approval steps for the teams required by vendor category or risk.

  3. 03

    Activate through a governed decision

    Allow activation only after the required state and approvals are present, then retain the decision trail for later review.

Onboarding evidence
Typed vendor and evidence records
Department-specific permissions
Durable approval steps
Actor-linked change history
Vendor onboarding questions

What your team builds and what Relpin governs.

Is vendor onboarding a prebuilt Relpin application?

It is a solution pattern teams build on Relpin, not a fixed procurement product. Your team owns the fields, review policy, integrations, and user experience.

Can onboarding branch by vendor risk or category?

Yes. Application code and workflow branch nodes can route different records through the checks and approvals your policy requires.

Can external vendors use the same internal console?

Relpin supports authenticated app access patterns, but the exact external portal and invitation model must be designed for your organization rather than assumed by this page.

Structured from first intake

Replace the onboarding spreadsheet with an operable internal system.

Build the forms, review queues, approvals, and audit trail as real code on governed data.

Create a Relpin account Discuss vendor onboarding
Open beta · Solution pattern