Back to all blog articles

THE LEDGER BLACK BLOG / FOR ADVISERS

FMA Compliance Automation: A Guide for NZ Financial Advisers

How New Zealand financial advisers can use technology to automate FMA compliance obligations including record-keeping, Statement of Advice generation, and audit trail management under the Financial Markets Conduct Act 2013.

FMA Compliance · Automation · Financial Advisers · New Zealand · Regulation

Understanding FMA Compliance Requirements

Every licensed financial adviser in New Zealand operates under the Financial Markets Conduct Act 2013 (FMC Act) and must comply with the Code of Professional Conduct for Financial Advice Services. In practice, this means maintaining detailed records of client interactions, providing clear Statements of Advice, and demonstrating that recommendations are suitable for each client's situation.

The Financial Markets Authority (FMA) actively monitors compliance and can take enforcement action when advisers fall short. According to the FMA's published guidance on financial advice provider obligations, providers must ensure their advice processes, record-keeping, and client communications meet the standards set out in the Code.

For most advisers, the challenge isn't understanding these requirements — it's the time and effort needed to maintain compliant records while running a busy practice.

The Compliance Burden

Industry surveys consistently report that NZ financial advisers spend approximately 30 to 40 percent of their working week on compliance and administrative tasks. For a full-time adviser, that's roughly 12 to 16 hours per week. The major time sinks include:

  • Documenting client meetings and conversations
  • Creating and updating fact-find records
  • Drafting Statements of Advice for each recommendation
  • Maintaining audit trails for every client interaction
  • Preparing for FMA reviews and audits
  • Managing document storage and retrieval

All of that time comes directly out of client-facing work — time that could be spent growing the practice and delivering value to clients.

What the FMA Actually Expects

It's worth understanding the specific obligations that create the compliance workload. The FMA's regulatory framework centres on several key areas:

Record-Keeping

The FMA requires that financial advice providers maintain adequate records of the advice given. Under Standard Condition 1 of the FAP licence, providers must keep records that demonstrate the nature of the advice, the basis for it, and how it was communicated to the client.

In practice, this means every client conversation, every recommendation, and every decision needs to be documented in a way that could withstand FMA scrutiny. Manual record-keeping is not only slow — it's inconsistent, and inconsistency is where compliance risk lives.

Statement of Advice Documentation

SOAs are the formal record of the advice given. They must clearly set out the basis for the advice, any limitations, and how the recommendation addresses the client's specific goals and circumstances. The Code of Professional Conduct doesn't specify an exact format, but the FMA has made it clear that vague or template-heavy SOAs that don't address the individual client are not sufficient.

For advisers handling multiple clients per week, SOA preparation is often the single largest time commitment in the compliance workload.

Audit Trails

The FMA can request evidence of an adviser's compliance at any time. The ability to produce a complete, timestamped record of all client interactions and advice decisions is not optional — it's a core obligation. Advisers who rely on disparate systems (email, spreadsheets, filing cabinets) will struggle to produce a coherent audit trail when it's needed.

Ongoing Suitability

The Code requires that advice is suitable for the client at the time it's given. This means the adviser must demonstrate that they understood the client's situation, considered relevant factors, and made a recommendation that was appropriate. Documenting this suitability assessment is where many advisers find the compliance burden most acute.

Where Automation Fits

The compliance obligations above have something in common: they're documentation-heavy. The adviser's expertise lies in understanding the client, assessing their needs, and recommending appropriate products. The compliance burden comes from the administrative overhead of documenting that process to a standard that satisfies the regulator.

This is exactly where automation adds value. The repetitive, mechanical parts of compliance — logging interactions, structuring records, maintaining trails, and preparing documentation — can be handled systematically. The adviser's judgment and expertise remain central to the advice itself.

The key distinction is between compliance as admin (which can be automated) and compliance as quality (which requires human judgment). A well-designed system handles the former so the adviser can focus on the latter.

Choosing the Right Approach

Not all compliance tools are equal, and the wrong choice can add work rather than remove it. When evaluating options, these are the questions worth asking:

  • Does it understand NZ regulation specifically? A generic compliance tool adapted for the NZ market is not the same as one built for it. Look for native support of FMA requirements and the Code of Professional Conduct.
  • Does it reduce SOA preparation time? SOA drafting is the biggest time sink. If the tool doesn't meaningfully address this, it's solving the wrong problem.
  • Does it fit your existing workflow? If the tool requires parallel processes or double-handling, it's creating work, not removing it. Compliance should be a byproduct of how you already work, not an additional layer.
  • Where is client data stored? Data sovereignty matters. Under the NZ Privacy Act 2020, personal information shared overseas must receive comparable protection. Many FAPs now mandate onshore hosting.
  • How quickly can you produce a compliance report? If the answer is "a few hours of preparation," that's not real automation.
  • Will it keep up with regulatory changes? NZ regulation evolves. Your compliance tooling needs to evolve with it.

The Opportunity

The compliance burden is real, but it's also an opportunity. Advisers who solve it effectively free up 12 to 16 hours per week — time that goes back into client relationships, business development, and delivering better outcomes.

The FMA's increasing focus on advice quality and documentation standards isn't going away. The advisers who find efficient, systematic ways to meet those standards will have a genuine competitive advantage over those still relying on manual processes and generic tools.

Frequently Asked Questions

What are the main FMA compliance requirements for NZ financial advisers?

Under the Financial Markets Conduct Act 2013 and the Code of Professional Conduct for Financial Advice Services, NZ financial advisers must maintain detailed records of client interactions, provide Statements of Advice documenting their recommendations and reasoning, demonstrate suitability of advice for each client, and maintain audit trails. The FMA actively monitors and enforces these standards.

How much time do NZ financial advisers spend on compliance?

Industry surveys consistently report that NZ financial advisers spend approximately 30–40% of their working week on compliance and administrative tasks. This includes documenting client meetings, drafting Statements of Advice, maintaining audit trails, and preparing for FMA reviews. That equates to roughly 12–16 hours per week for a full-time adviser.

Can compliance tasks be automated without compromising quality?

Yes. The repetitive, mechanical parts of compliance — logging interactions, filing documents, generating audit trails — can be handled automatically. The adviser retains judgment and oversight over all advice and documentation. Automation handles the admin so the adviser can focus on quality.

What is a Statement of Advice (SOA) and can it be automated?

A Statement of Advice is a formal compliance document that records the financial advice given to a client, the basis for that advice, and how it aligns with the client's goals and risk profile. Much of the SOA preparation process can be automated, significantly reducing the time advisers spend on drafting while maintaining the quality and compliance standards required by the FMA.

What should I look for in an FMA compliance automation tool?

Key criteria include: native understanding of NZ FMA regulations (not just generic compliance), the ability to reduce SOA preparation time, automatic audit trail creation, data hosting within New Zealand, and seamless integration with your advice workflow rather than requiring a separate process.

Is NZ data hosting required for financial adviser compliance?

The NZ Privacy Act 2020 does not strictly prohibit offshore data storage, but it requires comparable protections for data shared overseas. In practice, many NZ dealer groups and FAPs mandate onshore data hosting as part of their compliance frameworks. Hosting data within New Zealand also reduces jurisdictional risk and strengthens the trust conversation with clients.