AFS licensee changes: keeping ASIC records aligned with the business

The licensee, not the individual adviser, owns the process

ASIC’s Regulatory Portal is a channel for AFS licensees to change information associated with their licence. That distinction matters for financial planning businesses. An individual financial adviser or authorised representative may have separate records and obligations, but does not generally manage the AFS licence itself.

For a licensee, a change in the business can therefore have more than one regulatory consequence. The relevant question is not simply whether someone has joined, left or changed roles. It is which record has changed, whether the change affects the licence, and whether ASIC requires a notification, an amendment, a separate update or a variation application.

ASIC’s guidance on changing licence details through the Regulatory Portal should be the starting point for that assessment.

The practical implication is that licence management needs a defined owner. It should not depend on an adviser, practice manager or external compliance provider noticing a change after the event and assuming that the relevant ASIC record will be updated automatically.

Separate the types of change

Changes to licence details

Some events may require the licensee to change information recorded against its AFS licence through the Regulatory Portal. The licensee should use ASIC’s current guidance to identify the relevant request and the information required.

Examples may include changes to business or contact information, but the correct treatment depends on the detail being changed and the licensee’s circumstances. The practice should not assume that every change to its business can be dealt with through the same portal request.

Changes involving advisers and authorised representatives

Updates to adviser or authorised‑representative information should be considered separately from changes to the AFS licence. ASIC provides a separate online service for financial advisers and authorised representatives.

That separation is important when an adviser joins, leaves or changes status. The licensee should determine which adviser or representative record needs attention, whether any licence information is also affected, and whether the change has consequences for supervision, authority or internal registers.

Changes that may require a variation

A change to the financial services or products a licensee is authorised to provide may not be an ordinary administrative update. It may require a variation or another process under ASIC’s guidance on applying for and managing an AFS licence.

The same caution applies to changes in ownership, control, corporate structure or responsible‑manager arrangements. The business should identify the regulatory question first, rather than treating every structural or staffing change as a routine portal amendment.

This classification is an editorial practice recommendation, not a substitute for ASIC’s process guidance. Where the treatment is unclear, the licensee should confirm the applicable ASIC process before lodging anything.

A workable internal trigger

ASIC’s public guidance explains the available processes. It does not, by itself, prescribe the internal workflow a practice must use. The following is a suggested control for licensees and advice businesses.

When a potentially relevant event occurs, record it and assign responsibility for assessing the ASIC consequences. Possible triggers include:

• a change to the licensee’s legal entity, ownership or control;
• a change to business, principal‑place‑of‑business or contact information;
• the appointment or departure of a responsible manager;
• the appointment, departure or status change of an adviser or authorised representative;
• a proposed change to the financial services or products covered by the licence.

These events do not all belong in the same ASIC process. Their value as triggers is that they prompt a documented assessment of the relevant licence, adviser, representative or variation requirements.

The assessment should identify:

• 1. what has changed and when;
• 2. which legal entity and ASIC record are affected;
• 3. whether the event concerns licence details, an adviser or representative record, or a possible variation;
• 4. who is authorised to lodge the relevant request; and
• 5. what follow‑up is required after lodgement.

What to retain

A licensee should retain the documents needed to explain the change and the decision made about the ASIC process. Depending on the event, that may include a board or ownership record, appointment or resignation document, organisational information, corporate details or evidence supporting a change in business information.

This is a suggested record‑keeping control. The documents required for a particular ASIC request will depend on the request and the information ASIC asks the licensee to provide.

Before lodging, compare the proposed information with the licensee’s corporate and internal records. Names, dates, addresses and entity identifiers should be checked against the source documents. The purpose is not to create an additional ASIC requirement, but to reduce the risk of submitting information that is incomplete or inconsistent with the underlying event.

Access to the Regulatory Portal should also be managed as an internal control. The licensee should know who can lodge requests, keep access details current, and document handovers when responsibility changes.

Lodgement is not close‑out

The licensee’s process should distinguish between preparing a request, lodging it and completing the resulting action.

After lodgement, the responsible person should retain the submission record and monitor the portal or ASIC communications for the status of the request and any request for further information. The licensee should follow the instructions in ASIC’s process guidance and respond within any applicable timeframe.

The internal file should record the outcome, not merely the fact that someone started a request. If ASIC asks for more information or identifies a further step, that should be assigned and closed out. The practice should also update its own registers, policies and operational records where the change affects them.

This does not mean that a particular screenshot or receipt has no value. It means that the evidence retained should show the relevant request, its status and any subsequent ASIC communication, rather than relying on an informal assumption that lodgement has completed the matter.

A practical licence‑management checklist

A licensee may find it useful to maintain:

• 1. a register of events that require an ASIC assessment;
• 2. a named owner for licence, adviser and representative records;
• 3. a classification step distinguishing an amendment, a separate record update and a possible variation;
• 4. a controlled list of Regulatory Portal users;
• 5. a checklist for names, dates, entities and supporting information;
• 6. the lodged request, its status and ASIC correspondence;
• 7. evidence that related internal records were reviewed and updated where necessary.

For larger licensees, periodic testing of this process is a sensible governance control. The test should be designed by the business and could compare selected business events with the relevant internal and ASIC records. It is not an ASIC‑prescribed control identified in the sources cited here.