Your alert queue is 800 deep. Your compliance team is three people. It is Monday morning, and PayNow settlements have been running since 6 AM.

This is not a bank CCO's problem. A bank CCO has a 30-person team, a legacy core banking system that batches transactions overnight, and customers whose transactions average thousands of dollars. You have real-time rails, high-volume low-value transactions, and customers who are often more anonymous at onboarding than any bank customer would be. The regulator, however, is looking at both of you with the same rulebook.

That asymmetry — same obligations, entirely different operating context — is where transaction monitoring for payment companies breaks down. The systems that banks deploy were built for bank-shaped problems. Payment companies have different transaction patterns, different fraud vectors, and different compliance team capacities. A system calibrated for a retail bank will generate noise at a scale that makes genuine detection nearly impossible for a small compliance team.

This guide covers what AML transaction monitoring for payment companies and e-wallet operators actually requires in the APAC context — and where the gaps are most likely to cause problems.

Why Payment Companies Face Different TM Challenges Than Banks

The difference is not just volume. It is the combination of volume, speed, transaction size, customer anonymity, and team size — all at once.

Transaction volumes and per-transaction values create a false-positive problem at scale. A rule-based system set to flag transactions above a threshold will generate a manageable number of alerts for a bank processing 50,000 transactions per day at an average value of SGD 3,000. Apply the same logic to an e-wallet operator processing 500,000 transactions per day at an average value of SGD 45, and the alert volume scales disproportionately. Most of those alerts are noise. At 95% false positive rates — which is not unusual for legacy rule-based systems applied to high-frequency, low-value transaction patterns — a three-person compliance team cannot triage what the system produces.

B2C and B2B exposure run simultaneously. Many payment companies serve both retail customers and merchants. The transaction patterns for each are completely different. A merchant receiving 300 settlements in a day looks anomalous by consumer account standards. A retail customer sending five PayNow transfers to five different individuals looks like normal bill-splitting. When both populations sit in the same monitoring environment with the same rules, the rules are wrong for everyone.

Real-time rails are irrevocable. NPP in Australia, PayNow and FAST in Singapore, FPX and DuitNow in Malaysia, InstaPay in the Philippines — all of these settle within seconds. There is no post-settlement hold. If a transaction is suspicious, the only point of intervention is before the money moves. Batch monitoring systems — which review transactions after they have settled — are structurally inadequate for payment companies operating on instant rails. This is not a performance issue; it is an architecture issue.

Mule account layering and APP scams concentrate at payment companies. Payment companies are often the first point of fund movement after a victim transfers money. Authorised push payment (APP) scams work because the victim initiates the transfer themselves — the transaction looks legitimate from a technical standpoint. The only way to detect it is by identifying the pattern: transaction to a new payee, atypical transfer amount for this customer, inconsistent with the customer's normal behaviour. At scale, across an anonymised customer base, this requires behavioural monitoring that most rule-based systems cannot do.

A three-person compliance team cannot triage 800 alerts per day. This is arithmetic. At 8 hours per working day, 800 alerts means 36 seconds per alert. That is not compliance — it is box-ticking.

APAC Regulatory Obligations for Payment Companies

The headline fact here is this: in most APAC jurisdictions, the AML monitoring obligation for licensed payment companies is functionally equivalent to the obligation for banks. What differs is the compliance infrastructure available to meet it.

Singapore (MAS). Payment service providers licensed under the Payment Services Act 2019 — both Major Payment Institutions (MPIs) and Standard Payment Institutions (SPIs) — must comply with MAS Notice PSN01 (for digital payment token services) and MAS Notice PSN02 (for other payment services). The CDD threshold for e-money accounts is SGD 5,000 on a cumulative basis — lower than the threshold applied to bank accounts. MAS expects real-time monitoring capability for account takeover and mule account detection. For detail on the PSA licensing framework and its AML implications, see our article on the Payment Services Act Singapore AML requirements.

Australia (AUSTRAC). Non-bank payment providers registered as remittance dealers or under a Designated Service category face the same Chapter 16 obligations as banks under the AML/CTF Act 2006. The monitoring obligation — transaction monitoring, threshold-based reporting, suspicious matter reports — is identical. The compliance team at the payment provider is not.

Malaysia (BNM). E-money issuers under the Financial Services Act 2013 must comply with BNM's AML/CFT Policy Document. Tier 1 e-money accounts — which carry a wallet balance limit of MYR 5,000 — still require CDD and ongoing transaction monitoring for anomalies. Tier 1 status does not reduce monitoring obligations; it limits what the customer can hold, not what the institution must do.

