AML/CTF (Anti-Money Laundering and Counter-Terrorism Financing) compliance is not a legal checkbox. It is a system architecture requirement. For Australian FinTech and RegTech companies, AML/CTF obligations translate directly into data models, event logging, transaction monitoring pipelines, and audit-ready infrastructure.

Quick summary

  • What it is: controls and processes that prevent your platform from being used for money laundering or terrorism financing
  • Who it applies to: reporting entities regulated by AUSTRAC (banks, remitters, DCEs, gambling, bullion, securities; from July 2026: legal, accounting, real estate, TCSP)
  • Core obligations: risk assessment, CDD, transaction monitoring, reporting (SMRs, TTRs, IFTIs), record keeping (7 years)
  • What to build: identity verification pipeline, risk scoring engine, transaction monitoring, case management, audit trail infrastructure

Definition

AML refers to Anti-Money Laundering: the controls and processes that prevent your platform from being used to convert illegally obtained funds into legitimate-seeming assets. CTF refers to Counter-Terrorism Financing: the controls that prevent your platform from facilitating the movement of funds to individuals or organisations engaged in terrorism.

In regulatory terms, these are combined obligations under the Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth). In engineering terms, they require continuous monitoring, risk-based decision logic, and immutable audit trails across every customer touchpoint and transaction.

The practical implication: your system must be able to explain every customer relationship and every transaction, retrospectively, to a regulator. If your database cannot reconstruct the who, what, when, where, and why of any given transaction from seven years ago, you have a compliance gap.

If you are building or scaling a regulated product in Australia, your engineering decisions today determine whether you pass an AUSTRAC audit tomorrow. This page explains what AML/CTF means in practice: not as compliance theory, but as system design.

Who AML/CTF Applies to in Australia

AUSTRAC (Australian Transaction Reports and Analysis Centre) is both Australia’s financial intelligence unit and the regulator for AML/CTF compliance. Currently, approximately 17,000 reporting entities operate under AUSTRAC supervision.

Current reporting entities (pre-Tranche 2)

Current reporting entities before Tranche 2: sectors and examples
Current reporting entities before Tranche 2: sectors and examples

Tranche 2 sectors (from 1 July 2026)

The AML/CTF Amendment Act 2024 expands AUSTRAC’s regulatory scope to an estimated 80,000 to 100,000 additional entities. From 1 July 2026, the following sectors become reporting entities:

Tranche 2 sectors from 1 July 2026 and what brings them into scope
Tranche 2 sectors from 1 July 2026 and what brings them into scope

Tranche 2 AML reforms

Key compliance dates

Key AML/CTF compliance dates in 2026 and who each one affects
Key AML/CTF compliance dates in 2026 and who each one affects

Check if you may be regulated (AUSTRAC)

Core AML/CTF Obligations

AML/CTF is risk-based: controls must be proportionate to your actual exposure.

Core AML/CTF obligations: what each means and the system requirement
Core AML/CTF obligations: what each means and the system requirement

AML/CTF From a System Design Perspective

Compliance must be embedded in your data architecture from day one.

  • Capture and verify customer identity documents with biometric matching. Integrate with Document Verification Service (DVS). Store verification results, not just outcomes.
  • Risk scoring engine. Dynamic scoring based on customer attributes, transaction patterns, and external data. Risk levels determine CDD intensity and monitoring frequency.
  • Transaction monitoring. Real-time analysis against configurable rules and anomaly detection. Generate alerts for human review.
  • Case management. Analysts investigate alerts, document findings, escalate to SMRs, and record resolutions.
  • Reporting integration. Automated generation of SMRs, TTRs, and IFTIs in AUSTRAC-compliant formats.
  • Sanctions screening. Real-time screening against DFAT Consolidated List and international sanctions lists.
  • Audit trail infrastructure. Why 40,000 API attacks in 6 months should warn every Australian FinTech Every action logged with timestamp, actor, and context. Logs immutable and retained for seven years.

Data and Events Your System Must Log

AUSTRAC expects you to reconstruct any customer relationship or transaction on demand. Your logging infrastructure must capture the following categories of events.

Required event logging categories

Required AML/CTF event logging categories, event types and required fields
Required AML/CTF event logging categories, event types and required fields

Evidence and Audit Trail Expectations

