Vendor due diligence automation for each new supplier
The agent reads the vendor pack, checks the papers against your list, screens the company and its owners and sends anything that does not add up to a reviewer before the vendor is set up.
Works with

- Custom REST
- Procurement system · via Custom REST
and any system with an API via Custom REST
What is vendor due diligence?
The procedure
Before a bank or fintech pays a new supplier, someone checks that the company is real, that the bank account belongs to it and that neither the company nor its owners raise screening concerns. The papers required depend on the vendor type in your policy. Gaps and hits hold the setup until a person decides.
What the agent does
Finds the vendor pack in Google Drive
Checks the registration, bank letter and insurance papers against your list
Screens the company and its owners in ComplyAdvantage
Checks that the bank account name matches the registration
What your team decides
Whether a screening hit on an owner stands
Approving any request for missing papers
Setting up a vendor after a hit is cleared
Escalations to your MLRO or compliance officer
Example runs for procurement, vendor risk and compliance operations
Vendor Due Diligence Agent
Checks new suppliers' papers and screens them before setup.

- +1
Trigger: Inbound webhook · new vendor
From a procedure Vendor due diligence · v1.0
Maya
Onboard Lumen Print as a new supplier.
Vendor Due Diligence Agent
Found the vendor pack in Google Drive
- Read the registration certificate and the bank letter
Screened the company and its owners in ComplyAdvantage: no hits- Bank account name matches the registration
bank.name == registration.name
Vendor approved. Lumen Print passed all four steps. The documents and screening result are linked to the run.
4 steps · 0 reviews
Vendor Due Diligence Agent
Checks new suppliers' papers and screens them before setup.

- +1
Trigger: Inbound webhook · new vendor
From a procedure Vendor due diligence · v1.0
Diego
Onboard Ostrava Metals as a new supplier.
Vendor Due Diligence Agent
Found the vendor pack in Google Drive
- Read the registration certificate and the ownership declaration
Screened the company and its owners in ComplyAdvantage: 1 possible match- Held for a reviewer: an owner returned a possible match Waiting for a reviewerTom: possible match stands, escalate to your MLRO or compliance officer
- Held the vendor setup and recorded the escalation
Escalated. The vendor setup is on hold and the case is with your compliance officer, along with the pack and the match.
5 steps · 1 review
Vendor Due Diligence Agent
Checks new suppliers' papers and screens them before setup.
- API
- +1
Trigger: Inbound webhook · new vendor
From a procedure Vendor due diligence · v1.0
Priya
Onboard Corvid Freight as a new supplier.
Vendor Due Diligence Agent
Found the vendor pack in Google Drive
- The insurance certificate on your list is not in the pack
pack.missing.size() > 0 - Drafted the request for the certificate
- Asked a reviewer to approve the request first Waiting for a reviewerMaya: approved, your team sends it
Waiting on the vendor. The request for the missing certificate was approved and handed to your team to send. The run resumes when it is uploaded.
4 steps · 1 review
Setting up the Vendor Due Diligence Agent
Connect your systems
Read the vendor pack in Google Drive, screen in ComplyAdvantage, and update your procurement system through Custom REST.


- Custom REST
- Procurement system · via Custom REST
Write the rules
Which papers each vendor type needs, and which findings need a person, are CEL rules your team can read and version.
pack.missing.size() > 0Request documentsscreening.hits > 0Ask a reviewerbank.name == registration.nameContinueAdd reviewers where the procedure says
The reviewer sees the pack, the screening result and the agent's notes together, and the vendor setup waits for the decision.
Review requested: Ostrava Metals
- Reason
- Possible match on an owner
- Rule
- screening.hits > 0
- Procedure
- Vendor due diligence · v1.0
Not a matchEscalate
Start it from the event
A new vendor in your procurement system starts the checks by webhook, and so does a change to its details. A daily schedule lists vendors still waiting on documents.
- Inbound webhook · new vendor
- Daily at 06:00 · vendors awaiting documents
- Inbound webhook · vendor details changed
Version and evaluate
Keep a clean vendor, an owner with a screening hit and a pack missing its insurance certificate as scenarios. Each due diligence version runs them before it is published.
Vendor due diligence · v1.0Published
12/12 scenarios passed
Vendor due diligence · v1.2 Superseded
Vendor due diligence · v1.1 Superseded
Share with the team
Procurement can follow each vendor's checks, vendor risk takes the Reviewer role, and compliance operations author the checklist. Auditors read the pack, the screening and the decision.
Admin
Author
Reviewer
Auditor
Questions about vendor due diligence automation
Does the agent set up vendors in our procurement system?
It can update your procurement system through Custom REST once the checks pass and your procedure allows it. Any gap or hit holds the setup for a person.
Can different vendor types need different papers?
Yes. A payroll provider and a stationery supplier can have different lists in your procedure, and the agent checks each pack against the right one.
What if a vendor's details change later?
A webhook from your procurement system starts the checks again when vendor details change, so the new bank account or owner is screened.
Controls your auditors will ask about
These controls apply to each agent you build. Sample data
Admin
Author
Reviewer
Auditor
Role-based access
Admin, Author, Reviewer and Auditor roles, scoped to each workspace.
- 41
7c2e… - 42
a91f… ← 7c2e - 43
03d8… ← a91f
Hash-chained audit log
Each entry carries the hash of the one before it. Verifying the log recomputes the chain and flags entries that no longer match.
- 41
- v1.1v1.2v1.3Published
Versioned specs
Each run records the exact version it followed; old versions stay readable.
- vault/sumsub/key
Secrets in a vault
Steps point to a vault path, and the key stays in the vault.
- Signed delivery accepted
- Unsigned delivery rejected
Signed webhook triggers
Unsigned or stale deliveries are rejected before a run starts.
- SandboxLive
Sandbox before live
New versions run on test data first. Going live is a separate step.
Related use cases
-
Complaints triageCategorize each complaint on arrival, apply your response timelines and route sensitive cases to a person.
-

Account closure reviewCheck each closure request against your list of holds, open items and alerts before anyone closes the account.
-


KYC onboarding reviewCheck documents, screen the applicant and apply your risk rules, with a reviewer where the procedure asks.
Run this procedure as an agent
Book a demo with your own version of this procedure, and we'll show it running with each step logged.
Book a demo