How to Write an Audit Working Paper
A junior hands over a tidy paper: a title, a result, a conclusion. “Checked, no exceptions.” It looks finished. It isn’t — a reviewer still can’t answer three basic questions from it.
The standard a working paper has to meet
An experienced auditor with no connection to the engagement should be able to understand what was done, what was found, and what was concluded — without phoning the person who wrote it. That matters because papers are reviewed by seniors, checked by regulators, and used by a different team a year later. If it isn’t written down, then as far as the file is concerned, it wasn’t done.
What “checked, no exceptions” is missing
Play the reviewer. Three questions, and a bare “checked, no exceptions” paper can’t answer any of them: Which items were tested, and how were they chosen? There’s no population, no sample, no method named. What were they compared to? No source is named — dispatch records, customer orders, cash received? How does the conclusion follow? “Fairly stated” is a very large claim resting on a test nobody can see. It sounds like a result, but it’s really only a statement that someone did something.
Five elements, in order
- —Purpose. The risk or assertion it addresses. If you can’t say what a test is for, you shouldn’t be doing it.
- —Source. Where the data came from, and why it can be relied on. A report the client generated tells you less than a document from outside.
- —Procedure. What was done, on how many items, and how they were chosen.
- —Results. What was found, including every exception, however small.
- —Conclusion. Whether the purpose was achieved, and why — tied directly to the purpose, never broader than the test can support.
The most common weakness: overreach
Testing 25 sales invoices and finding no errors supports a narrow conclusion: the sample supports the tested assertion for the population, within the limits of sampling. It does not support “revenue is fairly stated” — that’s a claim about the whole of revenue, far larger than 25 invoices can carry. The same logic applies to confirmations: 9 of 10 balances agreeing does not mean “receivables are correct” — the tenth, unconfirmed balance might be the largest.
An honest paper is allowed to leave a matter open. “Reply disagrees by ₹2.4 crore — unresolved, carried forward” is a better conclusion than a confident “fairly stated” that the evidence doesn’t actually support. A paper that says a matter is open, with a reference to where it’s dealt with, is far better than one that says everything is fine.
Tick-marks and review
Tick-marks — small shorthand marks in the margin — only work if every mark is defined on the paper itself. The exact symbols vary by firm; what matters is that a stranger can read the legend and know exactly what was done to each figure. Review has to leave the same kind of trace: the preparer signs and dates the paper, the reviewer signs and dates it, and any questions the reviewer raised get answered directly on the file — not just in conversation. A review that happened only over coffee, as far as the file is concerned, didn’t happen.
This guide illustrates standard audit-documentation practice using a fictional teaching case. It is practical educational content, not professional audit guidance — a real engagement follows its own firm’s documentation standards and methodology.
Go deeper with the full engagement
This documentation standard is Lesson 11 of Advanced Audit & Assurance, one module inside a full fictional engagement — from accepting the client through planning, testing, and forming the final opinion.
Have a question this guide didn’t answer? See the full FAQ or contact us directly.