One ASIC portal, two clocks

ASIC's guidance dated 24 August 2026 sets two notification clocks for AFS licensees. The difference turns on whether the change concerns licence details or the administration of a CPD year. ASIC's Regulatory Portal guidance sets out the distinction.

At first glance, this looks like routine portal housekeeping. A practice may reasonably put every change to its licence record into one register, assign one internal deadline and move on. If the shortest period is used for everything, the control appears cautious.

That is where the administrative shortcut becomes misleading. ASIC treats a CPD year change as the exception to its general notification timeframe. A register that records only "licence change" has already lost the information needed to calculate the right deadline.

The 10 business day rule

The general rule is straightforward. ASIC says an AFS licensee must notify it of changes within 10 business days of the change occurring.

The Regulatory Portal transaction covers a broad range of changes. These include changing the name of the licensee, advising ASIC that the licensee has obtained an ABN, changing the principal business address, notifying ASIC whether the business uses a website, changing a website address, changing the address for service of notices, adding or removing a business name, changing the ongoing contact person and changing details of the external dispute resolution scheme.

Those are not all events that will arise in the same part of a practice. An office move may sit with operations. A change to the ongoing contact person may sit with compliance. A new business name may involve corporate administration. The regulatory clock, however, is the same: 10 business days from when the change occurs.

That starting point matters. The relevant question is not when someone notices the change, when the next compliance meeting is held or when the person responsible returns from leave. It is when the change occurs. A practice control that records only the date the task was allocated cannot reliably calculate the timeframe ASIC has stated.

CPD year has a separate clock

The CPD year change is different. ASIC identifies advising or modifying the licensee's CPD year as the only exception to the 10 business day timeframe.

For that change, ASIC gives a 30 business day window. The period runs from the day the licence is granted, or from the day the CPD year is to begin where the CPD year is being changed.

That is easy to miss because CPD sits beside other licence administration in the same portal transaction. The screen may make the tasks feel like one category. The timing rule does not.

Consider the practical prediction. If a practice has trained its staff to apply 10 business days to every licence notification, it will probably escalate a CPD year change earlier than ASIC's stated exception requires. That may be an acceptable internal choice, but it should be recognised as an internal buffer, not confused with the timeframe that applies to the CPD year change itself.

The opposite approach is more dangerous. If the practice has adopted the longer period as its general rule, a change to the business address, website, contact person or dispute resolution details could remain unnotified beyond ASIC's stated 10 business day timeframe.

The problem is therefore not simply knowing that the portal exists. It is classifying the event before calculating the due date.

A register needs more than one due date

The cleanest operational response is to make the classification explicit. A practice change register should identify at least:

• What changed, using a category that separates CPD year administration from other licence details.
• When the change occurred, rather than only when it was discovered or assigned.
• Which ASIC timeframe applies, either 10 business days or the 30 business day CPD year exception.
• Who owns the notification and who checks that it has been completed.
• What evidence confirms the notification was lodged.

The second item is particularly important for changes that develop gradually. If an address, contact person or website change is discussed over several weeks, the control should still identify the event that triggered the obligation and preserve a clear record of the date used for the calculation.

For CPD administration, the register should also record whether the entry concerns the licence being granted or a CPD year that is to begin. ASIC's wording gives those events different starting points within the same 30 business day timeframe.

This does not require a complicated system. It requires the register to carry the distinction that ASIC's portal guidance carries. A single generic task called "update ASIC licence details" is too blunt. It can conceal whether the practice is dealing with a corporate detail, a contact or website record, an external dispute resolution detail, or the CPD year.

Put the distinction into ownership

The control should operate before the portal is opened. When a change is raised, the person receiving it should classify it first, identify the event date and allocate the appropriate timeframe. Only then should the task move to lodgement.

That sequence also helps avoid a common ownership gap. Corporate administration may identify a licence detail change, while the person responsible for CPD may identify a change to the CPD year. If both are sent through the same general compliance queue, the task can look complete when the underlying classification has never been made.

A periodic review can test whether the register contains the event date, the relevant category, the calculated timeframe and evidence of completion. The review is not checking whether every task used the shortest period. It is checking whether the practice applied the correct rule consistently.

The accurate operational conclusion is simple. ASIC's portal uses a 10 business day timeframe for licence detail changes and a 30 business day exception for advising or modifying the licensee's CPD year. A licensee's change register should preserve that distinction rather than flattening both into one administrative deadline.