APES 325 Risk Management for Firms: what it requires, and how AI fits.
In short: APES 325 Risk Management for Firms is the standard that requires an Australian accounting firm to establish, maintain, monitor and document a risk management framework. The Accounting Professional & Ethical Standards Board (APESB) revised it in March 2023, with firms required to update their frameworks by 1 April 2023. It does not mention AI, but the risks it names include technology risks (including cyber security) and business continuity risks, and an AI tool raises both.
APES 325 is nine pages long and has no international equivalent. This page explains the standard itself, then how AI tools fall inside it. Paragraph numbers refer to the March 2023 revision.
General information only. This guide summarises published professional standards, legislation and regulator guidance and is not legal or professional advice. Read the primary sources linked throughout, and take advice on your firm’s specific position.
What APES 325 is, and who it binds
Paragraph 1.5 says members in public practice conducting the operations of a firm in Australia “shall follow the mandatory requirements of APES 325”. A member is a member of Chartered Accountants Australia and New Zealand, CPA Australia or the Institute of Public Accountants, and a firm includes a sole practitioner. The standard treats the firm as the entity that must implement the requirements, and its members in public practice as the people responsible for ensuring that happens (paragraph 1.3). Mandatory requirements are in bold type.
The standard defines risk as “the effect of uncertainty on objectives”. Paragraph 3.1 says an effective framework should help a firm meet its public interest obligations and business objectives by facilitating business continuity, enabling quality and ethical professional services, and protecting the firm’s reputation and credibility.
What it requires
A risk management framework that takes the firm’s public interest obligations into consideration, with the design and effectiveness evaluated periodically.
Policies and procedures for risks that may include governance, business continuity (including succession planning), business, financial, regulatory, technology (including cyber security), human resources and stakeholder risks.
The chief executive, managing partner or managing board takes ultimate responsibility, and the personnel given the work must have the necessary skills, experience, commitment and authority.
A monitoring process giving reasonable confidence that the policies and procedures are relevant, adequate and operating effectively, with non-compliance brought to the leadership for corrective action.
The framework must be documented, and the policies and procedures documented and communicated to personnel.
A documented succession plan, retention of relevant documentation, and a record of each instance of non-compliance detected and the action taken.
Paragraph 6.5 says the documentation should include the procedures for identifying risks, the firm’s risk appetite, the risks identified, their treatment, staff training and the procedures for regular review. Paragraph 4.3 makes the standard scalable: the nature and extent of the policies depend on the firm’s size and operating characteristics.
How it relates to APES 320, ASQM 1 and APES 110
Paragraph 3.3 says quality management policies developed under APES 320, or responses developed under ASQM 1 for an assurance practice, should be embedded within the risk management framework, so the firm keeps one consistent set of policies. Paragraph 1.7 requires members to comply with the fundamental principles in APES 110, and paragraph 4.2 requires firms to comply with Section 360 of that Code on non-compliance with laws and regulations.
Current version and where to read it
APES 325 was first issued in December 2011, and a framework was required by 1 January 2013. It was revised in October 2015, December 2017, September 2019 and March 2023. As at November 2026 it is the version published on the APESB website, where you can read the revised standard.
How AI tools fall inside the framework
The standard sets no rules for particular technologies. Using only what its text supports, four parts of it are engaged when a firm adopts an AI tool:
The categories the standard lists include technology risks (including cyber security), regulatory risks and business continuity risks. A tool that receives client information, or that staff come to depend on, belongs in that assessment. Regulatory risk includes the firm’s confidentiality obligations, which our APES 110 confidentiality guide covers.
Paragraph 6.5 says the documentation should include the risks identified and their treatment. If AI is in use, the risk record should show that it was considered and what the firm decided.
Policies must be communicated to personnel, with a message that each individual has a personal responsibility for risk management. An AI policy that staff have read is one way to do that for AI use.
If the firm’s policy limits which tools may be used with client information, the monitoring process should be capable of detecting departures, and each detected instance and the action taken must be documented.
Where deployment posture fits
No tool satisfies APES 325 for you: the framework, the monitoring and the records remain the firm’s. The deployment choice changes the content of the risk assessment under paragraph 4.2. With an AI service operated by a third party, the technology and business continuity questions turn on that provider: where client information goes, who can access it, and what happens if the service changes or stops. An AI unit inside the practice processes client information on the practice’s own hardware, so those questions become ones about the firm’s own premises, access controls and backups. On Ermos Edge, documents stay on the practice’s own instance in Australia and only permitted excerpts go, per question, to a named Australian provider under contract, which is the arrangement the firm would assess and record. Each posture leaves risks for the firm to identify, treat and document.
Common questions
What is APES 325?
Who must comply with APES 325 Risk Management for Firms?
What risks does APES 325 require a firm to consider?
Does APES 325 apply to AI tools?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo