Supplier Bank Detail Change Verification, Automated

What the service is

AiStaffo sets up an AI worker that collects every request to change an existing supplier's bank details from email, the vendor portal and phone notes into one queue, flags the request and any open payment due to the new account, creates a callback task that uses the phone number already on the approved vendor record, logs the verification, and routes the change for a second-person approval that must be recorded before any payment goes to the new account.

Who it is for

The service suits any business that pays suppliers by bank transfer and receives bank change requests from time to time. That includes a five-person firm that pays a few freight agents and a group with thousands of staff and a large supplier base. The common pattern is the same. A person in accounts payable receives a message that says the supplier has moved its bank, the payment run has no way to know whether the message is genuine, and the decision rests on one inbox.

Why the callback matters more than the email

Bank detail changes are a favourite target for fraudsters. The FBI's Internet Crime Complaint Center reported about 2.77 billion US dollars in business email compromise losses for 2024, making it one of the most costly fraud types the centre tracks. In the 2025 Payments Fraud and Control Survey by the Association for Financial Professionals, vendor impersonation rose to 45% of organisations in the 2024 data, an increase of 11 percentage points in one year. The attack usually does not need malware. It needs a convincing message and a payment team that acts on it.

The reason a callback works is that the attacker controls the email and often the phone number supplied with it. A callback to a number recorded before the request breaks that chain. Fraudsters have also been known to change a vendor's phone number or email in the master record first, so the callback reaches them. The control therefore depends on the vendor record being protected and its contact details being stable.

What is included

• One intake queue that receives bank-change requests from email, the vendor portal and phone notes, with a case reference for each.
• An automatic flag on the vendor record and on every open payment due to the new account, with the payment held until approval is logged.
• A callback task that shows the phone number from the approved vendor record and does not display the number given in the request.
• A verification record for each case: who made the call, when, through which channel, who answered, and the result. Full account numbers are kept out of the tracker.
• Routing to a second approver, who must be a different person from the one who made the callback.
• A monthly exception list of every bank change that has no callback record, for review by the finance lead.
• A one-page written procedure that matches the process map and the approval matrix you approve.

How it runs

1. Audit. We look at the last twelve months of supplier bank changes, the systems that hold vendor records and payments, the people who can edit bank fields, and the approval rules in place today. The output is a short list of gaps and volumes.
2. Process map. The current path from request to payment is drawn step by step, including the points where a person can edit a bank field without a second check. You confirm the map and the approval matrix before anything is built.
3. Build. The intake queue, flags, payment hold rule, callback task, verification record and approval routing are configured in the tools you already use. Nothing is set to release a payment without a logged approval.
4. Run. The system works in parallel with your existing process for an agreed period. Each case is compared with what your team did, and mismatches are reviewed before the new path becomes the only path.
5. Support. AiStaffo keeps the queue, rules and callback task running, updates them when your approval matrix or supplier contacts change, and produces the monthly exception list.

What you provide

You provide read access to the vendor master file, access to the accounts payable system and any mailbox or portal where requests arrive, your approval matrix with named approvers and their limits, and a current list of the callback numbers for each supplier. You also provide a sample of recent bank change cases, so the audit can test how the current process handled them. A named finance owner needs to sign off the process map and the exception rules.

Typical timeline

The table below is a planning scope for one payables team using one accounts system and one approval chain. The audit confirms the final plan.

What it does not cover

A callback confirms that the supplier asked for the change. It does not prove that the new account belongs to the supplier. Account ownership checks through a bank or a validation provider are a separate step, and this service does not include them. Forged bank letters attached to a request are also outside what the system can judge, so a person still reviews any supporting document and decides whether it is credible.

The system does not decide that a change is genuine, and it does not approve anything. A finance person makes the callback or reviews its record, and an authorised approver makes the final decision. The service also does not onboard new suppliers, does not change the bank's own payment rails, and does not cover staff payroll bank changes.

Some costs come with the control. A payment hold can delay a legitimate payment when a supplier is slow to answer the phone, and a stale callback number on the vendor record will stall a change until it is corrected. If your business changes supplier bank details only a few times a year and already has a tight, documented callback routine, a shared checklist may be enough and this service may be more than you need. Results depend on your own volumes, records and approval rules, which the free audit measures.

Scenario for a mid-sized importer

Consider a distributor in Mumbai that receives a bank change from a packaging supplier on a Friday afternoon, with an invoice due Monday. Under the process described above, the request is logged, the open invoice is flagged, and the payment is held. The callback task directs the finance person to the number on the supplier record, not the number in the email. The second approver sees the callback result before the change is released. The same flow applies to a contractor in Leeds paying its own suppliers, with the same record and the same approval step.