AUSTRAC Tranche 2 is expanding compliance obligations: are your records ready?

Australia’s anti-money laundering and counter-terrorism financing reforms are changing the compliance landscape for both existing reporting entities and newly regulated sectors. For compliance leaders, the immediate question is not simply whether a policy has been updated. It is whether the organisation can demonstrate that its controls, decisions and records operate as intended.

AUSTRAC Tranche 2 extends AML/CTF obligations to services commonly provided by lawyers, conveyancers, accountants, real estate professionals, trust and company service providers, and dealers in precious metals and stones. The reforms also sit alongside updated obligations for existing reporting entities.

That does not create a blanket requirement to record every customer call, meeting or digital interaction. It does, however, raise the importance of maintaining accurate, complete and retrievable records wherever customer interactions form part of customer due diligence, risk assessment, transaction monitoring, suspicious matter reporting, governance or audit processes.

What AUSTRAC Tranche 2 changes

The reforms bring a wider group of businesses into Australia’s AML/CTF regime and reinforce an outcomes-focused approach to compliance. Newly regulated entities need an AML/CTF programme, appropriate governance, a compliance officer, staff training and processes for customer due diligence and reporting. Existing reporting entities must also adapt to updated rules and requirements.

AUSTRAC’s official reform guidance explains the affected sectors, implementation expectations and practical obligations. Review the AUSTRAC AML/CTF reforms guidance.

For many organisations, the challenge will be operational rather than conceptual. A policy can say that records will be retained, controls will be followed and concerns will be escalated. An audit will test whether those things can be evidenced.

Record keeping is broader than storing documents

AUSTRAC requires reporting entities to make and maintain accurate and complete records relating to their AML/CTF programme and the activities undertaken to meet their obligations. Depending on the obligation, records may include programme documentation, customer due diligence evidence, transaction information, risk assessments, training records, reporting decisions and supporting material.

The practical weakness often appears between systems. Customer information may sit in a CRM, supporting documents in a case-management platform, interaction history in a contact-centre system and approvals in email or collaboration tools. Each system may be functioning, but the compliance record is fragmented.

A fragmented record creates questions that are difficult to answer under scrutiny:

• Can the organisation reconstruct why a customer was assessed at a particular risk level?
• Can it show which information was considered and who approved the decision?
• Can it retrieve the relevant interaction and associated records without relying on one individual’s knowledge?
• Can it demonstrate that access, amendment and retention controls were applied consistently?
• Can it produce the evidence within the timeframe of an audit or regulatory request?

Where customer interactions become part of the evidence

Customer interactions may be relevant when they help establish identity, explain source of funds, clarify the purpose of a transaction, document an escalation or record the handling of a suspicious matter. In those circumstances, the interaction is not important merely because it occurred. Its value lies in whether it can support the organisation’s decision-making and control environment.

The relevant record may be a call, meeting, email, secure message, screen activity or case note. The appropriate channel and retention approach will depend on the service provided, the organisation’s risk assessment and the obligations that apply. The key is to identify which interactions carry compliance significance and govern those records accordingly.

Five readiness checks for compliance teams

1. Map the customer journeys and decisions that create AML/CTF evidence requirements.
2. Identify where the supporting records are created, stored and retrieved across systems.
3. Confirm that retention rules are defined and applied to the correct record types.
4. Test whether a complete case can be reconstructed without manual searching across disconnected platforms.
5. Confirm that access, amendment and retrieval activity can be audited.

These checks should be proportionate to the organisation’s services and risk profile. They are not a substitute for legal interpretation, but they expose practical gaps between a written AML/CTF programme and the evidence available to support it.

Common gaps to look for

Records split across channels

Voice, video, messaging and case-management records may be retained separately, with no consistent way to bring them together for a review.

Manual evidence assembly

A compliance response depends on staff locating files individually, exporting records and explaining undocumented decisions. That approach is slow and difficult to repeat.

Inconsistent retention

Different platforms may keep records for different periods or rely on default settings that do not reflect the organisation’s policies.

Limited auditability

The organisation may be able to produce a file but not show who accessed it, whether it was altered or how it was governed over time.

From recording to governed evidence

The distinction between recording and evidence is central to readiness. A recording confirms that an interaction was captured. A governed evidence record can be associated with the correct customer or case, retained under policy, protected from unauthorised change, retrieved when needed and supported by an audit trail.

For organisations that rely on customer interactions within AML/CTF processes, that governance layer can help connect operational activity to the evidence needed for assurance, audit and investigation.

How Liquid Voice supports interaction governance

Liquid Voice provides recording, retention and interaction intelligence for organisations where communications must be trusted, usable and defensible. Its compliance solution is designed to help organisations capture relevant interactions across voice and digital channels, apply retention and access controls, and retrieve records when required.

Explore the Liquid Voice Compliance Solution and how it supports governed interaction records.

Read the Compliance Readiness Guide

The Compliance Readiness Guide provides a practical framework for reviewing capture, governance, retention, retrieval and auditability across customer interactions. Use it to identify where records support your AML/CTF controls and where further investigation may be needed.