What Practice Assurance looks for on an accounts preparation file comes down to whether a reviewer who was not involved can see what was done, who checked it and what the client agreed. This article is for partners and Practice Assurance principals in ICAEW firms that compile accounts without auditing them. It covers how a visit uses client files, what ICAEW’s Standard 4 guidance expects on the file, where the compilation guidance (TECH 07/16 AAF) fits, and how to prepare.
How a visit uses your files
ICAEW’s page on preparing for a Practice Assurance visit says firms can expect a visit at least every eight years, with firm size, complexity and visit history able to bring one sooner. The reviewer inspects a sample of client files, selected during the visit, and ICAEW says the files show how you have applied your processes in practice. You cannot choose which files are looked at, so every accounts file needs to be in a state you would be content to show.
Engagement letters are discussed as one of the key process areas, so the letter and the file are read together. Our overview of quality management for accounts preparation covers the engagement letter and the wider system, so this article stays with the file.
What the file should show
ICAEW’s Standard 4 guidance for smaller firms, published on 1 May 2018, sets out what to keep. Read as a list for an accounts file, it asks for the following (this is guidance, with essentials and best practice shown separately, not a rulebook).
- All significant work recorded, with the sources of information and evidence identified.
- Assumptions and estimates shown, and the thought processes behind judgemental decisions recorded.
- Evidence that the completed accounts have been agreed by the client.
- Final copies of signed accounts and other reports kept on file. Cross-referencing them to key working papers is listed as best practice, not as an essential.
The signed accounts matter most when something is questioned later. A file that holds the draft but not the signed version cannot show what the client approved. Cross-referencing shows how a figure in the accounts traces to its working paper, which is also the discipline behind The Signed Review.
ICAEW’s guidance also suggests reviewing some files cold from time to time to see whether you can follow all the work done, conclusions reached and evidence gathered, and its larger-firm guidance adds that cold file reviews on non-audit assignments should consider the adequacy of recording work. Following the file without the preparer’s help is a sensible test.
Evidence of review
The same Standard 4 guidance says all firms, other than sole practitioners with no staff, should have procedures to supervise and review work, and asks you to keep evidence of any review on file. It also asks for a policy for the review of files, including hot reviews. Where review papers are not retained, for example after an external consultant’s review for a sole practitioner, it says a note should be made on file that a review has taken place.
These questions are a practical test of whether the file shows its own review, and they would help in answering a reviewer who asks, although ICAEW does not set them out as requirements.
- Who reviewed the accounts, and were they a different person from the preparer?
- When was the review done, relative to the date the accounts were finalised?
- What did the reviewer raise, and how was each point cleared?
- Does the policy say this file needed this level of review, and was it followed?
Our review checklist for small company accounts gives the content a reviewer tests, and a record of that test is the kind of evidence of review ICAEW’s guidance asks you to keep on file.
Where TECH 07/16 AAF fits
For accounts of incorporated entities, the current ICAEW release on compilation reports is TECH 07/16 AAF, Chartered Accountants’ Reports on the Compilation of Financial Information of Incorporated Entities, dated 28 March 2016. ICAEW’s list of Audit and Assurance Technical Releases shows it with that date, and the only other compilation release on the list is TECH 08/16 AAF for unincorporated entities, dated 29 March 2016. Checked against that list on 21 November 2026.
ICAEW’s accounts preparation page describes compilation as a practitioner receiving financial data and information from a client and rearranging it into a set of financial statements, and says this type of engagement does not constitute an assurance engagement. It points practitioners to ISRS 4410, Engagement to Compile Financial Statements. The same page still refers to AAF 2/10 and AAF 3/10, so check which version of that guidance your report template follows. On the file, the report, the engagement letter and the accounts should describe the same engagement.
ISRS 4410 requires clear agreement with the engaging parties of the nature of the engagement, including that a compilation is not an audit or a review and that no assurance is expressed, together with its stated purpose, the reporting framework, the respective responsibilities of management and the practitioner, and any limits on the use and distribution of the report. It adds that independence is not a requirement for compilation engagements, although the ethical principles of the Code of Ethics apply and the value of a compilation rests on them. Audit-only rules do not carry over to accounts preparation.
After the visit
ICAEW says findings that need action are set out in a closing record, which the reviewer goes through with you at the end of the on-site visit. Written responses are due within 15 business days of the closing meeting. Firms do not need to resolve every issue in that window but should provide a realistic plan and timeline.
ICAEW’s Practice Assurance Monitoring Report 2026 adds a warning: failure to address issues raised at the previous review is a common reason for firms being reported to the Practice Assurance Committee. A finding on an accounts file therefore needs an owner and a date, because the next visit will check it.
A file readiness list
| Item on file | What a reviewer wants to see | Source |
|---|---|---|
| Significant work | Recorded, with sources identified | Standard 4 guidance |
| Judgements | Assumptions and reasoning shown | Standard 4 guidance |
| Client agreement | Evidence the completed accounts were agreed | Standard 4 guidance |
| Signed accounts | Final copy on file (essential); cross-referenced to working papers (best practice) | Standard 4 guidance |
| Review | Evidence of review, or a note that it took place | Standard 4 guidance |
The partner who signs remains responsible for the accounts however the review was done. Our guide to signing off AI-reviewed accounts explains how that applies where a tool contributes to the review.
Questions practices ask
How often will Practice Assurance visit us?
ICAEW says firms can expect a visit at least every eight years, with more frequent visits possible depending on size, complexity and visit history.
Which of our files will the reviewer look at?
The reviewer inspects a sample of client files selected during the visit, so none can be prepared specially. The sample shows how processes are applied in practice.
Is TECH 07/16 AAF still current?
It is the release shown on ICAEW’s technical releases list for compilation reports of incorporated entities, dated 28 March 2016, as checked on 21 November 2026. The list shows no later compilation release.
How long do we have to respond to the visit findings?
Written responses are due within 15 business days of the closing meeting, with a realistic plan and timeline for anything not yet resolved.
Sources
- Preparing for a Practice Assurance visit, ICAEW, 3 June 2025
- Practice Assurance guidance for sole practitioners and new / smaller firms: Standard 4, ICAEW, published 1 May 2018
- Practice Assurance guidance for larger firms: Standard 4, ICAEW, published 1 May 2018
- Audit and Assurance Technical Releases (TECH 07/16 AAF, TECH 08/16 AAF), ICAEW, read 21 November 2026
- Accounts preparation/Compilation, ICAEW, read 21 November 2026
- Practice Assurance Monitoring Report 2026, ICAEW, 2026