Cybersecurity guides

Practical business guide

A supplier changed their bank details. What should your team check?

A practical payment-check workflow for small businesses: pause, verify independently and record the decision before changing supplier details.

AIT Technology · Published and checked

Accounts administrator making a verification call beside an invoice and laptop
AI-generated editorial illustration; fictional scene.

An invoice arrives in a familiar email thread. The supplier says their bank account has changed and asks for payment today. It might be genuine, but a familiar name or conversation is not enough to approve the change. Give your team a repeatable way to check it.

1. Pause the change and the payment

Keep the existing supplier record unchanged while you investigate. Do not use a small test payment as your identity check: receiving money would only show that the destination account can receive it. Separate the question “is this invoice due?” from “have we verified the new destination?”.

2. Contact the supplier independently

Use a contact route established before the request, such as the number held in your approved supplier record. If you need to find a number, navigate independently to the organisation's official website. Avoid the telephone number, links and reply instructions supplied in the suspicious message. NCSC advises contacting the organisation directly through independently sourced details when a message is doubtful.

Ask your established contact whether the change is genuine and who is authorised to confirm it. If you cannot reach a suitable person, leave the change pending. Pressure to act quickly is a reason to follow the process carefully.

3. Record a clear decision

For a small team, a simple internal change record can be enough to make the check visible. Decide who verifies the request and who approves the update. Where practical, use different people for those steps. This is a suggested workflow, not a guarantee against fraud.

  • Supplier and invoice reference.
  • Date the request arrived and who received it.
  • Independent contact route used and person reached.
  • Verification outcome, approver and update date.

Keep financial information in the system your business has approved for it. Do not put real account details into a public AI chatbot to ask whether the request “looks safe”.

4. Rehearse with a fictional invoice

Use a made-up supplier and no real bank details. Ask a colleague to work through an urgent change request while the usual approver is absent. Can they find the trusted number? Do they know who can approve the update? Does the payment remain paused until the check is complete? Fix gaps in the process before a genuine request arrives.

If a payment may already have gone to the wrong account

Contact your bank immediately through a trusted channel and tell the person responsible for finance or incident response. Preserve the original messages and payment records. Follow the bank's instructions; do not assume that recovery is possible or delay the call while investigating yourself.

Source and scope

Checked 18 November 2026: NCSC: spotting cyber attacks. The change log and rehearsal above are AIT's practical suggestions. This guide does not certify a payment, assess a particular message or replace your bank's fraud response.

Also read: secure your business accounts.