Audit Documentation and Working Papers That “Stand Up”

Learning objectives

By the end of this chapter you should be able to:

• Explain how audit documentation supports audit quality, accountability, and the ability to defend conclusions in both exam scenarios and practice.
• Build a “stand-up” working paper that links the objective, work performed, evidence, results, and conclusion in a way another auditor can reperform.
• Apply good file hygiene: clear indexing, cross-referencing, consistent naming, version control, timely sign-off, and disciplined handling of review notes.
• Document professional judgement clearly, including alternatives considered and why they were rejected.
• Produce exam-ready documentation that is complete, concise, and logically presented, including the assembly and retention of the final file.

Overview & key concepts

Audit documentation is the recorded story of the audit: why a procedure was needed, what was done, what evidence supports the outcome, what exceptions were found, and how the conclusion was reached. Strong documentation does not change the financial statements by itself. It supports the auditor’s opinion and supports (or explains) any proposed adjustments arising from audit work.

A well-built audit file creates a reliable audit trail: a clear route from a financial statement caption (for example, revenue or trade receivables) to the underlying records and independent evidence, and back again. In an exam setting, your working papers must show that you understand the relevant assertions (such as cut-off, valuation, and completeness) and that your conclusions follow from the evidence.

Audit documentation

Audit documentation captures the audit’s output: the tests carried out, the evidence relied upon, the key findings (including exceptions), and the conclusion drawn.

It should make the work reviewable and defensible. Someone competent who was not part of the audit team should be able to follow the story of the file: what risk was addressed, what was done, what evidence supports the result, and how that result led to the conclusion. If a paper cannot be followed without the preparer explaining it, it is not “stand-up” documentation.

Working papers

A working paper is a single file item (or worksheet) covering one area or one procedure. A good working paper is self-contained: it states the objective, shows the work, points to the evidence, records exceptions, and closes with a clear conclusion.

Audit trail

An audit trail is the traceable path linking:

• the numbers in the financial statements,
• the entity’s accounting records, and
• the supporting evidence (internal and external).

A strong audit trail makes it easy to reperform the work and reduces the risk of unsupported conclusions.

Indexing and cross-referencing

• Indexingis the reference system used to locate working papers quickly (for example, “B1 Cash” or “R3 Revenue cut-off”).
• Cross-referencingconnects related documents (for example, the revenue cut-off test cross-referenced to the receivables lead schedule and the proposed adjustment summary).

Professional judgement

Professional judgement is the reasoned decision-making applied where there is more than one acceptable approach. In documentation, judgement must be visible: the issue, the options considered, the factors weighed, the decision, and the impact on the audit conclusion.

Core theory and frameworks

Building a stand-up working paper

A stand-up working paper should read logically from top to bottom:

1. Objective
2. What you are trying to prove or disprove, usually expressed in terms of an assertion and the risk being addressed.
3. Procedure (work performed)
4. What you did, in enough detail that another auditor could repeat it.
5. Evidence
6. What you relied on and where it sits in the file (or how to retrieve it). Record the source and the date obtained.
7. Results and exceptions
8. What you found, including errors, unusual items, and unresolved points.
9. Conclusion
10. A short, specific conclusion linked to the objective, including whether an adjustment is required and whether further work is needed.

Common exam weakness: conclusions that repeat the objective (“revenue is correct”) without showing what the evidence demonstrated and what the implication is.

File structure and organisation

A usable file is organised so that a reviewer can navigate quickly:

• Permanent section: information expected to be relevant across multiple years (for example, background on the business, system descriptions, significant contracts).
• Current-year section: planning, risk assessment, testing, completion, finalisation.

A practical folder structure is often grouped by phases (planning → risk → testing → completion), with working papers arranged by financial statement area inside each phase.

One working paper, one purpose. If a document contains multiple unrelated tests, it becomes difficult to review and easy to miss exceptions.

Evidence handling and data hygiene

Evidence quality and data discipline affect whether your work “stands up”:

• Naming conventions:use consistent, searchable names that show date, area, source, and version (for example,2025-12-31_BankStmt_MainAcct_BankPortal_v1).
• Source and date:record where the evidence came from and when it was obtained (client portal, third party, system report).
• One source of truth:avoid uncontrolled duplication; reference the authoritative file location.
• Confidentiality:restrict access to sensitive data; avoid including unnecessary personal data in working papers.
• Edits and versions:keep version history clear; do not overwrite without retaining the audit trail of changes.

Review workflow and closing notes

Review notes demonstrate quality control and must be handled professionally:

