For many small and medium-sized enterprises, finance runs on a practical mixture of trust, speed and personal knowledge. The person who handles supplier invoices knows the regular contacts. The owner approves payments between other tasks. A supplier asks for a routine update, a customer says its bank details have changed, or a colleague forwards a message from a known account. The request looks administrative, and the instinct is to process it quickly so that nothing disrupts the relationship.
That is precisely the moment when a simple change can become a serious financial and operational risk. A request to alter payment instructions is not just a finance task. It is a governance and continuity issue. For a lean SME, the controls needed are not a large compliance function. They are a small number of repeatable checks that protect cash, supplier relationships and commercial reputation.
Why a bank-detail change deserves attention
Payment instructions carry authority. When a supplier or customer asks to change bank details, the request is effectively asking the business to redirect money. Fraudsters understand this. They often imitate a known contact, use a plausible reason for the change, and create pressure to act quickly. The message may arrive by email or messaging, may refer to a genuine invoice or contract, and may appear to come from an address that looks familiar.
The risk is higher for SMEs because finance roles are often combined. One person may set up a new payee, prepare the payment and reconcile the bank account. That concentration is efficient in normal times, but it means a single lapse can lead to a payment being sent to the wrong account. The business may also have fewer people available to challenge an unusual request, and the owner may be away from the detail until the payment has already left.
Treating the change as a governance issue changes the response. The question is no longer simply whether the request looks genuine. It is whether the business has a controlled process for confirming the change, recording it and reviewing what happened afterwards.
Verify through a separate channel
The most important control is out-of-band verification. A request to change bank details should be confirmed using a known phone number or an existing contact route, not the reply address or phone number supplied in the request itself. If the request appears to come from a supplier, call the supplier’s existing accounts contact. If it appears to come from a customer, use the contact details already held in the business’s records.
This is not a matter of distrusting a known contact. It is a recognition that email accounts and messaging profiles can be compromised, and that a request can be made to look authentic. The verification call should confirm the change directly with someone who can speak for the organisation. It should also establish the reason for the change, the effective date and the account details to be used. If the business cannot verify the change, the payment should be held rather than processed on the assumption that the request is genuine.
For SMEs, a short script can help. The person making the call should confirm the organisation, the contact’s identity and the new payment details. They should avoid using contact information from the request and should record that the check took place. The aim is not to create a bureaucratic trail for its own sake. It is to make sure that a payment is not redirected because someone replied too quickly to a convincing message.
Separate duties and control payee data
Segregation of duties is the second practical safeguard. No single person should be able to both create a new payee and approve the payment. In a small team, that separation may be difficult to achieve in a formal sense, but it can be approximated. The owner or a second authorised person can review new payees before payment. A bookkeeper or external adviser can act as a check. Bank permissions can be configured so that payment approval sits with someone other than the person who enters supplier details.
Supplier master data also needs discipline. New payees and changes to bank details should be reviewed under a controlled process, with a record of who requested the change, who verified it and when it was approved. A change log does not need to be elaborate. It does need to be consistent. Regular reviews of the payee list can identify duplicates, inactive suppliers or details that do not match the supporting records.
This matters beyond fraud prevention. Clean master data supports accurate payment runs, reduces failed payments and makes reconciliation easier. It also gives the business a clearer view of who it owes money to and how those obligations are being settled.
Reconcile, monitor exceptions and rehearse the response
Regular bank reconciliation is an opportunity to look for exceptions, not just to confirm that the numbers match. New payees, changed bank details and unusual payment patterns should be reviewed as part of the process. A payment that does not fit the normal pattern, or a supplier whose details have changed shortly before an invoice is due, deserves a second look. The point is to catch problems while there is still time to act.
Staff also need a simple route to report suspicious requests. Employees should know who to tell and what to do if a payment request feels unusual. A reporting route that is easy to use and free from blame is more likely to be used early. Scenario testing can help. A short exercise in which a team talks through a fake bank-detail change request can reveal where the process is unclear and who needs to be involved.
If fraud is suspected, the response should be prompt and structured. The business should contact its bank quickly, preserve records and review what happened. The control failure should be examined rather than treated as an isolated mistake. That review may lead to changes in approval limits, verification steps or staff training. It may also require communication with the supplier or customer whose identity was used.
Payment security is part of operational readiness. Within the Global SME Awards category, which focuses on durable SME practice, the bank-detail change is a useful test of whether a business has built systems that protect its cash and its relationships. The controls are not complicated: verify through a known channel, separate duties, keep payee data under review, reconcile with attention to exceptions and give staff a clear way to escalate concerns. A bank-detail change should prompt a pause, not a race.
