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.
A supplier is proposed, and the file its class must produce before anyone pays it is opened.
02
A check is run against the sources configured for that class, and what each returned that day is kept.
Reason
03
A hit comes back, and it stays a hit — held for a person to read, never cleared by the agent.
04
A supplier is clean on every list and half-owned by a blocked person: the rule is ownership, not control.
05
A US supplier has no beneficial-ownership filing: none has been required since 14 August 2026.
Decide
06
A tax form arrives sworn by the supplier, and the buyer keeps it: backup withholding falls on the payer.
07
A payee threshold moves by statute, and the file follows the statute; the regulations are only proposed.
Out
08
A certificate ages past its term, and the supplier resting on it reads stale rather than approved.
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
AgentHuman
1Supplier proposedA buying request, a sourcing outcome, an existing payee record or a supplier intake form
2File assembledLegal name, registered address, ownership as the supplier states it, tax form and the certificates asked of it
3Checks runScreening sources, ownership questions, document completeness and confidence
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▼
6Supplier and payment records updatedOnly where write access and records policy allow it
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 required8 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 boundaryAgent 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 onboardingIllustrative example
Supplier
Recorded as
Class
Evidence of record
Confidence
Held for
Contract services supplier
Screened, nothing returned
Ownership as stated
Consolidated lists, 3 August 2026
Held unapproved
The named approver, by name
As receivedTaken from the supplier submission and the sources checked — nothing on this side is asserted by the agent.
What the file holdsScreening resultSupplier tax formStated ownership
Why no approval hereDeciding that a company may be a supplier is an approver judgement.
ActionApproveAdd documentSend to sanctions review
What the score decidesAny hit or ownership question picks up a sanctions review before the approver sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every supplierFrom 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.
04Build 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 sourcesOFAC SDN · consolidated lists Denied-party and debarment lists
Supplier submissionsSupplier portal · intake forms Tax forms and certificates
Registry and corporate dataCompany 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 systemsERP supplier master · AP/P2P Payment and remittance set-up records
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 defenceInward → 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 – L2Test whether a supplier file may stand
L3Leaves the approval to a named approver
L4 – L5Keep the supplier and the checks behind it
L6Leaves 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
Depth of coverage ▼
E1Final-output evaluationDid the file record which sources were checked, and when?
E2Step-level evaluationDid the agent read the right list sources, the right class rules and the live document set?
E3Tool evaluationDid it read and write the correct supplier and the correct record?
E4Confidence calibrationDo weak name matches actually attract more approver corrections?
E5Slice evaluationHow does performance change across specific supplier classes?
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 lifecycleDirection of processing →
01 · Retrieval1 mode
OI-03
Stale list read
The list checked is not the one now published.
Stage gathersThe sources, the forms, the classes and the dates
02 · Reasoning2 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 proposesThe sources checked, the hits and the ownership
03 · Tool / write2 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 writesOnly where write access and approval policy allow it
04 · Output1 mode
OI-01
Approved, checks unrecorded
The record shows approval but not what was checked.
Stage returnsThe supplier a payment run and an examiner see
05 · Change / Version1 mode
OI-07
Silent source drift
A list source changes while the stored result keeps the old one.
Stage tracksModel, prompt, class rules and list sources
Sev-1 · a supplier approved on no checkSev-2 · a stale check reaches the payment runSev-3 · a source degrades, supplier held back
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 aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Layered or opaque ownership
12.0%
3.7×
Review
Foreign-registered suppliers
8.6%
2.7×
Review
Individuals and sole traders
5.3%
1.6×
Watch
Established domestic suppliers
2.2%
0.7×
Normal
Bar: correction-rate lift vs. established-domestic baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 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 stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on suppliers with layered ownership.
02Diagnose
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.
03Improve
Changes leave numbered, and the suppliers behind them travel attached.
04Verify
A single red supplier case stops the whole release.
05Learn
One case joins the suite, one line joins the onboarding record.
Learn → DetectThe 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.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Onboarding-workflow and automation-boundary scoping.
02Screening, registry and submission sources.
03Supplier-class and screening-coverage rule mapping.
04Supplier-file ingestion and normalisation.
05Screening logic and check-source binding.
06Confidence scoring and review routing.
07Approver sign-off workflow.
08Supplier-master and payment integration.
09Screening and ownership cases.
10Guardrails and approval controls.
11Supplier-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 priceConfirmed after discovery based on integrations, workflow complexity, supplier volume, approval controls and deployment requirements.
Separate from buildBuild 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.
You bringWe build with it
01Your supplier classes and what each must produce→Class definition and document-set mappingWeek 1
02Representative supplier files, including the awkward ones→Source binding, check logic and the screening baselineWeek 2
03Your list sources and the approvers they route to→Class rules, document sets and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Screening, registry and submission source assessment, then integration setupWeek 2
05Suppliers you would not want examined→Screening cases and failure-mode testingWeek 4
06What no onboarding file may certify→Confidence scoring, review routing, guardrails and release controlsWeek 3
07A named approver who signs the supplier off→Release to the named approver, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, 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.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Class discovery, document-set mapping and the automation boundaryW2Screening-source integration and the supplier-master baselineW3Onboarding workflow, confidence logic and release controlsW4Evaluation suite, screening cases and failure-mode testingW5Supplier-master integration, pilot onboardings and targeted correctionsW6One onboarding quarter run under the supplier approver, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6When the approval record validates, Agent Care picks the agent up.
DurationSix-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.