Philippines (BSP). Electronic money issuers (EMIs) are classified as covered persons under the Anti-Money Laundering Act (AMLA). BSP Circular 706 applies. EMIs must file suspicious transaction reports (STRs) with the Anti-Money Laundering Council (AMLC). The compliance infrastructure that most Philippine EMIs operate with is substantially smaller than what large banks field — but the reporting obligation is the same.

Five Specific TM Requirements for Payment Companies

Generic TM system documentation lists capabilities. What payment companies actually need is more specific.

1. Pre-settlement transaction screening. Payment companies on instant rails need to screen transactions before they clear. This is not optional — it is the only window where intervention is possible. A system that reviews yesterday's transactions overnight is useless for a PayNow or FAST operator. The architecture requirement is real-time, pre-settlement processing.

2. Velocity monitoring across account networks. Mule networks do not operate through single accounts making large individual transfers. They operate through networks of accounts making many small transfers in tight time windows. Detecting this requires monitoring velocity patterns across linked accounts — not just flagging individual transactions that exceed a threshold. Account-to-account linkage analysis, combined with velocity monitoring over rolling time windows, is the detection mechanism. Rule-based systems that operate on individual transaction thresholds miss this pattern entirely.

3. Merchant monitoring. Payment companies providing B2B settlement services need to monitor merchant accounts separately from retail customer accounts. A merchant processing 400 transactions per day with a consistent average transaction value is normal. The same merchant processing 400 transactions per day where 30% are refunds, or where the transaction pattern shifts abruptly over a 48-hour window, is not. Merchant monitoring requires typologies and thresholds built specifically for merchant transaction patterns.

4. Account takeover detection. Payment companies — particularly fintechs and e-wallet operators — face account takeover attempts at higher rates than traditional banks because authentication standards at many providers are weaker. Account takeover detection requires monitoring for behavioural deviations: new device, new location, unusual transfer amount, transfer to a payee the account has never used. These signals need to be evaluated in combination, in real time, before settlement occurs.

5. Cross-border corridor monitoring. A large proportion of payment companies in APAC serve remittance customers. Cross-border flows require corridor-specific typologies — the risk profile of a transfer from Singapore to a Philippines bank account is different from a transfer within Singapore, and different again from a transfer to a jurisdiction with elevated FATF risk ratings. A single generic threshold applied to all cross-border transfers produces alerts that reflect geography rather than actual risk patterns.

What Good TM Looks Like for a Payment Company

The gap between what most payment companies are running and what good transaction monitoring looks like is large. Here is what it actually requires.

Pre-settlement processing across all major APAC instant rails. NPP, PayNow, FAST, FPX, DuitNow, InstaPay. The system needs to operate on the same timeline as the rail — which means pre-settlement, not batch.

False positive rates below 85% in production. Many legacy systems running on payment company transaction data operate at 95% false positive rates or above. At a three-person compliance team, the difference between 95% and 80% is the difference between a team that is permanently behind and a team that can do actual investigations. For a detailed overview of the technical factors that drive false positive rates, see our complete guide to transaction monitoring.

Explainable alert logic. When a compliance analyst opens an alert, they need to understand within 60 seconds why the system flagged it. Opaque model outputs — "risk score: 87" with no explanation — require the analyst to reconstruct the reasoning from raw transaction data. That adds 5–10 minutes per alert. At 100 alerts per day, that is 8–16 hours of analyst time that could be spent on actual investigation. Alert explanations should name the specific pattern or scenario that triggered the flag.

Thresholds calibrated to payment company transaction patterns. A threshold set for a retail bank will fail in a payment company environment. The average transaction value, velocity norms, and customer behaviour patterns at an e-wallet operator are structurally different from a savings account holder at a bank. Thresholds need to be set against the institution's own transaction data — and they need to be adjustable by compliance staff without requiring a vendor engagement.

Scenario coverage for the specific vectors that payment companies face. APP scam detection, mule account network identification, account takeover, cross-border corridor monitoring, and merchant anomaly detection. These are not edge cases for payment companies — they are the primary financial crime exposure.

See the Transaction Monitoring Software Buyer's Guide for a structured framework on evaluating vendors against these criteria.

How Tookitaki FinCense Fits the Payment Company Context

FinCense is deployed at payment institutions across APAC — e-wallet operators, licensed payment service providers, and remittance companies. The architecture was built for the payment company context, not adapted from a bank deployment.

Pre-settlement processing. FinCense processes transactions in real time across NPP, PayNow, FAST, FPX, DuitNow, and InstaPay. The system evaluates each transaction before settlement against the full scenario library — not as a batch job at the end of the day.

