SMR Deadlines: 3 Business Days, 24 Hours, and What Happens When You Miss Them

The SMR deadlines in the AML/CTF Act are strict and short. Missing them is a civil penalty contravention. Here is what the deadlines actually require, when the clock starts, and how to build a compliance program that never runs out of time.

The Two Statutory Deadlines

The AML/CTF Act imposes two SMR deadlines based on the nature of the suspicion:

24 Hours — Terrorism-Related Matters

If the suspicion relates to financing of terrorism, the SMR must be filed with AUSTRAC within 24 hours of the suspicion being formed. This is a continuous-clock deadline — it does not pause for business hours, weekends, or public holidays.

3 Business Days — All Other Matters

For all other suspicious matters — money laundering, proceeds of crime, tax evasion, other serious criminal activity — the SMR must be filed within 3 business days of the suspicion being formed. Business days exclude weekends and public holidays in the location where the suspicion was formed.

These deadlines are set by Part 3, Division 4 of the AML/CTF Act. They are not targets or guidelines. Missing a deadline is a specific civil penalty contravention with penalties up to $33 million per occurrence for corporations.

When Does the Clock Start?

This is the most important and most misunderstood aspect of SMR deadlines. The clock starts at the moment a person within the reporting entity forms the suspicion. It does not start when:

  • The transaction occurred (that can be much earlier)
  • A senior manager is informed
  • A consultant confirms the view
  • The compliance officer returns from leave
  • The SMR draft is ready for review
The clock starts when the suspicion is formed — not when it is acted on.
If a front-line staff member forms a suspicion on Monday, escalates on Tuesday, and the compliance officer starts work on it Thursday, the 3-business-day deadline is already strained. The delay between formation and action is not a pause in the statutory clock.

What “Forming Suspicion” Means

Suspicion is formed when a person at your venue concludes, on reasonable grounds, that the matter may relate to criminal activity of the types listed in the Act. The conclusion does not have to be articulated formally — it can be the moment a staff member thinks “something about this is wrong.”

The responsibility to act on the suspicion rests with the reporting entity, not the individual. Once any staff member has formed the suspicion, the venue as a whole is on the clock — regardless of whether the suspicion has yet been communicated to the compliance officer.

The Implication — Fast Internal Escalation

Because the statutory clock starts at the moment of formation, your venue’s internal escalation process must be fast. Slow escalation does not reset the clock; it eats into the time available for assessment and drafting.

Well-Designed Escalation Timeline

  • Hour 0: Staff member forms suspicion during shift
  • Hour 1 (or end of shift): Flag logged in compliance system and escalated to compliance officer
  • Hour 4–24: Compliance officer reviews flag, assesses grounds, makes filing decision
  • Hours 24–72 (Day 1–3): Compliance officer drafts, reviews, files SMR

A 3-business-day deadline looks generous on paper. In practice, once you subtract the time needed for escalation, assessment, drafting, review, and submission, the compliance officer often has less than a full business day of actual drafting time.

Calculating Business Days

Business days exclude weekends and public holidays. The excluded days are those in the location where the suspicion was formed — the state or territory of the venue.

Worked Examples

Example 1 — Suspicion on a Tuesday

Suspicion formed Tuesday 14 April 2026 at 15:00. Three business days later is Friday 17 April 2026 at 15:00. SMR must be filed by end of Friday.

Example 2 — Suspicion on a Friday

Suspicion formed Friday 17 April 2026 at 22:00. Three business days later skips the weekend — Monday 20 April, Tuesday 21 April, Wednesday 22 April. SMR must be filed by end of Wednesday.

Example 3 — Around a Public Holiday

Suspicion formed Wednesday 22 April 2026 (before Anzac Day). Anzac Day is a public holiday. Three business days: Thursday 23 April, Monday 28 April (skipping Friday Anzac Day and the weekend), Tuesday 29 April. SMR must be filed by end of Tuesday.

Err on the side of earlier, not later.
Business day calculations are tricky, especially around public holidays and state differences. A venue that consistently files by Day 2 rather than pushing to end-of-Day-3 avoids every ambiguity.

The 24-Hour Deadline

