Advanced audit work turns commercial facts into evidence-based judgements about risk, accounting, ethics and reporting. This guide develops those skills through twenty original written tasks and sixty technical concepts, covering acceptance, planning, complex evidence, groups, completion and other assurance. Model answers demonstrate reasoned conclusions; rubrics identify assessable decisions. Numerical exercises state their assumptions, and examples distinguish accounting errors from missing evidence. The material addresses the International route and the September 2026–June 2027 study period. Current official syllabus coverage has not been verified, and the domain allocations are editorial rather than published examination weights. Suggested task times are practice aids, not examination logistics.
What this guide covers
Practise advanced audit judgement with 20 written tasks, model answers and 60 technical study concepts.
Regulatory environment and professional ethics
1. Reasonable assurance and responsibility allocation
Management prepares financial statements and maintains relevant internal control; those charged with governance oversee financial reporting. The auditor obtains reasonable assurance about whether the statements as a whole contain material misstatement and expresses an independent opinion. Reasonable assurance is high rather than absolute because evidence is often persuasive, estimates involve judgement, and fraud can involve collusion or override. These limitations do not excuse weak procedures. Apply the distinction when evaluating engagement terms, misleading public statements or requests that the auditor take responsibility for accounting decisions.
Worked example: A board asks its auditor to certify that no fraud occurred. The auditor explains that management retains prevention responsibilities and replaces the proposed wording with an explanation of reasonable assurance over material financial statement misstatement.
Common mistake: Assuming an unmodified opinion guarantees every transaction is correct confuses a financial statement opinion with exhaustive verification.
2. The ethical conceptual framework
Apply the ethical framework by identifying threats to fundamental principles, evaluating their significance and addressing threats that are not at an acceptable level. Common categories are self-interest, self-review, advocacy, familiarity and intimidation. Consider how a reasonable and informed third party would assess the circumstances, including combined threats. Responses may eliminate the circumstance, apply effective safeguards or require declining or ending the activity. Some prohibitions cannot be overcome through safeguards. The analysis should connect a specific relationship or incentive to a threatened principle and a workable response.
Worked example: An audit manager's close friendship with the client's controller creates familiarity concerns over disputed estimates. The partner evaluates the relationship, reallocates the sensitive work and arranges independent review, rather than recording only a generic annual independence confirmation.
Common mistake: Naming several threat categories without explaining their causal link to the facts does not demonstrate an ethical assessment.
3. Independence of mind and appearance
Independence of mind supports judgement free from compromising influences; independence in appearance protects the credibility of that judgement to an informed observer. Financial interests and close relationships can affect either dimension even when an auditor believes they remain objective. Evaluate whose interest is involved, the person's engagement role and the applicable independence provisions. Where a prohibited interest exists, a review cannot simply legitimise it. Removal of the interest or affected person, and assessment of any breach and previous work, may be necessary before the engagement can continue.
Worked example: Before fieldwork, an audit team member discovers a direct shareholding in the client inherited recently. The firm assesses the applicable restriction, arranges prompt disposal or removal from the team and evaluates any work already performed.
Common mistake: Personal confidence in being unbiased does not resolve an independence restriction or the reasonable concerns of an informed observer.
4. Management responsibility and self-review services
A firm must not assume management responsibility for an audit client. Choosing policies, authorising transactions or determining key assumptions differs from explaining alternatives or giving technical advice. Management needs sufficient competence to understand the service, make decisions and accept responsibility for results. Even when management genuinely retains responsibility, the firm must evaluate whether auditing its own service creates a prohibited or unacceptable self-review threat. Public interest entity restrictions can be stricter. Separate teams may address some threats, but cannot cure an expressly prohibited service or the actual transfer of management decisions.
Worked example: A client asks the firm to determine its expected credit loss assumptions. The firm can explain modelling approaches where permitted, but management must select and approve assumptions; any subsequent audit still requires an independent assessment of service restrictions.
Common mistake: Obtaining management's signature after the firm makes every substantive decision does not turn management responsibility into permissible advice.
5. Fee incentives, dependence and overdue balances
Audit remuneration can create self-interest and intimidation threats when retaining a client or achieving a financial outcome influences judgement. A contingent audit fee is prohibited; an ordinary fixed fee still requires evaluation of fee dependence and commercial pressure. Significant overdue fees may resemble financing and affect continuance considerations. A low fee is not automatically unethical, but the firm must still provide competent personnel and sufficient work. Apply relevant ethical requirements to the client's circumstances without inventing universal percentage thresholds. Evaluate total relationships, duration, governance communication and any required external review.
Worked example: A major client offers a bonus if audited earnings support refinancing. The firm rejects the contingent element and negotiates a non-contingent fee, while separately assessing whether the client's importance to the office threatens independent judgement.
Common mistake: Treating a fixed fee as automatically safe overlooks dependence, collection pressure and the resources required to perform a proper audit.
6. Conflicts of interest and confidential information
A conflict arises when duties or interests compete, such as advising rival bidders while holding confidential information from both. Identify affected parties, assess objectivity and confidentiality threats, and determine whether disclosure and informed consent are appropriate and legally permitted. Information barriers, separate teams and restricted access may help, but some conflicts cannot be managed acceptably. Confidentiality continues after the relationship ends and does not permit using client knowledge for personal advantage. Conversely, confidentiality may yield to a legal or professional disclosure duty; the authority and permitted extent require careful assessment.
Worked example: Two clients request acquisition advice on the same target. The firm identifies the conflict before accepting the second assignment, assesses whether effective information barriers and informed consent are possible, and declines if confidential interests cannot be protected.
Common mistake: Assuming separate engagement teams automatically solve every conflict ignores informed consent, information leakage and circumstances where conflicting duties remain irreconcilable.
7. Non-compliance and lawful external reporting
Suspected non-compliance requires understanding the matter, its financial statement consequences and the applicable ethical and legal response. Obtain evidence without prematurely declaring guilt, discuss with an appropriate management or governance level where lawful, and consider legal advice. Reporting outside the entity depends on the relevant framework and jurisdiction; confidentiality is neither an automatic prohibition nor unlimited permission. Money laundering rules can impose designated reporting routes and tipping-off restrictions. Keep the external reporting decision distinct from audit work on provisions, disclosures, management integrity, evidence reliability and the audit opinion.
Worked example: Invoices suggest that consultancy payments conceal improper commissions. Under supplied local rules, the team reports through its designated officer, preserves records and investigates accounting consequences, while avoiding communications that could breach an applicable tipping-off prohibition.
Common mistake: Assuming every suspicion requires identical external disclosure in every country replaces jurisdiction-specific duties with an unsupported universal rule.
8. Association with misleading other information
The auditor's financial statement opinion does not ordinarily provide assurance over all narrative content in an annual report. Nevertheless, the auditor reads other information within the applicable reporting framework and considers material inconsistencies with the financial statements or audit knowledge. An apparent inconsistency requires discussion and investigation to determine whether the statements, other information or understanding is wrong. Request correction where necessary and communicate unresolved matters to governance. Reporting or further action depends on the circumstances. A disclaimer that narrative content is unaudited does not justify knowingly allowing a misleading association.
Worked example: An annual report claims that all borrowing is fixed-rate, while audited loan notes show substantial floating-rate debt. The auditor investigates the discrepancy, requests correction of the narrative and considers the required other-information reporting if management refuses.
Common mistake: Believing unaudited narrative is outside every auditor responsibility overlooks the duty to address material inconsistencies and misleading association.
Quality management and engagement acceptance
9. ISQM 1's quality risk process
A system of quality management establishes quality objectives, identifies and assesses risks to achieving them, and designs responses proportionate to the firm's circumstances. Relevant components include governance and leadership, ethics, acceptance and continuance, engagement performance, resources, information and communication, and monitoring and remediation. The system is iterative: changes in clients, technology or staffing can create new quality risks. A policy manual is only one response, not proof of an effective system. Evaluate whether responsibilities, resources and actual behaviour support consistent engagement quality across the firm's activities.
Worked example: A firm expands into complex financial instrument audits. It identifies insufficient valuation expertise as a quality risk, introduces acceptance criteria and specialist access, and later checks whether engagement teams actually obtain that expertise when required.
Common mistake: Equating a comprehensive policy manual with effective quality management ignores whether risks are identified and responses operate in practice.
10. Leadership incentives and audit quality
Leadership shapes quality through decisions about promotion, remuneration, budgets, consultation and accountability. If commercial targets reward early signing while penalising necessary specialist work, staff may rationally bypass quality procedures. Evaluate both stated values and observable incentives. Appropriate responses can include balanced performance measures, realistic budgets, protected consultation routes and consequences for ignoring significant issues. Commercial efficiency remains relevant, but it cannot justify insufficient evidence or unresolved judgements. Apply this mechanism when recurring engagement failures persist despite training and formally adequate policies.
Worked example: An office repeatedly clears estimates without consultation because consultation hours reduce partner bonuses. Management changes the reward measures, funds technical support and reviews later files to establish whether significant estimates now receive appropriate challenge.
Common mistake: Responding to incentive-driven failures only with more technical training leaves the organisational pressure that caused the failures intact.
11. Acceptance and continuance screening
Acceptance and continuance assess whether the firm can perform a quality engagement while complying with ethical and professional requirements. Evaluate management integrity, the reason for appointment, independence, competence, resources, reporting deadlines and the ability to obtain evidence. A profitable engagement may still be unacceptable. Existing clients require reassessment when ownership, activities, management behaviour or evidence access changes. Engagement risk includes commercial and reputational exposure, but is not identical to audit risk. Record the evidence, unresolved conditions and decision rationale rather than relying on the client's reputation or a partner's familiarity.
Worked example: A longstanding client acquires an overseas derivatives trader shortly before year end. Continuance requires fresh consideration of specialist capacity, component access and management integrity; the prior year's acceptance decision cannot establish suitability for the changed engagement.
Common mistake: Treating continuance as automatic because last year's audit was satisfactory ignores new risks, resource demands and restrictions on evidence.
12. Audit preconditions and engagement terms
Audit preconditions include an acceptable financial reporting framework and management's acknowledgement of its responsibilities for preparation, relevant internal control and access to information and people. Written engagement terms clarify scope, responsibilities and the expected report form. They do not permit contracting out of auditing standards. A management-imposed restriction expected to require a disclaimer ordinarily prevents acceptance unless law or regulation requires it. Distinguish a practical access arrangement, such as secure inspection of confidential records, from a substantive denial of evidence needed to audit a material balance.
Worked example: A technology company offers access to patents only through a secure room. That arrangement may be workable. A complete ban on inspecting the documents supporting a material intangible asset instead threatens audit evidence and acceptance.
Common mistake: Assuming a signed engagement letter validates any scope restriction confuses contractual agreement with the professional preconditions for an audit.
13. Predecessor communication and appointment integrity
Communication with a predecessor helps an incoming auditor assess appointment circumstances and information relevant to acceptance. Seek the prospective client's authority and comply with confidentiality and applicable professional requirements. A refusal requires investigation of the reasons and consideration of its implications for integrity and acceptance; it is not proof of wrongdoing. A predecessor's limited response is also not positive assurance that no concerns exist. Distinguish acceptance enquiries from later opening-balance audit procedures: permission to communicate and a cordial handover do not establish sufficient evidence over opening balances.
Worked example: A prospective client says it changed auditors solely for lower fees but refuses predecessor contact. The incoming firm seeks an explanation and lawful corroboration, recognising that the refusal weakens the information available for its acceptance decision.
Common mistake: Treating predecessor silence as a clean reference overlooks confidentiality constraints, incomplete enquiries and the incoming auditor's separate evidence responsibilities.
14. Direction, supervision and review
Direction explains objectives, risks, responsibilities and expected procedures. Supervision monitors progress, resolves problems and evaluates whether staff have suitable competence and time. Review assesses whether work supports conclusions and whether significant matters remain unresolved. The nature and extent should respond to experience and engagement complexity. A review signature without substantive consideration is ineffective. The engagement partner remains responsible for managing and achieving engagement quality, including sufficient involvement at appropriate stages. Escalate difficult judgements early enough for consultation and further work rather than using the report deadline as a reason to accept incomplete evidence.
Worked example: A junior tests lease payments without assessing omitted contracts. The senior redirects the work toward completeness, explains the search objective and reviews the added procedures, rather than merely signing the original payment-testing schedule.
Common mistake: Assuming review means checking arithmetic alone misses whether procedures address the relevant risks and support the overall conclusion.
15. Consultation and engagement quality review
Consultation obtains appropriate expertise on difficult or contentious matters and requires implementation of agreed conclusions. An engagement quality review provides an objective evaluation of significant judgements and conclusions on engagements requiring it; it is not a second audit or a transfer of partner responsibility. Reviewer eligibility and objectivity matter. Differences of opinion must be resolved through firm procedures, and the report cannot be dated before the required review is complete. Apply these distinctions when a team treats consultation as optional advice or proposes finishing the quality review after signing.
Worked example: The quality reviewer challenges a major revenue judgement one day before signing. The team consults its technical function, performs additional contract work and resolves the issue before completing the review and dating the auditor's report.
Common mistake: Treating the reviewer as the final owner of the audit conclusion wrongly transfers the engagement partner's responsibility for quality.
16. Root-cause analysis and remediation testing
Monitoring identifies deficiencies in the design, implementation or operation of quality responses. Root-cause analysis asks why deficiencies occurred, distinguishing symptoms from causes such as poor incentives, inadequate expertise or ineffective review timing. Design remediation that addresses those causes, assign responsibility and evaluate whether it operates effectively. A training session may be suitable for a knowledge gap but ineffective for chronic understaffing. Findings on an issued engagement also require consideration of whether additional action is necessary for that engagement. Closure of a remedial action is not the same as evidence of restored quality.
Worked example: Several files contain unsupported fair values. Interviews reveal that specialists were unavailable during peak season. The firm secures earlier specialist capacity and tests subsequent files for timely, substantive involvement rather than recording training attendance as the solution.
Common mistake: Closing an action because a new policy was issued confuses completion of an intervention with evidence that the deficiency stopped.
Business risk, audit risk and engagement planning
17. From business risk to assertion-level misstatement
Business risk threatens an entity's objectives; audit planning focuses on how circumstances could materially misstate financial statements. Translate the commercial fact into a recognition, measurement, presentation or disclosure consequence, identify the affected assertion and explain the mechanism. A new competitor might reduce inventory selling prices, creating valuation risk, while financing pressure may increase management bias. Not every business difficulty produces a material misstatement. Prioritise risks using magnitude, likelihood, complexity and susceptibility to fraud, rather than repeating a list of commercial problems without showing their accounting effects.
Worked example: A retailer faces cheaper competing products. The audit implication is potential inventory overstatement where expected selling proceeds less selling costs fall below cost. The team targets slow-moving lines and post-year-end selling prices rather than describing competition alone.
Common mistake: Listing declining demand as an audit risk without identifying the possible misstatement and assertion leaves the risk analysis incomplete.
18. Audit risk, inherent risk and control risk
Audit risk is the risk of expressing an inappropriate opinion when financial statements are materially misstated. Risks of material misstatement reflect inherent risk and control risk; detection risk concerns procedures failing to identify existing misstatement. Inherent risk is assessed before considering controls and is influenced by complexity, subjectivity, uncertainty, change and susceptibility to bias. Strong controls do not make an inherently complex estimate simple. Higher assessed misstatement risk generally requires more persuasive evidence. The model guides the nature, timing and extent of work rather than providing a mechanically measurable probability for every engagement.
Worked example: A highly subjective unquoted investment has high inherent valuation risk. Even if approval controls operate well, the auditor still evaluates the model and assumptions and obtains persuasive market evidence, instead of treating control effectiveness as proof of value.
Common mistake: Reducing inherent risk because a control appears strong mixes separate assessments and can understate the evidence needed for complex balances.
19. Choosing and revising overall materiality
Materiality reflects whether misstatements could reasonably influence users' decisions, considering size, nature and circumstances. Select a benchmark that reflects the entity and users, such as sustainable profit, revenue or assets, and justify any normalisation. A percentage is a judgement aid rather than a universal standard requirement. Reassess materiality when actual results or new information differ materially from planning assumptions. Lower materiality can require expanded procedures and reconsideration of previously identified errors. Avoid selecting a benchmark merely because it produces the largest amount and therefore reduces work.
Worked example: A hypothetical policy uses 5% of sustainable profit. Reported profit of $600,000 includes an evidenced exceptional expense of $400,000. Using supported normalised profit of $1 million produces $50,000 materiality, subject to qualitative considerations and later reassessment.
Common mistake: Applying the same percentage to every client without evaluating the benchmark mistakes a planning convention for a mandatory rule.
20. Performance and specific materiality
Performance materiality is set below overall materiality to reduce the probability that aggregate uncorrected and undetected misstatements exceed overall materiality. Its level reflects factors such as expected errors, control deficiencies and past audit findings; it is not simply an automatic discount. Some transaction classes, balances or disclosures may require lower specific materiality because smaller misstatements could influence users. The clearly trivial threshold serves a separate accumulation purpose and is not synonymous with immaterial. Apply these distinctions when designing procedures and assessing sensitive disclosures such as directors' transactions.
Worked example: Overall materiality is $200,000. Under a stated hypothetical planning decision, elevated aggregation risk leads to performance materiality of $120,000. A much smaller undisclosed director transaction is assessed separately because its nature may matter to users.
Common mistake: Treating performance materiality as the maximum acceptable final misstatement confuses a procedure-design amount with the overall evaluation of financial statements.
21. Controls reliance and substantive strategy
Understanding control design and determining implementation differ from testing operating effectiveness. Reliance requires evidence that relevant controls operated effectively over the period of reliance. Tests should address who performed the control, its precision, frequency, evidence and handling of exceptions. Substantive procedures remain necessary for material classes, balances and disclosures, while some highly automated processing risks cannot be addressed substantively alone. A failed control test requires reassessing the strategy and considering additional work. Choose controls for the assertions they address rather than because they are convenient to inspect.
Worked example: A monthly margin review is signed by the finance director. Before relying on it, the auditor assesses whether its thresholds could detect material errors and tests evidence of investigation; a signature alone does not demonstrate effective operation.
Common mistake: Using a walkthrough as proof of year-long operating effectiveness confuses understanding one process instance with testing consistent control performance.
22. Management override and journal selection
Management can override otherwise effective controls through journals, biased estimates and unusual transactions. Audit responses include testing journal entries and other adjustments, reviewing estimates for bias and evaluating the business rationale of significant unusual transactions. Journal selection should reflect assessed risks, access rights, unusual timing, accounts and preparers; it is not limited automatically to year-end or large entries. Validate the population before applying filters. A retrospective estimate review identifies possible bias without treating every difference from a later outcome as evidence that the original estimate was unreasonable.
Worked example: A covenant-sensitive client posts late revenue journals through a senior executive's account. The auditor validates the journal extract, inspects underlying contracts and authorisations, and examines related reversals, rather than selecting entries solely by monetary size.
Common mistake: Restricting override testing to large year-end journals can miss smaller coordinated entries and adjustments posted through other reporting mechanisms.
23. Using internal audit work
Before using internal audit work, evaluate organisational status and objectivity, competence, and whether the function applies a systematic and disciplined approach including quality control. Determine the nature and extent of usable work in light of risk and judgement. The external auditor must perform sufficient procedures on the work used, potentially including reperformance, and retain significant audit judgements. A technically capable function may still lack objectivity when reviewing its own designs. Distinguish using completed internal audit work from direct assistance, which has separate requirements and may be restricted by jurisdiction.
Worked example: Internal audit tested routine purchasing controls under an audit committee mandate. The external auditor evaluates its methods and samples, reperforms selected tests and uses suitable work, while independently addressing a highly judgemental acquisition valuation.
Common mistake: Assuming professional qualifications establish usable internal audit work overlooks organisational objectivity, methodology and the external auditor's necessary evaluation procedures.
24. Auditor's experts and responsibility for conclusions
An auditor's expert contributes expertise outside accounting or auditing, such as actuarial or mineral valuation knowledge. Evaluate competence, capabilities and objectivity; understand the expert's field sufficiently to determine appropriate scope. Agree objectives, roles, communication and confidentiality, then evaluate findings, significant assumptions, methods and relevant source data. A management expert is a different evidence source and requires its own evaluation. An expert report is not automatically sufficient evidence, particularly where scope exclusions undermine the audit purpose. The auditor remains responsible for the opinion and for integrating expert findings with other evidence.
Worked example: For a pension liability, the auditor engages an actuary to assess demographic and discount assumptions. The team also tests employee data and reconciles the liability, ensuring the expert's conclusions address the actual financial statement measurement.
Common mistake: Accepting an expert's impressive credentials without evaluating scope and findings overlooks whether the work answers the relevant audit question.
Audit evidence and complex financial reporting matters
25. Evidence reliability in automated and outsourced systems
Evidence appropriateness concerns relevance and reliability; sufficiency concerns quantity. Reliability depends on source, nature and circumstances, including controls over internally generated data. For automated or outsourced processing, assess relevant IT controls, interfaces, access and data completeness. A service auditor's type 1 report addresses design at a date, whereas a type 2 report also addresses operating effectiveness over a period. Evaluate scope, exceptions, period coverage and complementary user controls. Neither report replaces the user auditor's responsibility to obtain evidence over the client's assertions. More weak evidence does not necessarily overcome a fundamental reliability problem.
Worked example: Payroll is outsourced, but the service report assumes that the client authorises employee changes. The auditor tests that user control and report coverage, then reconciles payroll totals; outsourcing alone does not establish payroll accuracy or completeness.
Common mistake: Treating a service organisation report as blanket assurance ignores its scope, time period, exceptions and controls expected at the client.
26. IFRS 15 performance obligations and control
Revenue accounting identifies the contract, distinct performance obligations, transaction price, allocation and when control transfers. Recognise revenue over time only when an applicable criterion is met; otherwise recognise at a point in time. Advance receipts may create contract liabilities rather than immediate income. Variable consideration requires assessment of estimation and the constraint on significant reversal. Contract assets differ from unconditional receivables. Audit work should inspect enforceable terms and actual performance, not rely on invoices or management labels. Returns, consignment and bill-and-hold arrangements require specific attention to whether control has genuinely transferred.
Worked example: A customer pays $120,000 for twelve months of continuous hosting beginning in October. Assuming an even service pattern and no other obligations, three months' revenue is $30,000 at December year end, with $90,000 remaining as a contract liability.
Common mistake: Equating billing or cash collection with earned revenue ignores the performance obligations and timing of control transfer.
27. IFRS 16 lease completeness and measurement
A lease conveys control over the use of an identified asset for a period in exchange for consideration. Assess both economic benefits and the right to direct use; a supplier's substantive substitution right can affect identification. Lessees generally recognise a right-of-use asset and lease liability, subject to applicable exemptions. Measure the liability using relevant lease payments discounted at the appropriate rate; determine the lease term using enforceability and option assessments. Search expense accounts and contracts for omitted leases. Audit modifications, incentives and reassessment triggers rather than assuming the original payment schedule remains appropriate indefinitely.
Worked example: Four annual year-end payments of $50,000 discounted at an assumed 10% produce a liability of approximately $158,493. The auditor also checks commencement, incentives and initial costs before concluding that the right-of-use asset equals that liability.
Common mistake: Multiplying annual rent by the lease term without discounting or assessing contractual terms misstates the lease liability measurement.
28. IFRS 9 expected credit losses
Expected credit losses are probability-weighted cash shortfalls reflecting reasonable, supportable forward-looking information and the time value of money. Under the general approach, significant increases in credit risk can move measurement from twelve-month to lifetime losses; twelve-month losses concern lifetime shortfalls from defaults possible within twelve months, not merely next year's missed cash. Qualifying trade receivables use a simplified lifetime approach. Audit segmentation, historical loss data, forward-looking adjustments and recoveries. A provision matrix is a technique rather than proof that economic changes have been captured. Inspect post-year-end receipts without ignoring conditions at the reporting date.
Worked example: A simplified matrix applies an assumed 8% lifetime loss rate to $500,000 of a relevant overdue category, producing $40,000. The auditor challenges whether a recent customer-sector downturn requires an additional supported adjustment to that historical rate.
Common mistake: Treating twelve-month expected credit losses as cash payments missed only during the next twelve months misunderstands the measurement horizon.
29. IAS 37 provisions and restructuring obligations
Recognise a provision when a past event creates a present legal or constructive obligation, an outflow is probable and a reliable estimate can be made. Measurement reflects the best estimate, using expected values for large populations where appropriate and discounting when material. A board intention alone does not necessarily create a restructuring obligation; a sufficiently detailed plan and valid expectation are important. Future operating losses are not provisions. Distinguish provisions from contingent liabilities and assess disclosure. Audit correspondence, plans, communications, legal evidence and subsequent settlements rather than accepting a reserve based on management preference.
Worked example: A board privately approves a factory closure but has neither announced the detailed plan nor begun implementation by year end. The auditor challenges an immediate restructuring provision, while separately considering impairment and any existing contractual obligations.
Common mistake: Recognising every expected future cost as a provision ignores the need for a present obligation arising from a past event.
30. IAS 36 impairment and estimation uncertainty
An asset or cash-generating unit is impaired when carrying amount exceeds recoverable amount, the higher of value in use and fair value less costs of disposal. Value in use reflects the asset in its current condition and requires consistent cash flows and discounting. Allocate a CGU impairment first to goodwill, then other assets subject to applicable floors. Goodwill impairment is not reversed. Auditing estimates requires evaluating methods, assumptions, data and estimation uncertainty, including contradictory evidence and management bias. Sensitivities help identify how plausible assumption changes affect headroom and disclosure needs.
Worked example: A CGU carries $9 million, with value in use of $7.8 million and fair value less costs of disposal of $8.2 million. Recoverable amount is $8.2 million, so impairment is $800,000, initially allocated against available goodwill.
Common mistake: Using the lower of the two recoverable amount measures overstates impairment and reverses the required comparison.
31. Related parties and transaction substance
Related-party relationships can affect transaction terms, disclosure and susceptibility to concealment or management override. Identification goes beyond management's list: inspect governance minutes, ownership information, unusual contracts, confirmations and transactions outside normal business. Evaluate the substance and business rationale, authorisation and applicable accounting and disclosure. A related-party transaction is not automatically improper, and an apparently market-priced transaction can still require disclosure. Claims that terms are equivalent to arm's-length terms need substantiation. Management representations support, but do not replace, evidence about completeness of relationships and transactions.
Worked example: A customer with a large year-end balance shares an address with a director's private company. The auditor investigates ownership and control, confirms the balance and examines the contract, considering both recoverability and related-party disclosure rather than assuming fraud.
Common mistake: Concluding that market pricing removes disclosure requirements confuses transaction measurement with the separate reporting significance of the relationship.
32. Acquisition accounting and deferred tax effects
Business combination accounting identifies the acquirer and acquisition date, measures consideration and recognises identifiable assets and liabilities under the applicable requirements. Goodwill reflects consideration, non-controlling interests and any previously held interest less identifiable net assets. Fair value uplifts can create temporary differences where tax bases do not change, affecting deferred tax and goodwill. Use enacted or substantively enacted rates appropriate to expected reversal under IAS 12, with relevant exceptions considered. Deferred tax assets also require recoverability assessment. Audit contracts, control evidence, valuations, tax bases and consideration terms rather than treating the purchase price as the value of acquired net assets.
Worked example: An acquired building receives a $1 million fair value uplift with no tax-base change. Assuming a relevant 25% tax rate and no exception, a $250,000 deferred tax liability reduces identifiable net assets and increases goodwill by $250,000.
Common mistake: Ignoring deferred tax on an acquisition fair value uplift can overstate acquired net assets and understate goodwill.
Group audits
33. Risk-based group scoping
Group audit planning identifies where risks of material misstatement arise across entities, business units, shared services and the consolidation process. Components are determined for planning and performing the audit, rather than automatically equated with legal subsidiaries. Size informs scope but does not override unusual transactions, complex estimates or centralised risks. Determine the work needed to obtain evidence over the group statements and which team will perform it. Avoid relying on a fixed revenue-coverage percentage as a substitute for risk assessment. Reassess scope when new risks or consolidation problems emerge.
Worked example: A small subsidiary holds the group's only complex derivative portfolio. Although it contributes little revenue, the group team plans specialist valuation work there while addressing routine sales processing through the shared service centre that records several subsidiaries' transactions.
Common mistake: Scoping only the largest subsidiaries can omit small components containing the group's most complex or fraud-sensitive balances.
34. Component performance materiality and aggregation risk
Aggregation risk is the probability that combined uncorrected and undetected misstatements exceed group materiality. When work is performed on disaggregated component information, component performance materiality addresses that risk and is lower than group performance materiality. It is not necessarily a simple proportional allocation of group materiality, and the sum of component amounts need not equal the group amount. Consider the number, distribution and risk characteristics of components and prior errors. Communicate appropriate misstatement reporting requirements and evaluate aggregate findings, including consolidation errors, rather than accepting each component's local materiality unchanged.
Worked example: Several components each report errors below their local statutory thresholds. The group auditor uses group-directed component performance materiality and reporting instructions so these errors are communicated and evaluated together rather than disappearing through separate local judgements.
Common mistake: Assuming individually small component errors cannot matter to the group overlooks their accumulation and possible common direction.
35. Evaluating component auditor capability and ethics
The group auditor evaluates whether component auditors have appropriate competence, capabilities, time, resources and understanding of relevant requirements. Relevant ethical compliance, particularly independence, must also be established. Familiarity with a local reporting framework does not prove competence for group IFRS adjustments or complex estimates. Assess the ability to cooperate, communicate and provide access needed for group involvement. Network membership may inform the assessment but does not remove it. Where deficiencies cannot be addressed through appropriate involvement or other arrangements, the group auditor must reconsider how sufficient appropriate evidence can be obtained.
Worked example: A component auditor knows local tax reporting well but lacks experience with IFRS revenue estimates. The group team evaluates additional training and direct specialist involvement rather than relying on network affiliation as evidence of suitable capability.
Common mistake: Treating a shared firm name as proof of competence and independence bypasses the assessment required for the actual component work.
36. Two-way communication and component review
Group instructions communicate relevant risks, work objectives, materiality, deadlines, ethical requirements and matters to report. Effective communication is two-way: component auditors share local developments, fraud concerns, misstatements and significant judgements promptly. The group auditor determines appropriate direction, supervision and review, including relevant documentation, according to risk and component circumstances. A completion memorandum or local opinion may summarise results but does not automatically provide sufficient evidence. Resolve inconsistencies between component conclusions and group knowledge, and perform or request additional procedures when necessary before concluding on the group audit.
Worked example: A component reports unexpected customer defaults after receiving the original instructions. The group team discusses the development, revises receivable work, reviews the impairment judgement and considers whether similar exposure exists elsewhere in the group.
Common mistake: Sending standard instructions once and collecting signed opinions at the end overlooks changing risks and necessary group involvement.
37. Intercompany elimination and unrealised profit
Consolidated statements present the group as a single economic entity, requiring elimination of intragroup balances, transactions and unrealised profits. Reconcile differences before eliminating rather than netting unexplained amounts. Profit on inventory remaining within the group is removed from consolidated inventory and profit; subsequent external sale reverses the temporary adjustment. Consider associated tax effects and ownership attribution where relevant. Audit both parties' records, shipping terms, exchange differences and cut-off. A balanced consolidation journal can still be wrong if it eliminates an inappropriate amount or misses profit embedded in closing assets.
Worked example: One subsidiary sells goods costing $80,000 to another for $100,000. Half remain unsold externally at year end. The unrealised profit is $20,000 × 50% = $10,000, reducing consolidated inventory and profit, before considering any relevant tax effect.
Common mistake: Eliminating only intercompany sales and purchases leaves unrealised profit in closing inventory when goods have not reached external customers.
38. Foreign operations, goodwill and non-controlling interests
Consolidation must reflect control, ownership interests, consistent policies and the appropriate translation of foreign operations. Under IAS 21, assets and liabilities of a foreign operation generally translate at closing rates, while income and expenses use transaction-date rates or suitable approximations. Resulting translation differences generally enter other comprehensive income. Acquisition goodwill and fair value adjustments of a foreign operation are treated as its assets and liabilities for translation. Non-controlling interests affect attribution and acquisition measurement. Audit functional currency, exchange sources, ownership changes and calculations rather than treating every currency difference as a trading gain or loss.
Worked example: A foreign subsidiary's closing assets are translated using the year-end exchange rate, while its evenly earned revenue uses an appropriate average rate. The auditor reconciles the resulting translation reserve and checks that acquisition goodwill also uses the closing rate.
Common mistake: Translating every foreign operation balance at an annual average rate misstates closing assets, liabilities and the translation reserve.
39. Access restrictions and group evidence deficiencies
Restrictions on component records, personnel or auditor documentation can prevent sufficient appropriate group evidence. Investigate whether the restriction is legal, contractual or management-imposed and consider lawful alternatives such as authorised reviews or other direct procedures. A component's unmodified local opinion does not remove the group evidence requirement. If alternatives fail, assess the possible effects of undetected misstatements: material but non-pervasive effects lead toward qualification, while material and pervasive effects lead toward disclaimer. Communicate promptly with governance and consider acceptance or continuance implications, subject to legal obligations.
Worked example: A dominant subsidiary's records cannot be accessed and alternative work fails. The group auditor evaluates the potentially pervasive effects across assets, revenue and disclosures, rather than assuming the local auditor's clean opinion permits an unmodified group opinion.
Common mistake: Calling an access restriction an accounting misstatement confuses missing evidence with proof that the reported amounts are wrong.
Completion, review and reporting
40. Aggregate and qualitative misstatement evaluation
Accumulate identified misstatements other than those clearly trivial and evaluate uncorrected amounts individually and collectively. Consider their nature, circumstances, direction, prior-period effects and possible undetected errors. Errors that individually fall below materiality may collectively exceed it, while small items can matter because they conceal a covenant breach or affect sensitive disclosures. Ask management to correct misstatements and understand refusals. Reassess materiality using final results and communicate relevant uncorrected items to governance. Performance materiality is not the final opinion threshold, and offsetting errors should not automatically be netted without considering their separate effects.
Worked example: Three uncorrected expenses omitted by $25,000 each aggregate to $75,000 against $70,000 materiality. Even before considering any covenant effect, the combined profit overstatement is material although each individual omission is below overall materiality.
Common mistake: Clearing every error separately because it is below overall materiality ignores accumulation, common direction and qualitative consequences.
41. Adjusting and non-adjusting subsequent events
Subsequent events accounting distinguishes evidence about conditions existing at the reporting date from conditions arising afterward. Adjusting events change recognised amounts; material non-adjusting events may require disclosure of their nature and estimated financial effect. The discovery date alone does not determine classification. Audit procedures through the report date include enquiries, minutes, interim information and relevant later transactions. Facts discovered after the report date require a separate response based on timing and circumstances. The auditor has no general obligation to perform continuing procedures indefinitely, but cannot ignore a subsequently learned fact that may require action.
Worked example: A customer enters insolvency in February after severe financial distress existed in December. The later information may support adjusting the year-end receivable impairment. A fire first occurring in February instead generally indicates a later condition requiring material disclosure.
Common mistake: Classifying every event discovered after year end as non-adjusting overlooks later evidence of conditions already present at the reporting date.
42. Going concern basis and material uncertainty
Evaluate whether the going concern basis is appropriate and whether events or conditions create a material uncertainty requiring disclosure. Test management's assessment, forecast reliability, financing availability, covenant compliance and feasible mitigating plans over the applicable assessment period. An intention to refinance is weaker than evidence of available funding. If the basis is appropriate and a material uncertainty is adequately disclosed, an unmodified opinion includes the required separate going concern uncertainty section. Inadequate disclosure creates a misstatement; an inappropriate going concern basis generally requires an adverse opinion. Evidence limitations require their own reporting analysis.
Worked example: A company needs refinancing to meet a near-term maturity. Negotiations support continued use of the going concern basis, but success remains uncertain. Adequate disclosure supports an unmodified opinion with a separate material uncertainty section, rather than automatic qualification.
Common mistake: Assuming every going concern uncertainty requires qualification fails to distinguish adequate disclosure from an actual financial statement misstatement.
43. Final analytical review and written representations
Completion review considers whether the financial statements remain consistent with the auditor's understanding and whether sufficient appropriate evidence supports the conclusions. Final analytical procedures may expose unexplained trends or contradictions that require further work. Written representations confirm specified responsibilities and matters but do not replace other necessary evidence. Inconsistent representations require investigation; doubts about integrity can affect evidence reliability more widely. Review unresolved points, disclosures, misstatements and significant judgements before report dating. A completed checklist cannot compensate for an unsupported material balance or an explanation contradicted by reliable external information.
Worked example: Management represents that no customer disputes exist, but legal invoices mention a major claim. The auditor investigates the contradiction and assesses revenue, provisions and management integrity, rather than using the signed representation to close the issue.
Common mistake: Treating signed representations as a substitute for missing external evidence over a material matter overstates their reliability and purpose.
44. The opinion modification decision
First distinguish an identified material misstatement from an inability to obtain sufficient appropriate evidence. Then assess pervasiveness: effects may be confined, represent a substantial proportion of statements or be fundamental to users' understanding. Material non-pervasive misstatement leads to qualification; material pervasive misstatement leads to an adverse opinion. Material non-pervasive possible effects from missing evidence lead to qualification; material pervasive possible effects lead to disclaimer. Pervasiveness is not a fixed numerical threshold. Explain the cause and financial effects or possible effects in the appropriate basis section, consistent with the opinion wording.
Worked example: Reliable evidence shows a material but confined inventory overstatement: qualification for misstatement is appropriate. If records for most operations are unavailable and alternatives fail, pervasive possible effects instead point toward disclaimer rather than an adverse opinion.
Common mistake: Using an adverse opinion whenever evidence is missing confuses known misstatement with uncertainty about possible undetected misstatements.
45. Key audit matters and explanatory report sections
Where key audit matters reporting applies, select matters of most significance from those communicated to governance that required significant auditor attention. Explain why each mattered and how it was addressed without giving a separate opinion. An emphasis of matter highlights an appropriately presented or disclosed matter fundamental to understanding the financial statements, subject to applicable conditions. An other matter section concerns matters outside the statements relevant to understanding the audit, responsibilities or report. None substitutes for a modified opinion, required disclosure or a separate material uncertainty related to going concern section.
Worked example: A complex acquisition required extensive valuation work and is appropriately disclosed. It may be a key audit matter where that reporting applies. An omitted material acquisition disclosure instead requires evaluating opinion modification; highlighting the issue cannot repair the omission.
Common mistake: Using emphasis of matter to avoid qualifying a material disclosure error treats explanatory reporting as a substitute for correcting misstatement.
46. Communicating significant control deficiencies
A control deficiency exists when a necessary control is missing or a control cannot prevent, or detect and correct, misstatements on a timely basis. Determine significance through professional judgement, considering likelihood, magnitude, susceptibility and interaction with other deficiencies. Communicate significant deficiencies in writing to those charged with governance on a timely basis and inform appropriate management. Explain the deficiency, possible effects and practical recommendations, while clarifying the audit's purpose and limits. The auditor does not ordinarily express an opinion on overall control effectiveness during a financial statement audit, and management remains responsible for remediation.
Worked example: The same employee can create suppliers, amend bank details and release payments without independent review. The auditor explains the fraud and misstatement exposure, recommends separation and independent change approval, and communicates the significant deficiency to governance.
Common mistake: Reporting only that controls are weak gives governance neither the specific failure mechanism nor a practical basis for corrective action.
Other assurance engagements and related services
47. Reasonable, limited and no assurance
Reasonable assurance reduces engagement risk to an acceptably low level and ordinarily supports a positive-form conclusion. Limited assurance accepts a higher engagement risk, while still obtaining a meaningful level of assurance, and ordinarily uses a conclusion framed around whether anything came to attention. The work differs in nature and extent, not simply report wording. Agreed-upon procedures provide factual findings without assurance; compilation assists preparation without an assurance conclusion. Match the engagement to users' needs, available criteria, evidence and reporting purpose rather than describing every professional service as a smaller audit.
Worked example: A lender seeking an opinion on historical statements needs a different engagement from one requesting specified invoice comparisons. A review provides limited assurance; invoice comparisons under agreed procedures provide findings from which the lender draws its own conclusions.
Common mistake: Calling agreed-upon procedures limited assurance wrongly suggests that the practitioner evaluates the subject matter and expresses an assurance conclusion.
48. Suitable criteria and engagement preconditions
An assurance engagement needs an appropriate underlying subject matter, suitable criteria, intended users, a rational purpose and expected access to sufficient appropriate evidence. Suitable criteria are relevant, complete, reliable, neutral and understandable, and must be available to intended users as appropriate. An attractive metric can still fail if its boundaries or measurement rules are unclear. Distinguish measurement uncertainty, which may be transparently described, from criteria so vague that consistent evaluation is impossible. Agree responsibilities and the assurance level before acceptance; a polished report cannot repair an unsuitable subject matter or missing evaluative basis.
Worked example: A company requests assurance that it is environmentally excellent. The practitioner asks for defined reporting boundaries, measures and criteria. A measurable energy-use statement under specified rules may be suitable, while the original undefined claim is not.
Common mistake: Assuming any management-selected metric is suitable overlooks completeness, neutrality and whether users can understand the evaluation basis.
49. Review engagement enquiry and analytics
A review of historical financial statements provides limited assurance, principally through enquiry and analytical procedures, with additional work when matters suggest material misstatement. Understand the entity and reporting framework sufficiently to design meaningful comparisons and questions. Analytical expectations need plausible relationships and reliable information; unexplained differences cannot be cleared by repeating management's answer. Review procedures are substantially less extensive than audit procedures and do not support an audit opinion. Where the practitioner becomes aware of a possible material misstatement, perform sufficient additional procedures to conclude appropriately rather than asserting that further work is outside every review.
Worked example: During a review, gross margin rises sharply while sales mix is unchanged. The practitioner asks targeted questions, analyses inventory and sales data, and follows up a possible omitted purchase accrual instead of accepting an unsupported efficiency explanation.
Common mistake: Believing a review never requires work beyond enquiry and analytics ignores the response needed when a possible material misstatement emerges.
50. Forecasts, projections and prospective assumptions
A forecast uses best-estimate assumptions about events and actions management expects; a projection uses hypothetical assumptions, or a mixture, to illustrate possible outcomes. Evaluate whether assumptions fit the stated purpose, are internally consistent and are properly disclosed. Test preparation, calculations and consistency with historical information and accounting policies. Evidence supports the reasonableness or proper use of assumptions rather than proving that future results will occur. Report limitations clearly, including that actual results are likely to differ. A board-approved number remains unsupported if operational capacity, financing or contractual evidence contradicts it.
Worked example: A projection assumes a second factory opens next July to illustrate an expansion case, although approval is pending. Clear hypothetical disclosure can suit that purpose; presenting the same production increase as an evidenced best-estimate forecast requires additional support.
Common mistake: Treating approval of a forecast as proof of its achievability confuses management authorisation with evidence supporting future assumptions.
51. Due diligence versus forensic investigation
Financial due diligence supports a transaction decision by examining matters such as sustainable earnings, working capital, debt-like items and cash conversion within an agreed scope. It does not automatically provide an audit opinion or detect every fraud. Forensic work investigates specified suspected wrongdoing, often requiring controlled evidence preservation, provenance records and legal coordination. Objectives determine procedures and report users. Keep established facts, estimates and allegations distinct, and preserve original digital evidence appropriately. A transaction-focused adjustment is not necessarily an accounting error, while a suspicious payment is not proof of criminal conduct.
Worked example: A buyer asks whether reported earnings are sustainable, prompting analysis of one-off revenue and recurring costs. Separately, suspected supplier kickbacks require preservation of payment records and investigation of counterparties, rather than merely adjusting the acquisition earnings multiple.
Common mistake: Treating due diligence as a comprehensive fraud guarantee expands its agreed purpose and obscures the different evidence demands of forensic work.
52. Designing reproducible agreed-upon procedures
Agreed-upon procedures specify actions whose results can be reported objectively as factual findings. Define the population or named items, documents, dates, comparison fields and exception treatment. Avoid vague verbs such as verify or ensure unless the precise action is described. The practitioner does not express an assurance opinion or conclusion; users interpret the findings. Professional judgement remains necessary in acceptance, performance and reporting, but the reported findings should not become an implied overall evaluation. Apply the agreed reporting basis to every exception rather than silently introducing an audit materiality filter.
Worked example: For ten named grant payments, compare invoice amounts and dates with bank entries through 30 June and report each difference. This produces clear factual findings, unlike an instruction to confirm that grant spending was generally appropriate.
Common mistake: Reporting that a population is fairly stated after selected comparisons introduces an assurance conclusion beyond an agreed-upon procedures engagement.
53. Sustainability boundaries and measurement uncertainty
Sustainability assurance requires suitable criteria defining reporting boundaries, metrics, methodologies, estimates and disclosures. Evaluate completeness across included operations and value-chain categories where relevant, reliability of source data and consistency of conversion factors. Measurement uncertainty can be inherent, especially in indirect estimates, but should be transparently addressed rather than concealed through false precision. Assurance level affects the work and conclusion; financial statement materiality cannot simply be copied to non-financial metrics. Identify the applicable engagement framework and reporting period, distinguishing any future-effective requirements rather than assuming one framework applies universally.
Worked example: An emissions statement combines metered electricity with estimated supplier activity. The practitioner tests meter records, evaluates supplier estimation methods and checks the stated boundary, explaining significant uncertainty without treating every estimate as automatically unsuitable for assurance.
Common mistake: Using accurate conversion factors on an incomplete operational boundary can produce a precisely calculated but materially misleading sustainability statement.
Current issues, technology and professional judgement
54. Population validation before data analytics
Audit analytics depend on a complete, accurate and relevant population. Reconcile extracted totals and record counts to controlled source records, investigate exclusions and duplicates, and test field definitions, dates, signs and mappings. Agreeing one total may conceal compensating errors or missing categories. Preserve the extraction logic and transformations so results are reproducible. Full-population analysis can identify patterns across every imported record without proving that every transaction is valid or every assertion is addressed. The audit purpose determines whether the procedure is risk assessment, a control test or substantive evidence.
Worked example: A journal extract agrees by net amount but excludes equal debit and credit batches. Record-count and gross-value reconciliations expose the omission before anomaly testing, demonstrating why agreement of a single net total is insufficient validation.
Common mistake: Assuming software processed the whole ledger because it processed every imported row overlooks extraction omissions and transformation errors.
55. AI false negatives and automation bias
An AI-assisted tool's output depends on training, configuration, input quality and the task for which it is used. False positives flag legitimate items; false negatives miss relevant anomalies. Evaluate fitness for purpose, known limitations, validation evidence and whether changes in client data undermine performance. Generative explanations can be plausible without being factually supported, so trace claims to evidence. Human review should challenge rather than simply approve machine output. Confidentiality and access controls also apply to submitted client data. The auditor retains responsibility for procedures, judgements and conclusions regardless of automation.
Worked example: A model flags familiar round-number journals but misses an unusual linked sequence. The team tests known examples, investigates its selection logic and uses independent risk-based procedures rather than interpreting a low anomaly count as evidence of low fraud risk.
Common mistake: Assuming a confident model explanation establishes factual accuracy replaces corroborated audit evidence with an unvalidated machine-generated assertion.
56. Cyber incidents and financial statement assertions
Cybersecurity matters to a financial statement audit through its effects on transactions, balances, disclosures, controls and evidence. An incident can compromise completeness or accuracy, interrupt operations, create obligations or affect going concern. Establish the timing and extent of compromise, distinguish recovery from data integrity, and reconsider reliance on affected controls. Use specialist expertise where necessary, while obtaining independent corroboration such as customer, bank or dispatch records. Financial statement treatment depends on the facts and reporting-date conditions, not the label cyber incident. The audit does not automatically become an opinion on overall cybersecurity effectiveness.
Worked example: After ransomware restoration, management demonstrates that systems operate again. The auditor separately reconciles pre-incident sales to payment and dispatch evidence, because restored availability does not prove that historical records are complete or unchanged.
Common mistake: Treating a successful backup restoration as proof of historical financial accuracy confuses operational recovery with reliable transaction evidence.
57. Climate effects on existing accounting estimates
Climate-related developments can affect existing financial reporting judgements through asset lives, impairment cash flows, inventory values, provisions and credit losses. Evaluate the link between a specific physical or transition risk and a financial statement assumption rather than assuming every climate issue creates an immediate provision. Compare financial models with approved strategy, capital commitments and public narrative. Inconsistencies may reveal unsupported assumptions or incomplete disclosures. The relevant accounting recognition and measurement requirements still apply. Distinguish an announced ambition from a present obligation and assess uncertainty using evidenced scenarios rather than unsupported predictions.
Worked example: A manufacturer announces closure of a carbon-intensive plant within five years, but its impairment model assumes unchanged production for fifteen years. The auditor reconciles the assumptions, examines approved plans and reassesses useful lives, cash flows and related disclosures.
Common mistake: Assuming a public environmental target automatically creates a provision skips the present-obligation test and the facts supporting recognition.
58. Contradictory evidence and confirmation bias
Professional scepticism requires a questioning mind and critical assessment of evidence, including information that contradicts management or the team's initial expectation. Confirmation bias favours supporting evidence while discounting alternatives. Identify the inconsistency, evaluate each source's reliability and obtain procedures capable of discriminating between explanations. An unexpected result is not automatically fraud, but unresolved contradictions weaken the conclusion. Document why the selected explanation is better supported and what uncertainty remains. Evidence should determine the conclusion; a desired report date or a plausible management narrative should not determine which evidence is accepted.
Worked example: Management explains lower margins as temporary freight costs, but logistics invoices show falling rates. The auditor tests product mix, pricing and purchase cut-off to distinguish alternative causes, rather than collecting more management statements supporting the original explanation.
Common mistake: Seeking only evidence that supports the first plausible explanation creates apparent corroboration while leaving contradictory information unresolved.
59. Sensitivity analysis and scenario consistency
Sensitivity analysis changes assumptions to show how a model's output responds; scenario analysis changes a coherent set of related assumptions. Both help evaluate estimation uncertainty, headroom and the plausibility of management plans, but neither supplies missing evidence for the base case. Use supportable changes and maintain consistency between revenue, costs, working capital, financing and discount assumptions. A break-even analysis can identify the change that eliminates impairment or liquidity headroom. Interpret results alongside external and historical evidence rather than treating a mathematically possible scenario as an equally probable outcome.
Worked example: A cash forecast assumes sales growth but no additional inventory funding. The auditor models a coherent downside with slower receipts and necessary stock purchases, then assesses whether financing remains available, instead of reducing revenue alone and leaving linked cash flows unchanged.
Common mistake: Changing one input while ignoring economically linked assumptions can produce a precise sensitivity result that misrepresents the actual risk.
60. Evidence-led recommendations and version boundaries
A professional recommendation connects an established fact to its significance, the action required and the reason that action resolves the issue. Prioritise by urgency, likely magnitude and dependencies, and distinguish facts, assumptions and unresolved questions. When standards change, establish the applicable framework, effective date and any permitted early adoption before recommending treatment; an issued future requirement does not automatically govern the current period. Explain alternatives where evidence is incomplete and state a conditional conclusion. Commercial awareness makes recommendations workable, but does not justify weakening independence, evidence requirements or accurate reporting.
Worked example: A partner asks whether a newly issued assurance requirement applies immediately. The manager checks its effective-date provisions and the engagement terms, then explains the current treatment and future implementation actions separately, identifying any early-adoption conditions that require confirmation.
Common mistake: Applying a newly announced requirement without checking its effective date can produce confident advice under the wrong reporting framework.