Skip to main content

Help guide

Suspected business email compromise: what to do first

If a payment request or business email looks suspicious, pause the payment and stop communicating through the suspect thread. Contact your organisation’s incident lead using a known, trusted channel. If money has been sent, or bank details may have been exposed, contact your bank immediately using a number you already trust. Do not wait for proof that a scam has occurred.

This guide is for finance staff and business owners dealing with an unexpected payment change, a suspicious login or a possible email-account compromise. The aim is to prevent further payments, get the right people involved and preserve useful information—not to conduct your own investigation.

First actions: stop, contact and record

  1. Hold the payment or requested change. Do not update supplier or payroll bank details, approve the invoice or send sensitive information while the request is in doubt. Tell the person responsible for approvals that the request is on hold.
  2. Call the bank immediately if money has moved or financial details may be exposed. Use a number from your bank card, banking app or another previously verified source—not one in the suspicious message. Ask what can be stopped or recalled. Recovery is not guaranteed.
  3. Notify your incident lead. Use a known phone number or another trusted channel, preferably from a device and account not suspected of compromise. If you cannot reach that person, contact your business owner, finance manager or authorised IT provider. Do not delay the bank call while looking for an internal contact.
  4. Keep the original message and make a brief record. Do not reply, click links or open attachments in the suspect message. Ask the incident lead how to preserve and share evidence safely.

Scamwatch’s business email compromise guidance recommends checking payment changes by calling the business on an independently sourced number and contacting the bank immediately if affected.

Suspected email compromise

Stop. Escalate. Verify. Preserve.

  1. Stop Pause a payment or change that has not yet been made.
  2. Escalate If money was sent, call the bank immediately; notify your incident contact.
  3. Verify Use a trusted number already held independently of the message.
  4. Preserve Keep the message and relevant records as directed by the responder.

Do not wait for a callback before contacting the bank if money was sent. Do not reply to the suspicious message.

Verify the request independently

Use a supplier or colleague’s phone number from a previously verified record. Do not use the number in the suspicious email, its attachment, a reply in the same thread or the number supplied by an unexpected caller. If the old contact is unavailable, establish another contact independently through your normal supplier-verification process. Pressure to hurry or keep the change secret is a reason to stop, not to skip approval.

Example callback: “Hello, I’m calling about a request to change the bank details on an invoice. I used the number we already have for your business. Can you check your records and confirm whether you requested the change?” Ask the verified contact to state the correct details from their own records and compare them through your approved process. Do not read the new details out first as the means of verification.

If you cannot reach a verified person, the details do not match, or the explanation remains uncertain, keep the payment on hold and escalate. A genuine-looking logo, familiar sender name or existing conversation is not proof: a criminal may imitate a business or use an accessed account.

If a payment has already been sent

Tell your bank that you suspect a fraudulent payment and ask it to act on any pending transactions. Follow its instructions, including how to provide transaction details securely. Note who you spoke to, when and any reference number. If another business or customer may have paid the wrong account, tell your incident lead so that the affected party can be contacted through a verified channel and asked to call its own bank promptly.

Do not send passwords, PINs, one-time codes or recovery codes to anyone claiming to be helping. Contacting the bank quickly may limit further harm, but it does not ensure money will be recovered.

Choose the right route

Contact the people who can act

  1. Internal lead Use an established, trusted incident or IT contact.
  2. Bank If money was sent, contact the bank immediately using a known channel.
  3. Cyber reporting Check the Australian Cyber Security Centre reporting guidance.
  4. Evidence Follow the authorised responder’s instructions before deleting material.

Reporting and recovery depend on the situation; do not assume funds can be recovered.

If a mailbox or login may be compromised

Tell the incident lead immediately if you entered credentials, approved an unexpected sign-in, noticed messages you did not send or saw an unfamiliar login. A suspicious payment email alone does not establish that your own mailbox was accessed; it may be an impersonation or involve another organisation’s account. Either way, the request needs checking.

Leave containment and account recovery to your authorised IT or security responder, following the organisation’s incident plan. Do not independently reset or wipe a device, delete messages, change mailbox rules or disconnect the network. The responder can balance prompt account protection with evidence preservation. The Australian Cyber Security Centre’s recovery guidance describes account-security checks and notifying affected contacts.

A simple incident note card

Make a short note in an approved, access-controlled place. For example: “Accounts received a bank-details change request this morning. Payment is on hold; supplier callback not yet completed. Incident lead contacted by phone.” Add only what helps the responder:

  • When the request or suspicious activity was noticed, and the relevant invoice or transaction reference.
  • Whether a payment is on hold, pending or sent; whether a link was clicked or information was entered, without recording the secret itself.
  • Who was contacted, when, the next action owner and any bank or official report reference.
  • Where the original message and any other evidence are held, as directed by the incident lead.

Do not include passwords, codes, full bank details, payment-card details or unnecessary personal information in a general support message. Avoid forwarding the suspect email widely; ask the responder for an authorised way to share it.

Report it and get human help

The Australian Government’s cyber reporting page offers separate paths to report cybercrime, including scams, to police and to report a cyber security incident to the Australian Cyber Security Centre. Choose the path that matches what happened. For guidance by phone, the Australian Cyber Security Hotline is 1300 CYBER1 (1300 292 371).

You can also report suspicious contact to Scamwatch. A Scamwatch report does not replace an urgent call to the bank or a police report. If personal information may be involved, ask your privacy lead or a qualified adviser to assess the situation promptly against the OAIC’s data-breach guidance; notification requirements depend on the circumstances.

Before releasing a held payment: make sure the request has been independently verified, your normal approval process has been completed and the incident lead has confirmed how to proceed. If any of those remain uncertain, leave the payment on hold and seek further help through a trusted channel.

Sources and further reading