Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for accounts payable specialists

Vendor Bank Change Verification Agent

Every bank detail change verified by an independent callback before it is used

Vendor Bank Change Verification Agent: what goes in, what the agent does and what you get

What it does

Fake bank change requests are a common fraud, and a busy team can approve one in seconds. When a vendor asks to change bank details, this agent runs the verification steps. It reads the request, compares the sender address and domain to the vendor record, checks the new bank country and name against past details, and scores warning signs like urgency or a recent invoice spike. It prepares a callback script using the phone number already on file, never the one in the email. After the specialist logs the callback, it checks that the confirmed details match the request exactly, digit by digit. If anything differs, it holds the change and sets up a second contact. Only then does it prepare the change for a second person to approve. Edge case: the vendor's email domain differs by one letter, so the agent stops and routes it to fraud review.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Bank change request received 2 USES A TOOL Compare sender and domain to vendor record 3 DOES Score warning signs in the request 4 USES A TOOL Prepare callback script with number on file 5 DOES Specialist logs callback result 6 CHECKS THE RESULT Do confirmed details match the request exactly? If not: hold the change and prepare a second callback toa different contact. Back to step 4. 7 YOU APPROVE Second person approves the vendor master change 8 RESULT Verified change logged with evidence
Read the steps as a list
  1. Bank change request received
  2. Compare sender and domain to vendor record
  3. Score warning signs in the request
  4. Prepare callback script with number on file
  5. Specialist logs callback result
  6. Do confirmed details match the request exactly?If not: hold the change and prepare a second callback to a different contact. Back to step 4.
  7. Second person approves the vendor master changeThe agent waits here for your OK.
  8. Verified change logged with evidence

How it decides

It scores warning signs such as domain mismatch, new country and urgency. Any mismatch after the callback stops the change.

  • Domain differs from record: stop and send to fraud review
  • New bank country differs: require a second contact
  • Callback details differ in any digit: reject the request

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Warning signs that trigger fraud review
  • Number of contacts needed for high-value vendors
  • Payment hold period after a change
  • Who is the second approver

What keeps you in control

It always asks you first

  • Changing vendor bank details
  • Releasing a held payment

Hard limits

  • Never uses contact details from the request itself
  • Never changes bank details without two people

It stops when

  • Done: change verified and approved
  • Stop: callback not possible or warning signs too high

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensOn June 3 a request asked to move a vendor's payments to a new bank before a $48,000 invoice was due. The domain matched the record. The specialist called the number on file, but the contact gave an account ending 4471 while the request said 4417. The match check failed, so the agent held the change and set up a second callback, which confirmed the request was fake.

More agents for accounts payable specialists