Document working papers, significant findings, assessed risks, and conclusions.
Working papers should let an experienced practitioner understand what was planned, what was done, what evidence was obtained, what issues were found, and why the conclusion follows. Documentation is not a clerical afterthought. It is the record that connects professional judgment to the engagement conclusion.
The practical task is to decide whether the file supports the conclusion, whether significant findings were evaluated, and whether the issue is a documentation gap, an evidence gap, or both.
This lesson focuses on how to:
Good documentation is specific enough for review and future reference. It should not rely on memory, informal conversation, or unexplained tick marks.
| Element | Required clarity |
|---|---|
| Objective or risk | The file should state what assertion, criterion, control, estimate, disclosure, or compliance requirement is being tested. |
| Procedure performed | The work should be described in enough detail to show what was done, not just that it was “reviewed” or “agreed.” |
| Nature, timing, and extent | The file should show the type of work, when it was performed, and how much was tested. |
| Population and selection | The working paper should identify the population, source, selection method, and items tested. |
| Evidence obtained | The record should identify documents, reports, confirmations, recalculations, observations, inquiries, or analyses used. |
| Exceptions and follow-up | Exceptions should be described, investigated, evaluated, and cleared or carried forward. |
| Conclusion | The conclusion should answer the objective and be consistent with the evidence. |
| Preparation and review | The file should show who prepared and reviewed the work and when review points were cleared. |
Weak documentation often uses vague verbs. “Reviewed,” “checked,” “agreed,” and “discussed” may be acceptable only if the file also states what was reviewed, what source was used, what population was covered, what exceptions were found, and what conclusion follows.
Significant findings require more than a note that an issue exists. The file should show why the issue matters and how it affected the engagement.
| Finding | Documentation focus |
|---|---|
| Exception in a test of details | Item tested, nature of exception, dollar or qualitative effect, cause, projected effect if applicable, and conclusion. |
| Control deficiency | Control objective, failed control, frequency, cause, compensating controls, effect on reliance, and communication. |
| Judgmental estimate | Assumptions, data source, method, sensitivity, management bias indicators, and reasonableness conclusion. |
| Fraud indicator | Fact pattern, procedures performed, escalation, response, and communication implications. |
| Scope limitation | Procedure that could not be performed, reason, alternative evidence considered, and effect on conclusion. |
| Management disagreement | Issue, criteria, management position, practitioner assessment, unresolved effect, and communication. |
The significance of a finding depends on risk, materiality or significance, user sensitivity, and the effect on the conclusion. A small exception may still be significant if it indicates fraud, management bias, a control failure, or non-compliance with important criteria.
Cases often test whether the candidate can tell the difference between poor file writing and insufficient assurance work.
| Situation | Documentation gap or evidence gap? | Why it matters |
|---|---|---|
| File states “no issues noted” but does not identify items tested. | Documentation gap, unless evidence cannot be located. | The work may have been done, but the reviewer cannot assess extent or relevance. |
| No support exists for management’s explanation of an unusual variance. | Evidence gap. | The conclusion relies on unsupported inquiry. |
| Sample exceptions are listed, but no conclusion is documented. | Documentation gap and possible evidence evaluation gap. | The file does not show whether exceptions were isolated, projected, or material. |
| Procedure was performed on the wrong period. | Evidence gap. | Documentation cannot fix work that does not address the risk period. |
| Reviewer note asks for support and is cleared with “discussed with client.” | Evidence gap. | The resolution does not provide corroborating evidence. |
| Specialist report is included but assumptions are not assessed. | Documentation and evaluation gap. | The file does not show whether reliance on specialist work is justified. |
This distinction determines the remedy. If the evidence exists but the file is unclear, documentation should be improved. If the evidence was never obtained, the procedure must be performed or alternative evidence must be found.
The best improvement is the one that directly fixes the missing link in the file.
| Weak documentation | Better documentation |
|---|---|
| “Reviewed revenue.” | “Tested 25 revenue transactions selected from the current-year sales journal for occurrence, accuracy, and cut-off by agreeing invoice, shipping document, customer order, and subsequent cash receipt.” |
| “Management explanation accepted.” | “Management explained the variance; corroborated the explanation to contract amendments, board-approved price changes, and subsequent invoices.” |
| “Exception immaterial.” | “Exception amount is below materiality individually; evaluated whether similar exceptions exist and whether the cause indicates a control deficiency.” |
| “No further work needed.” | “No further work required because alternative procedures provided evidence over the complete population and exceptions were isolated.” |
| “Specialist report reviewed.” | “Reviewed specialist competence, scope, assumptions, source data, and conclusion; assumptions are consistent with engagement criteria.” |
Better documentation should not make weak evidence look stronger than it is. If the file does not support a conclusion, the correct response is additional work, not polished wording.
| Step | Question | Output |
|---|---|---|
| 1. Objective | What risk, assertion, criterion, or conclusion is the paper meant to support? | Documentation purpose. |
| 2. Work performed | What procedure was done, when, and over what population? | Nature, timing, extent, and selection. |
| 3. Evidence | What source documents, reports, confirmations, or analyses support the work? | Evidence trail. |
| 4. Findings | What exceptions, significant issues, or contradictions arose? | Finding and follow-up. |
| 5. Conclusion | Does the documented evidence support the conclusion? | Supported conclusion or required action. |
Use this sequence when a case provides a working paper excerpt, reviewer note, unresolved exception, specialist report, or file-quality concern.
| Pitfall | Correction |
|---|---|
| Treating documentation as formatting. | Focus on whether the file supports the engagement conclusion. |
| Writing generic procedure names. | Document objective, population, selection, evidence, exceptions, and conclusion. |
| Clearing exceptions without evaluation. | Explain cause, effect, materiality or significance, projection if relevant, and follow-up. |
| Confusing a missing memo with missing evidence. | Determine whether evidence exists before proposing only a documentation fix. |
| Ignoring reviewer needs. | Ensure an experienced reviewer can understand the work without oral explanation. |