Choosing a transaction monitoring solution in Australia is a different decision than it is anywhere else in the world — not because the technology is different, but because the regulatory and payment infrastructure context is.

AUSTRAC has one of the most active enforcement programmes of any financial intelligence unit globally. The New Payments Platform (NPP) makes irrevocable real-time transfers the default for domestic payments. And Australia's AML/CTF framework is mid-way through its most significant legislative reform in fifteen years, with Tranche 2 expanding obligations to lawyers, accountants, and real estate agents.

For compliance teams at Australian reporting entities, this means a transaction monitoring solution needs to do more than pass a vendor demonstration. It needs to perform under AUSTRAC examination and keep pace with payment infrastructure that moves faster than most legacy monitoring systems were designed for.

This guide covers what AUSTRAC actually requires, the criteria that matter most in the Australian market, and the questions to ask before committing to a solution.

What AUSTRAC Requires from Transaction Monitoring

The AML/CTF Act requires all reporting entities to implement and maintain an AML/CTF programme that includes ongoing customer due diligence and transaction monitoring. The specific monitoring obligations sit in Chapter 16 of the AML/CTF Rules.

Three points from Chapter 16 matter before any vendor evaluation begins:

Risk-based calibration is mandatory. Monitoring thresholds must reflect the institution's specific customer risk assessment — not vendor defaults. A retail bank, a remittance provider, and a cryptocurrency exchange each need monitoring calibrated to their own customer profile. AUSTRAC does not prescribe specific thresholds; it assesses whether the thresholds in place are appropriate for the risk present.

Ongoing monitoring is a continuous obligation. AUSTRAC expects transaction monitoring to be a live function, not a periodic review. The language in Rule 16 about real-time vigilance is not advisory — it reflects examination expectations.

The system must support regulatory reporting. Threshold Transaction Reports (TTRs) over AUD 10,000 and Suspicious Matter Reports (SMRs) must be filed within regulated timeframes. A monitoring system that cannot generate AUSTRAC-ready reports — or that requires significant manual handling to produce them — creates compliance risk at the reporting stage even when the detection stage works correctly.

The enforcement record illustrates what happens when monitoring falls short. The Commonwealth Bank of Australia's AUD 700 million AUSTRAC settlement in 2018 and Westpac's AUD 1.3 billion settlement in 2021 both named transaction monitoring failures as direct causes — not the absence of monitoring systems, but systems that failed to detect what they were required to detect. Both cases involved institutions with significant compliance investment already in place.

The NPP Factor

The New Payments Platform reshaped monitoring requirements for Australian institutions in a way that most global vendor comparisons do not account for.

Before NPP, Australia's payment infrastructure gave compliance teams a window between transaction initiation and settlement — a clearing delay during which a flagged transaction could be investigated before funds moved irrevocably. NPP eliminated that window. Domestic transfers now settle in seconds.

Batch-processing monitoring systems — even those with short batch intervals — cannot catch NPP fraud or structuring activity before settlement. The only viable approach is pre-settlement evaluation: risk assessment at the point of transaction initiation, before the payment is confirmed.

When evaluating vendors, ask specifically: at what point in the NPP payment lifecycle does your system evaluate the transaction? Vendors frequently describe their systems as "real-time" when they mean near-real-time or fast-batch. That distinction matters both for fraud loss prevention and for AUSTRAC examination.

6 Criteria for Evaluating Transaction Monitoring Solutions in Australia

1. Pre-settlement processing on NPP

The technical requirement above, stated as a discrete evaluation criterion. Ask for a live demonstration using NPP transaction scenarios, not hypothetical ones.

2. Alert quality over alert volume

High alert volume is not a sign of effective monitoring — it is often a sign of poorly calibrated thresholds. A system generating 600 alerts per day at a 96% false positive rate means approximately 576 dead-end investigations. That is not compliance; it is operational noise that crowds out genuine risk signals.

Ask for the vendor's false positive rate in production at a comparable Australian institution. A well-calibrated AI-augmented system should be below 85% in production. If the vendor cannot provide production data from a comparable client, that is itself informative.

3. AUSTRAC typology coverage

