Section 142 of the AML/CTF Act makes it an offence to break up transactions to avoid the TTR threshold. Structuring is a common pattern that produces SMRs in gaming venues. What it looks like, how it's detected, and the operational shape of a defensible structuring SMR. Working reference for AMLCOs and cage staff — not legal advice.
Working reference, not legal advice
Whether a specific transaction pattern is structuring is a fact-specific question. For a definitive view, talk to an AML lawyer or an external AML consultant.
Section 142 of the AML/CTF Act 2006 makes it a criminal offence to structure transactions for the purpose of avoiding the threshold-transaction reporting obligation (TTR — cash transactions of AUD 10,000 or more). The elements are: a transaction or series of transactions, broken into smaller amounts, with the purpose of avoiding the TTR obligation. Penalty: up to five years imprisonment, a fine, or both.
Structuring is its own offence so AUSTRAC and AFP can act on the structuring conduct directly, without first proving the broader money-laundering or terrorism-financing matter that prompted the structuring. The conduct is provable from the transaction pattern alone.
For a gaming venue, the practical implication is that detecting structuring is itself a regulatory expectation — the AMLCO's program is expected to surface structuring patterns through transaction monitoring, cage-staff observation, and pattern review. A program that structurally couldn't catch structuring is a program that has a documentation problem.
All three are detection problems with different operational answers. The AML/CTF policies document which detection layer the venue uses for which pattern, with the rule, the threshold, and the data source linked. The post-reform program-documentation requirements (AML/CTF Act 2006 (Cth) s 26F ↗) and record-keeping rules (s 111 ↗ for CDD records, s 116 ↗ for program records) expect the venue to be able to show that documentation against specific transactions when asked.
Structuring is breaking up a transaction (or a series of transactions) into smaller amounts to avoid triggering a reporting threshold — typically the AUD 10,000 cash threshold for Threshold Transaction Reports. Section 142 of the AML/CTF Act 2006 makes it a specific offence to structure transactions for the purpose of avoiding the TTR obligation. Penalty includes imprisonment of up to five years, a fine, or both. Structuring is also a strong indicator of underlying ML/TF activity — someone breaking a $25,000 transaction into three $8,500 buy-ins is doing it for a reason, and the reason is rarely innocent.
Three common patterns. (1) Single-session structuring — a patron walks in, buys $9,500 in chips, plays briefly, cashes out, returns 90 minutes later, buys $9,500 again. The same patron, the same day, with two transactions both just below the threshold. (2) Multi-day structuring — a patron buys $9,500 cash on Tuesday, $9,500 cash on Wednesday, $9,500 cash on Thursday, with similar play patterns each day. (3) Multi-venue structuring — a patron rotates between two or three venues in a region, each visit just below threshold, evading aggregation. The pattern is the breaking-up; the venue's job is to detect it across the relevant time window.
Because the structuring conduct itself is independently provable, even when the underlying ML/TF activity is harder to prove. Demonstrating actual money laundering requires showing that funds are proceeds of crime, which often requires investigation outside the venue's visibility. Demonstrating structuring just requires showing that transactions were broken up for the purpose of avoiding the threshold — which can be evidenced by the transaction pattern itself. The law makes structuring its own offence so AUSTRAC and AFP can act on the structuring evidence without first proving the broader ML/TF picture.
Three layers. (1) Cash-handling-staff observation — the cage staff member who notices a patron buying repeatedly just below threshold and reports the pattern. Human observation is still the strongest signal in many venues. (2) Transaction-pattern monitoring — automated detection across rolling windows (e.g. cumulative cash over 24 hours, 72 hours, 7 days) with alerts when patterns approach but don't cross the threshold. (3) Cross-venue or cross-system aggregation — for venues that participate in multi-venue intelligence sharing or operate across multiple licensed entities, cumulative-pattern detection across the broader footprint. The 2024 Amendment Act sharpens documentation expectations across all three.
Critical. Structuring is fundamentally a behavioural pattern, and well-trained cage staff can see it before any automated system flags it. Training has to cover the typical structuring patterns specific to gaming venues, the reporting workflow when the pattern is observed (usually a flag to the AMLCO, with details captured in the venue's standard observation form), and the tipping-off boundary so the staff member doesn't accidentally reveal scrutiny. The venue's AML/CTF policies document what cage staff are trained on (AML/CTF Act s.26F); the records demonstrate competency; the operational evidence shows the training is producing real flags. AUSTRAC's pubs-and-clubs guidance emphasises employee due diligence and training when assessing structuring detection.
A defensible structuring SMR captures (1) the specific transactions, with dates, amounts, and identifiers, (2) the pattern that crosses the structuring threshold (cumulative amount over a defined window, or pattern of just-below-threshold transactions), (3) the staff observation or system alert that surfaced the pattern, (4) the alternative explanations considered and ruled out (legitimate large-spender pattern, recurring promotional play, etc.), and (5) the supporting records — CCTV timestamps, gaming-system logs, CDD records — that back the suspicion. The five elements are the same as any SMR; structuring just typically has more transaction detail because the pattern itself is the substance.
Yes — and this is the overlap zone covered in /cdd-vs-smr. If the cumulative pattern crosses the $10,000 threshold (which is rare in single-day structuring by design, but common in multi-day), the venue files both a TTR for any single transaction at or above the threshold and an SMR for the structuring pattern. If no single transaction crosses the threshold but the cumulative pattern is suspicious, only the SMR applies — but the SMR is the more important filing because it captures the structuring intent that the threshold-by-itself analysis misses.
Larger venues face a different shape because their cumulative buy-in tracking is typically more sophisticated — patron-account systems track total session activity, machine-system logs aggregate by patron card, and dedicated AML monitoring rules fire on cumulative patterns. The structuring offence applies the same way; the detection layer is more automated. Smaller community clubs without patron-account systems rely more heavily on cash-handling-staff observation and weekly pattern reviews. Both are legitimate operational shapes; both require defensible documentation of the detection layer chosen, anchored to the AML/CTF policies and the record-keeping requirements in ss.107–116 of the Act.
Threshold Transaction Reports vs Suspicious Matter Reports — and how structuring patterns sit across both.
How to operate around a structuring SMR without revealing scrutiny to the patron.
How to draft a defensible SMR for a structuring pattern under the 2024 Amendment Act standard.
Server-side rolling-window cumulative-pattern detection, cage-staff observation flagging, every structuring alert wired to its rule and threshold. First three months free, no card up front.