Due Diligence 1 September 2026 · Gumshoe

ASIC's Broker Review: Disclosure Gaps and Onboarding Risks

The email looked legitimate. Same supplier name, same invoice format, same payment amount you'd processed last month — only the BSB and account number had changed.

The email looked legitimate. Same supplier name, same invoice format, same payment amount you'd processed last month — only the BSB and account number had changed.

That single altered detail, missed amid hundreds of routine payments, triggered an ASIC review into third-party onboarding failures across Australian financial services. The regulator's findings highlight a systemic risk: compliance officers now face personal liability when onboarding controls cannot demonstrate they took reasonable steps to verify counterparty identity before any funds moved.

That single altered detail, missed amid hundreds of routine payments, triggered an ASIC review into third-party onboarding failures across Australian financial services. The regulator's findings highlight a systemic risk: compliance officers now face personal liability when onboarding controls cannot demonstrate they took reasonable steps to verify counterparty identity before any funds moved.

This isn't about isolated slips; it's about the erosion of trust in the verification gate itself. When onboarding relies on static documentation or email confirmation without independent validation, the process becomes a theatre of compliance — one that collapses under the weight of volume or a sophisticated mimic. The stakes extend beyond recovered funds to potential civil penalties under the Corporations Act and disqualification orders that can end careers.

The Anatomy of an Onboarding Failure: Where Disclosure Gaps Create Liability

The failure often begins not with a forged document, but with a checked box. A supplier submits an ABN lookup printout and a voided cheque; the onboarding clerk files them as "verified" without cross-referencing ASIC Connect or performing a bank account validation. This satisfies the internal checklist but leaves a chasm between what the policy states and what the evidence actually proves.

Stated Control vs Actual Evidence Gap in Third-Party Onboarding
Stated Control (Policy/Procedure) Actual Evidence Gap (Common Practice)
Independent verification of identity and banking details Reliance on supplier-provided documents without external validation
Ongoing monitoring for changes to counterparty details Static onboarding; no periodic re-verification triggers
Documented audit trail of verification steps Checklist completion noted; underlying evidence not retained or inaccessible

The failure often begins not with malice but with misplaced efficiency. A procurement officer, under pressure to approve a new supplier for an urgent project, skips the independent verification step, accepting the counterparty’s self-certified ABN and bank details at face value. This shortcut is documented in the onboarding checklist as "verified," creating a false audit trail that satisfies internal governance but leaves the entity exposed to misdirection fraud or inadvertent dealing with an unlicensed intermediary.

Stated Control vs Actual Evidence Gap in Supplier Onboarding
Control ElementStated RequirementTypical Operational Reality
Initial ABN VerificationIndependent check via ABRReliance on supplier-provided ABN/invoice
Banking Detail ValidationConfirmation via bank letterAcceptance of emailed details or supplier portal entry
Change ManagementRe-verification on any banking detail changeAutomatic update upon supplier notification in ERP

This isn't merely an administrative oversight; it's a structural vulnerability where the stated control framework assumes honesty in disclosure that the operational process never verifies. The 'shadow broker' pattern identified over a decade ago — intermediaries posing as legitimate suppliers during onboarding only to intercept payments later — remains effective precisely because the onboarding checklist is treated as a ceremonial hurdle rather than a substantive barrier. Licensees often collect the required documents but fail to independently corroborate critical details like banking information or beneficial ownership against authoritative sources.

Beyond the Checklist: Operationalizing Best Interests Duty in Due Diligence

The shift from reactive compliance to operationalizing best interests duty means moving beyond collecting signed declarations to actively verifying that a broker or supplier’s disclosed risk profile matches observable reality. This requires embedding proactive checks — such as cross-referencing ABN details with ASIC Connect — into the onboarding workflow before any invoice is approved. Treating due diligence as a one-time gate creates a false sense of security; continuous monitoring is now the baseline expectation under evolving regulatory guidance.

The anticipated best interests duty report is expected to formalize this shift, setting benchmarks for how licensees must demonstrate they acted in clients’ best interests when selecting and managing third-party providers. Early indicators suggest the report will emphasize documented, repeatable processes over subjective judgment calls, particularly for high-volume supplier relationships where manual oversight consistently fails.

Proactive risk modelling transforms due diligence from a snapshot assessment into a continuous feedback loop. Instead of relying solely on initial declarations, leading teams now monitor supplier risk signals in real time — such as sudden changes in director associations flagged by ASIC Connect, or mismatches between declared business activity and actual transaction patterns in banking feeds. This approach acknowledges that a broker’s risk profile can deteriorate months after onboarding, particularly in volatile sectors like construction or labour hire where shadow broker networks historically exploited lagged verification cycles.

The shift from reactive compliance to proactive risk modelling requires embedding continuous monitoring into the supplier lifecycle, not treating onboarding as a one-off gate. For example, a supplier may pass initial identity verification but later undergo a change in control that introduces undisclosed related-party risks — a scenario where static checks fail but real-time ASIC Connect alerts on director or shareholder changes could trigger enhanced due diligence before further payments are released. This transforms due diligence from a documentation exercise into an operational control.

