---
title: "ASIC Calling Compliance for Australian Financial Firms"
description: "Meet ASIC calling compliance requirements with this guide to Market Integrity Rules, hawking prohibitions, and recording obligations in Australia."
canonical: https://callsphere.ai/blog/asic-calling-compliance-australian-financial-services
category: "Guides"
tags: ["ASIC Compliance", "Australian Financial Services", "Market Integrity Rules", "Call Recording Australia", "Hawking Laws", "AFS License"]
author: "CallSphere Team"
published: 2026-04-08T00:00:00.000Z
updated: 2026-05-06T01:02:47.312Z
---

# ASIC Calling Compliance for Australian Financial Firms

> Meet ASIC calling compliance requirements with this guide to Market Integrity Rules, hawking prohibitions, and recording obligations in Australia.

## ASIC's Regulatory Framework for Financial Communications

The Australian Securities and Investments Commission (ASIC) is Australia's integrated corporate, markets, financial services, and consumer credit regulator. For financial services firms that communicate with clients by telephone, ASIC's regulatory framework imposes specific obligations around call recording, disclosure, conduct, and record retention.

ASIC's enforcement posture has intensified significantly. In FY2024-25, ASIC initiated 57 enforcement actions related to financial services conduct, with communication compliance failures cited in 23 of those actions. Civil penalties exceeded AUD $412 million, including several landmark penalties for unsolicited telephone marketing (hawking) violations.

This guide covers the complete framework for ASIC calling compliance, from Australian Financial Services (AFS) license conditions through to the detailed requirements of the Market Integrity Rules and the anti-hawking provisions.

## AFS License Conditions Related to Calling

### General Obligations (Corporations Act 2001, Section 912A)

Every AFS licensee must:

```mermaid
flowchart LR
    CALLER(["Client or Lead"])
    subgraph TEL["Telephony"]
        SIP["Twilio SIP and PSTN"]
    end
    subgraph BRAIN["Financial Services AI
Agent"]
        STT["Streaming STT
Deepgram or Whisper"]
        NLU{"Intent and
Entity Extraction"}
        TOOLS["Tool Calls"]
        TTS["Streaming TTS
ElevenLabs or Rime"]
    end
    subgraph DATA["Live Data Plane"]
        CRM[("CRM and Notes")]
        CAL[("Calendar and
Schedule")]
        KB[("Knowledge Base
and Policies")]
    end
    subgraph OUT["Outcomes"]
        O1(["KYC pre-fill done"])
        O2(["Funding instructions sent"])
        O3(["Compliance officer
escalation"])
    end
    CALLER --> SIP --> STT --> NLU
    NLU -->|Lookup| TOOLS
    TOOLS  CRM
    TOOLS  CAL
    TOOLS  KB
    NLU --> TTS --> SIP --> CALLER
    NLU -->|Resolved| O1
    NLU -->|Schedule| O2
    NLU -->|Escalate| O3
    style CALLER fill:#f1f5f9,stroke:#64748b,color:#0f172a
    style NLU fill:#4f46e5,stroke:#4338ca,color:#fff
    style O1 fill:#059669,stroke:#047857,color:#fff
    style O2 fill:#0ea5e9,stroke:#0369a1,color:#fff
    style O3 fill:#f59e0b,stroke:#d97706,color:#1f2937
```

- **Act efficiently, honestly, and fairly** (s912A(1)(a)) — applies to all telephone communications with clients
- **Comply with financial services laws** (s912A(1)(c)) — including the specific calling requirements detailed below
- **Have adequate risk management systems** (s912A(1)(h)) — which must encompass communication monitoring
- **Maintain competence** (s912A(1)(e)) — staff conducting telephone sales or advice must be adequately trained

### Organizational Competence

ASIC Regulatory Guide 105 (RG 105) requires that representatives providing financial services by telephone have:

- Completed relevant training (typically Tier 1 or Tier 2 under the Financial Adviser Standards and Ethics Authority)
- Demonstrated competence in the specific financial products being discussed
- Ongoing supervision arrangements documented in the licensee's compliance plan

## Anti-Hawking Provisions

### What is Hawking?

The Corporations Act 2001, Part 7.9, Division 8 contains Australia's anti-hawking provisions, which were significantly strengthened in October 2021 through the **Design and Distribution Obligations (DDO) reforms**.

