Top 5 AFSL Application Mistakes & How to Avoid Delays

Introduction

Obtaining an Australian financial services licence (AFSL) is a major step for businesses operating in the financial services industry in New South Wales and across the country. Following process change that took effect on 16 June 2025, applicants must use a new digital ASIC Regulatory Portal to demonstrate their organisational competence and meet strict compliance obligations under the Corporations Act 2001 (Cth).

Because the licence application process is highly complex, easily avoidable errors can lead to delays, requests for further information, a modified or conditional licence outcome, withdrawal, or refusal, which is why many businesses seek advice from AFSL application lawyers. This article explains the top mistakes in the AFSL application process for financial services businesses so you can secure timely approval.

Interactive Tool: Check Your Risk of AFSL Application Delay & Refusal

Mistake 1: Incomplete Applications & Missing People Proofs

The Impact of Unanswered Fields & Missing Documents

Submitting an incomplete application can delay assessment or prevent the Australian Securities and Investments Commission (ASIC) from granting an AFSL. Sections 913A and 913B of the Corporations Act 2001 (Cth) state that an application must be filed in the prescribed format and with all necessary information and documents, and should not contain anything that is materially false or misleading or omits an important matter. If the applicant does not comply with this, ASIC must refuse the application.

Administrative error most frequently involves the failure to provide a complete set of “People Proofs” for all fit-and-proper persons, such as directors and any nominated responsible manager. This leads to non-compliance with Section 913BA of the Corporations Act 2001 (Cth).

As per ASIC’s Regulatory Guide (RG) 1, required documents typically include:

• A complete Statement of Personal Information for each relevant person.
• A national criminal history check that is less than 12 months old.
• A current bankruptcy check.
• Copies of all relevant qualification certificates and transcripts.

These documents are essential for ASIC to assess the character and competence of the individuals who will oversee the financial services business.

How to Use the ASIC Regulatory Portal Checklist Effectively

To prevent these administrative errors, applicants should strictly follow the checklist provided within the ASIC Regulatory Portal. The updated digital application process requires all supporting documents to be uploaded directly. ASIC no longer describes documents as “core” and “non-core” proofs; it refers to People Proofs and application-specific supporting information.

As a best practice, it is important to label every uploaded document distinctly and cross-reference it correctly within the application. For example, a file named “JSmith_Criminal_History_Check_May2026.pdf” is much more effective than a generic “scan_123.pdf”. Clear labelling allows the ASIC analyst to easily match each proof to the relevant section of your submission, streamlining their review.

Mistake 2: Nominating Unsuitable Responsible Managers

Understanding Organisational Competence & RG 105 Requirements

A primary reason for delays in the AFSL application process is failing the organisational competence test. Section 912A(1)(e) of the Corporations Act 2001 (Cth) requires a licensee to maintain the competence to provide the financial services covered by its licence. ASIC must not grant an AFSL if it has reason to believe that the applicant is likely to contravene that obligation, as stated in Section 913B(1)(b). Further, RG 105 explains how ASIC generally assesses that statutory requirement, including through the knowledge, skills, and experience of nominated Responsible Managers.

A critical error is nominating an RM with a strong general background but without specialised experience in the specific financial products or services your licence will cover. While there is no statutory rule that each Responsible Manager must personally cover every authorisation, however, RG 105.39–RG 105.48 expects the nominated Responsible Managers’ combined knowledge and skills to cover all proposed financial services and products. ASIC is likely to reject a nomination if there is a mismatch between the RM’s expertise and the authorisations sought.

Common competence gaps that may stall your application include:

• Experience Mismatches: Appointing an RM with decades of general banking experience for a licence that involves complex derivatives or managed investment schemes.
• Coverage Gaps: The combined experience of your RMs does not extend to all financial products and services listed in your application.
• Outdated Knowledge: An RM’s experience is not recent, with ASIC typically looking for three to five years of relevant experience for appointment Options 1 to 4. Option 5 is flexible and does not prescribe a minimum period, but comes with its own set of requirements.
• Unrecognised Qualifications: RG 105.87–RG 105.93 allows ASIC to recognise comparable overseas qualifications, but applicants must demonstrate their relevance to the Responsible Manager’s proposed role and Australian licensing context.

The risks of nominating an unsuitable Responsible Manager are demonstrated in Global Financial Markets Pty Ltd and Australian Securities and Investments Commission [2017] AATA 1397. In Global Financial Markets, the Administrative Appeals Tribunal (AAT) upheld ASIC’s decision to refuse an AFSL application because the nominated RM could not demonstrate the specialised knowledge and skills required under RG 105 for the specific products sought. This case confirms that general financial experience is insufficient if it does not directly align with the licence authorisations.

Ensuring Direct Involvement in Day-to-Day Decisions

RG 105.22–RG 105.27 states that a nominated RM should have direct responsibility for significant day-to-day decisions about the ongoing provision of financial services. RG 105.28–RG 105.35 recognises a limited exception for some RM in small-scale, heavily automated businesses. Nominating a “trophy” Responsible Manager who is a consultant or well-known name but has no genuine operational role may therefore undermine the application. 

In addition to possessing the right skills, each nominated RM must pass the “fit and proper” person test. ASIC must be satisfied that there is no reason to believe the applicant, relevant officers, partners, trustees, senior managers and controllers are not fit and proper for the purposes specified in Section 913BA(1) of the Corporations Act 2001 (Cth).