• Raising notes:reviewers should be specific: what is missing or unclear, and what outcome is expected.
• Responding:preparers should document what was done, attach the new evidence, and state how the note is resolved.
• Closure:final sign-off should show preparer and reviewer, with dates. Open notes must not remain at file lock.

Documenting professional judgement

When judgement is involved, document it in a structured way:

• Issue:what decision was required?
• Options:what alternatives were available?
• Factors:what evidence and considerations mattered (risk, reliability of evidence, size, sensitivity)?
• Decision:what was chosen and why?
• Impact:effect on procedures, conclusions, and any proposed adjustment.

Keep it concise. The aim is clarity, not volume.

Exam and practice anchors (high-level)

Strong documentation usually shows, at a minimum:

• who prepared the working paper and when, and who reviewed it and when;
• the significant matters identified, and how they were resolved or concluded on;
• the key judgements made and what evidence supported them;
• clear finalisation: the file is assembled promptly after completion, and retained under the firm’s policies and applicable regulation(retention periods vary by jurisdiction and firm policy).

Worked example

Narrative scenario

You are auditing a mid-sized manufacturing company, ABC Ltd, with a year-end of 31 December 2025.

During the audit, the following matters arise:

• Opening balance for trade receivables is £250,000.
• Sales revenue for the year is £1,775,000.
• A sales invoice for £50,000 is dated 28 December 2025, but the related goods were dispatched on 3 January 2026.
• A bank reconciliation shows a difference of £5,000 caused by an unrecorded bank charge.
• The inventory count identifies £10,000 of goods that are damaged and require a write-down.
• A VAT refund of £15,000 is due from the tax authority at the year-end but has not yet been received.
• New machinery costing £149,000 was acquired and financed by a bank loan.
• Payroll records show total payroll cost of £500,000, with £50,000 unpaid at the year-end.
• A trade receivable of £20,000 is in dispute and is considered unlikely to be collected.
• A review note queries the absence of sensitivity analysis in the going concern assessment.

Required

1. Prepare a working paper for the sales invoice dated 28 December 2025 (cut-off).
2. Reconcile and document the bank statement discrepancy.
3. Document the inventory count discrepancy and required adjustment.
4. Explain the VAT refund’s impact on the year-end position and cash flow.
5. Assess the impact of the disputed receivable on the financial statements.
6. Document and resolve the review note on sensitivity analysis for going concern.

Solution

1) Revenue cut-off working paper (invoice dated 28 December 2025)

Index: R3 – Revenue cut-off (Dispatch after year-end)

Objective
To confirm revenue is recognised in the correct period and that trade receivables at 31 December 2025 are not overstated (cut-off / occurrence).

Work performed (procedure)

• Obtained the sales invoice dated 28 December 2025 for £50,000 and traced it to the sales ledger entry.
• Obtained dispatch documentation and verified the dispatch date.
• Evaluated whether dispatch is an appropriate point of transfer for recognising revenue for this sale by considering delivery terms (for example, whether the entity’s obligation is satisfied on dispatch or on delivery), supported by dispatch evidence and the entity’s usual shipping arrangements.
• Confirmed dispatch occurred on 3 January 2026, after the year-end.

Evidence

• Sales invoice: SI20251228 (£50,000).
• Dispatch note / delivery record: DN20260103.
• Sales ledger extract showing posting date and customer account: SL_R3.
• Shipping terms reference (order confirmation / standard terms): ST_R3.

Results / exceptions

• Invoice posted in December 2025, but dispatch was 3 January 2026.
• Revenue and trade receivables are overstated at 31 December 2025 by £50,000.

Proposed adjustment (journal entry)
To reverse the premature recognition:

• Dr Revenue (Sales)£50,000
• Cr Trade receivables£50,000

If the entity’s system separates dispatch/delivery and invoicing, the correction may be presented via deferred income/contract liability or other timing accounts. The audit point is that revenue and the related asset must not be recognised before the performance obligation is satisfied.

Conclusion
Revenue and receivables are overstated by £50,000 due to cut-off error. Adjustment required to recognise the sale in 2026 when the performance obligation is satisfied.

Accounting equation impact (of proposed adjustment)

• Assets:Trade receivables decrease£50,000
• Income:Revenue decreases£50,000
• Equity:Retained earnings decreases£50,000 (via reduced profit)

2) Bank reconciliation discrepancy (unrecorded bank charge)

Index: B1 – Cash and bank (Year-end reconciling items)

