Accounts file review quality management is how a chartered practice shows, file by file, that the compiled accounts it sends out were prepared to a standard and checked by someone able to challenge them. This guide is for partners and compliance principals in practices that prepare accounts without auditing them. It covers the ICAEW guidance on compilation reports and engagement letters, what Practice Assurance reviewers look at, hot and cold file review, how to record a review, and which ideas from ISQM (UK) 1 are worth borrowing where that standard does not apply.
Compiled accounts: the ICAEW guidance and the report
Which technical release is current
For accounts prepared under the Companies Act 2006, the ICAEW guidance is TECH 07/16 AAF, Chartered Accountants’ Reports on the Compilation of Financial Information of Incorporated Entities, dated 28 March 2016. Its companion for unincorporated clients is TECH 08/16 AAF, dated 29 March 2016, which replaced AUDIT 03/10. Both are member-only content. ICAEW’s list of Audit and Assurance Technical Releases still carries TECH 07/16 AAF and shows no later release on compilation. Checked against that list on 21 November 2026.
ICAEW’s own “Accounts preparation/Compilation” page still tells practitioners to follow AAF 2/10 and AAF 3/10, the 2010 releases, and refers to ISQC 1. Its principles are still useful, but quote the 2016 releases in your manuals and reports.
What a compilation is
ICAEW describes the common compilation engagement as one in which the practitioner takes financial data and information from the client and arranges it into financial statements. The procedures do not verify the data, the practitioner expresses no conclusion on the compiled information, and the engagement is not an assurance engagement. The compilation report sets out the nature of the engagement and the respective responsibilities, to avoid expectation gaps among its readers.
The same page points to the IAASB’s ISRS 4410, Engagement to Compile Financial Statements, and says practitioners should make as much use of it as possible even where they do not follow it in full. Independence is not a requirement for compilation engagements, though the ethical principles still apply. A client who wants more than a compilation can be offered an assurance review under TECH 09/13 AAF (Revised), which applies ISRE 2400 (Revised) and was last updated in March 2019.
Report wording points
We have not quoted the TECH 07/16 AAF example report, because the release sits behind the ICAEW member login. These points come from ICAEW pages that are open to read.
- Start from the example wording in the release. ICAEW’s helpsheet on references on clients’ financial status points members to TECH 07/16 AAF and TECH 08/16 AAF for example wording that includes disclaimers designed to discourage third parties from relying on the report.
- Keep any hint of an audit opinion out of the report. An ICAEW note from 2015 (still the clearest ICAEW statement on the point) found firms including an opinion on the truth and fairness of the accounts when they were not registered auditors, and warned that this may result in disciplinary action.
- Check that the firm is eligible to use the description “Chartered Accountants” before it appears in the heading. The Practice Assurance Monitoring Report 2026 lists ineligible use of the description among its findings.
- Label drafts. The references helpsheet advises that draft accounts be clearly labelled as such, and not provided directly to a bank.
- Make the report and the engagement letter describe the same engagement, entity, period and framework.
Engagement letters for accounts preparation
The engagement letter is where the limits of a compilation are agreed before work starts, and engagement letters are among the areas the Practice Assurance reviewer goes on to discuss after the opening meeting of a visit. ICAEW’s summary of ISRS 4410 lists what should be clearly agreed with the client:
- the nature of the engagement, including that a compilation is not an audit or a review and expresses no assurance;
- the stated purpose of the engagement and the reporting framework to be used;
- the respective responsibilities of management and the practitioner, including management’s responsibility for the information compiled and for the accuracy and completeness of the underlying records;
- the limitations on the use and distribution of the report.
Those responsibilities sit with the client in law. Every company must keep adequate accounting records (Companies Act 2006 s386(1)), the directors must prepare accounts for each financial year (s394, unless exempt under s394A), and the board approves the accounts and a director signs the balance sheet (s414(1) and (2)).
ICAEW’s engagement letter helpsheet, updated on 10 March 2026, includes schedule B for the preparation of statutory financial statements in compliance with the Companies Act 2006. It is best practice guidance and does not constitute a professional standard, so the wording needs tailoring to each client. The March 2026 update added schedules on identity verification and on filing company accounts on behalf of clients, and the terms of business now cover whether AI or other software tools will be used in service delivery, their limitations, and responsibilities for data protection and due diligence on providers. Our note on client data and AI tools under UK GDPR takes that further.
Two monitoring points belong on the file checklist. Engagement letters are not compulsory, but the basis on which fees are charged and the complaints procedure must be communicated to every client in writing (Practice Assurance Monitoring Report 2026). And ICAEW recommends reviewing engagement letters ideally each year or whenever the scope of work changes, keeping evidence of the version issued.
What Practice Assurance reviewers look at
Practice Assurance covers ICAEW member firms, practising certificate holders and firms with a Practice Assurance contract, and firms can expect a visit at least every eight years, more often where size, complexity, history or risk call for it. Its primary purpose, ICAEW says, is to reassure firms that they continue to meet the Practice Assurance Standards, other relevant regulations and the ICAEW Code of Ethics.
A visit opens with a meeting with the Practice Assurance principal, then moves to the documents requested and a sample of client files selected during the visit, to see how processes work in practice. Findings go on a closing record, and the firm sends written responses within 15 business days of the closing meeting, with a realistic plan for anything not yet fixed.
Quality sits under Standard 4, Quality Control: work should be conducted in an environment where quality is monitored. ICAEW’s guidance for smaller firms on that standard (published May 2018) describes good practice on an accounts file:
- significant work, conclusions and judgements recorded, with the thought processes behind judgemental decisions;
- evidence that the completed accounts were agreed by the client, and final signed copies on file;
- supervision and review before work is finalised, under a policy for the review of files, including hot reviews, with evidence of any review kept on file;
- a compliance review that includes a sample of accounts, checked to see that they are materially correct and comply with statute, and client files checked against the engagement letter.
There is no requirement under the Practice Assurance Regulations or Standards to carry out a formal compliance review, but ICAEW publishes a compliance review helpsheet and checklist (updated 8 October 2025) for firms that do.
Hot review and cold file review
A hot review happens before the work is finalised, so a point it raises can still be corrected in the accounts. A cold review looks at a completed file. It cannot change those accounts, but it shows whether the firm’s procedures are followed and whether the output is good enough.
| Question | Hot review | Cold file review |
|---|---|---|
| When | Before the work is finalised | After the file is complete |
| Purpose | Correct the accounts in hand | Test procedures and the quality of output |
| Who | A more experienced reviewer, or a third party for a sole practitioner | Someone who did not work on the file |
| Output | Points raised and cleared on file | Findings, remedial actions and follow-up |
ICAEW’s Standard 4 guidance for smaller firms says every firm other than a sole practitioner with no staff should have work supervised and reviewed before it is finalised, on a policy set by risk: with competent staff you need not review everything hot, but you should review a sample cold from time to time. For a sole practitioner with a complex engagement, it suggests a hot review by a third party and, if the review papers are not kept, a note on file that the review took place.
ICAEW’s best practice is to conduct whole-firm and cold file reviews annually (the essential level only asks firms to consider annual review and cold review of particularly high-risk assignments), consider periodic external reviews, give the results to all principals and staff with any remedial action, and follow that action up. The guidance for larger firms adds, as best practice, that cold file reviews should cover non-audit assignments, and both compliance with procedures and technical content. Weight the sample towards higher risk work, such as reports to third parties, while covering every office, professional member of staff and type of work over time.
ISQM (UK) 1 draws a similar line. Paragraph A140 separates an inspection, which is a monitoring activity, from a review of an engagement in progress that responds to a quality risk. Deciding in advance which of your reviews is which makes the monitoring easier to explain.
Documenting the review
ICAEW’s larger-firm guidance asks firms to document reviews so it is clear what has been reviewed and who reviewed it, and to record who did the work and when. For each point raised on an accounts file, we would expect the record to show:
- the point, with the reference behind it (the Companies Act section, FRS paragraph or firm procedure);
- who raised it, and on which version of the draft;
- the preparer’s response: what changed, or why nothing needed to;
- who cleared it and when, and whether it went to the partner;
- any difference of opinion and how it was settled, which ISQM (UK) 1 paragraph 31(e) expects to be brought to the attention of the firm and resolved.
ISQM (UK) 2 sets a useful benchmark, though it is written for engagement quality reviews on in-scope work. Paragraph 30 asks for documentation that would let an experienced practitioner with no previous connection with the engagement understand what the reviewer did and concluded, including the names of the reviewer and anyone who assisted, the documents reviewed, and the date the review was completed. A cold reviewer of an accounts file needs the same.
The content of the review itself is set out in our line-by-line checklist for small company accounts under FRS 102 and FRS 105, and the judgement areas in our guide to going concern, related parties, directors’ loans and dividends. The Signed Review explains why every figure the partner signs should trace back to its source.
Borrowing from ISQM (UK) 1 for non-audit work
What the standard covers
ISQM (UK) 1 deals with a firm’s system of quality management for audits or reviews of financial statements, or other assurance or related services engagements. The current FRC edition was issued in July 2021 and updated in September 2025, and the standard has been effective since 15 December 2022. In the UK, paragraph 5 applies it to firms performing engagements under FRC performance standards: audits under ISAs (UK), reporting accountant work on investment circulars, interim reviews by the auditor under ISRE (UK) 2410, client asset assurance for the FCA, and public interest assurance engagements under ISAE (UK) 3000. Compilation engagements are not on that list. A practice that prepares accounts and does no in-scope work is not required by ISQM (UK) 1 to run a system of quality management for its accounts work (a firm that does any in-scope work, including audit, must run the system across all its engagements, accounts work included); its obligations come from the Practice Assurance Standards, other relevant regulations and the ICAEW Code of Ethics.
The standard recognises that a compilation-only firm needs a less complex system. Paragraph 10 says a firm auditing listed entities will need a more complex and formalised system than a firm that performs only reviews of financial statements or compilation engagements.
Ideas worth borrowing
- A risk assessment: set quality objectives, identify the risks to them and design responses (paragraph 8). For an accounts practice the risks might be a new preparer, a client whose records arrive late, or a client moving to new accounting requirements.
- The eight components in paragraph 6, from risk assessment and governance through ethics, acceptance, engagement performance, resources and communication to monitoring and remediation. They make a workable contents page for a short quality manual.
- Review matched to experience, with work by less experienced staff directed, supervised and reviewed by more experienced members of the team (paragraph 31(b)).
- Files assembled on a timely basis after the report date and kept as law and professional standards require (paragraph 31(f)).
- An annual evaluation of the system by whoever is ultimately responsible for it (paragraph 53). For an accounts practice, the Practice Assurance principal can sign off a short yearly note of what the cold reviews found and what changed.
Paragraph A29 accepts that some requirements are not relevant to a firm that performs only related services engagements. Borrow what helps and note why you left the rest.
Reviewer independence, monitoring and remediation
Independence and cooling-off in small teams
ICAEW’s larger-firm guidance says reviewers should not review their own work or that of their close colleagues, and should have the expertise and authority to challenge. ISQM (UK) 1 paragraph 39(b) prohibits engagement team members and the engagement quality reviewer from inspecting that engagement. ISQM (UK) 2 paragraph 19 requires the firm’s policies to specify a cooling-off period of two years, or longer if ethical requirements demand it, before a former engagement partner can take on the role of engagement quality reviewer.
Those rules are written for in-scope work, but the threats are the same in a three-person accounts team. ISQM (UK) 2 paragraph A14 names an intimidation threat where the reviewer has a reporting line to the engagement partner. In a small practice:
- rotate cold reviews so that nobody inspects a file they prepared or reviewed hot;
- borrow the two-year idea, so a partner who signed off a client does not cold review that client for two years;
- look outside where nobody inside is suitable: ISQM (UK) 1 paragraph A156 lets a less complex firm use a service provider for monitoring, ISQM (UK) 2 paragraph A4 allows external engagement quality reviewers, and ICAEW’s smaller-firm guidance suggests training groups, consultancies or a reciprocal arrangement with another member;
- record the threat and the safeguard. ICAEW’s monitoring report lists changing the personnel on the engagement, and internal or external reviews of the work, among safeguards for threats to objectivity.
Monitoring and remediation
ISQM (UK) 1 paragraphs 35 to 47 set out a cycle an accounts practice can run on a smaller scale:
- Plan monitoring around the risks, previous results and other information such as complaints and external inspection findings (paragraph 37).
- Inspect completed engagements, at least one for each engagement partner on a cyclical basis the firm sets (paragraph 38(c)).
- Evaluate the findings and investigate the root cause of each deficiency (paragraphs 40 and 41).
- Design remedial actions that respond to the root cause, then check they were implemented and worked (paragraphs 42 and 43).
Root cause matters most when the same point keeps coming back. If cold reviews keep finding comparatives that do not agree to last year’s signed accounts, ask whether the template, the training or the time allowed is the cause. ICAEW’s guidance asks for action plans on review findings with their progress monitored, and its monitoring report warns that failing to address issues from the previous visit is a common reason for firms being reported to the Practice Assurance Committee.
Where an AI tool is part of the hot review, monitor it as well: what it checked, what it raised, and which points the reviewer accepted or overruled. Our guide on professional responsibility when AI reviews the accounts explains why the judgement and the sign-off stay with the partner.
Further reading
- Accountants' report on unaudited accounts and the work behind it
- Cold file review or hot review for accounts preparation
- ISQM 1 annual evaluation: what the responsible partner must record
- What Practice Assurance looks for on an accounts file
Questions practices ask
Is TECH 07/16 AAF still the current ICAEW guidance on compilation reports?
Yes, on ICAEW’s list of Audit and Assurance Technical Releases as at 21 November 2026. TECH 07/16 AAF, dated 28 March 2016, covers accounts prepared under the Companies Act 2006, and TECH 08/16 AAF covers unincorporated entities. Some older ICAEW pages still refer to the 2010 releases.
Does ISQM (UK) 1 apply to a practice that only prepares accounts?
Not for compilation work alone. In the UK it applies to firms performing engagements under FRC performance standards, such as audits under ISAs (UK), and compilation engagements are not among them. Such a practice answers to the Practice Assurance Standards and the ICAEW Code of Ethics, and can borrow ISQM ideas voluntarily. A firm that does any in-scope work, including audit, must run the system across all its engagements.
Do we have to issue engagement letters for accounts preparation?
ICAEW says engagement letters are not compulsory, but every client must be told in writing the basis on which fees are charged and the complaints procedure. The letter is also where the client accepts that a compilation is not an audit or review, so issuing one and reviewing it each year is the safer course.
How many files should we cold review?
ICAEW’s guidance does not set a number. It asks for a sample weighted towards higher risk assignments that covers every office, professional member of staff and type of work over time, with annual cold file reviews as best practice.
Can a sole practitioner review their own accounts files?
ICAEW accepts that a sole practitioner may review their own procedures, perhaps with a proprietary review programme, but suggests an external reviewer or a reciprocal arrangement with another member, and a third-party hot review for complex engagements. Keep evidence on file that the review took place.
Sources
- Audit and Assurance Technical Releases (listing TECH 07/16 AAF, TECH 08/16 AAF and TECH 09/13 AAF), ICAEW, read 21 November 2026
- TECH 07/16 AAF Chartered Accountants’ Reports on the Compilation of Financial Information of Incorporated Entities, ICAEW Audit and Assurance Faculty, 28 March 2016 (ICAEW members only)
- Accounts preparation/Compilation, ICAEW, read 21 November 2026
- References on clients’ financial status, ICAEW Technical Advisory Services helpsheet, published 30 August 2018, reviewed 1 January 2020
- Accounts filed at Companies House: avoid a difficult conversation, ICAEW, 2015
- Engagement letters and privacy notices, ICAEW Technical Advisory Services helpsheet, updated 10 March 2026
- ICAEW issues Engagement Letter updates: Key changes and guidance for firms, ICAEW, 13 March 2026
- Practice Assurance Monitoring Report 2026, ICAEW, 2026
- Preparing for a Practice Assurance visit, ICAEW, 3 June 2025
- Practice Assurance guidance for sole practitioners and new / smaller firms: Standard 4, ICAEW, 1 May 2018
- Practice Assurance guidance for larger firms: Standard 4, ICAEW, 1 May 2018
- Practice Assurance compliance review, ICAEW Technical Advisory Services helpsheet, updated 8 October 2025
- ISQM (UK) 1 Quality Management for Firms that Perform Audits or Reviews of Financial Statements, or Other Assurance or Related Services Engagements (Issued July 2021, Updated September 2025), Financial Reporting Council, 25 September 2025
- ISQM (UK) 2 Engagement Quality Reviews (Issued July 2021, Updated September 2025), Financial Reporting Council, 25 September 2025
- Companies Act 2006, section 386: duty to keep accounting records, legislation.gov.uk, read 21 November 2026
- Companies Act 2006, section 394: duty to prepare individual accounts, legislation.gov.uk, read 21 November 2026
- Companies Act 2006, section 414: approval and signing of accounts, legislation.gov.uk, read 21 November 2026