Australia has specific financial crime patterns that global rule libraries do not always cover — cross-border cash couriering, mule account networks across retail banking, and real estate-linked layering using NPP for settlement. These typologies are documented in AUSTRAC's annual financial intelligence assessments and should be represented in any system deployed for an Australian institution.

Ask to see the vendor's AUSTRAC-specific typology library and when it was last updated. Ask how the vendor tracks and incorporates new AUSTRAC guidance.

4. Explainable alert logic

Every AUSTRAC examination includes review of alert documentation. For each sampled alert, examiners expect to see: what triggered it, who reviewed it, the analyst's written rationale, and the disposition decision. A monitoring system built on opaque models — where alerts are generated but the logic is not traceable — makes this documentation impossible to produce correctly.

Explainability also improves investigation quality. An analyst who understands why an alert was raised makes a better disposition decision than one who cannot reconstruct the reasoning.

5. Calibration without constant vendor involvement

AUSTRAC requires monitoring thresholds to reflect the institution's current customer risk profile. Customer profiles change: books grow, customer mix shifts, new products are launched. A monitoring system that requires a vendor engagement to update detection scenarios or adjust thresholds will always lag behind the institution's actual risk position.

Ask specifically: can your compliance team modify thresholds, create new scenarios, and adjust rule weightings independently? What is the governance process for documenting calibration changes for AUSTRAC audit purposes?

6. Integration with existing case management

Transaction monitoring does not exist in isolation. Alerts feed into case management, case management informs SMR decisions, and SMR decisions must be filed with AUSTRAC within regulated timeframes. A monitoring solution that requires manual data transfer between systems at any of these stages creates delay, error risk, and audit trail gaps.

Ask for the vendor's standard integration points and reference implementations with Australian case management platforms.

Questions to Ask Before Committing

Most vendor sales processes focus on features. These questions get at operational and regulatory reality:

Do you have current AUSTRAC-supervised clients? Ask for references — not case studies. Speak to compliance teams at comparable institutions running the system in production.

How did your system handle the NPP real-time payment requirement when it was introduced? A vendor's response to an infrastructure change already in the past tells you more about adaptability than any forward-looking roadmap.

What is your typical time from contract to production-ready performance? Not go-live — production-ready. The gap between those two dates is where most implementation budgets fail.

What does your model retraining schedule look like? Transaction patterns change. A model trained on 2023 data that has not been retrained will underperform against current fraud and laundering patterns.

How do you handle Tranche 2 obligations for our institution? For institutions with subsidiary or affiliated entities in Tranche 2 sectors, the monitoring solution needs to be able to extend coverage without a separate implementation.

Common Mistakes in Vendor Selection

Three patterns appear consistently in post-implementation reviews of Australian institutions that struggled with their monitoring solution:

Selecting on cost rather than calibration. The cheapest system at procurement often becomes the most expensive when AUSTRAC examination findings require remediation. Remediation costs — additional vendor work, internal team time, reputational risk management — typically exceed the original licence cost difference many times over.

Underestimating integration complexity. A system that performs well in isolation but requires significant custom integration with the institution's core banking platform and case management tool will consistently underperform its demonstration capabilities. Ask for the implementation architecture documentation before signing, not after.

Treating go-live as done. Transaction monitoring requires ongoing calibration. Banks that deploy a system and then do not actively tune it — adjusting thresholds, adding new typologies, reviewing alert quality — see performance degrade within 12–18 months as their customer profile evolves away from the profile the system was originally calibrated for.

How Tookitaki's FinCense Works in the Australian Market

FinCense is used by financial institutions across APAC including Australia, Singapore, Malaysia, and the Philippines. In Australia specifically, the platform is configured with AUSTRAC-aligned typologies, supports TTR and SMR reporting formats, and processes transactions pre-settlement for NPP compatibility.

The federated learning architecture allows FinCense models to incorporate typology patterns from across the client network without sharing raw transaction data — which means Australian institutions benefit from detection intelligence learned from cross-institution fraud patterns, including coordinated mule account activity that moves between banks.

In production, FinCense has reduced false positive rates by up to 50% compared to legacy rule-based systems. For a team managing 400 daily alerts, that translates to approximately 200 fewer dead-end investigations per day.

