Statutory audit planning has four core components: understanding the entity and its environment well enough to identify where misstatement is likely, setting materiality at the financial statement and performance levels, assessing risk at the assertion level for significant classes of transactions, and briefing the engagement team with a timeline that reflects the entity's actual closing schedule rather than a generic one. Each has to be documented as a judgement made for this year, not carried forward from last year's file unchanged.
Understanding the entity and its environment
This is the step most often done thinly, because for a continuing client the team already knows the business. The requirement is not to relearn the client from scratch every year — it is to update last year's understanding for what actually changed, and to record that the update happened.
- Nature of the entity: operations, ownership and governance structure, the way it is financed, and its accounting policies.
- Industry, regulatory, and other external factors, including the applicable financial reporting framework.
- Objectives, strategies, and the related business risks that could result in material misstatement.
- Measurement and review of the entity's financial performance — what management itself tracks, since that is often where pressure to misstate shows up first.
- The entity's system of internal control, to the extent relevant to the audit approach being planned.
Regulatory requirement
SA 315 requires the auditor to obtain an understanding of the entity and its environment, including its internal control, sufficient to identify and assess the risks of material misstatement. Read the current text of the standard rather than relying on this summary.
| Area | What to check |
|---|---|
| Management and governance | Any change in key management personnel, board composition, or those charged with governance. |
| Business operations | New product lines, new locations, discontinued operations, a significant change in revenue mix. |
| Financing | New borrowings, changed covenants, a change in the lender, related party funding. |
| IT systems | A new or upgraded accounting or ERP system, since this can change where controls actually sit. |
| Regulatory environment | Applicability thresholds crossed — Ind AS, CARO classification, tax regime changes. |
Setting materiality
Materiality is set at two levels that get confused in practice: overall materiality for the financial statements as a whole, and performance materiality, which is set lower to reduce to an appropriately low level the probability that the aggregate of uncorrected and undetected misstatements exceeds overall materiality.
- 01Choose a benchmarkProfit before tax is common for profit-oriented entities, but revenue or total assets may be more appropriate where earnings are volatile or the entity is not profit-driven. The choice should reflect what users of the financial statements actually focus on.
- 02Apply a percentage, with reasoning recordedThe percentage applied is a matter of professional judgement. What matters for the file is that the reasoning for the chosen benchmark and percentage is recorded, not just the resulting figure.
- 03Set performance materiality below itBased on the auditor's assessment of the risk of misstatement and the entity's history of corrected and uncorrected misstatements in prior periods.
- 04Set a threshold for clearly trivial amountsBelow which misstatements need not be accumulated, because they are clearly inconsequential even in aggregate.
- 05Revisit during the auditIf information comes to light during the audit that would have led to a different materiality judgement had it been known at planning, materiality is revised, and the effect on the nature, timing and extent of further procedures is considered.
A materiality figure that is the same percentage of the same benchmark as every prior year, with no fresh reasoning recorded, reads as a number copied forward rather than a judgement made for the current year. Reviewers and inspectors look specifically for the reasoning, not just the figure.
Risk assessment at the planning stage
Planning-stage risk assessment sets the audit approach for the rest of the engagement — it determines where procedures concentrate and which risks get treated as significant. Getting this stage right is what makes the rest of the engagement efficient; getting it wrong means procedures are misallocated and the gaps surface late, when there is no time left to fix them.
- Identify significant classes of transactions, account balances, and disclosures, and the relevant assertions for each.
- Assess risk at the assertion level, not only at the financial statement level — a risk stated as "revenue may be misstated" is not specific enough to drive a procedure.
- Identify significant risks, which by definition require special audit consideration, and document why each was treated as significant.
- Consider the risk of management override of controls on every engagement — this is a presumed significant risk, not one assessed away by a clean control environment.
- Assess fraud risk specifically, including in revenue recognition, and document the discussion the engagement team had on susceptibility to fraud.
- Link each identified risk to the planned response — the procedure that addresses it — so the risk assessment actually drives the audit programme rather than sitting separately from it.
| Input | Typical source |
|---|---|
| Analytical review at planning | Comparing current management figures or provisional numbers against prior year and budget. |
| Prior year misstatements and review points | The summary of misstatements and the outstanding matters list from the previous audit. |
| Entity-level controls | Walkthroughs, discussions with management, and observation of the control environment. |
| External factors | Industry conditions, regulatory changes, and economic conditions affecting the entity's sector. |
| Team discussion | A documented discussion among the engagement team on where the financial statements are susceptible to material misstatement, including fraud. |
Team briefing and timeline
A planning memorandum that never reaches the team doing the fieldwork accomplishes little. The briefing is where the planning decisions — materiality, significant risks, the audit approach for each area — actually transfer to the people executing the programme.
- Walk the team through the significant risks and why each was assessed as significant, not just hand over a list.
- Communicate materiality and performance materiality explicitly — these numbers drive sample sizes and the threshold for what gets investigated, so the team needs them before fieldwork starts, not partway through.
- Assign ownership of each audit area to a named team member, matched to experience where a significant risk is involved.
- Set a timeline anchored to the entity's actual closing schedule and the statutory filing deadline, with interim milestones for fieldwork completion, review, and partner sign-off — not just a single final deadline.
- Build in time for review and query resolution before the deadline, rather than treating the deadline as the date fieldwork finishes.
Common practice, not a requirement
A short written briefing note, even one page, that the whole team can refer back to during fieldwork tends to hold up better than a verbal briefing at the kickoff meeting that half the team wasn't present for.
Checklist: before fieldwork starts
- Engagement letter current for this year and the preconditions for the audit established.
- Understanding of the entity updated for what changed since last year, not carried forward unchanged.
- Overall materiality, performance materiality, and the clearly trivial threshold set and documented with reasoning.
- Significant risks identified, including the presumed risks of management override and fraud in revenue recognition.
- Each identified risk linked to a planned procedure.
- Team discussion on fraud and misstatement susceptibility documented.
- Areas assigned to named team members, matched to the risks involved.
- Timeline set against the entity's actual closing schedule, with milestones for review before the final deadline.
How we think about this
In Lekhya the planning memorandum, materiality, and the risk assessment live as linked records rather than a static document: a risk without a linked procedure is visible as a gap, and a procedure with no risk behind it is visible as unexplained scope. The system does not set materiality or decide what is significant — those stay professional judgements made by the engagement team — but it will not let a plan quietly go unexecuted without that gap being visible to the reviewer.
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 workflow & automationThe statutory audit workflow, from evidence collection to sign-offAn engagement end to end: acceptance through to sign-off, with where the time actually goes and the four points at which engagements reliably stall.
- Audit workflow & automationAudit automation for CA firms: what to automate firstHow to decide what to automate, ranked by return rather than by how impressive it sounds, with a scored ranking of common audit tasks and what to leave alone.
- Audit workflow & automationAudit sampling methods for Indian CA firmsStatistical vs judgmental sampling, when full-population testing removes the need to sample, when sampling still applies, and what drives sample size.
- Audit workflow & automationAI in audit: what it is good at, and what it must not touchThe three tasks language models genuinely do well in audit, the three they must never be given, and the questions to ask a vendor before any client data moves.
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.