Due Diligence 16 November 2026 · Gumshoe

Preventing Payment Fraud: Auditing Supplier Email Security and Payment Reconciliation

An email lands from a supplier you've paid fifty times. The logo is perfect. The invoice number follows the sequence. Only the BSB and account number are new.

An email lands from a supplier you've paid fifty times. The logo is perfect. The invoice number follows the sequence. Only the BSB and account number are new.

The request comes from their real email address — because someone has been inside their inbox for weeks, reading the rhythm of your payment runs, learning which approvers sign off on Fridays, watching the exact language your AP team expects.

This isn't phishing. It's Business Email Compromise — a threat actor living inside a legitimate supplier mailbox, often for months, mapping your payment cadence and approval hierarchy. They don't need to spoof a domain when they own the real one. The invoice arrives from the correct address, with the correct history, referencing the correct PO. The only anomaly is the bank account.

Consider a typical case: a construction firm loses a progress payment when attackers intercept a genuine supplier email thread and insert updated banking details days before the scheduled payment. The AP team processes it — same supplier, same project, same approver. The funds clear to a mule account before the supplier notices they haven't been paid. In another scenario, a manufacturing buyer diverts funds after attackers compromise the vendor's finance controller mailbox and reply to a live payment confirmation thread with "urgent" revised details. The buyer's dual-authorisation control exists on paper — but both approvers rely on the email thread as verification.

The pattern repeats because the controls most teams rely on — callback to a number on the invoice, a second approver ticking the same PDF — verify the document, not the identity behind it. When the mailbox is compromised, the callback number rings the attacker. The second approver sees the same corrupted thread. The fraud succeeds not because the invoice looked wrong, but because the verification chain trusted the compromised channel.

Attackers exploit the gap between when a supplier's credentials are stolen and when the breach is detected — often weeks. During that window, every invoice, every payment confirmation, every "urgent" change request carries the full weight of the supplier's legitimate history. No amount of invoice-level scrutiny catches a threat actor who already sits inside the trusted relationship.

Beyond the Invoice: Vetting the Supplier's Digital Perimeter

You verified the invoice. The ABN matches. The bank details match the last payment. The email came from the supplier's actual domain — because the threat actor is sitting in their mailbox, not spoofing it. Invoice-level controls cannot catch a compromise that lives upstream of the document.

The risk moves the moment a supplier's credentials are stolen. From that point, every "urgent" change request, every revised payment schedule, every confirmation of banking details carries the full authority of the legitimate relationship. Your AP team is not fighting a fake invoice; they are fighting the supplier's own compromised identity.

Procurement usually onboards a supplier once — ABN check, insurance certificates, maybe a financial health screen — and treats the security posture as static. It isn't. A supplier who had MFA on email in 2022 may have disabled it for a legacy application last month. A supplier who enforced unique logins may have shared a mailbox password across three staff to clear a backlog. The control environment you approved at onboarding is not the one attacking you today.

Standard due diligence asks whether a supplier holds ISO 27001 or Cyber Essentials certification. Those frameworks prove a policy exists; they do not prove the control is active on the mailbox that just approved a $191,000 bank-account change. A certification audit samples controls at a point in time. Credential theft operates in the gaps between audits — shared mailboxes without MFA, service accounts excluded from conditional access, legacy IMAP/POP protocols still enabled on the tenant.

Procurement needs a living audit, not a certificate. That means requiring the supplier to demonstrate, on demand: MFA enforcement across every identity that can authorise payment changes, including service accounts and delegated mailboxes; conditional access policies that block legacy authentication; and a tested process for revoking access within hours when a key contact leaves. If a supplier cannot produce a current Entra ID sign-in log showing MFA challenges for their finance team, the certification on the wall is irrelevant to the payment you are about to approve.

