Compliance Guide 2026

AFSL Monitoring Requirements: What Every Licensee Must Have in Place

Vincent Keogh23 April 202612 min read

AFSL monitoring requirements for Australian financial services licensees — Callyx.ai
Executive Summary

Under section 912A(1)(ca) of the Corporations Act 2001, every AFSL holder must take reasonable steps to ensure their representatives comply with financial services laws. For firms relying on manual call sampling, that standard is increasingly difficult to meet — and ASIC is paying attention. Callyx.ai automatically monitors 100% of your recorded conversations, turning a compliance obligation into operational intelligence with no manual effort required.

01

The AFSL Monitoring Obligation ASIC Actually Cares About

ASIC's enforcement posture has hardened significantly since the Hayne Royal Commission handed down its final report in 2019. Of the many systemic failures identified across the industry, the most consistent thread was not deliberate misconduct — it was a persistent failure by licensees to actually supervise what their representatives were doing. Since 2020, ASIC has secured more than $700 million in civil penalties against financial services firms, with a significant proportion relating directly to inadequate monitoring and supervision arrangements.

The legal trigger is section 912A(1)(ca) of the Corporations Act 2001, which requires every AFSL holder to take reasonable steps to ensure their representatives comply with financial services laws. ASIC's Regulatory Guide 104 expands on what "reasonable steps" looks like in practice — and it goes well beyond having a compliance policy on file. Firms relying on complaint-driven monitoring, rather than proactive systematic review, are unlikely to meet the standard.

This guide breaks down exactly what the monitoring obligation requires, where most licensees are currently falling short, and how Callyx.ai closes the gap between what ASIC expects and what most compliance teams can realistically deliver at volume.

Three numbers that define the monitoring gap facing most AFSL holders:

  • $700M+ in civil penalties secured by ASIC since 2020 — much of it tied to inadequate supervision and monitoring failures.
  • 30 days to report a significant breach under s.912D once identified — or face compounded liability for late reporting.
  • 3% of calls reviewed on average by firms using manual monitoring — leaving 97% of conversations unexamined.
02

The Legal Framework Behind Your AFSL Monitoring Obligation

The monitoring obligation doesn't sit in one place. Several pieces of legislation and regulatory guidance interact to create a layered compliance requirement — and understanding all of them is necessary to assess whether your current approach is actually adequate.

Together, these instruments establish that monitoring is not a discretionary activity — it is a legal obligation with a live 30-day breach reporting trigger attached. A licensee who discovers a pattern of non-compliance only through a client complaint, rather than systematic monitoring, is likely to find themselves in breach of both the supervision obligation and the breach reporting timeline simultaneously.

Corporations Act 2001 (Cth) s.912A(1)(ca)

CORE MONITORING OBLIGATION

Requires AFSL holders to take "reasonable steps" to ensure representatives comply with financial services laws. This is the core ongoing monitoring obligation — it cannot be satisfied by passive record storage alone.

Corporations Act 2001 (Cth) s.912D

BREACH REPORTING — 30-DAY WINDOW

Breach reporting obligation. Licensees must identify and report significant breaches within 30 days of becoming aware. This makes proactive monitoring a prerequisite — you cannot report what you haven't detected.

ASIC Regulatory Guide 104

MEETING THE GENERAL OBLIGATIONS

Provides detailed guidance on what ASIC considers adequate monitoring of representatives, including documentation requirements, methodology, escalation pathways and record-keeping.

Privacy Act 1988 (Cth)

AUSTRALIAN PRIVACY PRINCIPLES

The Australian Privacy Principles govern how client information captured in recorded calls must be stored, accessed and used — including for monitoring purposes. Monitoring programmes must be compatible with privacy obligations.

Telecommunications (Interception and Access) Act 1979 (Cth)

CALL RECORDING CONSENT

Establishes consent requirements for call recording in Australia. Participants must be informed that calls may be recorded. Relevant to both your recording programme and any monitoring activity built on top of it.

03

What "Reasonable Steps" Actually Means for Your Monitoring Programme