**Hawking** is the unsolicited offer of financial products to retail clients during a telephone call (or in-person meeting) that the client did not request for the purpose of acquiring that product.

### The Current Hawking Prohibition (Section 992A)

Since October 2021, it is an offense to offer a financial product to a retail client during an unsolicited contact (including a telephone call) unless specific conditions are met:

**Prohibited conduct:**

- Cold-calling to sell financial products (insurance, investments, superannuation, credit)
- Offering additional products during a call initiated by the client for a different purpose
- Offering products to a client who was referred from a general marketing campaign without a specific product request

**Permitted conduct:**

- Client specifically requested information about the product prior to the call
- The call is a return call in response to the client's inquiry about that specific product
- The product is offered during an appointment that the client arranged for the purpose of discussing that product type

### Penalties for Hawking Violations

| Entity | Maximum Penalty |
| --- | --- |
| Individual | AUD $1.11 million or 5 years imprisonment or both |
| Corporation | The greater of AUD $5.55 million, three times the benefit obtained, or 10% of annual turnover (capped at AUD $555 million) |

### ASIC Enforcement Examples

In 2024-2025, ASIC brought hawking-related actions against several major financial institutions:

- **Major insurer (2024):** AUD $15.2 million penalty for systematic hawking of add-on insurance during claims calls
- **Superannuation fund (2025):** AUD $8.7 million penalty for offering rollover products during inbound member inquiry calls
- **Retail bank (2025):** AUD $23.4 million penalty for offering credit products during unrelated service calls

## Market Integrity Rules: Recording Obligations

### ASIC Market Integrity Rules (Securities Markets) 2017

Rule 7.3.2 requires market participants to:

- **Record all telephone conversations** and electronic communications in connection with dealing, arranging, or advising in relation to financial products
- **Retain recordings for a minimum of 7 years** from the date of the recording
- **Make recordings available to ASIC** upon request

### Scope of Recording Obligations

The recording obligation covers:

- All calls where orders are received, placed, or executed
- Calls where investment advice is provided
- Calls where arrangements are made for dealing in financial products
- Internal calls between dealers, advisors, and compliance personnel relating to the above

### Technical Requirements

ASIC expects that recording systems:

- Capture both sides of the conversation with adequate audio quality
- Assign unique identifiers to each recording linked to the transaction record
- Support search and retrieval by date, time, participant, and account/transaction reference
- Include tamper-evident controls to prevent alteration of recordings
- Operate continuously during business hours with documented failover procedures

### What Happens When Recording Systems Fail?

ASIC Regulatory Guide 242 (RG 242) addresses recording system failures:

1. **Immediate notification:** If recording systems fail during market hours, the failure must be reported to the compliance team immediately
2. **Alternative recording:** Implement backup recording mechanisms (secondary system, mobile recording app, manual logging)
3. **Trade restrictions:** Some licensees implement policies restricting telephone dealing when recording systems are unavailable
4. **Incident documentation:** Document the failure, duration, affected calls, and remediation steps
5. **ASIC notification:** Significant or prolonged recording failures should be reported to ASIC under breach reporting obligations (s912D)

## Disclosure Requirements During Calls

### Product Disclosure Statements (PDS)

Before recommending or selling a financial product by telephone, the AFS licensee must ensure the client has received (or will receive) a Product Disclosure Statement:

- **General products:** PDS must be provided before the product is issued (s1012B)
- **Telephone timing:** If the product is sold during a call, the PDS must be sent to the client within 5 business days (s1015C)
- **Key fact verification:** The client must be informed of key product features, risks, fees, and cooling-off rights during the call

### Financial Services Guide (FSG)

- FSG must be provided as soon as practicable after it becomes apparent that a financial service will be provided (s941A)
- During a telephone call, the key elements of the FSG must be communicated verbally, with the written FSG sent within 5 business days
- FSG must disclose any conflicts of interest, remuneration arrangements, and complaint handling procedures

### General Advice Warning

When providing general advice during a telephone call:

- Must include the general advice warning: that the advice does not take into account the client's personal objectives, financial situation, or needs (s949A)
- Must recommend that the client consider the relevant PDS before making a decision
- The warning must be given verbally during the call, not just included in follow-up documentation

