Vendor & counterparty verification.
Confirm that vendors, suppliers, and counterparties, and their authorized contacts, are real before you add them to AP or release payments.
Book a demoThe scenario
Procurement adds a new supplier. AP receives updated contact details for an existing vendor. A partner portal submits onboarding data.
Each case asks the same question: did the real authorized representative of this organization confirm this?
What goes wrong today
- Onboarding checks validate documents, not ongoing authorization at execution.
- Email domains and PDFs are easy to forge.
- Counterparty records drift without cryptographic linkage to who approved each change.
What changes at execution
Foundry dispatches verification challenges to known authorized signers for that counterparty, matched by enterprise identity, aliases, and signing policy.
Approval produces a trust report bound to the onboarding or change artifact.
| Time | Request | Counterparty | Confirmed by | Status |
|---|---|---|---|---|
| 10:02 | New supplier | Kestrel Freight | –AskedAuthorized representative | ReceivedChallenge sentConfirmedRecord created |
| 09:40 | Contact change | Northwind Supply | Authorized representative | Released |
| 09:11 | New supplier | Aldgate Logistics | No answer | Held |
01Procurement submits a new supplier. No vendor record is created yet.02Foundry challenges the known authorized signers for that organization.03The supplier’s authorized representative confirms on their own device.04The trust report passes. The vendor record is created, bound to who confirmed it.
Soft gate, hard gate
Start with out-of-band verification via an operator console.
Graduate to hard gates in procurement, vendor master, or partner portals that block record creation until trust reports pass.
See it in actionEvidence for compliance
Third parties and internal audit can verify counterparty confirmations independently.
They no longer have to trust your vendor database alone.