The 24-hour deadline for terrorism-related matters is a continuous-clock deadline. It runs across weekends, public holidays, and overnight. A suspicion formed at 18:00 on Saturday must be filed by 18:00 on Sunday.

This deadline poses a practical challenge: the compliance officer may not be on duty. Your program must describe how terrorism-related suspicions are handled out of hours. Options include:

  • A designated out-of-hours contact process (compliance officer mobile, on-call protocol)
  • A delegation process that allows a designated deputy to file
  • A standing AUSTRAC Online account with the appropriate permissions available to the compliance officer remotely

In practice, genuine terrorism-related suspicions in a pub or club context are rare but not hypothetical. Your program must still be able to handle them.

What Happens When You Miss a Deadline

Missing an SMR deadline is a specific civil penalty contravention. It is also a red flag in any subsequent AUSTRAC compliance assessment — late SMRs signal that the reporting process is not functioning as described in the venue’s AML/CTF program.

Consequences of Late SMRs

  • Civil penalty exposure — each late SMR is a separate contravention, with penalties up to $33 million per contravention for corporations
  • Compliance assessment impact — late SMRs indicate broken internal processes and typically trigger broader scrutiny
  • Intelligence value — SMRs filed late have reduced operational value to AUSTRAC, police, and other agencies, reducing the benefit of filing
  • Aggravation in enforcement — a pattern of late SMRs tends to be treated more severely than isolated instances, and aggregate penalty exposure compounds quickly

In recent enforcement actions, AUSTRAC has treated delayed SMRs as evidence of systemic compliance failure — not just individual late filings. The systemic characterisation increases the penalty base and supports broader findings.

Should You Still File a Late SMR?

Yes. If your venue missed an SMR deadline, file the SMR as soon as the delay is identified. Filing late is a contravention; not filing at all is a more serious and continuing contravention.

In the SMR itself, note the date on which the suspicion was formed and explain the reason for the delay. A candid acknowledgment of late filing is always better than attempting to backdate or obscure the timing — AUSTRAC will detect the timeline through cross-referenced records.

Follow up internally by identifying why the deadline was missed and remediating the process. If the failure was escalation delay, fix the escalation channel. If it was compliance officer unavailability, build in a deputy. If it was drafting time, compress the drafting process.

Building a Timing-Safe SMR Program

Timestamp Everything

Every step of the SMR process should generate a timestamp — staff flag, compliance officer review, drafting start, submission. Timestamped records make deadline calculations automatic and produce the evidence trail AUSTRAC expects to see.

Front-End the Escalation

The most common source of deadline pressure is slow escalation from staff to compliance officer. A well-designed program makes escalation fast and frictionless — a single channel, a clear threshold for what to escalate, no second-guessing.

Build In a Deputy

The compliance officer cannot always be available. A named deputy with training, authority, and AUSTRAC Online credentials prevents the statutory clock from running out during leave or sickness.

Integrate with Transaction Records

SMR drafting is fastest when the underlying transaction records, CCTV references, and identification records are already linked to the escalation flag. A system that pulls everything together into one workspace saves hours of evidence-gathering per SMR.

Do Not Delay Low-Confidence Cases

Some compliance officers delay filing while waiting for additional information or clarification. This is a trap. If grounds for suspicion exist, the clock is running. Waiting for more information does not pause the clock. File on what you know, and provide further information to AUSTRAC under section 43 if new facts emerge.

Where ComplyIQ Fits

ComplyIQ timestamps every step of the SMR lifecycle — staff flag, compliance officer acknowledgement, review, drafting, submission. Deadlines are calculated automatically from the moment of suspicion, with visible countdowns on every open SMR. Source records are linked directly to the flag, so the compliance officer drafts against the evidence in a single workspace. Late-filing risk is managed by design.

For the full SMR guide, see our Suspicious Matter Reports Pillar Guide. For deadline-specific workflows, see our forthcoming How to Write an SMR walkthrough.

The Clock Starts When Suspicion Forms. Your System Should Start Then Too.

ComplyIQ timestamps suspicion from the moment staff flag it, runs deadline countdowns automatically, routes to the compliance officer (or delegate) without delay, and documents every step of the decision trail. Never miss an SMR deadline. One platform for AUSTRAC and state gaming compliance. Support from a team who know your venue.

Book a Demo