Northstar Sporting Goods, Inc. is a non-issuer with a 12/31/20X5 year end, and we are building the documentation package that supports the opinion we plan to release on 3/31/20X6. The business facts that drive the documentation are the size of the entity and what could be material to users, so we anchor the file to Northstar’s planning materiality of $96,000, performance materiality of $72,000, and the requirement to complete final file assembly by 5/30/20X6, which is 60 days after the report release date. Before we think about file structure, we need the timeline straight because the timing determines what can still be assembled and what becomes a locked record for retention and inspection purposes. To orient our file clocks and responsibilities, map Northstar’s key dates and what each date controls:
An engagement file earns its keep when a reviewer can pick up one risk, trace what we did, and see why we signed off. That is the practical point of the audit documentation objective in AU-C 230 for the auditor, which is to prepare audit documentation that provides a sufficient and appropriate record of the basis for the auditor’s report and evidence that the audit was planned and performed in accordance with GAAS and applicable legal and regulatory requirements. We operationalize that objective using the “experienced auditor” benchmark, meaning someone with audit experience, who has no previous connection with this engagement, can understand what we did, when we did it, what evidence we obtained, and the conclusions we reached without needing us to fill in missing context from memory.
To make that benchmark concrete, we anchor the file around one thread that is easy to review for completeness and linkage, a presumed higher risk of material misstatement in revenue recognition because revenue is $48,600,000 and small percentage errors can exceed planning materiality of $96,000. The decision we have to make in documentation is whether a reader can see the full chain from the identified risk, to the response in our audit program, to the specific evidence obtained, to the conclusion and its impact on the auditor’s report, with materiality used consistently to explain why the work was sufficient. Before we write anything, choose what the minimum complete “thread” must contain so the file is re-performable in concept: