FAQ

When does a compliance breach become a reportable situation under ASIC’s regime?

SIC’s reportable situations regime applies when an AFS licensee identifies a breach, or likely breach, that is significant, deemed significant under the Corporations Act, constitutes gross negligence or serious fraud, or involves certain investigations that continue beyond prescribed timeframes. Not every compliance breach is reportable. Reporting is required when the breach meets a statutory reporting trigger.

Expanded Answer

The reportable situations regime requires AFS licensees to assess more than whether a breach occurred. The key question is whether the breach meets one of the reporting triggers established under the Corporations Act. A breach becomes reportable when it is significant, automatically deemed significant by law, involves gross negligence or serious fraud, or falls within investigation reporting requirements. ASIC expects licensees to apply a structured and evidence-based assessment process rather than relying on subjective judgement.

For financial advisers operating under an AFSL, the reporting obligation generally sits with the AFS licensee rather than the individual adviser. Licensees should have systems that identify incidents, assess significance, document decisions, escalate potential reportable situations, and maintain evidence supporting the outcome. A breach may be reportable even where client loss is limited if the conduct reflects systemic weaknesses, repeated failures, ineffective controls, or breaches specifically deemed significant by legislation.

Key obligations:

  • A reportable situation must be assessed against statutory reporting triggers.
  • Significance must be evaluated using documented criteria and evidence.
  • Reportable situations must be lodged with ASIC within the applicable reporting timeframe.

Not required when:

A breach does not meet a reporting trigger and is not otherwise deemed significant under the regime.

Why it matters

Failure to identify and report reportable situations can create separate compliance breaches and attract regulatory scrutiny. ASIC increasingly focuses on governance, escalation pathways, root-cause analysis, and whether licensees can demonstrate a consistent and defensible breach assessment process.

Unsure how this applies to you?

Get a clear answer in a 15-minute call with a compliance specialist. Book your call

Practical guidance

  • Assess every compliance incident against documented reportable situations criteria.
  • Document the rationale for significance assessments and reporting decisions.
  • Escalate potential reportable situations promptly to the AFS licensee’s compliance function.

Further reading

Report or not: managing breaches

The Reportable Situations Framework: A Practical Approach to ASIC Breach Reporting

Why compliance reporting matters for licensees

Subscribe

Every fortnight “Three Hit Tuesday” delivers thought leadership, considered analysis and insights that will help you improve your advice, more effectively manage your regulatory risks and make you better informed than your peers.

AS-Subscribe Form

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

We respect your privacy. We know everyone says that, but we promise that we won’t sell your contact details to dodgy telemarketers, spam your email or otherwise exploit your trust.

Step 1 of 8 - Your Role

This field is for validation purposes and should be left unchanged.

Assess your ASIC exposure

Answer a few targeted questions to identify where your compliance may not stand up under ASIC review.

Takes less than 2 minutes. No preparation required.

What best describes your role?