Next Steps

If your institution is evaluating transaction monitoring solutions for 2026, three resources will help structure the process:

• AUSTRAC Transaction Monitoring Requirements — detailed breakdown of Chapter 16 obligations and what AUSTRAC examines in practice
• Transaction Monitoring Software Buyer's Guide — the 7 questions to ask any vendor before you sign
• What Is Transaction Monitoring? — the complete technical and regulatory overview

Or talk to Tookitaki's team directly to discuss your institution's specific requirements.

Australian banks lost AUD 2.74 billion to fraud in the 2024–25 financial year, according to the Australian Banking Association. That figure has increased every year for the past five years. And yet many of the banks sitting on the wrong side of those numbers had fraud detection software in place when the losses occurred.

The problem is rarely the absence of a system. It is a system that cannot keep pace with how fraud actually moves through modern payment rails — particularly since the New Payments Platform (NPP) made real-time, irrevocable fund transfers the standard for Australian banking.

This guide covers what genuinely separates effective fraud detection software from systems that look adequate until they are tested.

What AUSTRAC Requires — and What That Means in Practice

Before evaluating any vendor, it helps to understand the regulatory floor.

AUSTRAC's AML/CTF Act requires all reporting entities to maintain systems capable of detecting and reporting suspicious activity. For transaction monitoring specifically, Rule 16 of the AML/CTF Rules mandates risk-based monitoring — meaning detection thresholds must reflect each institution's specific customer risk profile, not generic industry defaults.

The enforcement record on this is specific. The Commonwealth Bank of Australia's AUD 700 million settlement with AUSTRAC in 2018 cited failures in transaction monitoring as a direct cause. Westpac's AUD 1.3 billion settlement in 2021 followed similar deficiencies at a larger scale. In both cases, the institution had monitoring systems in place. The systems failed to detect what they were supposed to detect because they were not calibrated to the risk actually present in the customer base.

The practical takeaway: AUSTRAC does not assess whether a system exists. It assesses whether the system works. Vendor selection that does not account for this distinction is selecting for demo performance, not regulatory performance.

The NPP Problem: Why Legacy Systems Struggle

The New Payments Platform changed the risk environment for Australian banks in a specific way. Before NPP, a suspicious transaction could often be caught during a clearing delay — there was a window between initiation and settlement in which a flagged transaction could be stopped or investigated.

With NPP, that window is gone. Funds move in seconds and are irrevocable once settled. A fraud detection system that operates on batch processing — reviewing transactions at the end of day or in periodic sweeps — cannot catch NPP fraud before the money has moved.

This is the single most important technical requirement for Australian fraud detection software today: genuine real-time processing, not near-real-time, not batch with a short lag. The system must evaluate risk at the point of transaction initiation, before settlement.

Most legacy rule-based systems were built for the batch processing era. Many vendors have retrofitted real-time capabilities onto batch architectures. Ask specifically: at what point in the payment lifecycle does your system evaluate the transaction? And what is the latency between transaction initiation and alert generation in a production environment?

7 Criteria for Evaluating Fraud Detection Software

1. Real-time processing before settlement

Already covered above, but worth stating as a discrete criterion. Ask the vendor to demonstrate alert generation against an NPP-format transaction scenario. The alert should fire before confirmation reaches the customer.

2. False positive rate in production

False positives are not just an efficiency problem — they are a customer experience problem and a regulatory attention problem. A system generating 500 alerts per day at a 97% false positive rate means 485 legitimate transactions flagged. At scale, that creates analyst backlog, customer complaints, and a compliance team spending most of its time reviewing non-suspicious activity.

Ask vendors for their false positive rate in a live environment comparable to yours — not a demonstration environment. Well-tuned AI-augmented systems reach 80–85% in production. Legacy rule-based systems typically run at 95–99%.

3. Detection coverage across all channels

Fraud in Australia does not stay within a single payment channel. The most common attack patterns involve coordinated activity across multiple channels: a fraudster may compromise credentials via phishing, initiate a small test transaction via BPAY, and execute the main transfer via NPP once the account is confirmed accessible.

