How Australia’s Tranche 2 Reforms Turn Gatekeeper Professions Into an Enterprise Monitoring Problem

AUSTRAC Tranche 2 real estate transaction monitoring obligations are now live across a wide set of gatekeeper professions. Since 1 July 2026, Australia’s Tranche 2 reforms have brought real estate agents, lawyers, accountants, conveyancers, precious metals dealers, and trust and company service providers, an estimated 80,000 to 100,000 businesses in total, into the AML/CTF Act’s reporting entity regime for the first time.

AUSTRAC opened enrolment on 31 March 2026, and newly regulated businesses were required to enrol by 29 July 2026. For a single independent agency, this is a significant but contained project: build a risk-based programme, verify customers, monitor and report.

For a franchise network, a national real estate group, or a professional-services consolidator that owns several of these newly captured business types, it is a different problem entirely: a coordinated monitoring architecture question across many previously unregulated entities at once.

For a group that owns several newly regulated businesses, one central monitoring standard replaces a separate programme at every office.

What Tranche 2 actually requires

Covered businesses must be enrolled as reporting entities with AUSTRAC, build and operate an AML/CTF programme, not just a policy document, conduct customer due diligence on the parties to relevant transactions, monitor client behaviour on an ongoing basis, lodge Threshold Transaction Reports and Suspicious Matter Reports where required, and keep records for at least seven years. In practice this is an operating framework that has to run in day-to-day work, not a one-off checklist exercise.

Why one owner behind several entities changes the shape of the problem

A national real estate franchise, a multi-office conveyancing group, or a consolidator that has acquired several accounting practices now faces a version of Tranche 2 that a single independent agency does not: the same underlying obligation, repeated across dozens or hundreds of previously unregulated offices, each historically running its own client files and its own informal sense of who its customers are.

Building a separate AML/CTF programme, and a separate monitoring approach, at each office is the path of least resistance under deadline pressure, and it is also the path most likely to produce exactly the inconsistency that regulators look for once a sector is newly supervised. AUSTRAC’s own enforcement history in the banking sector shows how costly inconsistent monitoring standards across a large organisation can become once regulatory attention arrives.

Treating Tranche 2 as an architecture decision, not a compliance sprint

For groups in this position, the more defensible approach is to design one customer due diligence and monitoring standard centrally, and deploy it consistently across every captured entity, rather than letting each office or practice build its own. This mirrors the same operating-model logic playing out in other jurisdictions where regulators are moving from checking that a programme exists to checking that it actually works across an organisation.

A consolidated approach also has a practical upside beyond compliance risk: it means a single, coherent monitoring and case-management view across the group, rather than a patchwork of separate spreadsheets and manual processes that nobody outside a single office can meaningfully audit.

Building monitoring that scales across newly regulated entities

A monitoring capability that can be configured once and deployed consistently across many small, previously unregulated offices is the practical answer to Tranche 2 at scale. FraudShield’s configurable rule logic and case-management workflows are designed to support exactly this kind of consistent rollout across multiple entities under one group, giving a group compliance function a single view of monitoring and reporting quality across every captured business, rather than one view per office.

Frequently Asked Questions

This article was accurate at the time of publication in October 2026 and is intended for general informational purposes only. It does not constitute legal, regulatory or compliance advice. Organisations should seek qualified professional guidance in relation to their specific obligations.