Main site

Procurement AI agent · Supplier onboarding

Supplier Onboarding AI Agent

Collect what a supplier class must produce, run the configured checks, and hold it for a named approver: the duty not to deal with a blocked person is strict, the method nowhere prescribed.

Typical delivery
4–6 weeks
Deployment
Your stack
Named approver
Ownership first
After launch
Agent Care

What this agent does

Collects the file, never approves the supplier

In

  1. 01

    A supplier is proposed, and the file its class must produce before anyone pays it is opened.

  2. 02

    A check is run against the sources configured for that class, and what each returned that day is kept.

Reason

  1. 03

    A hit comes back, and it stays a hit — held for a person to read, never cleared by the agent.

  2. 04

    A supplier is clean on every list and half-owned by a blocked person: the rule is ownership, not control.

  3. 05

    A US supplier has no beneficial-ownership filing: none has been required since 14 August 2026.

Decide

  1. 06

    A tax form arrives sworn by the supplier, and the buyer keeps it: backup withholding falls on the payer.

  2. 07

    A payee threshold moves by statute, and the file follows the statute; the regulations are only proposed.

Out

  1. 08

    A certificate ages past its term, and the supplier resting on it reads stale rather than approved.

  2. 09

    Execute write actions only inside the approval boundaries agreed during implementation.

Product statement

Collection, checking and recording belong to the agent. The decision that a company may be a supplier belongs to a named approver, who signs it and owns it.

Example workflow

One supplier, proposal to approval

  1. 1Supplier proposedA buying request, a sourcing outcome, an existing payee record or a supplier intake form
  2. 2File assembledLegal name, registered address, ownership as the supplier states it, tax form and the certificates asked of it
  3. 3Checks runScreening sources, ownership questions, document completeness and confidence
  4. 4Controls appliedList-source checks, name-match checks, document-expiry checks and confidence threshold

No human action required

Stages 1 to 4 run unaided, and no supplier is approved at any of them — the agent is collecting, and the approver lane opens at the screening gate.

5DecisionSplits at the screening gate
Nothing returned

Goes to the named approver to sign.

Any hit or ownership question

Adds a sanctions review first.

Approver review

The supplier is held with its checks, what each returned and the day it returned it.

Approve · Add document · Send to sanctions review

Approved — by the named approver

  1. 6Supplier and payment records updatedOnly where write access and records policy allow it
  2. 7Outcome evaluatedScreening accuracy, ownership findings, approver corrections and what review found

Corrections

Each approver correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Deciding that a company may be a supplier.
    • Clearing a screening hit against any list.
    • Judging who ultimately owns a supplier.
    • Certifying anything to a tax authority.

  • Automation boundary

    Agent acts unaided

    • ✓Collect the documents each supplier class requires.
    • ✓Record what each check returned, and when it did.
    • ✓Run the screening and ownership checks configured for that class.
    • ✓Show which checks have gone stale and which documents are missing.

    A supplier becomes approved only by a named approver, inside the agreed boundaries.

    • Deciding whether a state licence rule reaches you.
    • Waiving a document a contract asks for.
    • Judging whether a supplier is in truth an employee.
  • Changes to screening sources or approval rules.

Example output

One supplier file, annotated

This serves a procurement team that may have to show what was checked before a supplier was paid, long after the payment; below is one file exactly as the agent leaves it.

Supplier file · single onboarding

Illustrative example
Supplier
Contract services supplier
Recorded as
Screened, nothing returned
Class
Ownership as stated
Evidence of record
Consolidated lists, 3 August 2026
Confidence
Held unapproved
Held for
The named approver, by name

As received

Taken from the supplier submission and the sources checked — nothing on this side is asserted by the agent.

What the file holds

  • Screening result
  • Supplier tax form
  • Stated ownership

Why no approval here

Deciding that a company may be a supplier is an approver judgement.

What the score decides

Any hit or ownership question picks up a sanctions review before the approver sees it.

Action

