Insights

AI scams: a payment-verification checklist for your finance team

10 October 2026

Strengthen payment verification with trusted-number callbacks, supplier bank-detail checks and second-person approval for Australian businesses.

National Trading Standards in the UK has released findings about consumers’ difficulty recognising AI-enabled scams. For Australian business owners and finance teams, the practical response is stronger payment verification, rather than expecting staff to recognise every fake voice, message or invoice.

According to Computer Weekly’s report on the National Trading Standards findings, 47% of surveyed UK adults struggled to distinguish legitimate online offers from AI-generated fakes. These are overseas consumer findings, not a measure of fraud exposure among businesses in Australia. They nevertheless highlight why a convincing request should never be enough to authorise a payment.

What the UK findings mean for business payments

National Trading Standards identifies techniques including cloned voices, fabricated video and fake websites in its AI Scam Watchlist. Its central warning is that AI can make familiar fraud methods more persuasive and easier to scale.

The business risk is straightforward: a criminal may impersonate a supplier asking for new bank details, or an executive requesting an urgent transfer. Good spelling, familiar branding and a recognisable voice do not establish authority.

Nor does every fraudulent request need AI. A compromised supplier mailbox can deliver a convincing instruction inside a genuine email conversation. Controls should therefore work whether the request involves synthetic media, account compromise or simple impersonation.

The aim is to verify the instruction through an independently trusted route before money moves.

Set payment verification triggers before an urgent request arrives

Write down which events require additional checks. At minimum, include:

  • A new supplier’s first payment.
  • Any change to an existing supplier’s bank account.
  • A request to pay an unrelated person or entity.
  • An urgent transfer outside the normal payment run.
  • Conflicting account details across an invoice, supplier record or email.
  • Instructions to bypass an approver or keep a payment secret.

Apply bank-change checks regardless of payment value. A small transfer can still send money to the wrong account and leave an unsafe supplier record ready for a larger payment.

Give staff explicit authority to pause payment without being penalised for delaying an urgent request. Name a primary approver and a backup so the process does not disappear when someone is on leave.

Call back using a trusted number

A callback is useful only when the contact details come from a source independent of the request being checked.

Use a number established during supplier onboarding or previously verified and stored in a controlled supplier record. Do not use a replacement number in the change request, its signature block, an attached invoice or a link supplied by the sender. Caller ID is not proof of identity either.

For each callback:

  • End the incoming call or stop the message exchange.
  • Retrieve the established contact number from your approved record.
  • Call a known, authorised supplier contact.
  • Confirm whether they requested the change, then reconcile the legal entity, account name, BSB, account number and effective date.
  • Record who confirmed it, when the call occurred and where you obtained the number.

Avoid simply asking whether the invoice is genuine. The invoice may be legitimate while its bank details have been altered.

If the established contact cannot be reached, hold the change. If the supplier says its telephone number has also changed, use your documented re-verification process rather than accepting both changes together.

Treat supplier bank changes as a controlled process

Separate a bank-detail amendment from routine invoice entry. Payment verification becomes weaker when the same person can receive an email, edit the supplier record and release funds without another check.

Use a change request or ticket that captures:

  • The supplier identity and reason for the amendment.
  • The previous and proposed banking details, with access restricted appropriately.
  • The original request and independent callback record.
  • The person entering the change and the person approving it.
  • Any affected invoices or payments already queued.

Do not automatically update supplier banking details from an invoice attachment. Supporting documents can help explain a change, but a bank letter or screenshot is not independent proof: documents can also be fabricated.

Check whether your accounting system records supplier amendments and restricts who can make them. Where supported, prevent an unapproved change from flowing into a payment run. After approval, check that any prepared payment file uses the verified details, not an earlier or manually substituted version.

Make second-person approval genuinely independent

A second approval should test the evidence, not just acknowledge that someone else completed a form.

The reviewer should confirm that the callback used an established number, the person contacted had authority, and the destination account matches the approved supplier record. They should also check the amount, invoice purpose and any unresolved exceptions.

Use separate user accounts. Shared finance logins make it difficult to establish who changed a record or approved a payment. Where available, configure banking controls so one person prepares the payment and another releases it.

For small teams, the second approver might be an owner or an authorised finance adviser. Define that arrangement in advance and give the reviewer appropriate access without sharing passwords.

An apparent instruction from the managing director should follow the same payment verification rules as any other request. Seniority is not an exception to the process.

Support the checklist with system controls

Payment verification works best alongside secure email, accounting and banking access. Review multifactor authentication, finance-user permissions, mailbox forwarding rules and alerts for unusual account activity.

Our Microsoft 365 hardening checklist covers supporting account and administration controls. These reduce opportunities for compromise, but do not independently establish whether a supplier’s banking instruction is legitimate.

Automation also needs a defined boundary. An AP/AR Automation Agent can match invoices to records and flag discrepancies; it should not treat an emailed bank amendment as authority to change the payment destination. Tech Engine’s managed AI agents run in a private Australian-hosted environment and retain human approval. Our guide to human approval in AI invoice processing explains where review belongs.

Test the process with a clearly labelled exercise: a familiar supplier requests new bank details shortly before payment day. Check whether staff pause, use the trusted number, record evidence and obtain independent approval.

If a suspicious payment has already been sent

Contact your bank’s fraud team immediately using a trusted contact route. Ask about stopping or recalling the payment; recovery is not assured. Do not wait until you have proved that AI was involved.

Preserve the messages, attachments, transaction references and approval records. Notify your finance lead and IT or security provider, and contact the genuine supplier through an established channel. Check for other queued payments using the same altered details.

If account compromise is suspected, have your IT team investigate access, sessions and forwarding rules. Report suspected cybercrime through the relevant official reporting channel, such as ReportCyber, and assess any contractual, insurance or privacy notification obligations.

Review the controls before the next payment run

A useful payment verification process answers three questions: who independently confirmed the instruction, which trusted contact route was used, and who approved the final destination?

Tech Engine can help review your cyber security and the access controls supporting your finance workflow. Call 1300 088 324, email sales@techengine.au or visit aiaas.au to discuss where your payment process needs stronger checks.

Want this applied to your business?

Request an AI Blueprint and we will map the processes worth automating first.

Request an AI Blueprint