Trained on payment institution data. FinCense's detection models are trained using federated learning across a network that includes payment institutions, not only bank data. A model trained exclusively on bank transaction patterns will misread the normal behaviour of an e-wallet customer base. The training data matters for false positive rates — which is why FinCense has reduced false positives by up to 50% compared to legacy rule-based systems in production deployments at payment companies.

Over 50 scenarios covering payment-specific vectors. APP scam detection, mule account network analysis, account takeover patterns, cross-border corridor typologies, and merchant anomaly detection are all in the standard scenario library. These are not add-ons; they are part of the base deployment.

No in-house quant team required. Compliance staff can configure thresholds and adjust scenario parameters directly. The system generates plain-language alert explanations that a compliance analyst — not a data scientist — can act on. At a three-person compliance team, this is the difference between a usable system and a system that is technically running but practically unmanageable.

Scales from licensed payment institutions to large e-wallet operators. The architecture does not require a different deployment for a 50,000-transaction-per-day provider versus a 5,000,000-transaction-per-day operator. The monitoring logic, the scenario library, and the compliance workflows are the same.

If you run compliance at a payment company, an e-wallet operator, or a licensed payment service provider in APAC and your current TM system was either built for a bank or has never been calibrated against your actual transaction data — the problem is not going away on its own.

Book a demo to see FinCense running against payment company transaction patterns, on the specific rails your institution operates, in the regulatory environment you are actually accountable to. The conversation takes 30 minutes and is specific to your payment rails and jurisdiction — not a generic product walkthrough.

AUSTRAC publishes its examination priorities for the year. The CCO at a regional Australian bank reads the list. Calibrated alert thresholds. Documentation of alert dispositions. EDD for high-risk customers. Periodic re-screening for PEPs.

The list looks the same as last year. And the year before.

The difference is that her team is 8 people — not 80. The obligation does not scale down with the headcount.

This is the operating reality for AML compliance at Tier 2 banks across Australia, Singapore, and Malaysia. Regional banks, digital banks, foreign bank branches, credit unions with banking licences — institutions that are fully regulated, fully examined, and fully liable, but are not Commonwealth Bank, DBS, or Maybank. The same rules apply. The resources do not.

This article covers where Tier 2 AML programmes most commonly fail examination, what "proportionate" compliance actually requires in practice, and how mid-size institutions build programmes that hold up without the 50-person compliance team.

The Regulatory Reality: Same Obligations, Different Resources

AUSTRAC, MAS, and BNM do not operate two-tier AML standards. The AML/CTF Act 2006 applies to every reporting entity in Australia regardless of asset size. MAS Notice 626 applies to every bank licensed in Singapore. BNM's AML/CFT Policy Document applies to every licensed institution in Malaysia.

The only concession regulators make is proportionality. A risk-based approach means the scale of an AML programme should reflect the scale of the risk — the volume and nature of transactions, the customer risk profile, the jurisdictions involved. But the programme must exist, be effective, and produce documentation that survives examination.

Proportionality is not a waiver.

Westpac's AUD 1.3 billion penalty in 2020 was for a major bank. But AUSTRAC has also pursued civil penalty orders against smaller ADIs and credit unions for the same category of failures: uncalibrated monitoring thresholds, inadequate EDD, insufficient transaction reporting. The regulator's methodology does not change based on the institution's size. The fine may differ; the finding does not.

For Tier 2 banks in Singapore, MAS has been direct: digital banks licensed under the 2020 digital banking framework should reach AML maturity equivalent to established banks within 2–3 years of licensing. "We are new" has a shelf life. For Tier 2 institutions in Malaysia, BNM's Policy Document draws no distinction between Maybank and a smaller licensed Islamic bank on the core obligations for CDD, transaction monitoring, and suspicious transaction reporting.

Five Gaps Where Tier 2 Banks Fail Examination

Gap 1: Default Threshold Settings on Transaction Monitoring

The most common finding across AUSTRAC and MAS examinations of smaller institutions is transaction monitoring software running on vendor-default alert thresholds.

Default thresholds are calibrated for a generic customer population. A regional Australian bank with 80% SME customers needs different alert logic than a consumer retail bank. A digital bank in Singapore whose customers are predominantly salaried individuals transferring payroll needs different parameters than a trade finance operation. When the thresholds do not reflect the institution's actual customer base, two things happen: analysts receive alerts that are irrelevant to real risk, and the transactions that represent genuine risk pass without triggering review.

