Bank Detail Change Check Agent · Use case
How can we use an AI agent to check a request to change a vendor's bank details on our own infrastructure?
A bank detail change check agent reads one request to change where a vendor is paid, compares it with the vendor record and the history of changes to it, lists what does not fit, with the record behind each point, and prepares the call-back sheet your procedure asks for. A person calls the vendor on a number the company already holds, and a second person approves the change. The agent changes no record, contacts no one, and does not say whether a request is genuine.
The request looks like the vendor's.
So does a fraudster's.
- ✗ 01A request to change bank details arrives by email, on the vendor's letterhead, from an address that looks right, and the clerk who receives it has a payment run to prepare.
- ✗ 02The check that protects the company is a call to a number it already holds and a second approval, and under pressure that check is the step that gets shortened.
Where it stops for a person
Always. A person calls the vendor, and a second person approves the change.Always. It compares a request with the record, it does not clear it: a request with nothing on the list still goes through the call-back and the second approval, because whether a request is genuine is settled by the call, not by the agent. The number called is the one already on file, never one given in the request. The change is made by a person in your own system and approved by a second person.
It prepares the call-back.
Two people make the change.
Step · 01
A payables clerk or the vendor file owner uploads the request, or opens it from the ticket.
Step · 02
The agent reads what is asked: the vendor, the old and new account, who sent it and how it arrived.
Step · 03
It reads the vendor record and its change history through your own APIs: contacts on file, past changes, and payments falling due.
Step · 04
It lists what does not fit: a sender or a contact not on the record, an account in a new country or a new name, a second change in a short time, a large payment due soon, an account already held by another vendor.
Step · 05
It prepares the call-back sheet from your procedure, with the number already on file, and a person makes the call and a second person approves the change in your own system.
Reads from · connectors
Your own APIs
The request and its attachments, as uploaded files or from the ticket; the vendor record, its change history and the open payments to that vendor, read through your own APIs with the operations that change something left out; and your bank detail change procedure, indexed as a knowledge source.
Acts through · MCP servers
Nothing. It holds no tool that changes the vendor file, places a payment hold, releases a payment or sends a message. It calls and emails no one.
What you set up
- Index your bank detail change procedure and the call-back sheet as a knowledge source.
- Import the description of the API that holds the vendor file and its change history, and keep only the operations that read.
- Build the agent in Katonic Studio and test it on past requests, including any your team refused.
- Publish it to the vendor file owners, and give it no tool another agent uses to change a record or release a payment.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Vendor bank details and the requests to change them stay inside the company.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it change the vendor's bank details?
No. It has no tool that changes the vendor file. A person makes the change in your own system, and a second person approves it.
Does it call or email the vendor?
No. It prepares the call-back sheet. A person calls the vendor on a number the company already holds.
If the agent finds nothing wrong, is the request safe?
No. An empty list means the request fits the record, not that it is genuine. The call-back and the second approval still happen, every time.