The cited ASIC page does not establish new record keeping duties

The claim needs a primary source

The claim being corrected is that ASIC has announced expanded record keeping duties for financial advice practices through its page, Financial advisers and authorised representatives.

The material supplied for this article does not include the page's publication or update date, a change history, the text said to have been added, or an ASIC announcement identifying a new record keeping requirement. The URL alone therefore cannot establish either that the page was revised or that it introduced a new obligation.

That makes the original claim too broad to publish as a regulatory development. A page describing an ASIC portal or administrative process may be relevant to how information is submitted or maintained. It does not, without more, demonstrate a change to the legal duties applying to advice providers or licencees.

What the legislation actually says

The relevant primary source for advice record keeping is the Corporations Act 2001. Section 961K requires a provider to keep records sufficient to demonstrate compliance with the provider's obligations under Part 7.7A, which contains the best interests duty and related advice obligations.

The legislation is available through the Federal Register of Legislation.

That provision is materially different from a claim that ASIC has created a new, generally applicable documentation standard through a webpage. Whether a particular record is required depends on the statutory obligation engaged, the circumstances of the advice and any applicable legislative or licensing requirements. The cited portal page does not, on the evidence supplied, identify a new commencement date, affected population or additional category of records.

The practical distinction is important for practice leaders. A business may choose to maintain records beyond the statutory minimum as part of its licence‑e‑controls, risk management or file review process. That internal standard should not be described as a new ASIC obligation unless the underlying source supports that description.

Distinguish creation, interpretation and enforcement

A source checklist should also distinguish between different types of regulatory material.

• An Act of Parliament, regulation or legislative instrument may create or amend a legal obligation, subject to its terms and commencement provisions.
• An ASIC regulatory guide may explain ASIC's approach and expectations. It should not automatically be treated as legislation, although it may be important evidence of how ASIC administers the law.
• An ASIC information page may explain an administrative process. Its significance depends on the specific content and the legal source behind it.
• An enforcement action may show how ASIC has applied the law in a particular matter. It does not, by itself, create a generally applicable new duty.
• A court decision may be binding according to the court, jurisdiction and issue decided. An AFCA determination is not equivalent to binding judicial authority and generally concerns the particular complaint and parties involved.

Those distinctions should be recorded when a proposed process change is being assessed. They prevent a practice from treating commentary, administration or enforcement material as though it were a new statutory requirement.

What practices should verify

Before changing advice templates, file checklists or workflows, the person identifying the supposed change should provide:

• the exact ASIC text said to announce the change
• the page's publication or update date, if available
• the Act, regulation, legislative instrument or licence condition said to create the obligation
• the commencement date and the firms or providers affected
• any ASIC guidance explaining how the requirement is to be applied

Compliance or legal review can then classify the change. It may be a new legal obligation, an interpretation of an existing obligation, an administrative reporting change, a licence‑e control or an internal standard. Those categories have different implementation consequences.

If the source cannot be produced, the claimed expansion should not be presented to advisers as a new regulatory duty. That does not mean a practice should abandon its existing controls. It means any decision to strengthen documentation should be described accurately as a risk or governance decision unless a primary source establishes a legal change.

The correction

The supplied ASIC page does not provide enough evidence to report that ASIC has announced expanded record keeping duties. The original claim should therefore be narrowed or withdrawn unless the page text, its update history and the underlying legal source can be documented.

Any additional requirement must be traced to its own primary source rather than inferred from an administrative webpage.¹