What the Inspector Will Ask
The File Is Read Years Later, Sceptically
The audit file is an unusual work product: assembled under deadline, then read at leisure, years later, by reviewers and inspectors whose professional duty is scepticism about the team that wrote it. That asymmetry has always disciplined audit work, and AI does not change it — it hands the sceptical reader a new object. The predictable findings write themselves: reliance on a tool the file cannot explain; evidence that turns out to be a screenshot of a results screen; a conclusion resting on output nobody tied back to a source document. None of these is a new category of finding. Inspectors have always asked why the team relied on what it relied on, whether the thing relied on was a junior's schedule, a specialist's valuation or an analytics routine. The questions are old; the tool is merely the newest thing they attach to.
- The file is written under deadline and read years later by people paid to be sceptical of its authors
- Reliance the file cannot explain is a finding, whatever was relied on — junior, specialist or tool
- A screenshot records that output existed, not what produced it or what anyone did about it
- The inspector's AI questions are the profession's old questions attached to a new object
The Questions, Concretely
The questions themselves are worth rehearsing, because they are answerable in advance or not at all. What did the tool do on this engagement — which procedures did its output feed? What went into it, and was that within what the firm permits? What came out, and where is it now? What did the team do about the output — which flags were followed to source documents, and what happened to the rest? And why was reliance reasonable — what did the team, or the firm on its behalf, actually know about how the tool behaves? These are the workpaper questions from earlier in this course, unchanged by the setting. The uncomfortable follow-up is the one about the misstatement the tool did not flag: the only defensible answer is a file showing that the team's procedures did not stop where the tool's flags stopped.
- What the tool did, what went in, what came out, what the team did about it, and why reliance was reasonable
- The answers exist in advance or not at all — a file cannot be explained backwards three years on
- Flags followed to source documents are evidence; flags noted and filed are a list of open questions
- The hardest question concerns what the tool missed, and the answer is procedures that did not stop at its flags
The Firm Above the File
Above the engagement sits the firm, and above the file sits the firm's system of quality management. The quality-management standards — ISQM 1 is the international instrument — ask, in substance, that a firm identify risks to engagement quality and design responses to them. A tool that engagement teams adopted faster than the firm noticed is precisely such a risk: nobody assessed it, nobody monitors it, nobody trained anyone on its failure modes, and yet audit evidence now passes through it. The firm's system is inspection territory as well as the individual file, because a gap at firm level predicts findings in files not yet inspected. The firm-level questions are the workpaper question at scale: not why did this team rely on this tool, but how does the firm know, for every team, that the answer is a good one.
- Firm-level quality management is meant to govern how audits are performed, and tools are now part of how
- A tool adopted faster than the firm noticed is an unidentified, unanswered risk to engagement quality
- A gap in the firm's system predicts findings in files that have not been inspected yet
- The firm-scale question: how does the firm know every team's reliance would survive the same scrutiny
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.