ApproveAdd documentSend to sanctions review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every supplier

From the class it is onboarded under

03Checks

Collect and check the file

Vendor-master payment verification is banking-detail fraud and the payment file; this is the decision that a company may be a supplier at all.

01Approved path

The supplier signs, not you

The tax certification is sworn by the supplier and handed to you; the buyer signs nothing here, files nothing and certifies nothing.

02Human review

What was checked, and not found

No register open to a private buyer settles the ownership the fifty percent rule turns on, and nothing found obliges an ordinary buyer to screen or to collect a certificate; one is unprescribed, the other is contract.

04

Build an evidence trail

The supplier, the checks run against it and the person who approved stay together.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Screening sources

    • OFAC SDN
    • consolidated lists
    • Denied-party and debarment lists

  • Supplier submissions

    • Supplier portal
    • intake forms
    • Tax forms and certificates

  • Registry and corporate data

    • Company registers
    • state filings
    • Ownership and good-standing status

Agent

Supplier onboarding and screening

  • Collects the file
  • Runs the checks
  • Holds for the approver

  • Purchasing and payment systems

    • ERP supplier master
    • AP/P2P
    • Payment and remittance set-up records

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six turnpikes between the model and the supplier master

Six turnpikes on one road, the last the dearest. What passes is drawn in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to document collection when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and class rules, and note the version each check was run under.Track
L4TraceabilityRecord each supplier, the checks run against it, what each returned and every read of the file.Record
L3Approver releaseHold the supplier for a named approver; the hold governs release, not whether a check was right.Gate
L2Screening guardrailsTest each file against the list sources, the document set and the state licence rule configured for its class; a failure returns the file.Restrict
L1Confidence thresholdsRoute a weak name match, an unresolved ownership question, or a sole trader engaged inside your own line of work, to a review first.Require review
Model coreSupplier file assembled — the documents, the checks run, what each returned and confidence
L1 – L2
Test whether a supplier file may stand
L3
Leaves the approval to a named approver
L4 – L5
Keep the supplier and the checks behind it
L6
Leaves the supplier unapproved when signals degrade

How Nestack evaluates it

Evaluate the whole onboarding — not only the supplier that comes out.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the supplier a payment run sees

  1. E1Final-output evaluationDid the file record which sources were checked, and when?
  2. E2Step-level evaluationDid the agent read the right list sources, the right class rules and the live document set?
  3. E3Tool evaluationDid it read and write the correct supplier and the correct record?
  4. E4Confidence calibrationDo weak name matches actually attract more approver corrections?
  5. E5Slice evaluationHow does performance change across specific supplier classes?
  6. E6Business outcomeHow many suppliers needed a correction before the approver signed?

Floor — the payment the buyer answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage it first shows itself.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • OI-03

      Stale list read

      The list checked is not the one now published.

    Stage gathers

    The sources, the forms, the classes and the dates

  2. 02 · Reasoning

    2 modes

    • OI-04

      Hit resolved, not held

      A screening return is settled without a person.

    • OI-06

      Ownership read as control

      A minority holder is treated as the owner.

    Stage proposes

    The sources checked, the hits and the ownership

  3. 03 · Tool / write

    2 modes

    • OI-02

      Weak match passed forward

      A partial name match moves on without a review.

    • OI-05

      File bound to wrong supplier

      The checks are filed against another supplier.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • OI-01

      Approved, checks unrecorded

      The record shows approval but not what was checked.

    Stage returns

    The supplier a payment run and an examiner see

  5. 05 · Change / Version

    1 mode

    • OI-07

      Silent source drift

      A list source changes while the stored result keeps the old one.

    Stage tracks

    Model, prompt, class rules and list sources

  • Sev-1 · a supplier approved on no check
  • Sev-2 · a stale check reaches the payment run
  • Sev-3 · a source degrades, supplier held back
See the complete Procurement failure-mode catalogue

Affected slices

Opaque ownership absorbs the corrections