Objective
To confirm the cash and bank balance is stated correctly and reconciling items are valid (existence / accuracy).

Work performed (procedure)

• Agreed the bank statement closing balance to the bank reconciliation.
• Compared reconciling items to subsequent clearing on the bank statement where applicable.
• Identified a £5,000 bank charge shown on the bank statement that is not recorded in the ledger.

Evidence

• Bank statement to 31 December 2025: BS20251231.
• Cashbook / ledger extract: CB20251231.
• Bank reconciliation prepared by client: BR20251231.

Results / exceptions

• Bank charge of £5,000 appears on bank statement; no corresponding ledger entry.

Proposed adjustment (journal entry)

• Dr Bank charges expense (operating expense)£5,000
• Cr Bank (cash)£5,000

Conclusion
Cash is overstated by £5,000 and operating expenses understated by £5,000 unless adjusted.

Accounting equation impact (of proposed adjustment)

• Assets:Cash decreases£5,000
• Expenses:Increase£5,000 (reducing profit)
• Equity:Retained earnings decreases£5,000

3) Inventory count discrepancy (damaged goods requiring write-down)

Index: I2 – Inventory valuation (Damage / write-down)

Objective
To confirm inventory is not overstated at year-end and is carried at an appropriate value (existence / valuation).

Work performed (procedure)

• Reviewed inventory count records and investigated the variance relating to damaged goods.
• Inspected evidence of damage (photos / warehouse report where available).
• Compared cost to expected recoverable amount; concluded the items require a write-down of £10,000.
• Confirmed the write-down relates to goods included in the year-end count.

Evidence

• Inventory count sheets: IC20251231.
• Warehouse/quality report on damaged items: WH_DMG_202512.
• Inventory valuation listing showing affected lines: IVL_I2.

Results / exceptions

• Damaged goods included in inventory require a reduction in carrying value of £10,000.

Proposed adjustment (journal entry)
Common presentation is either within cost of sales or as a separate inventory write-down expense:

• Dr Cost of sales (or Inventory write-down expense)£10,000
• Cr Inventory£10,000

Conclusion
Inventory is overstated by £10,000 unless adjusted. The adjustment reduces profit for the year.

Accounting equation impact (of proposed adjustment)

• Assets:Inventory decreases£10,000
• Expenses:Increase£10,000 (reducing profit)
• Equity:Retained earnings decreases£10,000

4) VAT refund (amount due but not yet received)

Index: T1 – Indirect tax (VAT control and year-end position)

Year-end position (mechanics)
VAT is typically recorded through a VAT control (or similar) account as output VAT (on sales) and input VAT (on purchases) are accumulated and netted. At the reporting date, the VAT control position will normally be:

• anet receivable(current asset) if recoverable from the tax authority, or
• anet payable(current liability) if owed.

A refund due of £15,000 at 31 December 2025 indicates a net VAT receivable at year-end (assuming it is valid and recoverable).

Evidence (what would be filed)

• VAT return / VAT control reconciliation for the period end showing the net refund position.
• Tax authority portal screenshot or correspondence confirming the submitted claim or stated balance.
• Subsequent receipt testing (if received after year-end): bank statement entry agreeing to £15,000 and trace to clearing of the VAT balance.

Presentation / reclassification
If the trial balance already shows a net VAT receivable balance, there may be no journal required—only audit evidence that the receivable exists and is recoverable.

If the VAT balance is sitting in the wrong place (for example, shown as a payable when it should be a receivable), the correction is typically a reclassification within current assets/liabilities, not a profit adjustment.

Profit impact (tight exam wording)
VAT should not normally be recognised as income or expense for a VAT-registered entity acting as a collecting agent. A profit impact arises only if VAT has been incorrectly posted to income or expense lines (for example, grossing up sales or expenses incorrectly), in which case the correction depends on the underlying posting error.

Cash flow impact

• There isno cash inflow at year-endbecause the refund is not yet received.
• Cash increases by £15,000when receivedin the subsequent period.
• At 31 December 2025, the entity reports aVAT receivable(asset) of £15,000.

5) Disputed receivable (likely uncollectible)

Index: R5 – Trade receivables valuation (Specific impairment)

Objective
To confirm trade receivables are stated at an amount expected to be collected (valuation).

Work performed (procedure)

• Identified the disputed balance of £20,000 and obtained correspondence supporting the dispute.
• Considered payment history and current status of the dispute.
• Reviewed any subsequent cash receipts after year-end (if available).
• Concluded collection is unlikely; a full specific allowance is appropriate unless compelling recovery evidence exists.

