Skip to content

Vendor onboarding approval: Procurement first, Management above spend

How onboarding a new vendor gets approved: Procurement checks every vendor, spend of 10,000 or more also needs Management with the registration document.

Updated · 7 min read

In short

  • A new vendor usually gets onboarded on a Procurement lead's say-so, with no written record of why the vendor was accepted or what its expected spend was.
  • DueReason's vendor onboarding template has Procurement check every new vendor, and adds a Management sign-off - with the registration document as evidence - once estimated annual spend reaches 10,000.
  • The request carries the vendor name, contact, category, estimated annual spend, payment terms and tax ID, so the record is the same fields every time, not whatever a Slack message happened to include.
  • A shareable, no-login intake link (Settings > Actions) lets an outside vendor file the onboarding request itself with no DueReason account; it still runs through the same Procurement/Management workflow. DueReason has no accounting-system connector: a second or third step beyond Procurement and Management is something you build with a custom field and the workflow's own conditions.

Onboarding a new vendor usually means someone in Procurement decides a supplier is fine to pay, and the written record of that decision is whatever is left in an email or a shared sheet - if the estimated spend, the tax ID or the reason it was approved survive at all. DueReason's vendor onboarding template turns that into a request with a fixed set of fields and a sign-off that scales with how much the vendor is expected to cost.

Procurement checks every vendor; Management joins above 10,000

DueReason's vendor onboarding template (action key vendor.onboarding, in core/src/approval-templates.ts) has two workflows:

Estimated annual spendSteps
Under 10,000Procurement lead reviews, with a written reason
10,000 and overProcurement lead reviews, then Management approves with the vendor's registration document as evidence

The request names the vendor, a contact, the category of what they supply, the estimated annual spend and currency, payment terms, a tax or VAT ID and a justification - the same fields on every vendor, so comparing two onboarded vendors a year apart does not depend on who happened to write the email.

Finance or a security step: build it with a custom field and a conditional step

The shipped template is Procurement, then Management above the threshold - it has no separate Finance or Security step out of the box. DueReason's workflow engine supports a step that only applies when a condition on the request holds (core/src/approvals.ts, a step's own when), the same mechanism the vendor onboarding workflow already uses at the workflow level for the spend threshold. An organization that wants Finance to review payment terms, or Security to review a vendor only when it will handle personal data, edits the installed template's action to add that fact as a custom field (DueReason's precedent-matching already compares "an org's custom fields" the same way as any other field on the action) and adds a step with a when condition on it - a third, conditional step that only appears for the vendors it actually applies to, not a step that shows up for every vendor regardless.

Letting the vendor file it themselves

For the common case where Procurement would rather have the vendor or contractor supply its own details than retype them, Settings > Actions can generate one shareable, no-login link for the vendor onboarding Action (services/approvals/intake-links.ts's /intake/[token]). An outside vendor who opens it, with no DueReason account and no session, sees only that Action's own fields plus who they are - no precedents, no mandate panel, no file upload, and nothing else in the organization. The link does not expire or wear out after one use (generating a new link revokes the old one instead); the same link is typically shared with several different vendors over time, and each submission still becomes a normal onboarding request that runs through the same Procurement, then Management, workflow and record described above. This is not a dedicated multi-page intake wizard: it renders the same fields the vendor onboarding action defines, just without the console around them. DueReason also has no native connector to an accounting or ERP system (Xero, QuickBooks, NetSuite) that creates the vendor record there once approved - a worked example shows a payment request's amount and payee reaching Xero or QuickBooks through a webhook and a no-code tool, the same approach a vendor record would need, via the API or the SDK rather than a built-in integration.

Segregation of duties and the record

Whoever files the vendor onboarding request is never one of the people who can approve it, the same rule every DueReason action enforces. Once Procurement (and, above the threshold, Management) have answered, the request can produce a signed, verifiable record and a JSON or CSV export at any point, including while it is still pending - the vendor's name, category, estimated spend and who signed off on it, not a line in a spreadsheet nobody has touched since.

Questions

Can I change the 10,000 spend threshold?
The threshold is set on the vendor onboarding workflow's conditions when it is installed for your organization - changing it means editing the workflow, not a setting on the request form.
Can an outside vendor fill in the onboarding request themselves, without a DueReason account?
Yes. Settings > Actions can generate one shareable, no-login link for the vendor onboarding Action (revoked and replaced, not stacked, each time you generate a new one). A vendor who opens it sees only that Action's fields (vendor name, contact, category, spend, payment terms, tax ID) plus who they are, with no session, no precedents and no file upload - and their submission runs through the same Procurement/Management workflow as any other request. It is still the same generic request form the action defines, not a dedicated multi-page intake wizard or a separate form product.
Can I add a Finance or Security step before or after Management?
Yes, by editing the installed template: add the fact you want to route on as a custom field on the action, then add a step with its own condition (DueReason's per-step "when") so it only applies to the vendors that need it - for example, a Security step that only appears when a custom field says the vendor will handle personal data.
Does approving the request create the vendor in our accounting system?
No. DueReason records the decision and issues a signed grant for it. Creating the vendor or supplier record in Xero, QuickBooks or another system still happens separately, through your own integration or a no-code webhook flow.

Give vendor onboarding a threshold, evidence and a record

Create an account, install the vendor onboarding template, and let estimated spend decide whether Procurement alone or Procurement plus Management signs off - with the registration document attached above the threshold.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates