FAQ

When does poor documentation become a breach rather than a process issue?

ASIC expects AFS licensees to maintain adequate records to demonstrate compliance with advice obligations, and poor documentation constitutes a breach if it prevents the licensee from evidencing that the advice complied with the law. If the absence or weakness of records undermines best interests, appropriateness, or client understanding, it is treated as a compliance breach, not just a process issue.

Expanded Answer
ASIC’s position is that documentation is not merely administrative; it is the primary evidence that advice obligations have been met. Where records are incomplete, unclear, or inconsistent, ASIC assesses whether the adviser can still demonstrate that the advice was appropriate, in the client’s best interests, and based on relevant circumstances. If this cannot be shown, the issue moves beyond process failure to a breach of core obligations.

In practice, poor documentation is more likely to be treated as a process issue, even when the underlying advice is clearly sound and can be substantiated by other evidence. However, where documentation gaps relate to client objectives, scope, risk profiling, or strategy rationale, ASIC is likely to infer that proper processes were not followed. This is particularly relevant when file notes, fact finds, or advice records do not align or lack critical reasoning.

Regulatory scrutiny increases where documentation failures are systemic, repeated, or linked to client harm. ASIC and AFCA often draw adverse inferences from missing or inconsistent records, treating the absence of evidence as evidence of non-compliance. This risk is highlighted in Doh! Better file notes and Info 292: clear, captured and client-centric.

Why it matters
Inadequate documentation can convert otherwise defensible advice into a regulatory breach. Licensees face enforcement, remediation, and dispute risk where they cannot evidence compliance, even if the advice itself may have been appropriate.

Practical guidance

  • Document client objectives, scope, and strategy rationale clearly so the advice can be understood without inference
  • Ensure file notes and advice records are consistent, contemporaneous, and aligned with the final recommendation
  • Review files for evidentiary sufficiency, not just completeness, focusing on whether the advice can be defended under scrutiny

Further reading
Doh! Better file notes
Info 292: clear, captured and client-centric

Subscribe

Every fortnight “Three Hit Tuesday” delivers thought leadership, considered analysis and insights that will help you improve your advice, more effectively manage your regulatory risks and make you better informed than your peers.

AS-Subscribe Form

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

We respect your privacy. We know everyone says that, but we promise that we won’t sell your contact details to dodgy telemarketers, spam your email or otherwise exploit your trust.

Step 1 of 8 - Your Role

This field is for validation purposes and should be left unchanged.

Assess your ASIC exposure

Answer a few targeted questions to identify where your compliance may not stand up under ASIC review.

Takes less than 2 minutes. No preparation required.

What best describes your role?