The best interests duty shifts the onus from ticking boxes to demonstrably acting in the client's or beneficiary's interest — here, the organisation's own financial and reputational position. When vetting a supplier, this means moving beyond verifying an ABN matches an invoice to assessing whether the entity's structure, ownership changes, or adverse findings in ASIC Connect could impair its ability to perform the contract honestly and competently. It requires linking due diligence findings to specific risk outcomes, not just collecting documents.

Proactive risk modelling operationalises this duty by treating supplier data as dynamic inputs. For instance, a change in beneficial ownership flagged via ASIC Connect — particularly if linked to a party with prior enforcement action under the Corporations Act — should trigger enhanced scrutiny before the next payment cycle, not wait for an annual review. This transforms due diligence from a compliance artefact into a real-time risk mitigant.

Common failure metrics reveal why reactive checks fail: identity verification often relies on outdated document uploads, and the average time to remediate a high-risk finding leaves an ample window for fraudulent payment cycles. Embedding real-time validation gates at PO creation and payment initiation closes this gap, converting duty of care into enforceable process.

Uncommon Insights

The most dangerous invoice fraud isn’t caught because it looks perfect — it’s missed because the reviewer is exhausted. Processing 200 invoices a week turns vigilance into a background task, where an unusual sender domain or a one-digit BSB tweak blends into the noise. This isn’t lapsed attention; it’s cognitive overload baked into the process design.

Consider the mechanics of anomaly detection under load: when an AP clerk processes 200 invoices weekly, each decision averages under 90 seconds. At that pace, the brain defaults to pattern-matching, not verification. A sender domain shifting from @trustedsupply.com.au to @trustedsupply-support.net isn’t flagged as suspicious — it’s filed as “IT updated something.” This isn’t negligence; it’s the predictable outcome of a system that demands flawless microscopic scrutiny while delivering firehose volume.

The real danger isn't that staff miss the odd anomaly; it's that the system assumes they won't. When compliance relies on human spot-checks at volume, you're not managing risk — you're pricing in an expected failure rate. Think of it like safety margins in engineering: if your process only works when everyone is perfectly rested, attentive, and unhindered by cognitive load, it has no margin for error. Yet that's exactly how many onboarding and invoice approval workflows are designed — as if the 197th invoice of the day receives the same scrutiny as the first.

This creates a perverse incentive where the most diligent employees become the biggest liability. They develop workarounds — keeping personal lists of trusted suppliers, flagging oddities in notebooks — precisely because the formal process fails them under load. But these adaptations are invisible to auditors, unrecorded in systems, and vanish when the employee leaves. The control environment isn't weak; it's actively undermined by its own design, which mistakes procedural compliance for actual risk mitigation when human fatigue is a guaranteed variable in the equation.

The fatigue factor isn't a flaw in the people; it's a flaw in the process architecture that treats humans as infallible scanners. When you design controls that require sustained, high-fidelity attention across hundreds of routine transactions, you embed an assumption of unlimited cognitive capacity — a capacity that simply doesn't exist. This isn't about lapses in vigilance; it's about the inevitability of vigilance decay under load, a principle as reliable as gravity in any high-throughput operational environment.

ASIC s Broker Review Disclosure

Framing this as human error lets the system off the hook. It shifts focus to training more, trying harder, when the real fix is reducing the cognitive load through automation and intelligent gating. The most dangerous invoices aren't the obvious forgeries; they're the ones that slip through because the 197th check felt identical to the first, and the system was never built to detect that sameness as a risk signal in itself. True resilience comes from designing for the tired, distracted, overworked operator — not despite them.

Key Takeaways

CFOs and procurement heads must treat third-party onboarding as a pre-commitment control point, not a back-office formality. Mandate technology-backed due diligence gates — such as real-time ABN/ACN validation, continuous adverse media screening, and automated bank detail change verification — that trigger hard stops before any invoice is processed or payment authorised. These gates should be non-negotiable and embedded in the ERP or procure-to-pay workflow, removing reliance on manual checks that degrade under volume.

The cost of remediation — including ASIC enforcement actions under the Corporations Act, potential civil penalties, and reputational harm — consistently outweighs the investment in automated onboarding protocols. ASIC’s ongoing scrutiny, highlighted in its shadow brokers review and anticipated best interests duty report, confirms that procedural checkboxes are insufficient; regulators expect demonstrable, ongoing risk mitigation. Investing in intelligent gating isn’t a compliance cost — it’s a capital preservation strategy.

One specific mechanism gaining traction is the use of cryptographic hashes for supplier bank account details. Instead of storing or transmitting raw BSB and account numbers, systems generate a unique, one-way hash of the verified details at onboarding. Any subsequent payment instruction must present bank details that hash to the exact same value; even a single digit alteration produces a completely different hash, triggering an automatic block. This eliminates the risk of transcription error or social engineering attempting to mimic a legitimate change, as the verification is mathematically certain rather than reliant on visual comparison by fatigued staff.

  • Embed cryptographic verification at onboarding: Require suppliers to provide a one-way hash of their bank details during initial vetting, making any subsequent alteration mathematically impossible to accept without triggering an automatic block.
  • Automate pre-payment validation gates: Integrate real-time checks against ASIC Connect, ABN Lookup, and adverse media feeds directly into your ERP or AP workflow before approving any supplier master file change.
  • Shift liability through contractual tech standards: Mandate in supplier contracts that all banking detail updates must pass your automated cryptographic verification system, transferring the burden of proof to the supplier.
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.