Audit Strategy, Planning and Programme
Weightage: Chapter 2 of ICAI's Paper 5 syllabus, roughly 10 marks. This is the "design responses and plan" stage of the audit sequence — everything here happens before evidence is actually gathered.
Why planning is itself a Standard, not just good practice
SA 300 requires the auditor to plan the audit so that it is performed in an effective manner. Planning is not preparatory administration bolted onto the real work; it is where the auditor decides what work needs doing, who should do it, and when, based on the risk assessment the auditor has formed — get planning wrong, and everything downstream (which balances get tested, how deeply, with what procedures) inherits the error.
Benefits of planning, as SA 300 frames them: helping the auditor devote appropriate attention to important areas; helping identify and resolve potential problems on a timely basis; helping the audit be organised and managed so it is performed in an effective and efficient manner; assisting in the selection of engagement team members with appropriate capabilities; facilitating direction and supervision of team members; and assisting coordination of work done by auditors of components and experts.
The two-tier structure: strategy above planning
Overall audit strategy sets the scope, timing and direction of the audit, and guides the development of the more detailed audit plan. It involves determining the characteristics of the engagement that define its scope; ascertaining the reporting objectives to plan the timing and nature of communications; considering factors significant in directing the team's efforts; considering results of preliminary engagement activities; and ascertaining the nature, timing and extent of resources necessary.
The audit plan is more detailed than the strategy and includes the nature, timing and extent of planned risk assessment procedures, and of further audit procedures at the assertion level — it converts the strategy's high-level direction into a specific plan of what will actually be done.
The relationship: strategy is set first, at a higher level, and the plan is then developed within that strategy, more detailed and closer to the actual work; but the two are not rigidly sequential and separate in practice — as the audit progresses, the plan (and sometimes the strategy itself) is updated and changed as necessary in response to unexpected events, changes in conditions, or audit evidence obtained from performing procedures, which is itself examined as a point (planning is not a one-time, fixed exercise completed before fieldwork and then abandoned).
Audit programme
An audit programme is a detailed plan of the auditing work to be performed, specifying the procedures to be followed in verification of each item in the financial statements, giving the necessary instructions to the audit staff and acting as a means of controlling the proper execution of the work.
Advantages of a written audit programme: it provides a total perspective of the work to be performed; helps in fixing responsibility for the work done, since work done can be identified with the staff member concerned; is a useful tool for planning the future audit programme; serves as evidence of work done; facilitates supervision and review; and acts as a guide for audits in succeeding years.
Disadvantages/limitations, examined precisely because a written programme can also become a liability if used mechanically: the work may become mechanical, and important, unusual items may be missed because they were not part of the standardised programme; efficient staff may lose initiative, since a fixed programme can discourage a team member from applying independent judgement beyond what the programme literally specifies; a rigid programme may not be suited to every client, since clients differ in size, complexity and internal control quality; and the programme may become outdated if not reviewed and revised regularly to reflect changed circumstances.
The resolution: an audit programme should be treated as a guide, subject to alteration as circumstances require during the course of the audit, and a competent auditor uses it as a structured baseline while remaining alert (professional scepticism, again) to matters the programme itself did not anticipate.
Materiality — the concept that decides how much evidence is enough
Materiality is the concept applied by the auditor both in planning and performing the audit, and in evaluating the effect of identified misstatements on the audit and of uncorrected misstatements, if any, on the financial statements.
Misstatements, including omissions, are considered material if they, individually or in the aggregate, could reasonably be expected to influence the economic decisions of users taken on the basis of the financial statements.
Materiality is assessed in the context of surrounding circumstances, and is affected by the auditor's perception of the financial information needs of users, and by the size and nature of a misstatement. Judgements about materiality are made in light of surrounding circumstances and are affected by the auditor's perception of the financial information needs of users as a group — the auditor is not required to consider the specific needs of any individual user, who may have needs that vary widely.
Performance materiality is set at an amount lower than overall materiality, to reduce to an appropriately low level the probability that the aggregate of uncorrected and undetected misstatements exceeds materiality for the financial statements as a whole. This is examined precisely because candidates conflate materiality and performance materiality: materiality is the threshold for the financial statements as a whole (or for particular classes of transactions, balances or disclosures); performance materiality is a lower, working figure applied to individual items or samples during the audit, deliberately set lower so that the sum of many small, individually immaterial errors does not silently accumulate into a materially misstated whole without being caught.
Revision of materiality — materiality determined at the planning stage may need to be revised as the audit progresses, if the auditor becomes aware of information during the audit that would have caused a different determination initially (for instance, actual financial results differing significantly from what was expected at planning).
Documentation of planning
SA 300 requires the auditor to document: the overall audit strategy; the audit plan; and any significant changes made during the audit engagement to either, and the reasons for such changes — this documentation requirement connects directly to the completion and review chapter's broader theme that everything the auditor does, and every significant change of approach, must be recorded, not merely performed.