A class-level screening figure can read clean while the suppliers with layered ownership carry most of the review work. Nestack reports the correction rate by supplier class, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Layered or opaque ownership12.0%3.7×Review
Foreign-registered suppliers8.6%2.7×Review
Individuals and sole traders5.3%1.6×Watch
Established domestic suppliers2.2%0.7×Normal

Bar: correction-rate lift vs. established-domestic baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What a half-owned supplier costs

A loop ends when the supplier approved on a stale check is a standing case. That suite is what the next approval made is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Correction rate rises on suppliers with layered ownership.

  2. 02

    Diagnose

    The supplier that was clean on every list and half-owned by somebody who was not is worked backwards until one cause is left standing.

  3. 03

    Improve

    Changes leave numbered, and the suppliers behind them travel attached.

  4. 04

    Verify

    A single red supplier case stops the whole release.

  5. 05

    Learn

    One case joins the suite, one line joins the onboarding record.

  6. Learn → Detect

    The return edge. The next supplier is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, onboarding workflow, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Onboarding-workflow and automation-boundary scoping.Week 1
  2. 02Screening, registry and submission sources.Week 1, Week 2
  3. 03Supplier-class and screening-coverage rule mapping.Week 1, Week 2
  4. 04Supplier-file ingestion and normalisation.Week 2
  5. 05Screening logic and check-source binding.Week 2, Week 3
  6. 06Confidence scoring and review routing.Week 3
  7. 07Approver sign-off workflow.Week 3, Week 4
  8. 08Supplier-master and payment integration.Week 5
  9. 09Screening and ownership cases.Week 4, Week 5
  10. 10Guardrails and approval controls.Week 4
  11. 11Supplier-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne supplier class, one entityProductionProduction supplier masterAdvancedMultiple entities / jurisdictions
Introduced at Pilot
Checks run to your class rules✓✓✓
Named approver sign-off✓✓✓
Supplier-master baseline✓✓✓
Introduced at Production
Reporting by supplier class—✓✓
Sanctions review workflow in your systems—✓✓
Approved write-back—✓✓
Screening-source integration—✓✓
Introduced at Advanced
Multi-source list reconciliation——✓
Multi-stage approval chains——✓
Large supplier populations——✓
Multi-list screening controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, supplier volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your supplier classes and what each must produce

    Class definition and document-set mapping

    Week 1

  2. 02Representative supplier files, including the awkward ones

    Source binding, check logic and the screening baseline

    Week 2

  3. 03Your list sources and the approvers they route to

    Class rules, document sets and the automation boundary

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Screening, registry and submission source assessment, then integration setup

    Week 2

  5. 05Suppliers you would not want examined

    Screening cases and failure-mode testing

    Week 4

  6. 06What no onboarding file may certify

    Confidence scoring, review routing, guardrails and release controls

    Week 3

  7. 07A named approver who signs the supplier off

    Release to the named approver, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Two phases share week five because they genuinely do, and not one band was widened to look tidy.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Class discovery, document-set mapping and the automation boundary

W2Screening-source integration and the supplier-master baseline

W3Onboarding workflow, confidence logic and release controls

W4Evaluation suite, screening cases and failure-mode testing

W5Supplier-master integration, pilot onboardings and targeted corrections

W6One onboarding quarter run under the supplier approver, then Agent Care handover

Reading the band
Each bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6
When the approval record validates, Agent Care picks the agent up.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Procurement AI agent

Build a supplier onboarding agent around the ownership question your last screening never asked.

Show us one supplier class and the file you collect before anybody is paid. The supplier signs the tax certification under penalty of perjury; the buyer signs nothing at onboarding, files nothing and certifies nothing. A supplier nobody can trace comes back as a finding.

Typical delivery
4–6 weeks
Deployment
Your supplier classes
Named approver
Ownership first
After launch
Agent Care available

Nestack Agents · Supplier onboarding

AGT-PR-03 · Agent Care available after launch

Build a supplier onboarding agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your suppliers

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.