How-To 2 June 2026 · Gumshoe Team

The Three-Second Check That Prevents a Five-Figure Mistake

Most invoice fraud isn't a heist. It's a typo you were meant to trust. Three habits defuse most of it — and the third one is the whole game.

Most invoice fraud isn't a heist. It's a typo you were meant to trust. An email arrives from a supplier you've paid a dozen times, asking you to update their bank details. The logo is right. The invoice number follows the sequence. Only the BSB and account number are new. In a busy accounts-payable week, that payment goes out — and the money is gone before anyone notices the real supplier never sent the email.

It works because it doesn't look like fraud. It looks like admin.

Why the Classic Controls Keep Failing

The accounts payable team at most Australian businesses has some version of the same controls: check the ABN, look up the business online, maybe call the supplier if something feels off. These controls are not useless. But they are incomplete — and increasingly insufficient against the way payment fraud actually operates in 2026.

An ABN lookup confirms a number is registered. It does not tell you that the email requesting the banking change was sent from a domain registered three weeks ago. It does not tell you the sender's domain has no DMARC policy, meaning anyone can impersonate it. It does not tell you the invoice attached to the email came from a server in Eastern Europe. The gap between what a basic ABN check reveals and what you need to know to safely authorise a payment is exactly where business email compromise lives.

The ACCC's Scamwatch data shows payment redirection fraud remains a serious threat to Australian businesses, with significant losses reported. Attackers increasingly tailor their approaches, researching victims to craft convincing emails that mimic legitimate business communications.

The First Habit: Treat Banking Changes as Verification Events

Legitimate bank-detail changes almost never arrive by email alone. When that email arrives — however legitimate it looks — the response should be a phone call. Not to a number on the email. Not to a number on the new invoice. To the number already in your accounting system, or to a number found independently.

This single control defeats the vast majority of payment-redirection attacks. It costs one phone call. It requires no technology. It has no downside if the request is genuine — the supplier will confirm it took two seconds. If the request is fraudulent, that phone call is the moment the fraud fails.

The call-back control sounds obvious. It is. It is also skipped routinely — because the email looks right, because the week is busy, because it feels unnecessarily suspicious to call a supplier you have paid for years. The fraudster is counting on exactly that calculation.

The Second Habit: Check the Sender, Not the Display Name

Most email clients display the sender's name, not the underlying address. "Accounts — Smith Plumbing" looks identical whether it arrived from [email protected] or from [email protected]. Checking the actual address by clicking or hovering over the sender name is a simple step that is almost never done.

For a supplier whose invoices have always arrived from @smithplumbing.com.au, a banking-change request from any other domain is an immediate red flag. But the check goes further than the domain itself. A recently registered domain — even one that looks legitimate — is a strong indicator of a fraudulent setup. Legitimate suppliers have domains with history. Fraudulent setups use domains registered shortly before the attack, because they only need the domain to survive long enough to collect one payment.

Checking domain age via WHOIS or certificate transparency is quick. A structured verification tool surfaces it automatically alongside email infrastructure checks. It shows up in almost every payment-redirection fraud investigated after the fact.

The Third Habit: Make Verification a Step, Not a Scramble

The reason these checks get skipped is not negligence. It is friction. If verifying a supplier requires opening four browser tabs, knowing how to read a WHOIS record, and spending thirty minutes cross-referencing government registers — it will not happen consistently. It will happen when someone has time, which in a busy AP function means it will happen rarely.

Typical manual verification time for a new supplier
Gumshoe automated verification across multiple checks
Simultaneous checks across ABR, ASIC, DNS, and reputation databases

The fix is not training people to be more careful. The fix is making the careful thing the easy thing. A verification that takes 60 seconds, runs automatically against ABR, ASIC, domain registrars, DNS records, and threat intelligence databases, and produces a timestamped report — is a verification that actually happens. Every time. For every supplier. As part of the standard workflow.

What a Complete Supplier Check Covers

A verification that is actually fit for purpose covers more than the ABN. The eight checks that matter are:

  • ABN status and age — check whether the ABN is active and how long it has been registered.
  • GST registration — confirm it is consistent with the entity type and claimed invoicing.
  • ASIC company status — verify the underlying company has not been deregistered while the ABN stays active.
  • Web presence — check whether a real website exists, on HTTPS, with an established history.
  • Domain age — check when the domain was first registered; a very recent registration can be a warning sign.
  • Email infrastructure — check whether SPF and DMARC are present and whether the domain is mail-capable.
  • Reputation — check whether the domain has appeared in phishing or spam threat databases.
  • Address consistency — confirm the registered postcode matches the stated state.

None of these checks is slow. Individually, each takes seconds. Run simultaneously and reported as a single assurance score, they take a minute. The result is a PASS, WARN, or FAIL on each dimension — showing whether this supplier warrants more scrutiny before money moves.

The Audit Trail That Saves You Twice

There is a second benefit to systematic verification that rarely gets discussed: it protects you even when fraud succeeds. A timestamped report showing that you verified this supplier on this date, across these checks, with these results, is evidence of reasonable due diligence. That evidence matters when you are talking to your insurer, your auditor, or your board about what went wrong.

"We checked the ABN" is not a demonstrable control; a saved verification report with a timestamp and a methodology is.

The money you don't lose is the best kind. But the paper trail that protects you when loss happens anyway is the second-best kind.

Uncommon Insights

One of the lesser-known aspects of the Australian Securities and Investments Commission (ASIC) regulations is that under the Corporations Act 2001, directors have a duty to exercise care and diligence in relation to the financial affairs of the company. This includes ensuring that adequate internal controls are in place to prevent and detect invoice fraud. By implementing the three habits outlined above, CFOs and accountants can demonstrate their commitment to fulfilling this duty.

The Australian Taxation Office (ATO) also plays a critical role in preventing invoice fraud, particularly in relation to the Goods and Services Tax (GST). Businesses can reduce the risk of invoice fraud by incorporating GST registration checks into their verification processes.

ASIC provides guidance on the obligations of Australian financial services licensees to have adequate risk management systems in place. While this guidance is primarily focused on financial services licensees, its principles can be applied more broadly to any business seeking to manage the risks associated with invoice fraud. By implementing robust verification processes and internal controls, businesses can demonstrate their commitment to risk management.

The use of Business Email Compromise (BEC) scams to facilitate invoice fraud is a growing concern in Australia. To mitigate this risk, businesses should consider implementing email authentication protocols to prevent spoofing and phishing attacks. By combining email authentication with the three habits outlined above, businesses can significantly reduce the risk of invoice fraud and protect their financial assets.

RUN A CHECK NOW

Verify Before You Pay

Gumshoe runs eight simultaneous checks across ABR, ASIC, domain registrars, DNS records, and reputation databases in under 60 seconds. Free for most checks. No account required to start.

Start verifying →
VERIFY A SUPPLIER
Run a free check in seconds

Search by business name, ABN, or ACN. Get a real-time PASS/WARN/FAIL report across 8 verification checks.

Start verifying →

Contains data sourced from the Australian Business Register and ASIC, © Commonwealth of Australia, licensed under CC BY 3.0 AU.