Evidence

• Aged receivables listing: AR_AGED_20251231.
• Dispute correspondence / legal letter: AR_DISP_20K.
• Subsequent receipts review (if available): AR_SUBREC_JAN26.

Proposed adjustment (journal entry)
To recognise a specific allowance (impairment) against trade receivables:

• Dr Impairment loss on receivables (operating expense)£20,000
• Cr Allowance for doubtful debts (contra-asset)£20,000

Conclusion
Receivables are overstated by £20,000 unless an allowance is recognised. Profit is overstated by £20,000.

Accounting equation impact (of proposed adjustment)

• Assets:Net trade receivables decrease£20,000 (via allowance)
• Expenses:Increase£20,000 (reducing profit)
• Equity:Retained earnings decreases£20,000

6) Review note completion: going concern sensitivity analysis

Index: C3 – Going concern (Model review and sensitivities)
Linked note: RN-07 (Completion review notes log)

Review note (raised by reviewer)

RN-07: Sensitivity analysis not evidenced in going concern assessment. Please document management’s base case and at least one downside scenario, including the impact on cash headroom and covenant compliance, and conclude whether going concern remains appropriate.

• Raised by:Reviewer (initials)
• Date raised:(date)
• Target paper:C3 Going concern memo

Management information requested and obtained

Objective
To obtain sufficient evidence that management has assessed going concern using reasonable assumptions and that the conclusion is supported, including consideration of downside scenarios.

Work performed (procedure)

• Obtained management’s going concern assessment and cash flow forecast covering at least 12 months from the reporting date.
• Confirmed the forecast is internally consistent (opening cash agrees to bank reconciliation, payroll and major cost lines agree to records, debt repayments agree to loan schedules).
• Identified key assumptions (sales volume, gross margin, collection period, input costs, and timing of major payments).
• Requested management’s sensitivity analysis. Where not prepared, performed auditor-run sensitivities on the model and discussed results with management.

Evidence

• Management cash flow forecast and assumption pack: GC_Model_v2.
• Loan agreement and repayment schedule: Loan_Sched_C3.
• Covenant calculation support (if applicable): Cov_Calc_C3.
• Minutes/emails confirming management approval of forecast: GC_Mgmt_Approval.

Sensitivity analysis (documented)

Base case summary (management)

• Forecast shows positive cash headroom throughout the period and no covenant breaches.

Downside scenarios (example sensitivities documented)

• Scenario 1: Revenue 10% below base case for the first 6 months; gross margin unchanged.
• Scenario 2: Customer receipts delayed by 15 days across the forecast period (working capital stress).

Results (what the model shows)

• Scenario 1: Headroom reduces but remains positive; no covenant breach noted.
• Scenario 2: Lowest cash headroom occurs in (month), but remains above the minimum facility buffer; no covenant breach noted.

Auditor evaluation and conclusion

• Considered whether the sensitivities selected reflect realistic downside risks given the business and current trading conditions.
• Evaluated management actions (if needed) for plausibility and whether they are within management control (for example, deferring discretionary spend vs. raising new finance).
• Considered whether disclosures are adequate, and whether the auditor’s report would require emphasis or modification depending on the presence of a material uncertainty.
• Concluded whether there is (i) no material uncertainty, (ii) a material uncertainty requiring disclosure, or (iii) an inappropriate going concern basis (rare), based on the evidence obtained.

Conclusion (example)
Sensitivity analysis has been obtained/performed and documented. Under tested downside scenarios, the entity maintains sufficient liquidity headroom and remains within covenant limits. Going concern basis remains appropriate. No material uncertainty identified based on the evidence reviewed.

Review note closure

• Preparer response:Completed. Evidence added to C3 and linked.
• Closed by reviewer:(initials)
• Date closed:(date)

Pulling the adjustments together (overall effect)

If the proposed adjustments are processed (and assuming each item was originally recorded incorrectly or omitted as described):

• Revenue decreases by£50,000(cut-off correction).
• Operating expenses increase by£5,000(bank charge) and£20,000(receivable impairment).
• Cost of sales (or inventory write-down) increases by£10,000.

Total reduction in profit for 2025 = £50,000 + £5,000 + £10,000 + £20,000 = £85,000.

Balance sheet impacts from these profit-related adjustments:

• Trade receivables decrease by£50,000(cut-off reversal).
• Cash decreases by£5,000(bank charge).
• Inventory decreases by£10,000(write-down).
• Net trade receivables decrease by£20,000(allowance).

