AML/CTF Act 2006 (Cth) s 123 ↗ makes it an offence to disclose SMR-related information where the disclosure would, or could reasonably be expected to, prejudice an investigation. Post-31- March-2026 the offence has four conjunctive elements — who discloses, to whom, what information, and the prejudice test. What counts as tipping off, what staff training must cover, and how routine CDD operates without accidentally revealing suspicion. Working reference for AMLCOs and senior management — not legal advice.
Working reference, not legal advice
Tipping-off questions turn on the specific facts of each interaction. For a definitive view, talk to an AML lawyer.
AML/CTF Act 2006 (Cth) s 123 ↗, as amended, sets four conjunctive elements. The offence is committed where (a) the person is a covered person (a reporting entity, or its officer/employee/agent, a member of a reporting group, or a person required to give information under s.49 or s.49B); (b) the person discloses information to someone other than an AUSTRAC entrusted person; (c) the information is “covered information” under s.123(2) — broadly SMR-related information, including the existence of an SMR, its substance, or material that would set out information from one; and (d) the disclosure would, or could reasonably be expected to, prejudice an investigation of a Commonwealth, state or territory offence, or proceedings under the Proceeds of Crime Act or its state/territory equivalents. All four elements must be present for the offence to be made out; for s.123(1)(d) it is immaterial whether an investigation has actually commenced (s.123(3)).
The maximum penalty is imprisonment for two years or 120 penalty units, or both. The offence applies to the reporting entity, its officers, employees, contractors and agents, and to members and personnel of reporting groups. Default Criminal Code fault elements apply; the offence can be committed without an intention to prejudice an investigation, but element (d) — the objective “would or could reasonably be expected to prejudice” test — is the gate.
What this means operationally: every staff member who could plausibly know about an SMR — through their role, through casual conversation, through workflow visibility — is potentially inside the prohibition. The prejudice element is what distinguishes a criminal disclosure from a routine internal AML communication. Training has to make both the covered-information boundary and the prejudice test real for staff, not theoretical.
Direct disclosure is the obvious case — and the one staff training tends to focus on. The hard cases are indirect:
All four are operational-design problems, not staff-quality problems. The fix is structural: AML discussions in defined channels, written policies on what staff can say to patrons, behavioural-change pathways that route through the existing CDD framework rather than as one-offs.
Section 123 of the AML/CTF Act 2006 (Cth) makes it an offence for a covered person — broadly, a reporting entity or its officer, employee or agent (and members of a reporting group, and persons required under s.49 or s.49B) — to disclose SMR-related information to someone other than an AUSTRAC entrusted person, where the disclosure would or could reasonably be expected to prejudice an investigation (s.123(1)(d)). The 'covered information' in s.123(2) includes the fact a Suspicious Matter Report has been or is required to be given, the report itself, copies, or documents setting out information from the report. All four elements must be present. Maximum penalty: imprisonment for two years or 120 penalty units, or both.
Anyone working for or on behalf of the reporting entity — directors, officers, employees, contractors, agents, AML consulting firms engaged by the venue. The obligation applies whether the person actually drafted the SMR or merely knows about it. Floor staff who observe the AMLCO discussing an SMR-relevant patron with senior management are bound by the prohibition; the secretary who sees the SMR submission record is bound; cage staff who notice escalated CDD on a patron and infer there's a suspicion concern are bound. The boundary is broad by design — the protection is for the integrity of the AML intelligence pipeline.
Direct disclosure is the obvious case — a staff member telling a patron 'we filed an SMR about you' is a clear breach, because it discloses covered information and would plainly be expected to prejudice any related investigation. The harder cases are indirect: changing the venue's behaviour toward the patron in a way that signals scrutiny ('we suddenly need extra ID from you', 'a manager wants to talk to you about your buy-ins'), discussing the SMR within hearing range of the patron, posting a photo or note that allows the patron to identify themselves as a subject, or telling a third party (the patron's accountant, family member) who would naturally relay the information. The legal test under post-reform s.123 is whether covered information has been disclosed AND the disclosure would or could reasonably be expected to prejudice an investigation; operationally, treat every indirect disclosure as if it meets both limbs.
Yes — and this is the most common operational question. Customer-due-diligence (CDD) questions, source-of-funds enquiries, identification requests, and ongoing-monitoring conversations are all permitted, even when they're triggered by a suspicion that a report may be needed. The key is framing: the conversation has to land within the venue's normal CDD framework ('our AML/CTF program requires us to ask about source of funds for cash transactions over $X'), not as a special enquiry tied to a specific suspicion. The AMLCO's program documents the standard CDD scenarios; staff follow the program; the patron experiences a CDD interaction, not a suspicion enquiry.
Permitted, with care. Internal discussion among the AMLCO, senior management, the AML consulting firm engaged by the venue, and AUSTRAC itself is allowed and necessary — the SMR has to be drafted, reviewed, lodged, and tracked. The protection extends to the people who genuinely need to know for AML/CTF purposes. The risk pattern is informal disclosure outside that chain — mentioning the SMR to a director who isn't on the AML committee, discussing it with a venue lawyer who isn't engaged on AML matters, or letting the substance leak into general management meetings. The structural protection is to keep AML discussions in defined channels with defined participants.
If a patron asks whether an SMR has been or will be filed about them, the safest practice is to neither confirm nor deny. The response should redirect to the venue's general AML obligations ('we operate under the AML/CTF Act 2006 and follow our AML/CTF program; we're not able to discuss specific compliance matters about any individual patron') and, where appropriate, suggest the patron seek their own legal advice. Confirming an SMR can be tipping off — it discloses covered information and would typically meet the prejudice test under s.123(1)(d). An explicit denial where an SMR exists can also be tipping off, because the denial discloses information by negation; whether the offence is made out then depends on whether the disclosure meets the prejudice test on the facts. Silence on specifics is the only response that reliably stays inside the rule.
The AML/CTF Act tipping-off provisions sit alongside the Privacy Act and modify the venue's normal data-access obligations. Australian Privacy Principle 12 (access to personal information) requires reporting entities to give individuals access to their personal information on request — but APP 12 has an exception where access would be inconsistent with another law. Tipping-off provisions are exactly such a law. A reporting entity faced with a patron's APP 12 request can refuse access to information that, if disclosed, would tip off the patron about an SMR. The OAIC and AUSTRAC have published guidance on managing this intersection; the practical answer is the AMLCO and the privacy officer coordinate access requests where suspicion-related records are involved.
Five areas. (1) What tipping off is and why it matters — the integrity-of-intelligence rationale, plus the four conjunctive elements under s.123. (2) The boundary cases — indirect disclosure, third-party leaks, behavioural-change leakage. (3) The framing of CDD interactions so they don't reveal underlying suspicion (standard CDD vs. enhanced CDD vs. suspicion-triggered conversation). (4) The internal communication channels for SMR-related discussion (who can talk to whom about what). (5) The patron-enquiry script — what to say if a patron asks. Training is a required content item of the venue's AML/CTF policies (AML/CTF Act s.26F) and is delivered regularly at the frequency the program specifies; training records are retained as part of the program records (s.116).
How to draft a defensible Suspicious Matter Report — the document tipping off protects.
The most common pattern that triggers SMRs in gaming venues, and how to detect it.
Who is responsible for managing tipping-off boundaries day-to-day, and what training they have to deliver.
SMR workflow that stays in defined chains, role-based access that limits casual disclosure, audit trails that show who knew what when. First three months free, no card up front.