APES 320: Quality Management for Non-Assurance Work

Identify the Current APES 320 Framework

The current title is APES 320 Quality Management for Firms that provide Non-Assurance Services. The 2022 standard replaces the 2019 Quality Control for Firms edition. APESB identifies seven elements, covering leadership, professional standards, client acceptance, resources, engagement performance, communication and monitoring. APESB’s standard overview explains that change.

Classify the services before selecting the framework. A forensic reconstruction does not automatically become assurance because someone reviews its calculations. APES 210 addresses conformity with auditing and assurance standards. ASQM 1 covers audits, reviews and other assurance or related services within its application provisions.

For agreed-upon procedures, the firm’s other services matter. APESB’s application chart distinguishes firms that also perform audits, reviews or other assurance engagements from firms that do not. The latter apply APES 320 to engagement quality management. A mixed practice can need both frameworks. Use the application chart in APESB’s explanatory presentation when mapping services.

Assign Responsibility for Quality

APES 320 assigns ultimate system responsibility to the firm’s leadership and requires that assignment to be documented. Operational owners need suitable authority, knowledge and time. Smaller firms can combine roles. The operative standard, paragraphs 3.12–3.18, distinguishes responsibility from documentation.

For a small forensic practice, a useful responsibility sheet names who approves acceptance, supervises reconstruction, resolves technical questions and authorises issue. Record the actual reviewer beside each task. A principal’s general oversight does not show who examined a disputed transfer or resolved a review point.

Give staff a route for raising missing records and conflicting instructions. Reserve review time before promising delivery. Decide who approves an outside provider and who communicates a changed method to the team. These are suggested operating decisions, adapted to the practice’s work and staffing.

The wider firm-risk system under APES 325 can inform these decisions, such as arranging cover when the only experienced reviewer becomes unavailable.

Control the Forensic Engagement From Acceptance to Output

Consider a fictional practice asked to reconstruct payments across three accounts. Its agreed output is a transaction schedule explaining transfers and unresolved entries. The following workflow illustrates how the practice can apply its policies.

1. Record the purpose, intended users and scope before acceptance. Check conflicts, available expertise and the time needed for review. Specify whether tracing ends at the supplied accounts.
2. Allocate preparation to staff who understand statement balances, reversals and internal transfers. Give written instructions for missing periods and uncertain descriptions. Keep the source PDFs identifiable throughout.
3. Supervise the reconstruction while it is underway. Compare progress with the account inventory and escalate gaps before they become assumptions in the report.
4. Consult on a difficult classification. For example, obtain a reasoned technical decision before treating a payment to a related entity as a loan repayment. Preserve the question and conclusion.
5. Review the schedule and proposed explanation together. Resolve duplicate transfers, check totals and confirm that the wording distinguishes observed payments from inferred purposes. Record who cleared each issue before release.

Where staff or a provider prepare the data, the responsible member can inspect the scope instructions, reconciliations and unresolved exceptions. The final explanation must follow the evidence and agreed purpose. Receiving a completed spreadsheet does not decide the engagement’s conclusions.

APES 320 requires team supervision and review responsibilities, including review of less experienced staff by more experienced members. Using a service provider leaves the firm responsible for its quality system.

Monitor Weaknesses and Remediate Affected Work

Engagement review checks a particular job before issue. System monitoring asks whether the practice’s policies work across jobs. APES 320 requires cyclical inspection of a completed engagement for each engagement partner, excluding its performers from the inspection.

Suppose monitoring finds that a template duplicates internal transfers. In this fictional case, trace the cause to its matching rule and identify every engagement using that version. Correct the rule, brief staff and inspect later work for recurrence. Keep the before-and-after reconciliation as evidence of the response.

Separately assess already-issued schedules. Establish whether the duplicate affects a conclusion or figure and decide the necessary communication and correction. A corrected template alone does not resolve an affected report. An external practice-review finding can trigger the same response.

Root-cause analysis is a useful method here. APES 320 presents it as remedial guidance, rather than a universal standalone requirement.

Keep the Quality Record Usable

APES 320 requires evidence that every system element operates and retention sufficient for monitoring, subject to longer legal requirements.

A suggested quality register records the policy owner, relevant engagements, review result, corrective action, responsible person and follow-up evidence. These fields are a practical design choice. Preserve the acceptance decision, instructions and resolved review points in the engagement’s working papers, with a clear connection to the issued version.

Review the practice’s actual service list against the operative standard. For each applicable requirement, identify both its policy and a record showing it worked. Where the file contains only a blank form, allocate the missing action and retain its completed evidence before treating the system review as finished.