A system that monitors each channel in isolation misses cross-channel patterns. Ask specifically: does the platform aggregate signals across NPP, BPAY, card, and digital wallet channels into a single customer risk view?

4. Explainability for AUSTRAC audit

When AUSTRAC examines a bank's fraud detection programme, they review alert logic: why a specific alert was generated, what the analyst decided, and the written rationale. If the underlying model is a black box — generating alerts it cannot explain in terms a human analyst can document — the audit trail fails.

This matters practically, not just in examination scenarios. An analyst who cannot understand why an alert was raised cannot make a confident disposition decision. Explainable models produce better analyst decisions and better regulatory documentation simultaneously.

5. Calibration flexibility

AUSTRAC requires risk-based monitoring — which means your detection logic should reflect your customer base, not the vendor's default library. A bank with a high proportion of small business customers needs different fraud typologies than a bank focused on high-net-worth retail clients.

Ask: can your team modify alert thresholds and add custom scenarios without vendor involvement? What is the process for calibrating the system to your customer risk assessment? How does the vendor support this without turning every calibration into a professional services engagement?

6. Scam detection capability

Authorised push payment (APP) scams — where the customer is manipulated into authorising a fraudulent transfer — are now the largest single category of fraud losses in Australia. Unlike traditional fraud, APP scams involve authorised transactions. Standard fraud rules built around unauthorised activity miss them entirely.

Ask vendors specifically how their system handles APP scam detection. The answer should go beyond "we have an education campaign" — it should describe specific detection logic: urgency pattern recognition, unusual payee analysis, first-time payee monitoring, and transaction amount pattern matching against known APP scam profiles.

7. AUSTRAC reporting integration

Threshold Transaction Reports (TTRs) and Suspicious Matter Reports (SMRs) must be filed with AUSTRAC within defined timeframes. A fraud detection system that requires manual export of alert data to a separate reporting tool introduces delay and error risk.

Ask whether the system supports direct AUSTRAC reporting integration or produces reports in a format that maps directly to AUSTRAC's Digital Service Provider (DSP) reporting specifications.

Questions to Ask Any Vendor Before You Sign

Beyond the seven criteria, these specific questions separate vendors with genuine Australian capability from those reselling global products with an AUSTRAC overlay:

• What is your alert-to-SMR conversion rate in production? A high SMR conversion rate (relative to total alerts) suggests alert logic is well-calibrated. A low rate suggests either over-alerting or under-reporting.
• Do you have clients currently running live under AUSTRAC supervision? Ask for reference clients, not case studies.
• How do you handle regulatory updates? AUSTRAC updates its rules. The vendor should have a defined content update process that does not require a re-implementation.
• What happened to your AUSTRAC clients during the NPP launch period? How the vendor managed the transition from batch to real-time processing tells you more about operational resilience than any benchmark.

AI and Machine Learning: What Actually Matters

Most fraud detection vendors now describe their systems as "AI-powered." That description covers a wide range — from basic logistic regression models to sophisticated ensemble systems trained on federated data.

Three AI capabilities are worth asking about specifically:

Federated learning: Models trained across multiple institutions detect cross-institution fraud patterns — particularly mule account activity that moves between banks. A system that only trains on your data cannot see attacks coordinated across your institution and three others.

Unsupervised anomaly detection: Supervised models learn from labelled fraud examples. They cannot detect novel fraud patterns they have not seen before. Unsupervised anomaly detection identifies unusual behaviour regardless of whether it matches a known typology — which is how new fraud patterns get caught.

Model retraining frequency: A model trained on 2023 data underperforms against 2026 fraud patterns. Ask how frequently models are retrained and what triggers a retraining event.

Frequently Asked Questions

What is the best fraud detection software for banks in Australia?

There is no single answer — the right system depends on the institution's size, customer mix, and payment channel profile. The evaluation criteria that matter most for Australian banks are real-time NPP processing, AUSTRAC reporting integration, and cross-channel visibility. Any short-list should include a live demonstration against AU-specific fraud scenarios, not just a product overview.

What does AUSTRAC require from bank fraud detection systems?