AUSTRAC's published guidance on transaction monitoring is explicit on this point. MAS expects institutions to document their threshold calibration rationale and demonstrate that calibration is reviewed periodically against the institution's current risk profile. An undated configuration file from the vendor implementation three years ago does not meet that standard.

See our transaction monitoring software buyer's guide for the evaluation criteria that matter when institutions are selecting a platform — threshold configurability is one of five criteria that directly affect examination outcomes.

Gap 2: Alert Backlogs from High False Positive Rates

A Tier 2 bank running a legacy rules-only transaction monitoring system at a 97% false positive rate and processing 200 alerts per day needs 2–3 full-time analysts to do nothing except clear the alert queue. For a compliance team of 8, that is 25–37% of total capacity consumed by alert triage before a single investigation has started.

The consequence is not just inefficiency. It is a programme that cannot function as designed. Analysts clearing high-volume, low-quality alert queues develop pattern fatigue. Genuine risk signals get the same 30-second review as the 97% of alerts that will be closed as false positives. EDD interviews do not happen because there is no analyst capacity to conduct them. Examination preparation is squeezed into the two weeks before the examiner arrives.

False positive rates are not a fixed cost of running a transaction monitoring programme. Legacy rules-only systems produce high false positive rates because they apply static thresholds to dynamic customer behaviour. Typology-driven, behaviour-based detection — which incorporates how a customer's transaction patterns change over time, not just whether a single transaction crosses a threshold — consistently produces lower false positive rates. The technology gap between rule-based and behaviour-based monitoring is the single largest source of operational inefficiency for Tier 2 compliance teams.

For background on how transaction monitoring works and why the architecture matters, see what is transaction monitoring.

Gap 3: Inconsistent EDD Application

Large banks have EDD workflows automated into their CRM and compliance systems. When a customer's risk rating changes, the system triggers an EDD task, assigns it to an analyst, and tracks completion. The process is not dependent on an individual's memory.

Tier 2 banks frequently run manual EDD processes. PEP screening happens at onboarding. Periodic re-screening often does not — or it happens for some customers and not others, depending on which analyst handles the review. Corporate customers with complex beneficial ownership structures receive initial CDD at onboarding; the review when the ultimate beneficial owner changes is missed because there is no system trigger.

BNM's Policy Document, MAS Notice 626, and AUSTRAC's rules all require EDD to be applied to high-risk customers on an ongoing basis, not just at the point of relationship establishment. "Ongoing" is not annual if the customer's risk profile changes quarterly. An examination finding in this area typically cites specific customer accounts where EDD was not conducted after a risk rating change — not a policy gap, but an execution gap.

Gap 4: Inadequate Documentation of Alert Dispositions

Alert closed. No SAR filed. No written rationale recorded.

In a team under sustained volume pressure, documentation shortcuts are predictable. An analyst who closes 40 alerts in a day and writes a full rationale for 15 of them is not cutting corners deliberately — the queue does not allow otherwise.

AUSTRAC and MAS treat undocumented alert closures as programme failures. Not because the disposition decision was necessarily wrong, but because there is no evidence that a human reviewed the alert and made a considered decision. From an examination standpoint, an alert with no documented rationale is indistinguishable from an alert that was never reviewed. The regulator cannot distinguish between "reviewed and correctly closed" and "bypassed."

This is a systems problem, not a people problem. Alert documentation should be generated as part of the disposition workflow, not as a separate manual step. Every alert closure should require a rationale field — even if the rationale is a structured selection from a drop-down of standard reasons. The documentation burden should be close to zero per alert for straightforward dispositions.

Gap 5: No Model Validation for ML-Based Detection

Tier 2 banks that have moved to AI-augmented transaction monitoring frequently lack the model governance infrastructure to validate that detection models are performing correctly over time.

A model trained on transaction data from 2022 that has never been retrained is not performing at specification in 2026. Customer behaviour shifts. Payment methods change. New typologies emerge. Without periodic model validation — testing whether the model's detection performance against current transaction patterns matches its baseline specification — the institution cannot make the assertion that its monitoring programme is effective.

MAS has flagged model governance as an emerging examination area. For Tier 2 banks, the challenge is that model validation at large banks is done by internal quant teams with the expertise to run performance tests, backtesting, and drift analysis. A 10-person compliance team at a regional bank does not have that capability in-house.

The answer is not to avoid AI-augmented monitoring. It is to select platforms where model validation documentation is generated automatically, and where retraining and recalibration is a vendor-supported function, not a requirement to build internal data science capability.

What "Proportionate" AML Compliance Actually Means

Proportionality is frequently misread as a licence to do less. It is not. It is permission to concentrate compliance resources where the actual risk is — rather than spreading equal effort across all customers regardless of their risk profile.