AUSTRAC can request records with retrieval expected within 24-72 hours.

Record retention requirements

AML/CTF record retention requirements: record type, retention period and start point
AML/CTF record retention requirements: record type, retention period and start point

Audit-ready requirements:

  • Secure storage with access controls and encryption.
  • Retrievable and translatable to English.
  • Legible and auditable regardless of format.
  • Complete timeline reconstruction for any customer relationship.

AUSTRAC enforcement cases consistently cite documentation failures. The standard is not “we had a system” but “we can prove the system operated as designed.”

High-Level Implementation Steps

Phase 1: Foundation (Weeks 1-4). Conduct ML/TF risk assessment. Define customer risk categories. Design data models for identity, transaction, and audit logging. Select verification and screening providers.

Phase 2: Core Systems (Weeks 5-12). Implement onboarding pipeline with identity verification. Build transaction monitoring with configurable rules. Implement case management for alert investigation. Develop AUSTRAC reporting infrastructure.

Phase 3: Integration and Testing (Weeks 13-16). Integrate sanctions screening. Implement audit logging across all components. Test monitoring and reporting workflows. Document AML/CTF policies.

Phase 4: Operational Readiness (Weeks 17-20). Train staff. Conduct independent review. Enrol with AUSTRAC. Establish ongoing monitoring cadence.

eKYC. Electronic Know Your Customer: the digital verification of customer identity using document scanning, biometric matching, and database checks. A core component of CDD.

Fraud Detection. Systems and processes for identifying potentially fraudulent transactions or account activity. Overlaps with but distinct from transaction monitoring for ML/TF purposes.

Transaction Monitoring. Continuous surveillance of customer transactions against rules, thresholds, and behavioural baselines to detect suspicious activity.

Tranche 2 AML Reforms. The extension of AML/CTF obligations to legal, accounting, real estate, and trust service sectors, effective 1 July 2026.

Tranche 2 AML Reforms

Suspicious Matter Report (SMR). A mandatory report to AUSTRAC when reasonable grounds for suspicion exist regarding money laundering, terrorism financing, or other serious crimes.

Threshold Transaction Report (TTR). A mandatory report to AUSTRAC for cash transactions of $10,000 or more.

Politically Exposed Person (PEP). An individual who holds or has held a prominent public position, or their close associates and family members. Requires enhanced due diligence.

Request a Compliance-Readiness Review

AUSTRAC’s enforcement history demonstrates that system failures and documentation gaps are the primary drivers of civil penalties. Building compliance into your architecture from day one is not optional: it is how you protect your business from regulatory exposure.

Ostride Labs specialises in compliance-ready engineering for Australian FinTech and RegTech companies. Our Technical Advisory engagement assesses your current architecture against AUSTRAC requirements and delivers a clear roadmap for closing gaps before they become enforcement risks.

Frequently Asked Questions

Reasonable grounds to suspect a transaction or customer activity relates to money laundering, terrorism financing, tax evasion, or other serious crime. “Reasonable grounds” is objective: would a reasonable person form the same suspicion?

24 hours for terrorism financing suspicions. Three business days for all other suspicions.

No. Continue services with appropriate risk mitigation. Do not “tip off” the customer.

Submit a threshold transaction report for any cash transaction of $10,000 or more.

No fixed schedule, but reviews must be triggered by material changes to business, customers, products, or regulatory environment.

Operational tasks yes, but responsibility for compliance cannot be delegated. Board and senior management remain accountable.

Civil penalties can reach $23 million per contravention. AUSTRAC has secured: $1.3 billion (Westpac, 2020), $700 million (Commonwealth Bank, 2018), $450 million (Crown, 2023), $67 million (SkyCity, 2024). Infringement notices range from $1,500 to $31,500 per violation.

Read more

Compliance & RegTech

How to Implement eKYC Without Killing User Experience: Technical Guide

Adam Miller
10 min12 November 2025
Read the article
technical-guide
Compliance & RegTech

Why 40,000 API Attacks in 6 Months Should Warn Every Australian FinTech: The Hidden Compliance Debt Crisis

Adam Miller
8 min9 October 2025
Read the article
The radar is sweeping

Need a technical read on your next product decision?

Tell us what is changing in the product, delivery plan or live system. We will help identify the right next conversation.