Net decrease in assets = £85,000, consistent with the profit reduction.

The VAT refund creates or confirms a £15,000 VAT receivable at year-end and affects cash only when received.

Common pitfalls and misunderstandings

• Saying “documentation affects the financial statements.”Documentation supports conclusions; it does not change the numbers unless an adjustment is proposed and processed.
• Cut-off errors explained without a journal entry.When you conclude an item is in the wrong period, show the correcting entry clearly and explain the impact on profit and net assets.
• Debits and credits inconsistent with the conclusion.For example, reversing overstated revenue requires a debit to revenue and a credit to receivables (if the invoice was posted).
• Cash versus receivable confusion.A VAT refund due is a receivable at the reporting date; it is not cash until received.
• Inventory write-down treated as a “missing stock” issue only.Damage and obsolescence are valuation matters; document evidence supporting the reduced recoverable amount.
• Allowance vs write-off muddled.If the balance still exists but is doubtful, use an allowance (contra-asset). A write-off requires evidence that the receivable is no longer valid.
• Review notes left open.A file is not complete until notes are answered with evidence and formally closed.
• Tick marks without meaning.Tick marks must have a legend; otherwise they add clutter without clarity.
• Weak cross-referencing.If your working paper does not link to the lead schedule and evidence, a reviewer cannot follow the audit trail.
• Uncontrolled versions of key schedules.Multiple competing “final” files undermine what was actually audited.
• Missing sign-off.If the file does not show who did the work, who reviewed it, and when, it is difficult to defend.

Summary and further reading

Audit documentation is the recorded basis for audit conclusions. A strong working paper is built around a clear objective, a procedure that can be repeated, reliable evidence, a transparent record of results, and a conclusion that follows logically.

Good organisation (indexing and cross-referencing), disciplined evidence handling, version control, timely sign-off, and professional treatment of review notes make the file usable under time pressure and defensible in review. Where audit findings lead to proposed adjustments, documentation should clearly set out the correction and the effect on profit, net assets, and key balances.

For broader context, review introductory financial reporting materials on recognition, measurement, cut-off, receivables valuation, and inventory write-downs, alongside general audit methodology guidance from professional bodies and regulators.

FAQ

Why is audit documentation so important?

Because it shows what was done, what evidence supports the work, what was found, and how conclusions were reached. It supports accountability, enables review and reperformance, and helps defend the work if challenged later.

What are the key elements of a strong working paper?

A clear objective, a step-by-step record of work performed, referenced evidence, documented results (including exceptions), a specific conclusion, and visible sign-off by preparer and reviewer with dates.

How do indexing and cross-referencing improve the audit file?

They make the file navigable and verifiable. Indexing helps you locate papers quickly; cross-referencing connects the financial statements, lead schedules, testing, and evidence into one coherent audit trail.

How should professional judgement be documented?

State the issue, outline realistic alternatives, record the factors considered (risk, evidence reliability, sensitivity, size), document the decision, and explain the impact on procedures and conclusions.

How should review notes be handled?

Answer them with evidence, not reassurance. Record what you did, attach or reference the supporting evidence, and close the note with reviewer sign-off and date once resolved.

Summary (Recap)

This chapter explains how to create audit documentation that is clear, complete, and defensible. It sets out how to build stand-up working papers that connect objectives, procedures, evidence, results, and conclusions. It also covers file organisation, evidence handling, version control, and review note discipline. The worked example demonstrates how to document common findings, show the related debit/credit entries and accounting equation effects, and complete a review note by obtaining and evaluating sensitivity analysis for going concern.

Glossary

Audit documentation
The recorded output of the audit: what risks were addressed, what work was done, what evidence was relied on, what was found, and what conclusion was reached.

Working paper
A single file item covering one audit area or procedure, designed so another auditor can follow and reperform the work.

Audit trail
The route linking financial statement figures to underlying records and supporting evidence, and back again.

Indexing
A reference system used to organise and locate working papers efficiently.

Cross-referencing
Links between working papers, schedules, and evidence that allow the reviewer to follow the audit trail.

Professional judgement
Reasoned decision-making where more than one acceptable approach exists, documented so the rationale is clear.

Review note
A reviewer query requiring action, evidence, and documented closure.

Sign-off
Recorded confirmation (name/initials/e-signature and date) that preparation and review responsibilities have been completed.

Version control
Controls that make the latest approved document identifiable and prevent confusion caused by multiple competing versions.

Confidentiality
The duty to protect client information and restrict access to those who need it for the audit.