Supplier Security Controls: Basic Check vs. Required Audit
Control AreaBasic Check (Onboarding)Required Audit (Ongoing)
MFA CoveragePolicy document states MFA enabledLive sign-in logs proving MFA on every finance mailbox, shared mailbox, and service account
Legacy AuthNot assessedConditional access policies blocking IMAP, POP, SMTP AUTH; protocol disablement verified
Access ReviewAnnual attestationQuarterly access certification for all identities with payment-change rights; offboarding SLA ≤ 4 hours
Compromise DetectionNoneMailbox forwarding rules, inbox rules, and delegate permissions monitored; alerting on anomalous sign-in locations
Change VerificationCallback to known numberOut-of-band verification mandated for any banking-detail change; logged in supplier's ticketing system with dual approval

The audit table is not a wish list — it is the minimum evidence a procurement team should demand before a supplier's next payment run. If a vendor cannot produce live sign-in logs showing MFA on every finance mailbox, or prove legacy protocols are blocked at the tenant level, their control environment has a gap wide enough for a credential-theft campaign to drive through. That gap is where the forwarding rule gets created, the delegate permission gets granted, and the "urgent" change-of-bank-details email originates — all from a legitimate, compromised account.

Contractual clauses that require suppliers to "maintain adequate security" are unenforceable without these specifics. Procurement should bake the audit requirements into the master services agreement as measurable service levels: quarterly access certifications with a four-hour offboarding SLA, continuous monitoring for anomalous sign-ins and mailbox rule changes, and a ticketed, dual-approval workflow for any banking-detail amendment. Suppliers who treat these as optional are signaling that their own finance process is not hardened.

Mandating Authentication: The MFA Compliance Checklist

MFA is not a binary switch — it is a set of implementation choices that determine whether a stolen credential still opens the finance mailbox. Procurement should require phishing-resistant authenticators for every identity that can approve a payment or change banking details. SMS, voice and push-with-number-matching are acceptable only as a transitional step; they remain vulnerable to fatigue attacks and SIM-swap takeovers that have already emptied Australian corporate accounts.

Equally critical is what the tenant blocks. Legacy authentication protocols must be disabled organisation-wide. If a supplier's tenant still permits basic auth, a credential harvested from a phishing page or a reused password list grants full mailbox access without ever touching an MFA prompt. The audit evidence is a tenant-level sign-in report filtered by authentication protocol showing no legacy auth events, or the control has not been implemented.

Session controls close the next gap. Procurement should require suppliers to enforce token lifetime limits with automatic revocation on password change, MFA method change, or admin-initiated revoke. Conditional Access policies that block access from non-compliant devices, anomalous locations, or impossible travel patterns must be documented and tested. The evidence is a Conditional Access gap analysis showing every financial identity covered by at least one policy that requires phishing-resistant MFA, compliant device state, and approved location.

Break-glass accounts are the exception that proves the rule. Suppliers should maintain emergency accounts that are excluded from Conditional Access, secured with hardware keys stored in separate physical safes, and monitored by alerting on any sign-in. Quarterly access reviews should confirm no standing guest invitations, no service accounts with mailbox permissions, and no delegated admin rights left over from old implementations. The checklist item is a signed attestation from the supplier's IT lead: date of last review, number of accounts remediated, and the next scheduled review.

Procurement contracts should embed these requirements as non-negotiable service levels, not aspirations. The same gate applies at renewal: no attestation, no purchase order. Gumshoe surfaces the intelligence that makes this enforceable — mapping the actual people behind the supplier's finance function, flagging when key contacts change, and correlating corporate events (mergers, restructuring, director changes) that historically precede credential-theft campaigns. The checklist is only as good as the signal that triggers it.

Dual-Authorization Workflows and Legal Exposure

Changing a supplier's bank details is the single highest-risk action in accounts payable, yet most ERPs still treat it as a routine master-data update. A single clerk, a compromised email, and a convincing PDF are all it takes to redirect the next payment cycle — often $100,000 or more — before anyone notices.