## Compliance Framework for Telephone Operations

### Pre-Call Compliance

1. **Call purpose classification:** Determine whether the call is a return call, a scheduled appointment, or an unsolicited contact before dialing
2. **Client categorization:** Verify whether the client is retail or wholesale (anti-hawking provisions apply to retail clients only)
3. **Product appropriateness:** Ensure the product to be discussed falls within the licensee's AFS authorization and the representative's competence
4. **Script compliance:** Telephone scripts reviewed and approved by compliance for regulatory accuracy

### During-Call Compliance

1. **Recording notification:** Inform the caller that the call is being recorded and the purpose of recording
2. **Identity verification:** Verify caller identity before discussing account-specific information
3. **Disclosure delivery:** Provide required verbal disclosures (general advice warning, key PDS information, FSG key elements)
4. **Hawking boundary monitoring:** Do not offer products outside the scope of the client's original request
5. **Consent documentation:** Record explicit consent for any product acquisition or application initiated during the call

### Post-Call Compliance

1. **Recording verification:** Confirm the call was successfully recorded and stored
2. **Documentation dispatch:** Send PDS, FSG, and any other required documents within mandated timeframes
3. **Transaction reconciliation:** Match telephone instructions to executed transactions
4. **Quality assurance sampling:** Include the call in the QA sampling program

CallSphere's compliance engine automates many of these checkpoints, providing real-time hawking boundary alerts, automated disclosure tracking, and post-call documentation workflows tailored to ASIC requirements.

## ASIC's Surveillance and Enforcement Approach

### How ASIC Monitors Communication Compliance

ASIC uses several methods to identify communication compliance failures:

- **Surveillance reviews:** Targeted reviews of market participants' telephone recording systems and processes
- **Thematic reviews:** Industry-wide reviews focusing on specific issues (e.g., the 2024 add-on insurance hawking review)
- **Breach reports:** AFS licensees are required to report significant breaches, including communication compliance failures
- **Consumer complaints:** Analysis of consumer complaints received by ASIC
- **Market surveillance data:** Cross-referencing transaction data with communication records to identify irregularities

### Responding to an ASIC Information Request

When ASIC requests call recordings or communication records:

1. **Acknowledge receipt** within the timeframe specified (typically 14 days for a compulsory notice)
2. **Identify relevant recordings** using your searchable archive
3. **Produce recordings in the requested format** (ASIC typically accepts WAV, MP3, or FLAC)
4. **Provide supporting metadata:** Call date/time, participants, account/transaction references
5. **Maintain privilege claims:** If any recordings contain privileged legal communications, clearly identify and separately log them

## Frequently Asked Questions

### Does every financial services call need to be recorded in Australia?

Not every call, but all calls related to dealing, arranging, or advising in financial products must be recorded under the Market Integrity Rules. Additionally, best practice for AFS licensees is to record all client-facing calls to manage hawking risk, ensure disclosure compliance, and provide evidence in case of disputes. The 7-year retention requirement applies to all recordings within scope.

### Can I cold-call potential clients to offer financial products?

No. The anti-hawking provisions in Section 992A of the Corporations Act prohibit unsolicited telephone offers of financial products to retail clients. You may only discuss a financial product during a call if the client specifically requested information about that product or arranged the call for the purpose of discussing it. Violations carry penalties up to AUD $555 million for corporations.

### What are the recording retention requirements for ASIC-regulated firms?

The ASIC Market Integrity Rules require retention of relevant call recordings for a minimum of 7 years from the date of recording. This is longer than many other jurisdictions (the EU MiFID II standard is 5 years). Recordings must be stored in a searchable, accessible format and produced to ASIC upon request.

### How does ASIC view AI-powered call monitoring?

ASIC has been receptive to technology-driven compliance solutions, provided they are properly validated and subject to human oversight. In its 2025 technology and compliance guidance, ASIC noted that AI-powered communication monitoring can improve the effectiveness of compliance programs, but cautioned that licensees remain responsible for the accuracy and completeness of their monitoring regardless of the technology used. ASIC expects firms using AI monitoring to document the technology's capabilities, limitations, testing methodology, and human review processes.

---

Source: https://callsphere.ai/blog/asic-calling-compliance-australian-financial-services