For a Tier 2 bank, proportionate compliance means three things in practice.

Automate the process work. Alert generation, threshold calibration triggers, EDD workflow initiation, documentation of alert dispositions — none of these should require analyst decision-making at each step. Every manual step is a point where volume pressure leads to shortcuts, and shortcuts are what examination findings are made of.

Free analyst capacity for work that requires judgement. Complex alert investigations, EDD interviews, SAR filing decisions, examination preparation — these require an experienced analyst's attention and cannot be automated. A team of 8 can do this work well, but only if they are not consuming 3–4 hours per day clearing a backlog of 200 low-quality alerts.

The arithmetic is specific: at a 97% false positive rate on 200 daily alerts, an analyst spends approximately 2.5 minutes on each alert just to clear the queue — that is 500 analyst-minutes, or roughly 8.3 hours, across a team. At a 50% false positive rate on the same 200 alerts, 100 alerts require substantive review. The remaining 100 are flagged for quick closure. Total review time drops to approximately 4–5 hours — returning 3–4 hours of analyst capacity daily for investigation and EDD work. At a 10-person team, that is 30–40% of daily compliance capacity returned to meaningful work.

Build documentation in, not on. Every compliance workflow should generate examination-ready records as a byproduct of normal operation, not as a separate documentation task.

Technology Requirements Specific to Tier 2

The enterprise transaction monitoring systems built for Tier 1 banks assume implementation resources that Tier 2 banks do not have. Multi-month professional services engagements, dedicated data engineering teams, internal model governance functions — these are not realistic for a regional bank with a 5-person technology team and a compliance budget that was set before the current regulatory environment.

Four technology requirements are specific to Tier 2:

Integration simplicity. Many Tier 2 banks run legacy core banking platforms. Cloud-native transaction monitoring platforms with standard API connectivity can connect to core banking data in weeks, not months, without requiring a custom integration project.

Compliance-configurable thresholds. Compliance staff should be able to adjust alert thresholds and add detection scenarios without vendor involvement. Calibration is a compliance function. If it requires a professional services engagement every time a threshold needs updating, calibration will not happen at the frequency regulators expect.

Predictable pricing. Per-transaction pricing models become unpredictable as transaction volumes grow. Tier 2 banks should look for flat-fee or tiered pricing that is budget-predictable against their transaction volume — one less variable in a constrained budget environment.

Exam-ready documentation, automatically. Alert audit trails, calibration records, and model validation documentation should be outputs of the platform's standard operation, not custom report builds. If producing the documentation package for an examination requires a week of manual compilation, the documentation package will always be incomplete.

For a structured framework on evaluating transaction monitoring vendors against these criteria, see the TM Software Buyer's Guide.

APAC-Specific Regulatory Context for Tier 2

Australia. AUSTRAC's risk-based approach explicitly accommodates proportionality — but AUSTRAC has examined and found against credit unions and smaller ADIs for the same monitoring failures as major banks. The AUSTRAC transaction monitoring requirements cover the specific obligations that apply to all reporting entities, regardless of size.

Singapore. MAS Notice 626 applies to all banks licensed in Singapore. For digital banks — which are structurally Tier 2 in Singapore's context — MAS has set explicit expectations that AML maturity should reach equivalence with established banks within 2–3 years of licensing. The MAS transaction monitoring requirements article covers the specific MAS standards in detail.

Malaysia. BNM's AML/CFT Policy Document applies to all licensed institutions. Smaller licensed banks, Islamic banks, and regionally focused institutions have the same CDD, monitoring, and reporting obligations as the major domestic banks. BNM's examination methodology does not grade on institution size.

What an Examination-Ready Tier 2 AML Programme Looks Like

Six elements characterise programmes that hold up to examination at Tier 2 institutions:

1. A written AML/CTF programme, Board-approved and reviewed annually
2. Transaction monitoring thresholds documented and calibrated against the institution's own customer risk assessment — with a dated record of when calibration was last reviewed and by whom
3. An alert investigation workflow that generates a written rationale for every closed alert, including a structured reason code for dispositions that do not result in SAR filing
4. EDD workflows triggered automatically by risk rating changes, not by analyst memory
5. Annual model validation or rule-set review with documented outcomes, even where the outcome is "no changes required"
6. Staff training records, including dates, completion rates, and assessment outcomes by employee

None of these six elements require a large compliance team. They require systems configured to produce the right outputs and workflows designed to generate documentation as a byproduct of normal operation.

How Tookitaki FinCense Fits the Tier 2 Context

