Reportable Situations (Part 2): How to Meet (and Exceed) ASIC’s Expectations

“It’s the terror of knowing what this world is about…”

Queen & David Bowie

What’s Happening

It’s a scary world out there! ASIC’s 2024 review of breach reporting shows many Australian Financial Services (AFS) licensees are falling short.

Even with a small sample, the findings highlight ongoing problems with how breaches are reported, how fast they’re reported, and whether firms are getting to the root cause.

ASIC reviewed:

  • The reportable situations by licensees between Oct 2021 and Jun 2024
  • Internal incident registers from a 3-month period in 2023; and
  • Their measures for complying with the regime.

This article builds on Part 1 and outlines what licensees can do to improve.


Updated note: Since publication, ASIC Instrument 2024/620 has modified aspects of the reportable situations regime, including limited carve-outs for some breaches that would otherwise be deemed significant. The practical guidance in this article remains relevant, but reportability should always be assessed against the current form of s912D, RG 78 and applicable ASIC relief.


How to Lift Your Compliance Game

1. Improve How You Find Breaches

What doesn’t kill you makes you stronger

Kelly Clarkson
  • Tools:
    • Implement automated compliance monitoring tools to detect issues early with real-time monitoring and alerts.
    • Tools like [complye] help by improving oversight, spotting unusual activity and reducing the risk of delayed detection and reporting.
  • Regular checks:
    • Check complaints, internal audits, and past incidents regularly. This helps spot issues early so that small issues can be fixed before they become major compliance failures.
  • Training:
    • Train frontline staff to spot and report potential breaches. This training should be mandatory, as the frontline staff deal directly with clients, so they will be the first to notice problems.
    • Regular training with real-life scenarios and ongoing reminders will help identify and report risks, supporting a strong compliance culture.

2. Report Quickly and Correctly

TiK ToK on the clock

Ke$ha
  • Clear reporting process:
    • Create a clear reporting process with roles, timeframes, and escalation paths. This will prevent issues from being missed and dealt with too late, leading to non-compliance.
    • Workflows should clearly assign responsibilities, set due dates, and define when to escalate issues.
    • All staff should understand how to report breaches and their role in the process.
  • Breach Team:
    • Have a compliance team dedicated to breach assessments and reporting to ASIC. Having a team skilled in assessing incidents, deciding if they need to be reported, and submitting reports on time helps avoid mistakes and improves communication across the business.
  • Detailed records.
    • Vague or missing data equals a red flag for ASIC. Licensees need clear, documented processes to identify and track breaches accurately and consistently.
    • If records are not recorded properly, it could suggest underreporting. Some businesses report very few breaches, raising concerns about whether they are identifying breaches correctly.
    • To avoid this, businesses should set clear rules for what counts as a breach, keep detailed records, and regularly review the processes to make sure all breaches are reported.
  • ASIC’s guidelines
    • Use ASIC guidelines to classify and report breaches properly.
    • Licensees should distinguish between a breach, a significant breach and a reportable situation. Under s912D, some breaches of core obligations are deemed significant by operation of law and do not require a separate significance assessment. However, ASIC Instrument 2024/620 now provides limited circumstances in which some breaches that would otherwise be deemed significant are not taken to be significant. Any reliance on these provisions should be carefully documented.
    • Following ASIC’s guidance is crucial, as getting it wrong can lead to penalties and regulatory attention.

3. Get to the Root of the Problem

Root of the problem

Roots Noir
  • Consistent process:
    • Use a consistent investigation process for every breach.
    • Having a clear and structured process, including investigation steps, assigned staff to manage breaches, and a consistent way to assess how serious each incident is and what caused it, will reduce the risk of repeated problems and broader compliance failures.
  • Breach register:
    • Keep a formal breach register with all the facts: what happened, what you did, and how you fixed it. This ensures accountability and transparency.
    • Good record keeping makes it easier to manage issues internally and shows regulators that the Licensee has taken the right steps to deal with breaches.
  • Analytics:
    • Use data analytics to spot patterns and fix recurring issues.
    • Data analytics can also pick up on hidden trends, allowing businesses to take focused action and improve their compliance systems.
  • RG 78:
    • Follow ASIC’s guide (especially Table 8 in RG 78) to structure your breach register. ASIC recommends keeping one detailed breach register that brings together all relevant breach information. This register should include details about each breach, how it was investigated and fixed, and any follow-up monitoring.
    • Keeping the register up to date improves transparency, supports accountability, and provides a clear record for both regulatory reporting and internal compliance.

4. Fix Breaches Fast and Properly

Lights will guide you home

Coldplay
  • Prioritise customers:
    • Put customers first—fix problems quickly and communicate clearly. When something goes wrong, businesses should act fast to understand the problem, be open with affected clients, and take prompt action to fix it.
    • Focusing on client remediation shows strong ethics, meets regulatory expectations, and helps maintain trust in the financial services industry.
  • Compliance staff:
    • Assign a compliance lead to oversee each fix and make sure it’s completed. This ensures clear responsibility and consistent action.
    • This also helps with ongoing checks to stop breaches from happening again.
  • Track and review:
    • Track remediation efforts to ensure the issue doesn’t come back. Regularly tracking and reviewing remediation actions is the key to making sure they work and avoiding a repeat of breaches.

5. Build a Strong Compliance Culture

Take a look at yourself and make a change

Michael Jackson

Accountability, safety and knowledge are all essential elements of your compliance culture.

The following are some suggestions for your business:

  • Protect whistleblowers so staff feel safe raising concerns.
  • Link executive bonuses to compliance outcomes to keep leaders accountable.
  • Provide regular training and test how well your team responds to breach scenarios.
    • Regular compliance training and scenario testing are important to strengthening breach reporting and building regulatory awareness.
    • Training should be engaging, using real examples and interactive activities.

Final Word

ASIC’s message is clear: delays, mistakes, and poor reporting are no longer acceptable.

Licensees must:

  • Detect incidents and potential reportable situations early
  • Report them properly and on time
  • Fix root causes
  • Prioritise customers
  • Make compliance a core part of their culture

Need help? Talk to Assured Support. We help Licensees stay ahead of ASIC’s expectations and reduce regulatory risk.

Don’t wait for trouble—act now.

Read ASIC’s full review here.

If you enjoyed this article, you might also like:


Frequently Asked Questions

What are ASIC’s key concerns about breach reporting?

ASIC is concerned about delayed, incorrect, or inconsistent breach reporting by AFS licensees. Their 2024 review revealed ongoing issues in identifying, assessing, and reporting breaches in line with regulatory expectations.

How can AFS licensees improve breach detection?

Licensees should adopt automated compliance monitoring tools, conduct regular internal reviews, and train frontline staff to recognise and report potential breaches early. Proactive detection helps prevent minor issues from escalating.

What makes a breach report compliant with ASIC’s guidelines?

A compliant breach report includes timely submission, detailed records, accurate classification, and adherence to ASIC’s RG 78 guidelines. A dedicated breach team and clear reporting workflows ensure consistency and avoid regulatory penalties.

Why is root cause analysis important in breach management?

Root cause analysis helps prevent recurring compliance issues. Using consistent investigation procedures, maintaining a detailed breach register, and applying data analytics can uncover trends and support long-term remediation.

How can businesses build a strong compliance culture?

A strong compliance culture includes whistleblower protection, leadership accountability, regular training, and scenario-based testing. Linking executive performance to compliance outcomes encourages ethical and proactive behaviour.

Keep exploring

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?