Dual authorization means the person who enters the change cannot be the person who approves it, and neither can be the requestor. The approver must verify the change through a channel the fraudster cannot intercept: a phone call to a pre-registered number, a video confirmation with a known contact, or a signed letter on company letterhead. Email confirmation alone fails this test because the inbox is the attack surface.

Consider a typical case: a buyer pays a fraudster instead of the real supplier. If the buyer's process consists of a single AP clerk clicking "approve" on an emailed request, a court may find the buyer failed to take reasonable steps to verify the instruction. The liability then sits with the buyer, not the supplier, and not the bank.

Reasonable steps, in practice, means a documented control that separates duties and forces out-of-band verification. The ERP workflow should enforce this: any change to BSB or account number triggers a mandatory second approver and an automatic alert to the supplier's primary contact on file. Without that audit trail, you are not defending a process — you are explaining a gap.

Segregation of duties breaks down the moment a single person can both request and approve a banking change. The ERP must enforce a hard stop: the user who submits the amendment cannot be the user who authorises it, and the authoriser cannot be the supplier's AP contact. That control needs to survive leave, resignation and system overrides — otherwise the exception becomes the rule.

Document the verification method in the same transaction record. A structured dropdown forces the approver to create evidence in real time. Free-text notes disappear under audit pressure; structured fields do not. The record then travels with the payment file, so the bank, the insurer and the court see the same trail.

Courts look for a verification chain that a reasonable business would build before handing over six or seven figures. If the only control is an email from the same compromised inbox that requested the change, the buyer wears the loss. The "reasonable steps" standard is not met by a policy document sitting on a share drive; it is met by a system that refuses to process the payment until a second, independent approver has confirmed the new details against a pre-registered contact method and logged the evidence.

Insurers apply the same lens. A cyber policy can exclude losses where the insured failed to maintain adequate controls — and the insurer's assessor will ask for the dual-authorisation log, the recorded verification call, and the timestamped audit trail. If the ERP cannot produce them in minutes, the claim is denied. The control is not the policy; the control is the software-enforced workflow that makes non-compliance impossible.

Uncommon Insights

Most organisations treat supplier verification as an accounts payable problem. It isn't. The decision to pay a new bank account is made months earlier, when a purchase order is raised against a supplier record that nobody has re-validated since onboarding. If the PO system accepts a supplier ID without confirming the human behind it, the fraud has already succeeded — AP is just the cashier handing over the money.

Embedding identity verification at the PO stage means every new supplier, and every material change to an existing supplier, triggers a live check before a single dollar is committed. Gumshoe checks the legal entity against the banking details on file, so the PO cannot be approved until they match. A supplier that changes its ABN, adds a director, or shifts its registered office flags automatically — no spreadsheet review required.

Escalation matrices fail when they rely on the AP clerk to decide what counts as suspicious. The threshold must be binary: any change to payment instructions — BSB, account number, SWIFT, intermediary bank, currency — routes automatically to a designated senior approver outside the payments team. No discretion. No "I know this supplier." The approver receives the original banking details, the new details, the supplier's written request, and the verification log showing who called whom and when. If the log is incomplete, the change is rejected. This removes the judgment call that fraudsters exploit.

Suppliers resisting this level of scrutiny are signalling their own control gaps. A mature vendor can produce an audit trail showing their own internal approval for the banking change, the MFA log for the authorising officer, and the callback record confirming the request with their treasury team. If they cannot, the buyer should treat the change as unverified and pay the original account until the evidence exists. Gumshoe surfaces the corporate structure behind the supplier — current directors, shareholder changes, registered address shifts — so the approver can cross-reference the request against the legal entity, not just the email signature.