Tookitaki's FinCense AML suite is deployed across institution sizes, including Tier 2 banks, digital banks, and licensed challengers in Australia, Singapore, and Malaysia.

FinCense is cloud-native with standard API connectivity, which reduces integration time for institutions that do not have dedicated implementation teams. Compliance staff can configure alert thresholds and detection scenarios without vendor support — calibration happens on the institution's schedule, not when a professional services engagement can be arranged.

APAC-specific typologies and pre-built documentation for AUSTRAC, MAS Notice 626, and BNM's Policy Document are included in the platform. These are not professional services add-ons; they are part of the standard deployment.

In production deployments, FinCense has reduced false positive rates by up to 50% compared to legacy rule-based systems. At a 10-person compliance team processing 200 daily alerts, that returns approximately 3–4 hours of analyst capacity per day — enough to run substantive investigations, keep EDD current, and arrive at examination with documentation that was built during normal operations, not assembled in a panic the week before.

See FinCense in a Tier 2 Bank Context

If your institution is carrying the same AML obligations as the major banks with a fraction of the compliance resources, the question is not whether you need a programme that works — it is whether your current programme will hold up when the examiner arrives.

Book a demo to see FinCense configured for a Tier 2 bank: realistic transaction volumes, a compliance team of fewer than 20, and the documentation outputs that AUSTRAC, MAS, and BNM expect.

If you are still evaluating options, the TM Software Buyer's Guide provides a structured framework for comparing platforms on the criteria that matter most for smaller compliance teams.

The email from your legal operations director lands on a Tuesday morning. It references something called the AML/CTF Amendment Act 2024. It asks whether your law firm is now a "reporting entity." It asks whether you need to enrol with AUSTRAC.

You are a managing partner. You run a mid-size conveyancing and commercial law practice. You have never thought of your firm as being in the same regulatory category as a bank. You do not have a compliance team. You do not have an AML programme. And somewhere in the back of your mind, you remember hearing about "Tranche 2" a few years ago — and then hearing it had been delayed again.

It has not been delayed again.

The AML/CTF Amendment Act 2024 received Royal Assent on 29 November 2024. If your firm provides designated legal services — real estate transactions, managing client funds, forming companies or trusts, managing assets on behalf of clients — you are captured. The clock is running.

What Tranche 2 Is, and Why It Took 17 Years

Australia's Anti-Money Laundering and Counter-Terrorism Financing Act 2006 — the AML/CTF Act — came into force as Tranche 1. It regulated financial institutions: banks, credit unions, remittance dealers, casinos. Lawyers, accountants, and real estate agents were left out, with an explicit commitment that a second tranche of reforms would extend the regime to designated non-financial businesses and professions (DNFBPs).

That commitment sat largely dormant for 17 years.

The Financial Action Task Force (FATF) conducted a Mutual Evaluation of Australia in 2015 and named the absence of Tranche 2 as a major gap in Australia's AML/CTF framework. Australia's national risk assessment consistently identified real estate, legal services, and corporate structuring as channels for money laundering — yet the lawyers, accountants, and property agents facilitating those transactions had no formal AML obligations. Australia was one of the last FATF member jurisdictions to operate without DNFBP coverage.

The AML/CTF Amendment Act 2024 ends that. It amends the AML/CTF Act 2006 to extend obligations to Tranche 2 entities for the first time. Royal Assent was 29 November 2024.

Who Is Captured Under Tranche 2

Not every professional in a captured sector becomes a reporting entity. The test is whether you provide a "designated service" as defined under the amended Act. The scope matters.

Lawyers and Law Firms

Law firms are captured when providing specific services:

• Acting in the purchase or sale of real property on behalf of a client
• Managing client money, securities, or other assets
• Forming companies, trusts, or other legal entities on behalf of a client
• Acting as a director, secretary, or nominee shareholder for a client
• Providing business sale or purchase advice involving fund transfers

Litigation is not captured. General legal advice is not captured. The obligations attach to the transaction-facing, fund-handling, and corporate-structuring work — the services most associated with money laundering risk.

Accountants

Accountants providing the following services are captured:

• Managing client funds or financial assets
• Forming companies, trusts, or other legal entities
• Providing advice on business acquisition or disposal that involves fund transfers

Tax return preparation alone is not captured. The risk-based logic is the same as for lawyers: the obligations follow the money and the structural work.

Real Estate Agents

Real estate agents acting in the purchase or sale of real property are captured. Property management services are not captured. This distinction matters for agencies that carry both a sales division and a property management business — the compliance obligations attach to the former, not the latter.

Dealers in Precious Metals and Stones