The phrase "reasonable steps" in section 912A(1)(ca) sounds deceptively manageable. In practice, ASIC's interpretation has become increasingly demanding. Regulatory Guide 104 makes clear that reasonable steps must be proportionate to the nature, scale and complexity of the licensee's business — which means a firm with 40 advisers providing personal advice to retail clients cannot satisfy the obligation by having a compliance officer listen to two calls per adviser per quarter.

What ASIC looks for is a systematic, documented monitoring programme with defined scope, methodology, frequency and escalation procedures. The monitoring must be capable of identifying both individual adviser conduct issues and systemic patterns across the business. Critically, the programme must generate records — ASIC will ask to see evidence of your monitoring activity, not just your monitoring policy.

"The obligation to monitor representatives is active and ongoing. Having the capability to monitor is not the same as monitoring."

ASIC Regulatory Guide 104 — Licensing: Meeting the General Obligations

This is where scale becomes the defining challenge. A licensee with 30 advisers each making 20 client calls per week generates more than 2,400 recorded conversations every month. A compliance team of two cannot meaningfully review that volume manually — and ASIC knows it. Callyx.ai resolves this by automatically scanning every call for the compliance signals your programme is designed to detect, generating a documented record of each review without any manual effort from your team.

The practical implication is that your monitoring programme needs to be designed around what you can sustainably operate at volume — not what looks adequate in a policy document. For the full picture on what ASIC expects, read Regulatory Guide 104 in full.

04

The Five AFSL Monitoring Failures That Land Firms in Trouble

Working with Australian financial services firms, we see the same monitoring gaps appear repeatedly — not because compliance teams don't care, but because the volume of calls makes thorough manual review genuinely impossible to sustain.

1. The 2–3% Sampling Problem

Most firms using manual monitoring review a small fraction of calls, selected at random or by the compliance team. The overwhelming majority of client conversations — including those most likely to contain conduct issues — are never reviewed. When ASIC investigates, the absence of coverage is itself evidence of an inadequate programme.

2. No Documented Monitoring Framework

Having a policy that says "we monitor calls" is not a monitoring framework. ASIC expects documented criteria for what is being monitored, how often, by whom, what the escalation pathway is, and how outcomes are recorded. Many firms have the policy but not the substance behind it.

3. Complaint-Triggered Monitoring Only

Monitoring that activates only after a client complaint is retrospective, not proactive. By the time a complaint surfaces, the conduct has already occurred — often repeatedly. ASIC's position is that proactive monitoring is required to meet the reasonable steps standard under s.912A.

4. Monitoring That Produces No Records

Listening to calls without documenting outcomes is not monitoring for compliance purposes. ASIC will ask for evidence of your monitoring programme — call-by-call records, outcomes, escalations. If your current process doesn't generate those records automatically, you have a material gap.

5. No Connection Between Monitoring and Coaching

Monitoring should drive remediation. Firms that identify conduct issues but have no structured pathway to address them at the adviser level are only doing half the job — and ASIC has been explicit that the loop must close. Intelligence without action is just documentation.

05

What ASIC Looks For When They Review Your Monitoring Programme

When ASIC conducts a surveillance or investigation of an AFSL holder's monitoring arrangements, they are looking for three specific things — and most firms are only prepared for one of them.

A Systematic, Evidenced Monitoring Programme

ASIC will ask for your monitoring framework, methodology, review records and escalation outcomes. They want to see that monitoring is happening systematically across your full representative population — not just when a complaint prompts it. See RG 104 for the standard.

Speed of Breach Identification

Under s.912D, once a significant breach is identified, the 30-day reporting clock starts. ASIC will assess whether your monitoring is capable of identifying breaches in a timeframe that makes that window achievable. Callyx.ai surfaces potential compliance flags in real time — not weeks after the fact.

Representative-Level Conduct Data

ASIC increasingly expects licensees to produce conduct data at the individual representative level — not just aggregate statistics. They want to know which advisers are consistently meeting disclosure standards, which aren't, and what you've done about it.

06

Turn Your Monitoring Obligation Into a Business Asset