AUSTRAC's AML/CTF Act requires reporting entities to detect and report suspicious activity. Rule 16 of the AML/CTF Rules mandates risk-based transaction monitoring calibrated to the institution's specific customer risk profile. There is no AUSTRAC-approved vendor list — the obligation is on the institution to ensure its system performs, not simply to have one in place.

How much does fraud detection software cost for a bank?

Licensing costs vary widely — from AUD 200,000 annually for smaller institutions to multi-million-dollar contracts for major banks. The total cost of ownership calculation should include implementation (typically 2–4x first-year licence), integration, ongoing calibration, and the cost of analyst time lost to false positives. The cost of a regulatory enforcement action should also feature in a realistic TCO analysis: Westpac's 2021 AUSTRAC settlement was AUD 1.3 billion.

How do fraud detection systems reduce false positives?

Effective false positive reduction combines three elements: AI models trained on data representative of the specific institution's transaction patterns, ongoing feedback loops that update alert logic based on analyst dispositions, and calibrated thresholds that reflect customer risk tiers. Blanket reduction of thresholds lowers false positives but increases missed fraud — the goal is more precise targeting, not lower sensitivity.

What is the difference between fraud detection and transaction monitoring?

Transaction monitoring is the broader compliance function covering both fraud and anti-money laundering (AML) obligations. Fraud detection focuses specifically on losses to the institution or its customers. Many modern platforms cover both — but the detection logic, alert typologies, and regulatory reporting requirements differ.

How Tookitaki Approaches This

Tookitaki's FinCense platform handles fraud detection and AML transaction monitoring within a single system — covering over 50 fraud and AML scenarios including APP scams, mule account detection, account takeover, and NPP-specific fraud patterns.

The platform's federated learning architecture means detection models are trained on typology patterns from across the Tookitaki client network, without sharing raw transaction data between institutions. This allows FinCense to detect cross-institution attack patterns that single-institution training data cannot surface.

For Australian institutions specifically, FinCense includes pre-built AUSTRAC-aligned detection scenarios and produces alert documentation in the format AUSTRAC examiners review — reducing the gap between detection and regulatory defensibility.

Book a discussion with our team to see FinCense running against Australian fraud scenarios. Or read our [Transaction Monitoring - The Complete Guide] for the broader evaluation framework that covers both fraud detection and AML.

When authority is fabricated and trust is engineered, even the most implausible promises can start to feel real.

The Scam That Made Headlines

In a recent crackdown, the Philippine National Police arrested 15 individuals linked to an alleged investment scam that had been quietly unfolding across parts of the country.

At the centre of it all was a man posing as a “King” — a self-styled figure of authority who convinced victims that he had access to exclusive investment opportunities capable of delivering extraordinary returns.

Victims were drawn in through a mix of persuasion, perceived legitimacy, and carefully orchestrated narratives. Money was collected, trust was exploited, and by the time doubts surfaced, the damage had already been done.

While the arrests mark a significant step forward, the mechanics behind this scam reveal something far more concerning, a pattern that financial institutions are increasingly struggling to detect in real time.

Inside the Illusion: How the “King” Investment Scam Worked

At first glance, the premise sounds almost unbelievable. But scams like these rarely rely on logic, they rely on psychology.

The operation appears to have followed a familiar but evolving playbook:

1. Authority Creation

The central figure positioned himself as a “King” — not in a literal sense, but as someone with influence, access, and insider privilege. This created an immediate power dynamic. People tend to trust authority, especially when it is presented confidently and consistently.

2. Exclusive Opportunity Framing

Victims were offered access to “limited” investment opportunities. The framing was deliberate — not everyone could participate. This sense of exclusivity reduced skepticism and increased urgency.

3. Social Proof and Reinforcement

Scams of this nature often rely on group dynamics. Early participants, whether real or planted, reinforce credibility. Testimonials, referrals, and word-of-mouth create a false sense of validation.

4. Controlled Payment Channels

Funds were collected through a combination of cash handling and potentially structured transfers. This reduces traceability and delays detection.

5. Delayed Realisation

By the time inconsistencies surfaced, victims had already committed funds. The illusion held just long enough for the operators to extract value and move on.

