A custom working paper template is a named set of sections — defined once at the firm level, not once per engagement — that every working paper for that procedure follows, so a reviewer moving from one client's file to another's finds the same structure in the same order. The template fixes the shape; the content inside each section, the tickmarks, the exceptions found and the conclusion reached, still comes entirely from the engagement team's own work on that specific client.
The cost of leaving the format to each engagement
Without a firm-level template, every engagement team ends up deciding its own working paper structure — sometimes well, sometimes by copying whatever the last file happened to look like. The result is a quality-control review where every file needs re-orientation: where does this firm put the scope statement, where's the exceptions summary, is the sign-off section at the top or the bottom this time. None of that variance adds any audit value. It's pure overhead the reviewer pays on every single file.
Common practice, not a requirement
Standardising the shape of a working paper is a firm quality-control decision, not a requirement of any standard. The standards require sufficient appropriate documentation of the work performed; they do not prescribe a template. A firm is free to decide its own, and free to change it as it learns what works.
What belongs in a template, and what doesn't
| Belongs in the template | Belongs to the engagement team |
|---|---|
| The named sections and their order | What each section actually says about this client |
| Where sign-off (preparer, reviewer, partner) sits | Who signs off, and when |
| Which sections are mandatory for this procedure | The specific exceptions found, if any |
| Cross-reference conventions | The population tested and the conclusion reached |
Building one without over-specifying it
- 01Start from what the firm already does wellThe firm's best existing working papers — the ones a partner would be happy to show a peer reviewer unannounced — are the template, formalised. Don't design one from scratch; extract one from practice that already works.
- 02Name sections by function, not by habit"Scope", "Population tested", "Exceptions", "Conclusion" orient a reviewer faster than section names that only make sense to whoever wrote the original file.
- 03Keep the template procedure-specific, not firm-wide-genericA purchase testing working paper and a bank reconciliation working paper don't need the same section structure. A single generic template that tries to fit every procedure usually fits none of them well.
- 04Revise it when a review finds the same gap twiceIf two unrelated engagements are missing the same thing, the template is probably missing a section for it — that's a stronger signal than any single preparer's mistake.
A template should never be used to pre-fill a conclusion. A section titled 'Conclusion' that always defaults to 'no exceptions noted' until someone deletes it is worse than no template at all — it makes an unfilled-in default look like a decision someone actually made.
What this buys at review and at inspection
A standardised template means a quality reviewer — internal, or ICAI's peer review, or a regulator — can move through a sample of files at the speed of checking content rather than first having to learn each file's bespoke layout. That speed is not a cosmetic benefit; it's the difference between a review that actually gets through the sample it was supposed to cover and one that runs out of time halfway through.
How we think about this
Lekhya lets a firm define its own named section structure once, per procedure, and every working paper generated for that procedure follows it — the structure is fixed by the firm; everything written inside it is the engagement team's own work, never generated or guessed at.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Audit documentationAudit working papers: what they should containThe anatomy of a paper that stands on its own: objective, population, sample basis, procedure, results, exceptions, conclusion and sign-off, and what each must establish.
- Audit documentationReviewing and signing off audit working papersWhat a reviewer is responsible for, a defensible review order, writing points that get cleared properly, and why approval must lapse when the paper changes.
- Audit documentationVersion control for audit working papersThe file name is a confession. If a working paper needs 'actualfinal' in its name, the firm has no real way of knowing which version was reviewed.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.