A working paper template should be defined per procedure, not once as a single generic template meant to cover every procedure a firm performs. A bank reconciliation working paper and a related-party transaction testing working paper record fundamentally different kinds of work — one is substantially a numeric tie-out with reconciling items, the other is substantially a search for undisclosed relationships and an assessment of whether disclosed transactions were on arm's-length terms. Forcing both into the same section structure means the structure fits neither one particularly well, because it was designed to fit an average of the two rather than either one specifically.
Why 'one template to rule them all' is a common first instinct
A single firm-wide template is simpler to build, simpler to explain, and simpler to maintain — one document instead of a dozen. That simplicity is real, but it's bought by pushing the mismatch cost onto every engagement team that uses the template for a procedure it wasn't really designed for. A generic 'Scope / Testing / Exceptions / Conclusion' structure works reasonably well for almost everything in a shallow way, and reasonably badly for anything that needs a section the generic template doesn't have.
Where a generic structure actually breaks
| Procedure | Section the generic template is missing |
|---|---|
| Bank reconciliation | Reconciling items, aged and individually explained — not just a single exceptions line |
| Related-party testing | Relationships identified independently of management's disclosure list |
| Fixed asset additions | Capitalisation versus revenue expenditure judgement, documented per addition |
| Revenue cut-off | Sample selected either side of the period end, documented separately from the main population |
| Payroll | Reconciliation of headcount movement to the attendance and payroll registers |
None of these missing sections are exotic. They're the specific thing that procedure is actually about. A generic template doesn't forbid writing that detail somewhere — it just doesn't give it a named place, which means it ends up buried inside a generic 'Testing' section, which is exactly the kind of structural inconsistency a template was supposed to prevent in the first place.
A practical way to decide how many templates a firm needs
- 01Group procedures by what they're actually documentingA reconciliation-type procedure (bank, debtors, creditors) documents differently from a search-type procedure (related parties, litigation) which documents differently from a cut-off-type procedure. Group by this, not by financial statement line item.
- 02Draft one template per group, not per line itemBank and cash reconciliations can usually share a structure. Revenue cut-off and purchase cut-off can usually share a structure. Related-party testing almost always needs its own.
- 03Test each draft against a real completed fileTake last year's actual working paper for that procedure and check whether every section it genuinely needed has a home in the new template. If something had to be crammed into 'Other', the template is still too generic.
- 04Resist the urge to add a section for a one-offA section that only one unusual client ever needs shouldn't bloat the template everyone else uses. Handle genuine one-offs as an added note within an existing section, not a permanent new section in the firm-wide template.
Common practice, not a requirement
Most mid-size firms land somewhere between six and twelve distinct templates once this is done properly — roughly one per major audit area, occasionally split further for an area like related parties that genuinely documents differently from everything around it. That's a maintenance burden worth carrying; it's a fraction of the cost of twelve procedures all limping along on one shared, too-generic structure.
Don't swing to the opposite extreme either. A template per client, or a template that changes every time a partner has a preference, defeats the entire point — a reviewer moving across engagements needs the SAME procedure to look the same everywhere. The right granularity is per procedure, firm-wide, not per client and not per engagement.
Why this still has to sit at the firm level
Even with templates split sensibly by procedure, the decision of how many templates exist and what each one contains should be made once, by whoever owns documentation quality for the firm — not re-derived by each engagement team deciding for itself whether this client's related-party testing is unusual enough to need a different structure than last year's. The split is about matching structure to the nature of the work, not about giving individual teams discretion over the shape of their files.
How we think about this
Lekhya lets a firm admin define a separate named template for each procedure, so a bank reconciliation and a related-party test can have entirely different section structures while each stays identical across every engagement and every client it's used on.
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 documentationCustom working paper templates: standardising a firm's own format, not inventing a new oneA reviewer should be able to open any engagement's working papers and know where to look. That only happens if the format was decided once, not reinvented per file.
- Audit documentationAuditing the deferred tax reconciliation — the working paper mechanicsA deferred tax working paper is only as reliable as the asset-by-asset tax base comparison underneath it — the effective rate reconciliation at the top is just the output of that comparison.
- 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.
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.