Skip to content

Set suppliers up without chasing forms and approvals.

A missing tax record or unapproved bank detail can hold up a supplier's first order and payment. Duvo gathers the documents, checks the vendor data and routes the required decisions, then creates the approved record in your ERP. Procurement and AP spend less time chasing forms and re-entering the same information.

Book a process call

Agree the supported records, system access and approval rules for your process before execution.

Supplier Onboarding

Needs input

Supplier 401

Validation
Bank evidence received
Scope
New supplier
Decision
Approve setup

Next action

Approvals follow your policy

Supplier type, country, spend, and risk determine which owners must approve the request.

View the wider product queue

Supplier Onboarding

Supplier details, tax records, bank evidence, and approvals are checked before the vendor record is created or changed.

Adds cases
Supplier Request
Processes cases
Supplier Setup Review
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Validation
Scope
Decision
Exceptions
Next action
Supplier 401
Needs Input
Bank evidence received
New supplier
Approve setup
1
Supplier 402
In Progress
Tax record missing
Bank change
Request document
0
Supplier 403
Completed
Duplicate found
New supplier
Review match
0
Supplier 404
Pending
Approval pending
Address change
Chase owner
1
Supplier 405
Postponed
Checks complete
New supplier
Create vendor
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Validation

    Validation is visible before the action

    Each request shows the records received, the checks completed, and the approval still needed before the supplier can transact.

Move the supplier from request to approved vendor record.

The request moves through forms, email, shared drives, and ERP screens. Missing evidence or an unanswered approval can hold it for days.

  1. 01Collect

    Gather the supplier records.

    Duvo collects the form, tax record, bank evidence, contacts, and required attachments from the supplier and internal teams.

  2. 02Validate

    Check the details against policy.

    Required fields, duplicates, tax identifiers, bank evidence, and policy rules are checked before the request moves on.

  3. 03Approve

    Your team decides

    Route the decisions to the right owners.

    Procurement, finance, tax, or compliance owners receive only the approvals and exceptions within their authority.

  4. 04Create

    Create or update the vendor record.

    Approved data is written into SAP or the relevant vendor master without asking the team to rekey the request.

  5. 05Confirm

    Leave a clear setup record.

    The supplier and internal owners receive confirmation, while every check, approval, and field change stays attached to the record.

Use the supplier and finance systems already in place.

Systems and control details

Duvo can collect records from forms, inboxes, portals, and shared drives, then create or update the approved supplier in the ERP.

SAP vendor master, procurement suites, supplier portals and forms, tax and company records, bank-detail evidence, email and shared inboxes, document repositories, approval workflows

  • Bank changes always stop for verification

    A routine-looking bank change can carry fraud risk. A new or changed account follows the customer-approved verification path before any vendor record is updated.

  • Approvals follow your policy

    Supplier type, country, spend, and risk determine which owners must approve the request.

  • Every field change is recorded

    The source value, approved value, person who approved it, and ERP update remain available for review.

Contracted guarantee

5x ROI, guaranteed

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Supplier Onboarding

  • What happens when a supplier asks to change its bank details?

    A new or changed account always follows your approved verification path before any vendor record is updated.

  • Which checks run before a new vendor reaches approval?

    Required fields, duplicates, tax identifiers, bank evidence and policy rules. Duvo gathers the form, tax record, bank evidence, contacts and attachments first.

  • Does every supplier need the same approvals?

    No. Supplier type, country, spend and risk decide which procurement, finance, tax or compliance owners must approve. Each owner sees only the decisions within their authority.

  • Does anyone still rekey the vendor record into SAP?

    No. Approved data is written into SAP or the relevant vendor master, and the source value, approved value, approver and ERP update stay on record.

Related processes