This wasn’t just deception. It was structured manipulation, designed to bypass rational thinking and exploit human behaviour.

Why This Scam Is More Dangerous Than It Looks

It’s easy to dismiss this as an isolated case of fraud. But that would be a mistake.

What makes this incident particularly concerning is not the narrative — it’s the adaptability of the model.

Unlike traditional fraud schemes that rely heavily on digital infrastructure, this scam blended offline trust-building with flexible payment collection methods. That makes it significantly harder to detect using conventional monitoring systems.

More importantly, it highlights a shift: Fraud is no longer just about exploiting system vulnerabilities. It’s about exploiting human behaviour and using financial systems as the final execution layer.

For banks and fintechs, this creates a blind spot.

Following the Money: The Likely Financial Footprint

From a compliance and AML perspective, scams like this leave behind patterns — but rarely in a clean, linear form.

Based on the nature of the operation, the financial footprint may include:

• Multiple small-value deposits or transfers from different individuals, often appearing unrelated
• Use of intermediary accounts to collect and consolidate funds
• Rapid movement of funds across accounts to break transaction trails
• Cash-heavy collection points, reducing digital visibility
• Inconsistent transaction behaviour compared to customer profiles

Individually, these signals may not trigger alerts. But together, they form a pattern — one that requires contextual intelligence to detect.

Red Flags Financial Institutions Should Watch

For compliance teams, the challenge lies in identifying these patterns early — before the damage escalates.

Transaction-Level Indicators

• Sudden inflow of funds from multiple unrelated individuals into a single account
• Frequent small-value transfers followed by rapid aggregation
• Outbound transfers shortly after deposits, often to new or unverified beneficiaries
• Structuring behaviour that avoids typical threshold-based alerts
• Unusual spikes in account activity inconsistent with historical patterns

Behavioural Indicators

• Customers participating in transactions tied to “investment opportunities” without clear documentation
• Increased urgency in fund transfers, often under external pressure
• Reluctance or inability to explain transaction purpose clearly
• Repeated interactions with a specific set of counterparties

Channel & Activity Indicators

• Use of informal or non-digital communication channels to coordinate transactions
• Sudden activation of dormant accounts
• Multiple accounts linked indirectly through shared beneficiaries or devices
• Patterns suggesting third-party control or influence

These are not standalone signals. They need to be connected, contextualised, and interpreted in real time.

The Real Challenge: Why These Scams Slip Through

This is where things get complicated.

Scams like the “King” investment scheme are difficult to detect because they often appear legitimate — at least on the surface.

• Transactions are customer-initiated, not system-triggered
• Payment amounts are often below risk thresholds
• There is no immediate fraud signal at the point of transaction
• The story behind the payment exists outside the financial system

Traditional rule-based systems struggle in such scenarios. They are designed to detect known patterns, not evolving behaviours.

And by the time a pattern becomes obvious, the funds have usually moved.

Where Technology Makes the Difference

Addressing these risks requires a shift in how financial institutions approach detection.

Instead of looking at transactions in isolation, institutions need to focus on behavioural patterns, contextual signals, and scenario-based intelligence.

This is where modern platforms like Tookitaki’s FinCense play a critical role.

By leveraging:

• Scenario-driven detection models informed by real-world cases
• Cross-entity behavioural analysis to identify hidden connections
• Real-time monitoring capabilities for faster intervention
• Collaborative intelligence from ecosystems like the AFC Ecosystem

…institutions can move from reactive detection to proactive prevention.

The goal is not just to catch fraud after it happens, but to interrupt it while it is still unfolding.

From Headlines to Prevention

The arrest of those involved in the “King” investment scam is a reminder that enforcement is catching up. But it also highlights a deeper truth: Scams are evolving faster than traditional detection systems.

What starts as an unbelievable story can quickly become a widespread financial risk — especially when trust is weaponised and financial systems are used as conduits.

For banks and fintechs, the takeaway is clear.

Prevention cannot rely on static rules or delayed signals. It requires continuous adaptation, shared intelligence, and a deeper understanding of how modern scams operate.

Because the next “King” may not call himself one.

But the playbook will look very familiar.