ASIC considers several statutory matters under Section 913BB(2) of the Corporations Act 2001 (Cth), including whether a relevant person has:

• had an AFSL or Australian credit licence suspended or cancelled;
• been subject to a banning order, disqualification order or corporate-management disqualification;
• been linked to a refusal or failure to give effect to an AFCA determination;
• been insolvent under administration or otherwise subject to insolvency matters;
• been convicted of an offence within the previous 10 years; or
• any other matter ASIC may consider relevant.

Mistake 3: Relying on Generic Compliance Documentation

The Danger of Off-the-Shelf Policy Templates

Submitting generic, off-the-shelf compliance documentation and policies that are not tailored to your specific business is a critical error that signals a lack of operational readiness. Furthermore, these theoretical frameworks often fail to align with the proposed business model or the authorisations being sought.

RG 1.188–RG 1.192 explains that ASIC may assess an applicant’s systems, compliance arrangements, representative supervision, financial resources, dispute-resolution arrangements and risk-management procedures. A polished but generic policy suite that does not reflect the proposed business may therefore provide weak evidence of operational readiness. Therefore, templates should be tailored and implemented, rather than treated as a substitute for actual systems and governance.

Demonstrating Operational Readiness & Governance Structures

Your AFSL application must include a compliance framework that reflects your actual business processes. Every policy, from risk management to dispute resolution, should be customised to your products, distribution channels, and operational structure. This demonstrates to ASIC that compliance is an integral part of your business from the outset, rather than a task to be addressed after the licence is granted.

To prove your systems are ready for operation, you must provide concrete evidence beyond policy documents as best practice, including:

• Practical Tools: Furnish examples of compliance registers, incident logs, and breach reporting workflows that you will use.
• Governance Evidence: Include meeting minutes from compliance or risk committees and clear diagrams of reporting lines.
• Procedural Outlines: Detail your processes for internal controls, customer dispute resolution, and ongoing staff training.
• Supervision Plans: Show how you will monitor representatives, review the quality of advice, and manage conflicts of interest.

Mistake 4: Providing a Vague Description of Financial Services

Distinguishing Between Retail & Wholesale Clients

Your AFSL application must be precise about the clients you intend to serve. A common error is submitting a business description that is ambiguous about whether you will provide services to:

• retail clients;
• wholesale clients; or
• both.

Client classification is determined by Corporations Act 2001 (Cth), Section 761G and, where relevant, Section 761GA. The lack of clarity in this matter signals to ASIC that you may not fully understand your regulatory obligations.

The compliance requirements for servicing retail clients are significantly more extensive than for wholesale clients. For example, licensees dealing with retail clients must have appropriate dispute resolution systems, including membership with the Australian Financial Complaints Authority (AFCA). Failing to clearly define your client base can cause ASIC to question your readiness to meet the specific obligations attached to each client type.

Accurately Categorising Products Under the Corporations Act

It is critical to explicitly define each financial service and product your business will offer. Your AFSL application must demonstrate a firm understanding of how your products are legally categorised under Sections 761A, 763A, 764A and 766A of the Corporations Act 2001 (Cth). A misunderstanding in this area can undermine ASIC’s confidence in your organisational competence.

Some financial products can be complex to classify, for instance, a warrant fall within the securities, derivatives or miscellaneous financial facility authorisation categories.

Each category may require different authorisation selections and different supporting evidence. The practical implication of this is that the application, business description, website, and pitch materials should consistently describe the actual products and services proposed.

Mistake 5: Inadequate Demonstration of Financial Resources

Navigating the Requirements Stage for Financial Statements

The recent portal updates also altered when financial statements must be provided. Previously submitted upfront as “core proofs”, these documents are now requested later during what is typically called the “requirements stage”.

This change has created a common and critical misunderstanding, as some applicants mistakenly believe that proof of financial resources is no longer a primary concern for their initial submission. However, the fact is that ASIC may request additional information, an audit report or a statement of material changes by written notice under Section 913B(3) of the Corporations Act 2001 (Cth).

If the applicant does not comply with such a notice by the specified deadline, the application is taken to have been withdrawn. A requirements letter may be issued after ASIC makes an in-principle licence offer, but ASIC may also seek supporting information earlier in its assessment. Therefore, being unprepared to provide them immediately may cause significant delays and can jeopardise the entire application.

Proving Solvency & Documenting Resource Management Policies

Section 912A(1)(d) of the Corporations Act 2001 (Cth) requires a licensee to have available adequate financial, technological and human resources to provide the financial services covered by its licence and supervise its representatives. The exact financial evidence required will depend on the business model, authorisations and applicable financial requirements.

As a best practice, before lodging your application, you should prepare financial assumptions, cash-flow forecasts and resource-management documentation that are appropriate to the proposed business. This may include:

• a balance sheet;
• a profit and loss statement; and
• detailed cash flow projections, etc.

Conclusion

Avoiding common mistakes such as submitting incomplete applications, nominating unsuitable responsible managers, and relying on generic compliance frameworks is essential for a successful AFSL application. Meticulous preparation, tailored documentation, and a clear demonstration of financial resources are critical to prevent delays and secure timely approval from ASIC.

Navigating the complexities of the AFSL application process requires proactive risk management and specialised legal support. To ensure your submission meets ASIC’s stringent requirements and avoids costly errors, contact our AFSL application lawyers at Click Legal for guidance on your application.

Frequently Asked Questions