Responsible Manager Changes and AFSL Variations: When a Key Person Change Triggers Action

Introduction

A change to an Australian financial services licence (AFSL) holder’s responsible managers does not automatically require an AFSL variation. An ordinary responsible manager change generally requires notification to the Australian Securities and Investments Commission (ASIC). However, where the person is named in a key person condition on the AFSL, their departure can also require an application to vary that condition.

The distinction matters because ASIC relies on responsible managers when assessing whether an AFSL holder maintains the organisational competence required by Section 912A(1)(e) of the Corporations Act 2001 (Cth) (‘Corporations Act‘). A key person departure can therefore create both a licence-condition issue and a competence issue. In this article, we explain when a responsible manager change triggers an AFSL variation, the applicable notification periods, and what licensees should do before a key person leaves.

Interactive Tool: Check If Your Responsible Manager Change Triggers an AFSL Variation

Responsible Managers and Organisational Competence

The Corporations Act does not create a statutory office called a “responsible manager”. Responsible managers are part of ASIC’s framework for assessing compliance with Section 912A(1)(e) of the Corporations Act, which requires an AFSL holder to maintain the competence to provide the financial services covered by its licence.

ASIC explains in Regulatory Guide (RG) 105 AFS licensing: Organisational competence (‘RG 105‘) that it looks to the knowledge and skills of the people who manage the financial services business. Responsible managers should be directly responsible for significant day-to-day decisions about the ongoing provision of financial services and, collectively, have the knowledge and skills relevant to the services and products covered by the AFSL.

This means a departure should be assessed by reference to the competence the person contributes, not simply the number of responsible managers remaining. A licensee may still have several responsible managers but lose coverage for a particular service or product if the departing person was the only one with relevant expertise.

When is Notifying ASIC Enough

The first question is whether the departing person is simply a responsible manager or is also named in a condition on the AFSL.

For an ordinary responsible manager change, the licence itself usually does not need to be varied. However, the change must generally be notified to ASIC.

The prescribed licence condition in Regulation 7.6.04(1)(b) of the Corporations Regulations 2001 (Cth) (‘Corporations Regulations‘) requires a licensee to lodge particulars of a change to information entered in the financial services licensee register within 10 business days after the change, unless the change results directly from an ASIC action. ASIC’s responsible manager process identifies Regulations 7.6.04(1)(b) and 7.6.05(1)(g) as relevant to responsible manager changes.

ASIC’s Regulatory Portal can be used to:

• appoint a new responsible manager;
• cease an existing responsible manager;
• change responsible manager details; and
• update the time a responsible manager spends performing the role.

The notification does not itself resolve the competence question, and ongoing AFSL compliance services may be needed to assess and address any gap. After the change, the licensee must still satisfy Section 912A(1)(e) of the Corporations Act. If the remaining responsible managers no longer collectively cover the AFSL authorisations, the business needs to address that gap.

When Varying Your AFSL May Be Required

Responsible Manager Named in a Key Person Condition

The position changes where the responsible manager is named in a key person condition.

ASIC may impose or vary AFSL conditions under Section 914A of the Corporations Act. ASIC’s standard key person condition appears in condition 3 of Pro Forma (PF) 209 Australian financial services licence conditions (‘PF 209′), although licensees should check the wording of their own AFSL because conditions can be tailored.

As per RG 105, a key person condition may be imposed where the licensee is heavily dependent on the knowledge and skills of one or two responsible managers. This can arise where:

• the business is small and relies heavily on one or two principals;
• only one responsible manager has expertise for a particular financial service or product; or
• the organisational competence assessment depends substantially on one individual.

A key person condition therefore identifies someone whose competence ASIC considers materially important to the licensee.

When the Variation Trigger Arises

If the responsible manager named in a key person condition is no longer a responsible manager for the licence, the licensee needs to apply to vary the AFSL.

The variation can generally take one of two forms:

• nominate another responsible manager as the key person; or
• ask ASIC to remove the key person condition by demonstrating that the licensee is no longer dependent on one responsible manager.

The statutory mechanism is an application under Section 914A(2)(b) of the Corporations Act to vary or revoke the relevant licence condition.

The practical distinction is straightforward: an ordinary responsible manager change updates ASIC’s records; a change to a responsible manager named in a key person condition also affects the AFSL itself.

Responsible Manager and Key Person Notification Periods

Responsible manager changes and key person departures can involve different notification periods.

As outlined above, an ordinary responsible manager change is generally notified within 10 business days after the change.

By contrast, the key person condition discussed above (condition 3 of PF 209) requires the licensee to notify ASIC in writing within five business days if a named key person ceases to be an officer of the licensee or ceases performing duties for its financial services business. The standard condition requires the notice to address:

• when the key person ceased;
• details of any replacement;
• if there is no replacement, why one has not been nominated; and
• how the licensee will continue to comply with the Corporations Act and its AFSL conditions.

The five-business-day period arises from the licence condition, not from a general rule applying to every responsible manager. The actual AFSL should therefore be checked.

For a named key person, the licensee may need to manage three connected steps:

• the ordinary responsible manager notification;
• the key person notification required by the licence condition; and
• the AFSL variation.

Replacing the Key Person or Removing the Condition

Replacing the Key Person

Where the business remains dependent on one person’s expertise, the likely pathway is to appoint an appropriately qualified replacement responsible manager and seek to substitute that person into the key person condition.

If the replacement is not already recorded as a responsible manager, ASIC currently requires the responsible manager change notification to be completed before the variation application is started.

The replacement should cover the relevant competence rather than merely occupy the departing person’s job title.

Removing the Key Person Condition

A licensee may instead seek to remove the condition if it is no longer dependent on a single person. This may be relevant where the licensee now has:

• several responsible managers with overlapping expertise;
• broader management capability;
• greater internal knowledge across its licensed services and products; or
• a structure that no longer relies heavily on the originally named person.

A variation applicant can explain why the licensee is no longer dependent on one responsible manager. The issue is whether the business can demonstrate continuing organisational competence without a named key person, not whether removal would simply be administratively convenient.

Evidence ASIC May Require

Where a new responsible manager is appointed, ASIC focuses on whether that person genuinely contributes relevant competence to the financial services business.

Depending on the application, supporting material may include:

• relevant roles and experience;
• qualifications;
• a Statement of Personal Information;
• criminal history checks; and
• where applicable, overseas police or bankruptcy checks.

For a key person variation, ASIC will also require information showing how the responsible manager or responsible managers support the proposed change.

The evidence should demonstrate how the responsible managers collectively cover the financial services and products authorised by the AFSL after the departure. An up-to-date competence matrix can make this considerably easier.

ASIC can also request further information or an audit report when assessing a variation application under Section 914B of the Corporations Act.

Why a Key Person Departure Should Be Managed Before It Happens

Licence Condition and Competence Risks

Under Section 912A(1)(b) of the Corporations Act, an AFSL holder must comply with the conditions on its licence. Section 912A(1)(e) separately requires the licensee to maintain the competence to provide the financial services covered by the AFSL.

If a named key person leaves without the issue being addressed, the licensee may face:

• a breach of the relevant key person condition;
• a gap in the organisational competence supporting one or more AFSL authorisations;
• a need to vary the AFSL or appoint a suitable replacement responsible manager; and
• a separate need to assess whether the circumstances give rise to a reportable situation under Sections 912D and 912DAA.

Reportability depends on the statutory tests and should be assessed separately from the variation application.

ASIC Enforcement Shows the Practical Risk

ASIC’s recent enforcement activity illustrates the consequences of leaving a key person issue unresolved.

In November 2025, ASIC suspended the AFSL of Focused Financial Advice Pty Ltd after its key person and responsible manager had ceased in 2023. ASIC stated that the licensee had neither applied to vary its licence nor made the five-business-day notification required by its licence condition, and had continued providing financial services without the required key person.

ASIC revoked the suspension in December 2025 after approving a licence variation. The case does not mean every delayed notification will result in suspension, but it shows that prolonged failure to address a key person condition can become a substantive AFSL compliance issue.

Common Responsible Manager and Key Person Mistakes

Common problems include:

• assuming every responsible manager change requires an AFSL variation;
• treating a named key person as though they were an ordinary responsible manager;
• checking ASIC’s records without checking the actual AFSL conditions;
• waiting until the key person leaves before identifying who covers their expertise;
• appointing a senior employee without testing whether they meet ASIC’s responsible manager criteria;
• applying the 10-business-day responsible manager deadline without checking whether a five-business-day key person condition also applies;
• assuming appointment of a replacement automatically changes the key person condition; and
• asking ASIC to remove the condition without evidence that competence is sufficiently distributed across the business.

The recurring problem is treating the departure as an HR change rather than a licensing and organisational competence event.

Responsible Manager Change Review Process

Before a responsible manager leaves or materially changes role, an AFSL holder should:

1. Check the actual AFSL conditions: Confirm whether the person is named as a key person.
2. Map their competence: Identify which financial services and products rely on their knowledge and experience.
3. Assess the remaining responsible managers: Confirm whether they collectively continue to cover the AFSL authorisations.
4. Identify the regulatory steps and deadlines: Determine whether the change requires ordinary responsible manager notification only or also a key person notification and AFSL variation.
5. Choose the variation pathway: Decide whether another responsible manager should replace the key person or whether there is evidence to support removing the condition.
6. Prepare before the departure where possible: Gather replacement competence evidence and supporting documents early.

For a broader review of ongoing AFSL obligations, Click Legal’s AFSL Compliance Checklist can be used alongside the responsible manager review.

Conclusion

A responsible manager change is not automatically an AFSL variation trigger. The critical question is whether the person is also named in a key person condition and whether their departure affects the licensee’s continuing organisational competence.

Where a key person is leaving, the responsible manager notification, key person condition and competence assessment should be managed together. Addressing those issues before departure reduces the risk of an outdated licence condition or an unaddressed competence gap, so contact our AFSL compliance lawyers at Click Legal for responsible manager and key person issues.

Frequently Asked Questions