The monitoring obligation is real, the enforcement risk is real, and the volume of calls makes manual compliance genuinely unsustainable for most firms. But there is a better way to think about it: the calls you are already recording contain some of the most valuable intelligence your business generates. Every conversation with a client captures what is working in your process, where advisers need support, and how clients are actually experiencing your firm.

Callyx.ai connects to your existing call recording setup, is configured to your specific compliance obligations during onboarding, and starts delivering intelligence from day one — with zero manual effort required from your compliance team. Your calls are already being recorded. Now make them count.

Automated Call Monitoring

Callyx automatically scans 100% of your recorded calls for disclosure gaps, fee discussions, complaint signals and conduct patterns. Every call reviewed, every time, with a documented record your compliance team can produce on demand.

Complete Call Records

Every call is transcribed, summarised and stored in a searchable archive. When ASIC asks for evidence of a specific conversation or an adviser's conduct history, you can produce it in minutes — not days.

Real-Time Compliance Alerts

Callyx flags conversations matching your defined compliance triggers before they have a chance to escalate. Catch a potential breach in real time — not weeks later when a client complaint lands on your desk.

Individual Adviser Intelligence

See exactly which advisers are consistently meeting your monitoring standards and which need support. Turn your compliance programme into a coaching pipeline that actually improves conduct across the business.

Callyx.ai connects to your existing call recording setup, is configured to your specific compliance obligations during onboarding, and starts delivering intelligence from day one — with zero manual effort required from your compliance team.

07

AFSL Monitoring: The Old Way vs the Callyx Way

Most firms are still operating their monitoring programme the way they always have — not because it works, but because there hasn't been a better option. Here's what that actually looks like, alongside what's now possible.

Without Callyx.ai
  • Compliance team manually reviews 2–3% of recorded calls — the rest go unheard
  • Call selection is ad hoc or random — high-risk conversations are never prioritised
  • No documented record of which calls were reviewed or what was found
  • Conduct issues surface only after a client complaint — by then, it's already too late
  • ASIC requests for call records and monitoring evidence take days to fulfil
  • Adviser performance data is anecdotal — coaching is guesswork
With Callyx.ai
  • 100% of recorded calls automatically scanned for compliance signals — nothing is missed
  • Every call reviewed against your defined monitoring criteria, consistently and at scale
  • Documented compliance record generated automatically for every conversation
  • Real-time alerts flag potential conduct issues before they escalate to complaints
  • Any call retrievable within seconds — full ASIC evidence package ready on demand
  • Adviser-level conduct data updated after every call — coaching becomes evidence-based
08

What You Need to Know

Under section 912A(1)(ca) of the Corporations Act 2001, every AFSL holder must take reasonable steps to ensure their representatives comply with financial services laws. ASIC's interpretation of that obligation has become increasingly demanding — documented, systematic, coverage-based monitoring is the standard, not periodic sampling of a small fraction of calls.

Most firms are operating with a monitoring gap they don't know exists. Manual call sampling covers a fraction of recorded conversations, leaves the majority of potential conduct issues undetected, and generates limited documentary evidence that ASIC will consider adequate. The 30-day breach reporting obligation under s.912D makes this gap a compliance risk in its own right — you cannot report what you haven't detected.

Callyx.ai automatically monitors 100% of your recorded calls, generates documented compliance records for every conversation, and delivers real-time alerts for your defined conduct triggers — turning an unsustainable manual obligation into an automated, always-on programme that costs your compliance team almost no time to run.

Frequently Asked Questions

About the Author

VK

Vincent Keogh

Vincent is an operations specialist on the Callyx.ai team, writing for compliance managers and principals on how to get maximum value from recorded calls: across compliance, staff training, and business performance.

This article provides general information about AFSL monitoring requirements as at April 2026. It is not legal advice. Regulatory requirements can change, and the specific obligations applicable to your licence depend on your authorisations, the nature of your client base, and the services you provide. Seek advice from a qualified compliance professional or AFSL lawyer for guidance specific to your situation.

Your calls are already being recorded.
Now make them count.

Recorded advice conversations are reviewed against your compliance criteria, with issues flagged and documented. Less reliance on sampling. Fewer blind spots.