Dealers conducting cash transactions at or above AUD 5,000 are captured. This threshold reflects the cash-intensity risk in this sector. Card or bank transfer transactions below that threshold are not in scope.

Trust and Company Service Providers (TCSPs)

TCSPs are captured for the full range of their entity formation, directorship, and registered office services.

What Tranche 2 Entities Must Do: The Core Obligations

Once captured, the obligations are substantive. They mirror the framework already imposed on financial institutions under the AML/CTF Act 2006, adapted to a professional services context.

Enrol with AUSTRAC. Reporting entities must register with AUSTRAC before providing designated services after the relevant commencement date. AUSTRAC maintains a public register of reporting entities.

Develop an AML/CTF programme. The programme has two parts. Part A is a board-approved risk assessment — a documented analysis of the ML/TF risks your firm faces based on the designated services you provide, the client types you serve, the jurisdictions involved, and the delivery channels used. Part B is the set of controls: customer identification procedures, ongoing monitoring, staff training, and reporting processes.

Customer identification and verification. Before providing a designated service, the entity must identify and verify the customer. For individuals, this typically means collecting and verifying name, date of birth, and address using reliable documentation. For companies and trusts, the obligations extend to beneficial ownership — understanding who ultimately controls or benefits from the entity.

Ongoing customer due diligence. The initial CDD is not a one-time exercise. Entities must monitor existing client relationships for changes in risk profile and update their CDD records accordingly.

Transaction monitoring. Entities must monitor for unusual or suspicious activity. The definition of "unusual" depends on the firm's own risk assessment — a conveyancing practice will have different baseline transaction patterns from an accounting firm that manages investment assets.

File Suspicious Matter Reports (SMRs). Where an entity has reasonable grounds to suspect that a customer or transaction is connected to money laundering or terrorism financing, an SMR must be filed with AUSTRAC within 3 business days of forming that suspicion. The 3-day clock is statutory — it is not extendable because the matter is complex.

File Threshold Transaction Reports (TTRs). Cash transactions of AUD 10,000 or more must be reported to AUSTRAC. This is the same threshold that applies to financial institutions.

Record keeping. Customer due diligence documents and transaction records must be retained for 7 years from the date of the relevant transaction or the end of the business relationship, whichever is later.

AUSTRAC annual compliance report. Reporting entities must submit an annual compliance report to AUSTRAC covering the adequacy of their AML/CTF programme and their compliance during the reporting period.

Phased Implementation: What Is Happening When

The AML/CTF Amendment Act 2024 received Royal Assent on 29 November 2024, but that date did not trigger immediate obligations for Tranche 2 entities. Commencement of specific provisions is subject to Ministerial instruments, and AUSTRAC has signalled a phased approach to give newly captured entities time to build their programmes.

AUSTRAC's published guidance indicates that enrolment obligations and AML/CTF programme development requirements are expected to commence in 2026, with the full suite of reporting and ongoing obligations to follow. However, specific commencement dates for each obligation type remain subject to confirmation through formal commencement instruments.

This is a meaningful distinction. The legislation exists. The obligation to eventually comply is not in doubt. But the date from which AUSTRAC can take enforcement action for non-compliance with a given obligation depends on the commencement date of that obligation — and those dates are being phased, not simultaneous.

What this means in practice: Firms should monitor AUSTRAC's website (austrac.gov.au) for confirmed commencement dates and guidance specific to their sector. AUSTRAC has already published Tranche 2 guidance for lawyers, accountants, real estate agents, and TCSPs. Waiting for a final date before starting programme development is not a sound approach — the lead time required to build a compliant AML/CTF programme is measured in months, not weeks.

What This Means for Banks and Existing Reporting Entities

Tranche 2 does not only affect the newly captured entities. For banks and other financial institutions already operating under the AML/CTF Act 2006, it changes the risk environment in two ways.

The counterparty risk picture changes. Law firms, accounting practices, real estate agencies, and precious metals dealers that were previously unregulated are now reporting entities with their own AML obligations. Banks that hold accounts for these businesses can factor their regulated status into CDD assessments. A law firm that has enrolled with AUSTRAC, implemented an AML/CTF programme, and is actively monitoring for suspicious activity is a materially different risk profile from one that had no such obligations.

Expectations around correspondent and professional services accounts will rise. AUSTRAC is likely to assess whether banks are reflecting the updated regulatory status of Tranche 2 sectors in their own monitoring and CDD frameworks. A bank that continues to treat a law firm client account as low-risk without considering whether that firm has enrolled and implemented its programme is exposed to questions about the adequacy of its own risk assessment.