Embedding identity verification at the PO stage forces the risk decision upstream, where the commercial relationship is still fresh and the stakes are visible. When a new vendor is onboarded, procurement captures the authorised signatories, their verified contact channels, and the supplier's internal approval chain for banking changes. That dataset travels with the PO through to AP, so the payments team never has to reconstruct trust from an email thread. If a change request arrives that doesn't match the onboarding record — different signatory, missing internal approval reference, callback to an unregistered number — the system blocks it before a single dollar moves.

Gumshoe automates the intelligence layer beneath this workflow. It maps the supplier's current directors, ultimate beneficial owners, and any ASIC-registered address or shareholder changes in the last 90 days. When a banking amendment lands, the approver sees a live corporate snapshot alongside the supplier's audit trail: internal approval minutes, MFA logs for the authorising officer, and a timestamped callback record to the supplier's treasury function. If the supplier cannot produce that trail within four business hours, the change sits in quarantine and the original account stays active. Fraudsters rely on urgency to bypass scrutiny; a hard SLA on evidence turns urgency into a control.

That trail must be the supplier's own, not the buyer's reconstruction. Procurement should require every strategic supplier to maintain and produce, on demand, a complete audit log of their internal payment-change process: who requested the change, who approved it, the MFA event that authenticated each approver, and the outbound verification call placed to the buyer's registered treasury contact. If a supplier cannot produce that log, the buyer treats the change as unverified and the original account remains active. No exceptions for "system upgrades" or "staff on leave" — the control is the supplier's obligation, not the buyer's goodwill.

Internally, the escalation matrix removes discretion. Any amendment to payment instructions — BSB, account number, SWIFT, payee name — is escalated for senior sign-off before the next payment run. The approver sees the supplier's audit trail, the Gumshoe corporate snapshot, and the PO-recorded authorisation chain in a single view. If any element is missing or inconsistent, the change is quarantined and the supplier is notified in writing that payments will continue to the previously verified account until the full evidence package is supplied. Urgency is the fraudster's lever; a hard SLA on evidence turns that lever into a lock.

Preventing Payment Fraud Auditing Supplier

Key Takeaways

The fraudster's advantage is asymmetry: they study your supplier's org chart, email cadence and approval gaps while you rely on a PDF invoice and a phone number that may have been compromised weeks ago. Gumshoe flips that asymmetry by continuously mapping the supplier's key financial contacts — CFO, treasury lead, AP manager — and flagging corporate changes (directorship shifts, address updates, ASIC charges) the moment they hit the public record. When a payment-change request arrives, you already know whether the person authorising it still holds the role they held at onboarding, or whether the company has quietly restructured its finance function.

That intelligence feeds a strict escalation process: any amendment to BSB, account number, SWIFT or payee name triggers an automatic hold and routes to the CFO or delegated finance director with a single evidence package — supplier audit trail, Gumshoe corporate snapshot, PO-recorded authorisation chain. No senior sign-off, no payment. The SLA is four business hours for the supplier to produce their internal log; missing or inconsistent elements keep the original account active. Urgency is the fraudster's lever; a hard evidentiary deadline turns it into a lock.

  • Continuous identity mapping — Gumshoe monitors ASIC records in real time so you know the moment a supplier's CFO, treasury lead or AP manager changes, not weeks later when a fraudulent payment request arrives.
  • Corporate-change alerts as early warnings — Directorship shifts, registered-office updates and ASIC charges are flagged instantly, giving you the context to reject a payment-change request before the money leaves.
  • Non-negotiable escalation matrix — Any amendment to BSB, account number, SWIFT or payee name triggers an automatic hold and routes to the CFO or delegated finance director with a single evidence package.
  • Four-hour evidentiary SLA — The supplier must produce their internal audit log within four business hours; missing or inconsistent elements keep the original account active and the payment blocked.
  • Urgency neutralised by process — Fraudsters rely on pressure; a hard deadline and a complete evidence pack turn that lever into a lock.
VERIFY NOW

Run a free supplier check in seconds

Search by business name, ABN, or ACN. Instant PASS/WARN/FAIL across 8 verification signals.

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.