Key Takeaways
- The trigger is suspicion on reasonable grounds, not proof.
- 3 business days for most SMRs, 24 hours for terrorism-financing matters.
- Section 123 makes tipping-off a criminal offence punishable by up to 2 years imprisonment, 120 penalty units, or both.
- The tipping-off rule has narrow exceptions (internal staff involved in lodgement, AUSTRAC, legal advice, the reporting group).
- Structure the workflow so the engagement partner can keep the file running while the Compliance Officer handles the SMR.
In this guide
What an SMR is When the suspicion threshold is crossed The two timelines: 3 business days and 24 hours The tipping-off offence in plain English How to discuss the matter internally without breaching s123 Three accounting scenarios What to record How AMLTranche handles the SMR workflow Frequently asked questionsWhat an SMR Is
A Suspicious Matter Report is a structured report that a reporting entity lodges with AUSTRAC when it forms a relevant suspicion about a customer or a transaction. The legal basis is the AML/CTF Act and the operational detail is in AUSTRAC's SMR guidance and the broader reporting overview.
For accountants brought into the regime by Tranche 2, the SMR sits at the intersection of three other obligations: customer due diligence (the firm learns enough about the client to recognise a red flag), ongoing monitoring (the firm spots a transaction that does not fit the customer's profile), and the firm's program (which describes how staff escalate a concern to the Compliance Officer). It is the operational endpoint of the rest of the program.
The full picture, including how SMRs fit alongside enrolment, CDD and the program, is in our accountants Tranche 2 guide. The wider section 123 walkthrough sits in our tipping-off section 123 guide.
When the Suspicion Threshold Is Crossed
The legal test is suspicion on reasonable grounds. The practitioner does not need proof. The practitioner does not need to know what the offence is. The practitioner does need to be in a position where, taking all the available information together, a reasonable person in the same role would suspect that the customer or the transaction is connected to one of the offences listed in the AML/CTF Act. Those include the proceeds of crime, terrorism financing, tax evasion, structuring, and a range of other federal offences.
What triggers a reasonable suspicion is judgement, not a checklist. AUSTRAC's published risk-and-indicators material lists patterns that experience has shown turn up in genuine cases. For an accountant the most common red flags include:
- Unexplained source of funds, especially large amounts of cash, third-party transfers, or money from jurisdictions inconsistent with the client's profile.
- Overly complex structures with no apparent commercial rationale (multiple thin entities in a chain, offshore layers, last-minute trustee swaps).
- A client unwilling to provide CDD information, evasive about beneficial ownership, or pushing back on standard questions.
- A client in a hurry, asking the firm to act before CDD is complete, or pressing for the firm to short-cut the process.
- Round-number transactions that look designed to stay just under threshold reporting amounts.
- Transactions inconsistent with the client's stated business (a small bookkeeping client suddenly buying a multi-million-dollar property through a new trust).
- A change in instructions immediately after a CDD question is asked.
No single indicator is conclusive. The test is the combination. Two or three of the above on the same file, taken together, will usually cross the threshold for at least an internal escalation.
The Two Timelines: 3 Business Days and 24 Hours
The lodgement clock starts when the suspicion is formed, not when the underlying transaction happens and not when the matter is first raised. That distinction matters in practice: an issue can sit on a file for weeks without crossing the threshold, and then cross it the moment a fresh piece of information lands.
- General SMRs: lodge with AUSTRAC inside 3 business days after forming the suspicion.
- Terrorism-financing matters: lodge inside 24 hours after forming the suspicion.
Lodgement is done online through AUSTRAC Online. The SMR captures the customer details, the transaction details, the grounds for suspicion, and any supporting information. The format is structured and the Compliance Officer normally drives lodgement with input from the engagement partner on the file. Late lodgement is itself a contravention of the Act, so the operational rule of thumb is to lodge inside the timeframe even if the report is later supplemented with further detail.
The Tipping-Off Offence in Plain English
Once an SMR is in play, section 123 of the AML/CTF Act kicks in. AUSTRAC's tipping-off guidance is the operational source.
In plain English, section 123 prohibits a reporting entity (and certain other persons connected to one) from disclosing information that would or could prejudice the SMR. The classic case is telling the client that a report has been lodged. It also covers disclosure that an SMR is being considered, disclosure that AUSTRAC has been contacted, and disclosure of information likely to put the customer or another person on notice of any of those things.
The offence is criminal. The maximum penalty is 2 years imprisonment, 120 penalty units, or both. The point is to stop the customer from disposing of assets, destroying records, or fleeing. For an accountant that means the firm cannot let the client see the SMR thinking on a file, cannot warn the client off, cannot encourage the client to "fix" something before AUSTRAC looks at it, and cannot drop hints that change the client's behaviour.
There are narrow exceptions in the Act. Disclosure inside the reporting entity for a permitted purpose (for example, to the staff actually working on lodgement, or to the Compliance Officer making the call) is allowed. Disclosure to AUSTRAC is allowed. Disclosure to a lawyer for the purpose of obtaining legal advice is allowed. Disclosure within the reporting group is allowed in defined circumstances. The exceptions are tightly drawn; treat them as exceptions, not as the default.
How to Discuss the Matter Internally Without Breaching s123
The hardest part of section 123 for an accounting firm is operational. The matter usually comes up in a conversation between an engagement partner and a junior staff member, both of whom continue to deal with the client. The legal rule says the firm cannot tip off the client. The practical question is: how do you keep working a file you cannot fully discuss?
The standard pattern in firms that handle SMRs well looks like this:
- Escalation in writing. The staff member who first sees the red flag writes a short escalation to the Compliance Officer (not to the engagement partner directly). The escalation goes to one person, not a group chat.
- Role split. The Compliance Officer becomes the SMR owner. The engagement partner continues client work where doing so does not itself prejudice the SMR.
- Limited internal circle. Only the people who need to know to lodge the SMR have access to the SMR file. The system records who looked, when, and why.
- Client-facing script. The engagement partner is briefed on what they can and cannot say. Routine engagement conversations continue. Anything that would reveal the SMR (or that one is being considered) does not.
- Legal advice when needed. Disclosure to a lawyer for the purpose of obtaining legal advice on the firm's obligations is permitted. Where the file is borderline, the call goes to counsel.
- Hard stop on certain instructions. If the client asks for something that would force the firm into a tipping-off position (for example, "please explain what AML checks you have done on this file"), the engagement partner refers the question to the Compliance Officer and considers whether continued engagement is appropriate.
The role-split is the part that prevents tipping-off by design. When the engagement partner does not know the precise SMR detail, they cannot accidentally reveal it. When the Compliance Officer drives the report, they manage the disclosure boundary.
Three Accounting Scenarios
The threshold is easier to feel with worked examples. The three below are common patterns we hear about from accounting firms preparing for Tranche 2. None is a hypothetical AUSTRAC case study; they are illustrations only.
Scenario 1: The "set up a structure by Friday" client
A new client walks in on Wednesday and asks the firm to incorporate a Pty Ltd with a discretionary trust beneficiary, source a nominee director, and have a registered office address in place by Friday. The client says the purpose is "to take a property". The client will not provide bank statements, will not say who the funds come from, and is impatient when CDD questions are asked. By Thursday the file has multiple red flags: urgency, opacity, nominee structure, refusal to engage on source of funds.
The pattern crosses the suspicion threshold once the Thursday refusal is on the record. The engagement partner escalates in writing to the Compliance Officer. The Compliance Officer drafts and lodges the SMR within 3 business days. The firm declines to act further. The decline is communicated to the client without reference to the SMR or to AUSTRAC.
Scenario 2: The unexplained in-specie SMSF transfer
A long-standing SMSF client has historically held listed Australian equities and a small property. The fund's accountant receives instructions to accept an in-specie contribution of a foreign-domiciled trust interest with no recent valuation, no source-of-wealth documentation for the contributing member's offshore holdings, and a transaction structure routed through two intermediate entities. The member's stated occupation does not align with the value being contributed.
This is a classic case where the SMSF accountant has formed a reasonable suspicion. The Compliance Officer lodges the SMR inside 3 business days. The engagement partner continues routine SMSF work (compliance audit prep, financial statements) where doing so does not prejudice the SMR.
Scenario 3: Round-number cash deposits ahead of a business sale
The firm is acting on the sale of a hospitality business. Two days before completion, the seller's bank statements show a series of cash deposits, each just under reporting threshold amounts, made into the business account over the previous fortnight. The seller's explanation ("tips") does not align with the venue's known revenue profile or the prior twelve months of statements.
The structuring pattern is itself a red flag. The Compliance Officer lodges the SMR. Whether the firm completes the sale is a separate decision involving the file partner, the Compliance Officer and (where appropriate) external legal counsel. The client is not told an SMR has been lodged.
What to Record
Every SMR-relevant file generates records that stay in the firm's 7-year audit trail. The minimum set is:
- The escalation note from the staff member to the Compliance Officer.
- The Compliance Officer's analysis: what the suspicion is, the grounds for it, what was considered, what was decided.
- The SMR itself and the AUSTRAC Online lodgement receipt.
- Any related CDD documents and screening hits.
- Internal access logs showing who saw the SMR record and when.
- Any communications with AUSTRAC about the report.
- The decision on continued engagement, including the rationale.
Records are kept in a way that supports both audit (the firm can prove what it did) and section 123 (only authorised staff can see them). A shared folder on a partner's laptop is not enough. The recordkeeping standard is set out in AUSTRAC's recordkeeping guidance, and the broader penalty picture for getting it wrong sits in AUSTRAC's consequences of not complying page.
What can go wrong
Two common failure modes turn an SMR situation into an enforcement matter. The first is late lodgement: the firm sat on the suspicion, hoped it would resolve, and missed the 3-business-day window. The second is inadvertent tipping-off: a partner mentioning the report in a corridor conversation, a staff member writing the SMR detail into a client-facing file note, or a billing description referencing AUSTRAC. Both are avoidable with a clear escalation path, a tight role split, and a system that controls who sees what.
How AMLTranche Handles the SMR Workflow
AMLTranche treats the SMR pathway as a designed workflow, not as a Word template. A staff member escalates a concern in the platform. The escalation routes to the Compliance Officer, not to the engagement partner. The SMR draft has the timeline countdown built in (3 business days for general SMRs, 24 hours for terrorism financing). Access is role-based, so the engagement partner sees only what they need to keep working the file without tipping off. Every access event is recorded against the SMR with a time stamp.
The SMR draft, the supporting CDD, the screening results and the lodgement receipt sit together in the 7-year tamper-proof audit log hosted in AWS Sydney. The full feature set and pricing for accountants is on the AML software for accountants page.
Run accountant SMRs with tipping-off controls by design
Structured escalation, role-split workflow, built-in timelines, and a 7-year audit log. Plans from $59/mo.
See the accountants page Book a DemoFrequently Asked Questions
What is the suspicion threshold for an SMR?
Suspicion on reasonable grounds. A reasonable person in the same role would suspect that the customer or the transaction is connected to a proceeds-of-crime offence, a terrorism-financing offence, tax evasion or another offence listed in the AML/CTF Act. The threshold is well below proof.
What are the SMR lodgement timelines?
3 business days from forming the suspicion for general SMRs. 24 hours for terrorism-financing matters. The clock starts when the suspicion is formed, not when the underlying transaction occurred.
What is the tipping-off offence?
Section 123 of the AML/CTF Act prohibits disclosure of information that would or could prejudice an SMR, including the fact that one has been lodged or that one is being considered. Maximum penalty: 2 years imprisonment, 120 penalty units, or both.
Can the accountant talk to the client about the file at all once an SMR is in play?
Yes, but carefully. The engagement can continue up to the point where doing so would prejudice the SMR. The accountant cannot reveal that an SMR has been lodged, that one is being considered, or that AUSTRAC has been contacted. Where a client question would force the practitioner into territory that would tip off, the question goes to the Compliance Officer.
Are there exceptions to the tipping-off prohibition?
Yes, but narrow ones. Disclosure within the reporting entity to staff involved in lodgement, disclosure to AUSTRAC, disclosure to a lawyer for the purpose of legal advice, and certain disclosures within the reporting group are permitted in defined circumstances. When in doubt, the file goes to the Compliance Officer and to legal counsel.
Disclaimer: This article provides general information about Suspicious Matter Reports and the section 123 tipping-off prohibition for Australian accounting firms. It is not legal advice. Confirm your specific obligations with AUSTRAC or a qualified legal adviser.