Property-linked layering — moving proceeds of crime through sequential real estate transactions — is documented in Australia's national money laundering risk assessments as a method that has operated with relative ease due to the absence of AML controls on real estate agents and conveyancers. That gap is now being closed. Banks whose transaction monitoring is tuned to detect this pattern should review whether the new regulated status of real estate agents affects their detection logic.

For more detail on AUSTRAC's expectations for transaction monitoring at financial institutions, see our guide to AUSTRAC transaction monitoring requirements.

Building an AML Programme from Scratch: Seven Steps

For Tranche 2 entities starting from zero, the AML/CTF programme requirement is the most substantive obligation. Here is the structure.

Step 1: Identify your designated services. Not all services a law firm or accounting practice provides are captured. Document which of your services meet the definition of a designated service under the amended Act. This is the scope boundary for everything that follows.

Step 2: Conduct a risk assessment (Part A). For each designated service, assess the money laundering and terrorism financing risks based on: client types (individuals, companies, trusts, politically exposed persons, foreign clients), delivery channels (in-person, remote, intermediary-introduced), transaction types and sizes, and the jurisdictions involved. The risk assessment must be documented and approved at board or senior management level.

Step 3: Design your customer identification procedures. Document exactly what identity information you collect from each customer type, at what point in the engagement, and how you verify it. Verification sources must be reliable and independent. Document what you do when you cannot complete verification.

Step 4: Define your ongoing monitoring approach. For your client base, define what an unusual transaction or instruction looks like. A real estate agent processing a cash contract at AUD 4,800 — just below the AUD 5,000 cash threshold — warrants scrutiny. A law firm receiving funds from an unexpected third party for a property settlement is a red flag regardless of amount. Document your red flag indicators and the escalation process.

Step 5: Establish your SMR and TTR filing process. Designate who is responsible for filing Suspicious Matter Reports. Build the 3-business-day clock into your workflow. For TTRs, create a process that captures cash transactions at or above AUD 10,000 at point of receipt — do not rely on end-of-period reconciliations.

Step 6: Train your staff. Everyone who interacts with clients or handles client funds needs AML/CTF awareness training. Training should cover: what money laundering looks like in your practice context, how to identify red flags, what to do when something feels wrong, and how to report internally without tipping off the client.

Step 7: Establish your record-keeping system. You need to retain CDD documents and transaction records for 7 years. If your firm's document management system was designed for legal file retention rather than AML compliance, you may need a separate system or process for AML records.

AUSTRAC's Enforcement Posture

AUSTRAC has a documented history of supporting newly regulated sectors through education before moving to enforcement. The regulator published Tranche 2-specific guidance and engaged with professional associations in the legal and accounting sectors during the consultation process.

That said, the context for Tranche 2 is different from previous regulatory expansions. Australia has operated without DNFBP AML coverage for 17 years, under sustained FATF scrutiny. The reputational and diplomatic pressure behind Tranche 2 is significant. AUSTRAC is unlikely to treat good-faith ignorance the same way it might have in an earlier era.

AUSTRAC's civil penalty powers apply from commencement. For body corporates, civil penalties can reach AUD 17.9 million per contravention. For individuals, penalties are lower but substantial. AUSTRAC also has the power to accept enforceable undertakings, issue infringement notices, and seek injunctions.

The enforcement risk is not theoretical. AUSTRAC has pursued major civil penalty actions against Westpac (AUD 1.3 billion), Commonwealth Bank (AUD 700 million), and SportsSuper. A newly captured entity that makes no effort to enrol or build a programme faces a different enforcement calculus from one that has enrolled, built a programme, and is working through implementation challenges.

Getting the Programme Right

For Tranche 2 entities building their first AML/CTF programme, technology makes a material difference in whether the programme works in practice. A documented policy that exists only on paper will not detect a suspicious transaction or generate a timely SMR.

For institutions already operating under the AML/CTF Act 2006 that need to review their transaction monitoring in light of Tranche 2, our transaction monitoring software buyer's guide covers what to look for in a compliant monitoring system. If you are newer to transaction monitoring concepts, our introduction to transaction monitoring sets out the fundamentals.

Tookitaki's AFC Ecosystem is built for the compliance requirements that AUSTRAC and other regulators enforce. If you are building or upgrading an AML programme for the Australian market — whether as a newly captured Tranche 2 entity or an existing reporting entity adjusting to the new environment — book a demo to see how the platform handles the specific detection and reporting requirements that apply under the AML/CTF Act.

AUSTRAC has confirmed that Tranche 2 obligations are coming. The question now is not whether to build a programme — it is whether to build one before commencement or after the first enforcement action arrives.