Advanced audit work connects commercial facts to financial reporting risks, persuasive evidence and defensible conclusions. This guide develops those skills through twenty original constructed-response tasks and sixty technical lessons covering Irish auditor responsibilities, independence, quality management, planning, complex evidence, group audits, reporting and other engagements. Model answers demonstrate calculations, precise procedures and justified recommendations; rubrics identify assessable performance. Suggested timings are practice aids. The allocation is editorial, rather than official examination weighting. Current official syllabus coverage as of 17 October 2026 has not been verified, and no future version is represented. Apply Irish legal and ethical requirements according to the entity, engagement date and relevant reporting framework.
What this guide covers
Practise advanced audit judgment with 20 original response tasks and 60 concepts for Irish audit scenarios.
Irish regulatory framework and auditor responsibilities
1. Directors' accountability and reasonable assurance
Directors are responsible for financial statements, accounting records and internal control. The external auditor independently obtains sufficient appropriate evidence to support an opinion on those statements. Reasonable assurance is high assurance, but inherent limitations remain because evidence can be persuasive rather than conclusive, estimates involve judgment and fraud may involve collusion. The audit does not transfer directors' responsibilities or guarantee future viability. Apply this distinction when a client asks the auditor to authorise transactions, choose accounting assumptions or certify that no fraud exists.
Worked example: A director asks the auditor to approve a doubtful-debt adjustment before posting it. The auditor explains the reporting requirements and challenges the estimate, while management evaluates the evidence, selects its estimate and authorises the journal.
Common mistake: Assuming that an auditor's discussion of an accounting adjustment makes the auditor responsible for management's decision to record it.
2. IAASA, accountancy bodies and governance oversight
Irish audit oversight operates at several levels. IAASA has statutory oversight and standard-setting responsibilities within its remit, including functions relating to statutory audit quality. Recognised accountancy bodies perform professional and regulatory functions subject to the applicable oversight arrangements. Those charged with governance oversee the entity's financial reporting and its relationship with the auditor. These roles are complementary: governance approval does not replace external regulation, and professional membership does not itself establish every required statutory authorisation. Identify the relevant function before deciding where an issue should be escalated.
Worked example: An audit committee questions a firm's independence assessment. It should challenge the engagement arrangements and obtain explanations, while any regulatory concern follows the appropriate oversight route; the committee cannot grant an exemption from an applicable independence prohibition.
Common mistake: Treating the audit committee, the firm's professional body and IAASA as interchangeable authorities with identical powers over every audit matter.
3. Appointment, removal and resignation are separate processes
Appointment establishes the auditor's authority through the applicable company-law process; an engagement letter records agreed terms but does not replace a valid appointment. Removal and resignation terminate office through different procedures and may involve statements, notices and communications to specified parties. In Ireland, determine the entity type and applicable Companies Act requirements before advising on these steps. Commercial disagreement alone does not establish the correct statutory procedure. Withdrawal also leaves existing duties, evidence concerns and potential reporting obligations to be assessed rather than automatically extinguishing them.
Worked example: A company emails that the audit firm has been replaced after a fee dispute. The partner establishes whether a valid removal and replacement process occurred, clarifies the firm's continuing position and evaluates the required communications before treating the appointment as ended.
Common mistake: Assuming an email ending the commercial relationship necessarily completes statutory removal or releases the auditor from all associated communication duties.
4. Information rights and evidence restrictions
An auditor needs access to relevant records, explanations and personnel to obtain audit evidence. A restriction can arise from management refusal, missing records or external circumstances, and its significance depends on the affected assertions and available alternatives. Request the information specifically, explain its audit purpose and escalate unresolved limitations to appropriate governance. Alternative procedures must answer the same evidence question; extra work elsewhere does not compensate for an unsupported material balance. If evidence remains insufficient, assess materiality and pervasiveness and consider reporting and continuance consequences.
Worked example: Management withholds a supplier dispute file. The auditor explains its relevance to liability completeness, seeks authorised legal correspondence and examines subsequent settlement payments. If those sources do not resolve the exposure, the remaining evidence limitation still requires evaluation.
Common mistake: Believing that a large volume of unrelated evidence can compensate for missing evidence about a particular material assertion.
5. Fraud indicators and professional scepticism
Fraud differs from error through intentional deception, but auditors often encounter indicators before intention can be established. Professional scepticism requires questioning contradictory evidence and evaluating reliability without assuming either universal dishonesty or unquestionable integrity. Management fraud can undermine otherwise strong controls through override and collusion. When indicators emerge, reassess risks, extend procedures, consider who may be involved and evaluate implications for other evidence and representations. The financial statement audit addresses material misstatement; it does not make the auditor a prosecutor or guarantee detection of every fraud.
Worked example: A sales credit note is issued immediately after year end for an unusually large December sale. The auditor examines dispatch, customer acceptance and correspondence, then searches for similar transactions rather than accepting the initial explanation that the credit was routine.
Common mistake: Equating scepticism with accusing management of fraud before evidence establishes intention, or accepting plausible explanations without corroboration.
6. Non-compliance and its financial statement consequences
Suspected non-compliance requires attention to both the underlying conduct and its accounting consequences. Some laws directly affect financial statement amounts; others can create penalties, provisions, disclosure needs or threats to continued operations. Understand the matter, obtain evidence, discuss it with an appropriate management or governance level and consider legal advice. External reporting depends on applicable duties and confidentiality exceptions, not a universal rule to disclose every suspicion publicly. Evaluate whether management involvement affects integrity, other audit evidence, continuance and the auditor's report.
Worked example: A manufacturer receives an environmental enforcement notice. The auditor examines correspondence and legal assessments to evaluate remediation costs, possible penalties and disclosures, while separately determining whether any professional or statutory external reporting duty applies to the circumstances.
Common mistake: Assuming every legal breach automatically modifies the audit opinion, regardless of its accounting effects, disclosure or evidence implications.
7. Money laundering indicators and controlled escalation
Unexplained ownership structures, transactions lacking commercial rationale and unusual payment routing can indicate money laundering risk without proving criminal conduct. Assess the facts through customer due diligence, beneficial ownership understanding and transaction evidence. Escalate suspicions through the firm's designated arrangements and determine applicable Irish external reporting requirements using appropriate specialist advice. Audit investigation and suspicious-transaction reporting have different purposes and evidential considerations. Communications must respect any applicable tipping-off restrictions. An internal report does not necessarily discharge every reporting obligation, and client approval is not required where disclosure is legally mandated.
Worked example: A customer repeatedly routes refunds to unrelated overseas accounts despite paying from a domestic account. The auditor preserves the payment trail, establishes the commercial explanation and escalates the concern confidentially before deciding what can safely be discussed with client personnel.
Common mistake: Waiting for proof of an underlying crime before considering suspicion reporting, or warning implicated individuals before assessing communication restrictions.
8. Confidentiality, privilege and lawful disclosure
Professional confidentiality protects information obtained through the engagement, but disclosure may be permitted or required by law or professional duty. Legal privilege is a distinct legal protection that may attach to particular communications; it should not be assumed to cover every document involving a lawyer. Establish the nature of the information, the proposed recipient and the legal basis before disclosing. Use legal advice where necessary, minimise disclosure to its proper purpose and retain a documented rationale. A broad appeal to public interest alone does not settle a difficult disclosure decision.
Worked example: A regulator requests acquisition correspondence. The auditor identifies the request's authority, separates ordinary commercial documents from potentially privileged advice and obtains advice about the appropriate response, rather than forwarding the entire file or refusing everything automatically.
Common mistake: Treating confidentiality as an absolute prohibition on disclosure or assuming that every communication copied to legal counsel is privileged.
Ethics, independence and engagement acceptance
9. Threat assessment and independence in appearance
Independence requires objective judgment and circumstances that support confidence in that judgment. Assess self-interest, self-review, advocacy, familiarity and intimidation threats using the perspective of an informed, reasonable third party. First identify applicable prohibitions: a forbidden arrangement cannot be retained merely because the team feels unbiased. For permitted arrangements, evaluate threat significance and whether effective actions eliminate or reduce threats to an acceptable level. Document the facts, relevant requirements and conclusion. Independence assessment continues throughout the engagement as personnel, services and relationships change.
Worked example: An audit partner believes a close commercial relationship with a client director has never affected judgment. The ethics assessment nevertheless examines financial dependence, shared interests and how an informed observer would view the relationship before deciding whether the partner can remain.
Common mistake: Using personal confidence in one's objectivity as sufficient evidence that a relationship is acceptable under applicable independence requirements.
10. Financial interests and business relationships
Financial interests create incentives to benefit from an audit client's performance, while business relationships can align commercial fortunes or create dependence. Evaluate whether an interest is direct or indirect, who holds it, the person's engagement role and applicable significance requirements. Different rules may apply to the firm, engagement personnel and close family relationships. Where an interest or relationship is prohibited, remove it or the relevant involvement as the requirements permit; additional review is not a universal cure. Assess prior work and the consequences of any period of non-compliance.
Worked example: A manager discovers that a spouse has acquired shares directly in the audit client. The manager promptly reports the acquisition so the firm can determine required disposal or removal actions and assess work performed while the interest existed.
Common mistake: Assuming a small direct holding is automatically harmless because it would not materially change the holder's personal wealth.
11. Employment negotiations and former audit personnel
Employment discussions with an audit client can create self-interest and familiarity threats before any contract is signed. Affected personnel should disclose negotiations promptly so the firm can alter responsibilities and assess previous judgments. When former audit personnel join a client, consider their new influence over financial reporting, continuing financial ties with the firm and relevant restrictions. The appropriate response depends on role, timing and applicable requirements. Review can address some work-quality concerns, but it does not override restrictions on who may serve in particular positions.
Worked example: A senior auditor interviews for a client's financial controller role while auditing payroll provisions. The firm removes the senior from relevant work, evaluates the negotiation timeline and arranges review of judgments that might have been affected by the prospective employment.
Common mistake: Treating independence concerns as beginning only when an employment offer is accepted, rather than when negotiations create an incentive.
12. Fees, gifts and economic dependence
Fees and benefits can influence judgment through economic dependence, anticipated rewards or pressure to retain a client. Evaluate fee concentration, overdue balances, disputes, contingent arrangements and gifts under the applicable requirements. An overdue fee may create financing-like concerns, but its significance depends on circumstances rather than a universal age threshold. Gifts require attention to value, intention and context; apparently modest hospitality can still be problematic when intended to influence. Separate commercial negotiations from audit judgments and consider whether permitted actions genuinely address the identified threat.
Worked example: A client offers an expensive sporting weekend shortly before a disputed impairment conclusion. The auditor considers the timing and influence risk, declines the benefit and reports the offer internally, rather than assessing acceptability solely against a hospitality budget.
Common mistake: Assuming that a benefit is acceptable merely because it is described as ordinary hospitality or offered to several people.
13. Long association, rotation and fresh challenge
Long association can produce familiarity, excessive trust and reluctance to challenge judgments previously accepted by the same personnel. Assess the individual's role, length and nature of involvement, client relationships and the applicable rotation or cooling-off requirements. Entity status and engagement circumstances matter, so do not apply an invented universal tenure limit. Rotation addresses particular threats but does not eliminate the need to assess other relationships. Where permitted, fresh senior review and changes in responsibilities can strengthen challenge, while mandatory restrictions must be followed rather than replaced by informal safeguards.
Worked example: A partner has audited a family business for many years and now accepts valuation explanations without current corroboration. The firm assesses applicable tenure requirements and considers changes in leadership and independent challenge of significant judgments before deciding on continuance.
Common mistake: Believing that familiarity becomes a concern only after a numerical rotation limit has been reached or formally exceeded.
14. Non-audit services and management responsibility
Non-audit services may create self-review when their output later enters the audited statements, advocacy when the firm promotes the client's position, or management responsibility when the firm makes client decisions. Determine applicable restrictions before evaluating safeguards, particularly where public-interest-entity requirements may apply. Management must retain informed responsibility for decisions, assumptions and acceptance of results. Calling work advisory does not change its substance. A separate team can reduce some threats but cannot make a prohibited service or assumption of management responsibility acceptable.
Worked example: A valuation team may be asked to explain alternative methods, but management asks it to choose the acquisition assumptions and approve the final allocation. The firm separates permissible explanation from decision-making and declines any role it cannot properly undertake.
Common mistake: Assuming that management's signature on a finished calculation proves it exercised informed responsibility for decisions actually made by the firm.
15. Acceptance preconditions and predecessor enquiries
Acceptance requires an acceptable reporting framework and management acknowledgement of responsibility for statements, controls and access to relevant information and people. Assess integrity, independence, competence, time and resources as well as formal terms. With appropriate authority, predecessor communication can reveal disputes, restrictions or other matters relevant to acceptance; the predecessor's confidentiality obligations remain important. A refusal of permission requires explanation and evaluation rather than automatic acceptance. An engagement letter documents a viable relationship but cannot create missing access or remedy a fundamentally unsuitable client.
Worked example: A prospective client offers a profitable audit but refuses access to divisional staff. The firm explains the required preconditions, investigates the restriction and predecessor relationship, and declines the proposed engagement if effective access and integrity concerns remain unresolved.
Common mistake: Treating a signed engagement letter and a favourable credit check as sufficient acceptance evidence when audit access remains restricted.
16. Conflicts of interest and informed engagement terms
A conflict arises when duties to different clients, parties or the firm's own interests pull professional judgment in competing directions. Identify affected interests before acceptance and evaluate confidentiality, objectivity and the possibility of effective protection. Where appropriate and permitted, informed consent, separate teams, restricted information access and independent oversight may help. Consent is not sufficient when a conflict cannot be managed or a prohibition applies. Engagement terms should define the client, purpose, users, scope and exclusions so that different parties do not reasonably expect incompatible loyalties.
Worked example: A firm is approached by both a buyer and seller to negotiate price. It evaluates the opposing interests and confidential information each role requires, rather than assuming that separate folders and general consent make both mandates acceptable.
Common mistake: Believing that obtaining consent automatically permits every conflicted engagement, regardless of whether confidentiality and objective performance can actually be protected.
Quality management and audit practice management
17. ISQM 1's risk-based quality management cycle
A system of quality management identifies quality objectives, assesses risks to their achievement and designs responses suited to the firm's engagements and circumstances. ISQM 1 uses this risk-based approach across leadership, ethics, acceptance, resources, engagement performance, information and monitoring. The system is iterative: new clients, technologies or inspection findings can change assessed risks and responses. Merely maintaining a policy manual does not demonstrate that the system operates effectively. Link each significant quality risk to an implemented response, responsible ownership and evidence used to evaluate performance.
Worked example: A firm begins auditing complex property valuations. It identifies a new competence and resource risk, establishes specialist-access arrangements and consultation triggers, then monitors whether teams use them early enough to influence significant valuation judgments before completion.
Common mistake: Treating quality management as a standard checklist that remains adequate despite substantial changes in the firm's clients and services.
18. Leadership incentives and quality culture
Leadership shapes quality through decisions about promotion, remuneration, workload and responses to challenge. A stated commitment to quality can be undermined when staff are rewarded only for fee recovery or punished for justified consultation time. Evaluate whether accountability and incentives support professional judgment, ethical behaviour and sufficient evidence. Culture is demonstrated by recurring decisions, not slogans alone. Appropriate measures combine engagement quality, staff development and commercial performance without reducing quality to a single easily manipulated score or treating every budget overrun as justified.
Worked example: A manager raises an unresolved revenue issue that delays signing. Leadership recognises the evidence need, allocates experienced support and examines the original budget, signalling that timely escalation is expected rather than quietly rewarding teams that avoid difficult questions.
Common mistake: Assuming that a written quality statement outweighs repeated remuneration and promotion decisions that reward premature completion and discouraged challenge.
19. Resource budgeting and economically viable audits
An audit budget should reflect assessed risks, the evidence required and the competence needed to obtain it. Consider staff experience, review time, specialists, technology and scheduling constraints when pricing and accepting work. A low fee is not inherently incompatible with quality, but it must not dictate an inadequate scope or unsupported conclusions. Where efficiencies are proposed, explain how they preserve evidence quality. If realistic resources cannot be provided, revise commercial terms, change the delivery model appropriately or decline rather than relying on unplanned overtime and optimistic assumptions.
Worked example: A tender assumes one day for auditing a complex pension estimate. The partner obtains specialist input on the likely work, revises staffing and review time, and renegotiates the fee instead of leaving the estimate to an inexperienced junior.
Common mistake: Assuming that competitive pricing justifies reducing necessary audit work because the client has agreed to the proposed fee.
20. Direction, supervision and review at engagement level
Direction explains objectives, responsibilities, risks and expected outputs; supervision tracks progress, difficulties and the need to adapt; review evaluates work performed, evidence and conclusions. Their nature and extent depend on complexity, risk and team experience. The engagement partner remains responsible for managing and achieving engagement quality, including sufficient involvement in significant judgments. Review should occur early enough to influence work rather than merely record approval after completion. A signature is evidence of review only when supported by meaningful consideration and resolution of issues.
Worked example: A junior is assigned warranty provisions. The manager explains the estimation risk and evidence sources, discusses unexpected claim trends during testing and reviews the model assumptions before the partner evaluates the significant conclusion at completion.
Common mistake: Equating supervision with checking whether tasks are marked complete, without considering whether procedures achieved their stated audit purposes.
21. Consultation and unresolved differences of opinion
Consultation provides informed support for difficult or contentious judgments, but the engagement team must communicate complete relevant facts and evaluate how advice applies. Document the issue, consultation conclusions and implementation. Differences of opinion within the team, with specialists or with reviewers require an established resolution process; hierarchy alone does not establish the correct technical answer. An audit report should not be dated while a significant unresolved difference prevents an adequately supported conclusion. Consultation is most useful early enough to change evidence gathering, accounting discussions or report drafting.
Worked example: The partner and valuation specialist disagree about an unsupported terminal growth assumption. The firm follows its technical resolution process, obtains further evidence and records the accepted treatment before signing, rather than allowing the partner's seniority to settle the matter.
Common mistake: Assuming that technical consultation transfers responsibility for the audit conclusion entirely to the adviser who provided the opinion.
22. Engagement quality review under ISQM 2
An engagement quality review objectively evaluates significant judgments and the conclusions supporting the proposed report. Determine whether a review is required by applicable requirements or the firm's quality responses. The reviewer needs appropriate competence, capabilities, authority, time and objectivity, including compliance with relevant eligibility restrictions. The review does not repeat the entire audit or replace the engagement partner's responsibilities. Perform it at appropriate stages, address concerns and complete it before report dating. A reviewer who effectively made the significant judgment may lack the independence of perspective needed to evaluate it.
Worked example: A reviewer questions why contradictory evidence was excluded from a goodwill assessment. The team obtains additional support and revises its conclusion where necessary, allowing the reviewer to complete the evaluation before the report is dated.
Common mistake: Treating engagement quality review as a final proofreading exercise that may be completed after the audit report has been signed.
23. Root-cause analysis and effective remediation
A deficiency describes what failed; root-cause analysis investigates why the failure occurred and whether similar conditions affect other engagements. Evidence may include file reviews, interviews, workload data, consultation patterns and incentives. Several causes can interact, such as inadequate competence and unrealistic deadlines. Design remedial actions addressing those causes, with owners, resources and completion dates. Monitoring then tests whether actions work, not merely whether they were implemented. Training attendance alone cannot demonstrate that teams now challenge estimates adequately or obtain sufficient evidence on difficult engagements.
Worked example: Repeated confirmation failures are traced to late scheduling and staff misunderstanding of alternative procedures. The firm changes planning milestones, provides targeted instruction and reinspects subsequent files to determine whether timely confirmations and appropriate alternatives now support receivable conclusions.
Common mistake: Calling 'staff did not follow policy' a complete root cause without investigating why the policy repeatedly failed in practice.
24. Technological resources, validation and controlled change
Audit technology is a quality resource whose reliability must be established for its intended use. Evaluate data security, access permissions, tool logic, version changes and the competence needed to interpret outputs. Validate important calculations and investigate how a tool handles missing, duplicated or malformed data. Firm approval does not remove engagement-specific responsibilities for input completeness and appropriate interpretation. For third-party or AI-enabled tools, consider confidentiality and unsupported outputs as well as efficiency. Maintain evidence of configuration and results so conclusions remain explainable and reproducible.
Worked example: A firm updates its journal-selection tool. Before deployment, it tests known journal populations, checks date and currency handling and documents changed selection logic; engagement teams still reconcile their own extracts to the ledger before relying on results.
Common mistake: Assuming that a firm-approved analytical tool produces reliable engagement evidence regardless of input quality, settings or software version.
Business understanding, risk assessment and audit strategy
25. From business conditions to assertion-level risk
Business risk concerns threats to objectives and strategy; a risk of material misstatement concerns how financial information could be materially wrong. Translate the commercial condition into an accounting mechanism, affected balance or disclosure and relevant assertion. A lost customer may affect inventory valuation, receivable recoverability and going concern differently. Avoid merely repeating the business fact as an audit risk. Prioritise using likelihood, potential magnitude and the importance of the affected information, then design procedures addressing the actual route through which misstatement could occur.
Worked example: A retailer's supplier stops producing a popular spare part. The auditor identifies potential obsolescence in related accessories, explains why net realisable value may fall and examines subsequent sales and alternative uses rather than simply recording 'supplier risk'.
Common mistake: Listing adverse trading developments as audit risks without explaining which financial statement assertion could be misstated and why.
26. Inherent risk factors and significant risks
Inherent risk is susceptibility to misstatement before considering controls. Complexity, subjectivity, uncertainty, change and susceptibility to management bias can increase that susceptibility. Assess likelihood and magnitude together and identify risks requiring special audit attention under the applicable standards. A large balance is not automatically the highest inherent risk, and effective controls do not reduce inherent risk itself. They affect the separate assessment of control risk and the planned response. Use the spectrum of inherent risk to direct expertise, scepticism and more persuasive evidence toward the most demanding judgments.
Worked example: A small acquisition includes an earn-out driven by uncertain clinical milestones. Although its initial carrying amount is modest, complex terms and management estimates place the valuation higher on the inherent-risk spectrum than a larger, straightforward bank balance.
Common mistake: Reducing assessed inherent risk because management describes its controls as strong, before separately evaluating those controls and their operation.
27. Overall materiality and benchmark selection
Materiality reflects whether misstatements could reasonably influence users' decisions, individually or collectively. Select a benchmark relevant to the entity and users, such as profit, revenue, assets or another suitable measure, and justify the applied percentage using engagement circumstances. No single percentage is universally correct. Volatile or distorted profit may require a different benchmark or a justified adjustment. Qualitative factors can make smaller items material, including covenant effects or sensitive disclosures. Revise materiality when new information would have changed the original determination and reassess the audit work accordingly.
Worked example: For an illustrative engagement, a justified policy applies 5% to expected profit of €3 million, giving €150,000 materiality. When expected profit falls to €2 million without exceptional items, the auditor revises materiality to €100,000 and reassesses coverage.
Common mistake: Treating a conventional benchmark percentage as a mandatory rule or assuming every error below calculated materiality is automatically insignificant.
28. Performance materiality and aggregation risk
Performance materiality is set below overall materiality to reduce the risk that aggregate uncorrected and undetected misstatements exceed overall materiality. Its determination reflects factors such as prior errors, expected misstatements and the reliability of the control environment; it is not simply a compulsory fixed percentage. Use it in designing procedures and determining testing extent, while recognising that specific balances or disclosures may need lower thresholds. More widespread errors can justify a reduction. Performance materiality is distinct from the clearly trivial threshold used when accumulating identified misstatements.
Worked example: An illustrative audit has overall materiality of €240,000. The partner sets performance materiality at 60%, or €144,000, because several balances contain recurring errors. This planning amount influences testing but does not mean each balance may contain €144,000 of acceptable error.
Common mistake: Treating performance materiality as an allowable error budget for each account or confusing it with the threshold for recording misstatements.
29. Revenue fraud risks and contract-specific responses
Revenue can be manipulated through fictitious transactions, premature recognition, concealed returns or changes to contractual terms. Evaluate the relevant revenue streams, transactions and assertions rather than assuming every stream presents the same risk. Audit standards presume fraud risk in revenue recognition, with any rebuttal requiring a supported rationale under the applicable requirements. Link incentives to mechanisms: a bonus target near year end may encourage accelerated sales. Examine contracts, performance, acceptance, returns and subsequent credits; ledger entries or invoices alone may not demonstrate that revenue was earned.
Worked example: A supplier records December revenue for goods delivered in January, claiming that invoicing establishes the sale. The auditor inspects contractual transfer terms and delivery evidence, then tests similar year-end transactions for premature recognition and subsequent reversals.
Common mistake: Assuming that a valid invoice proves revenue recognition is appropriate without examining performance obligations, transfer of control and contractual terms.
30. Management override and journal-entry testing
Management can override otherwise effective controls through journals, biased estimates or unusual transactions lacking sound commercial substance. Responses include testing journal entries and other adjustments, reviewing estimates for bias and evaluating the rationale for significant unusual transactions. Journal selection should reflect the entity's systems and risk indicators, such as unusual users, accounts, timing or descriptions. Reconcile the extracted population and consider entries outside standard processing routes. An authorised entry can still be fraudulent, so approval testing must be combined with examination of underlying substance and accounting treatment.
Worked example: An administrator posts a late debit to receivables and credit to revenue using a vague description. The auditor inspects access rights, support and subsequent settlement, then expands testing to related users and unusual manual postings across the year.
Common mistake: Concluding that management override has been addressed solely because selected journals carry the required electronic approval or fall within an authorised user's access.
31. Control design, implementation and operating effectiveness
A control is well designed if it can prevent, detect or correct relevant misstatements; implementation establishes that it exists and is used. Operating effectiveness concerns whether it worked consistently during the relevant period and was performed by appropriate people or systems. A walkthrough can support understanding and implementation but does not usually establish year-long effectiveness. For automated controls, relevant IT general controls support continuing reliability. Decide whether reliance is planned or necessary, then test the controls at an appropriate extent and period rather than assuming written procedures demonstrate actual operation.
Worked example: A credit manager is supposed to review overdue balances monthly. A walkthrough confirms one review exists, but reliance requires evidence across the period that reviews occurred, exceptions were investigated and the reviewer used complete and accurate ageing information.
Common mistake: Treating a documented policy or one observed control performance as proof that the control operated effectively throughout the audit year.
32. Risk-responsive nature, timing and extent
An audit strategy converts assessed risks into decisions about the nature, timing and extent of work. Nature concerns the procedures and evidence sources; timing concerns when they are performed; extent concerns coverage and testing volume. Higher risk may require more persuasive external evidence, work closer to year end, increased senior involvement or specialist expertise, rather than simply a larger sample. Combine overall financial-statement responses with assertion-specific procedures. Reassess the strategy when control failures, unexpected results or new business developments undermine the assumptions supporting the original plan.
Worked example: A new distributor has weak year-end dispatch controls. The auditor moves cut-off testing to year end, examines delivery evidence directly, increases experienced supervision and expands targeted selections, rather than merely increasing an interim invoice sample.
Common mistake: Responding to every heightened risk by increasing sample size while leaving unsuitable procedures, timing and staff expertise unchanged.
Audit evidence and complex financial reporting matters
33. Evidence reliability and work performed by others
Evidence quality depends on relevance and reliability, not volume alone. Specify each procedure's action, source and assertion purpose, and evaluate provenance, controls and contradictions. Maintain control over external confirmations. For experts, assess competence, capability, objectivity and the adequacy of relevant work. For internal audit, evaluate objectivity, competence and disciplined methods before deciding how its work can be used. Service-organisation reports require attention to scope, period and complementary user controls. None of these sources transfers the external auditor's responsibility for obtaining sufficient appropriate evidence.
Worked example: A service auditor's report covers payroll processing but excludes client-maintained employee master data. The external auditor evaluates the report and tests relevant client controls over new starters and salary changes before relying on the combined processing evidence.
Common mistake: Assuming that an expert's reputation, an internal audit report or an external service report automatically establishes sufficient evidence for every relevant assertion.
34. Estimation uncertainty and impairment models
Accounting estimates combine methods, assumptions and data, so auditing them requires more than recalculating arithmetic. Evaluate estimation uncertainty, model appropriateness, source-data integrity and management bias. For IFRS impairment, recoverable amount is the higher of value in use and fair value less costs of disposal. Challenge forecast support, discount-rate consistency, cash-generating-unit boundaries and sensitivity disclosures. Evidence can come from testing management's process, developing an auditor estimate or range, or relevant subsequent events. A wide reasonable range does not justify unsupported assumptions or inadequate explanation of uncertainty.
Worked example: A unit carries €9 million. Supported value in use is €8.2 million and fair value less disposal costs is €8.6 million, indicating €400,000 impairment. The auditor also tests forecast support and disclosures rather than accepting the arithmetic alone.
Common mistake: Using the lower valuation measure as recoverable amount or assuming that a mathematically correct model contains reasonable assumptions.
35. IFRS 15 performance obligations and variable consideration
Revenue analysis starts with enforceable customer arrangements and identifiable performance obligations, not invoicing dates. Under IFRS 15, allocate transaction price to distinct obligations using appropriate stand-alone selling prices and recognise revenue when or as each obligation is satisfied. Evaluate whether recognition is over time or at a point in time. Variable consideration, such as rebates or performance bonuses, requires estimation and application of the constraint against significant reversal. Audit the contract terms, delivery or service evidence and estimation inputs, including side agreements that alter the apparent commercial arrangement.
Worked example: A company sells equipment with a separate year of support for €120,000. Supported stand-alone prices allocate €100,000 to equipment and €20,000 to support. Delivery may justify equipment revenue, while support revenue follows performance over its service period.
Common mistake: Recognising the entire contract price when the first invoice is issued, without evaluating distinct obligations, service periods or variable amounts.
36. Provisions, contingent liabilities and legal evidence
Under IAS 37, a provision requires a present obligation from a past event, a probable outflow and a reliable estimate. A possible obligation, or a present obligation without probable outflow, may require contingent-liability disclosure unless the relevant disclosure exception applies. Distinguish evidence about the existence of an obligation from uncertainty over its measurement. Examine contracts, claims, board discussions, legal correspondence and subsequent settlements. External legal responses can corroborate exposure, but management's own assessment and completeness of the matters referred to lawyers also require evaluation.
Worked example: A customer files a claim supported by a pre-year-end product defect. Legal evidence indicates a probable settlement and supports an estimate. The auditor evaluates a provision, while separately checking whether other claims were omitted from the legal enquiry population.
Common mistake: Assuming that uncertainty over the exact settlement amount prevents any provision, even when an obligation and a reliable estimate are supported.
37. Expected credit losses and financial instrument evidence
Expected credit loss measurement incorporates credit risk, exposure and expected cash shortfalls using appropriate forward-looking information. The applicable IFRS 9 approach depends on the instrument and circumstances; many trade receivables use a simplified lifetime-loss approach. Audit ageing data, payment history, customer-specific developments and economic overlays rather than relying only on historical default rates. Reconcile model inputs and assess management bias in assumptions. For other financial instruments, classification, contractual cash flows and valuation inputs require separate analysis; a reliable balance confirmation does not establish correct measurement or classification.
Worked example: A receivable has historically paid on time, but the customer enters financial restructuring before year end. The auditor inspects restructuring correspondence and recovery forecasts, assessing whether the historical loss rate understates expected shortfalls for that specific exposure.
Common mistake: Concluding that a confirmed receivable needs no loss allowance because the customer acknowledges the amount legally owed at year end.
38. Lease measurement and related-party terms
For an IFRS 16 lessee, identify arrangements conveying control over the use of an identified asset before measuring relevant lease liabilities and right-of-use assets. Examine enforceable terms, payment streams, options, discount rates and subsequent modifications, applying relevant exemptions where appropriate. Related-party leases require additional scrutiny because unusual pricing, informal arrangements or undisclosed relationships can distort accounting and disclosure. A related-party transaction is not automatically misstated or necessarily at market terms. Evaluate substance and disclosure separately, and do not assume that a signed contract settles every measurement question.
Worked example: A warehouse is leased from a company owned by the chief executive's sibling. The auditor verifies the relationship and enforceable terms, recalculates relevant lease amounts and evaluates related-party disclosure without assuming either that the rent is market-based or that the arrangement is invalid.
Common mistake: Assuming related-party lease terms must equal market terms, or that recording a lease liability removes the need for related-party disclosure.
39. Data analytics, population integrity and anomalies
Analytics can examine full populations or identify risk-focused selections, but results depend on complete, accurate and appropriately structured data. Reconcile extracts to control totals and the ledger, test important fields and understand transformation logic. An anomaly is a lead requiring investigation, not proof of misstatement; a clean result establishes only what the procedure was capable of detecting. Define the audit purpose before choosing a test. Consider false positives, missing populations and transactions outside the system, and retain sufficient detail to reproduce the analysis and evaluate exceptions.
Worked example: A duplicate-payment test flags invoices with the same supplier, amount and date. The auditor reconciles the source population, inspects flagged payments and distinguishes genuine duplicates from valid instalments, while recognising that altered invoice details may escape the selected matching logic.
Common mistake: Treating full-population analysis as automatically conclusive, regardless of data omissions, test design or the need to investigate identified exceptions.
Group audits and multinational engagements
40. Group scoping around risks and financial information
Group audit planning starts with understanding the group, consolidation process and risks across components and central functions. Determine where work should be performed to obtain evidence over material group information, including risks concentrated in small or recently acquired operations. Revenue or asset size alone cannot establish the appropriate scope. Shared service centres and common systems can generate risks spanning several legal entities. The group engagement team plans its involvement and the use of component auditors so that the resulting evidence supports the group opinion rather than merely collecting local audit reports.
Worked example: A small overseas subsidiary holds the group's only complex derivative portfolio. The group team plans focused specialist work there despite low revenue, while evaluating whether central treasury controls provide evidence relevant to the portfolio and other components.
Common mistake: Excluding a component solely because its revenue is small, without considering qualitative risks, unusual balances or group-wide processes.
41. Component performance materiality and aggregation
Aggregation risk arises because misstatements across components can collectively exceed group materiality even when each appears small locally. The group auditor determines component performance materiality for work on disaggregated financial information to address that risk. It is lower than group performance materiality, but is not necessarily a uniform percentage or a simple allocation by revenue. Consider the number and characteristics of components, expected errors and how information is aggregated. Communicate reporting thresholds and requirements clearly so component findings can be evaluated consistently at group level.
Worked example: A group has numerous components with recurring small errors. The group auditor sets differentiated component performance materiality and requests timely reporting of relevant misstatements, recognising that individually modest errors could combine into a material group-level overstatement.
Common mistake: Assuming that every component can use group materiality independently because no single component's errors are expected to exceed it.
42. Component auditor evaluation and two-way communication
Before using component auditor work, evaluate competence, capabilities, relevant ethical compliance and the ability to cooperate with group requirements. Consider knowledge of the reporting framework, industry, local environment and available resources. Communicate group risks, required procedures, component performance materiality and reporting expectations, and obtain timely information about findings and difficulties. Direction, supervision and review depend on risk and circumstances rather than a uniform package. The group auditor remains responsible for the group opinion and must assess whether component work provides sufficient appropriate evidence for that purpose.
Worked example: A component auditor understands local reporting rules but lacks experience in the group's complex revenue model. The group team provides focused instructions, discusses the contracts, involves specialists and reviews the significant judgments rather than relying solely on the local audit opinion.
Common mistake: Assuming that membership of the same international network automatically proves sufficient competence, independence and evidence quality for the group engagement.
43. Consolidation eliminations and unrealised profit
Consolidated statements present the group as one economic entity, requiring elimination of intra-group balances, transactions and unrealised profits. Reconcile intercompany differences before elimination rather than forcing unmatched amounts to zero. Profit embedded in goods still held within the group is not realised through an external sale and must be removed, with associated tax effects considered under the reporting framework. Audit the consolidation entries, source schedules and ownership links. Pay attention to cut-off, currencies and disputes because apparent reconciliation differences can reveal errors in component accounting rather than mere consolidation administration.
Worked example: A parent sells goods costing €60,000 to a subsidiary for €90,000, and all remain in inventory. The group eliminates the €90,000 internal sale and removes €30,000 unrealised profit from inventory, while considering the associated tax accounting.
Common mistake: Eliminating intercompany receivables and sales but leaving the seller's internal profit in inventory that remains within the group.
44. Acquisition accounting, goodwill and non-controlling interests
For a business combination under IFRS 3, identify the acquirer and acquisition date, measure consideration and recognise identifiable acquired assets and liabilities under the applicable requirements. Goodwill reflects consideration, relevant non-controlling interests and any previously held interest compared with acquired net identifiable assets. Non-controlling-interest measurement can affect goodwill, so inspect the chosen permitted basis rather than assuming one method. Audit fair-value adjustments, contingent consideration and ownership calculations. Distinguish acquisition-date conditions from later events, and assess whether the transaction is actually a business combination before applying the model.
Worked example: A buyer pays €8 million for 80% of a business with €7 million identifiable net assets. Using proportionate net assets for non-controlling interests gives €1.4 million NCI and €2.4 million goodwill, before considering any additional relevant acquisition adjustments.
Common mistake: Calculating goodwill as cash paid minus all acquired net assets without accounting for the ownership percentage and non-controlling-interest measurement basis.
45. Uniform policies and foreign-operation translation
Group information must reflect appropriate uniform accounting policies before consolidation. Local statutory compliance does not establish conformity with the group's reporting framework. Evaluate adjustments for matters such as revenue, leases and provisions, then assess foreign-currency translation under the relevant requirements. For a foreign operation, translation of assets, liabilities, income and expenses follows different rate principles, with resulting exchange differences generally treated separately from ordinary trading results. Audit source exchange rates, functional-currency judgments and translation calculations, distinguishing transaction exchange differences from those arising on translating a foreign operation.
Worked example: An overseas component expenses an item that qualifies for recognition under the group's policy. The consolidation team first records the policy adjustment, then translates the adjusted information using appropriate rates, rather than translating unadjusted local statements and assuming consistency.
Common mistake: Assuming that translating local financial statements into the presentation currency also corrects differences between local and group accounting policies.
46. Access restrictions and unresolved component findings
Restrictions on records, personnel or component auditor documentation can threaten the evidence supporting the group opinion. Understand the precise restriction and seek lawful alternatives, including local review, targeted discussions, direct testing or other independent evidence. Evaluate unresolved component findings in group terms, including related disclosures and their interaction with other errors. A local unmodified opinion is not a substitute for evidence needed at group materiality. If evidence remains insufficient, assess the materiality and pervasiveness of possible effects to determine qualification or disclaimer and consider broader continuance implications.
Worked example: Privacy rules prevent exporting component personnel records. The group auditor explores secure on-site review and appropriately anonymised evidence, assessing whether these alternatives address payroll assertions before concluding that a report modification is necessary.
Common mistake: Assuming that any overseas restriction automatically requires a disclaimer, without assessing lawful alternatives and the possible effects on group information.
Completion, review and audit reporting
47. Uncorrected misstatements, direction and prior-period effects
Evaluate identified misstatements individually and collectively, considering size, nature, direction and circumstances. Include relevant disclosure errors and assess the effect of uncorrected prior-period items on current information and comparatives. Opposing errors do not automatically cancel when they affect different balances, classifications or sensitive disclosures. A pattern that increases profit can indicate management bias even if individual amounts are small. Request correction, communicate relevant uncorrected items to governance and reconsider whether additional misstatements may exist. Reassess materiality using final results before determining the overall reporting consequence.
Worked example: Three errors increase profit by €70,000, €90,000 and €60,000. Their €220,000 combined effect exceeds an illustrative €200,000 materiality level, and the auditor also considers whether their common direction suggests bias and affects covenant disclosures.
Common mistake: Assessing each error only against overall materiality and overlooking the aggregate effect, common direction or impact of omitted disclosures.
48. Going concern basis versus material uncertainty
Going concern assessment separates whether the accounting basis is appropriate from whether a material uncertainty requires disclosure and specific audit reporting. Examine forecasts, financing terms, covenant compliance and management's feasible actions, challenging assumptions and timing. The assessment period must satisfy applicable reporting and auditing requirements rather than an invented universal horizon. A material uncertainty can coexist with an appropriate basis. If adequately disclosed, it ordinarily receives a dedicated report section with an unmodified opinion; inadequate disclosure or an inappropriate basis leads to different opinion considerations.
Worked example: A viable business depends on an unresolved facility renewal and discloses that dependency adequately. Evidence supports continued use of going concern, but the financing uncertainty remains material, leading to a dedicated uncertainty section rather than automatic qualification.
Common mistake: Treating every liquidity problem as proof that the going concern basis is inappropriate, or every material uncertainty as requiring a modified opinion.
49. Subsequent events and conditions at the reporting date
Under IAS 10, adjusting events provide evidence about conditions existing at the reporting date; non-adjusting events concern conditions arising afterwards and may require disclosure if material. The date of cash settlement alone does not determine the category. Audit subsequent events through enquiries, minutes, interim information and relevant correspondence up to the auditor's report date. Facts discovered later require assessment under the applicable post-report responsibilities. Consider how events affect estimates, disclosures and going concern, rather than applying a mechanical rule that all later events belong only in the next period.
Worked example: A customer enters insolvency shortly after year end because of financial difficulties already evident before year end. The event may support adjustment of the year-end receivable allowance, unlike a loss caused solely by an unrelated later disaster.
Common mistake: Classifying an event as non-adjusting simply because its formal announcement or cash settlement occurred after the reporting date.
50. Final analytics and written representations
Final analytical procedures assess whether the financial statements are consistent with the auditor's understanding and whether unexpected relationships suggest an overlooked misstatement. They complement rather than replace detailed evidence already required. Written representations confirm specified management responsibilities and assertions, but do not substitute for other evidence reasonably expected to exist. Evaluate inconsistent representations and their implications for management integrity. Refusal to provide necessary representations requires assessment under the auditing requirements, potentially affecting the opinion. Completion therefore reconciles the overall story, outstanding evidence and management's formal acknowledgements.
Worked example: Final analytics reveal improving margins despite rising input prices and falling volumes. Management's representation that inventory is correctly valued does not resolve the contradiction; the auditor revisits costing, rebates and cut-off before completing the opinion.
Common mistake: Using a signed representation letter to close an unresolved material evidence gap or treating final analytics as a purely numerical formality.
51. Opinion modification and pervasiveness
First distinguish established material misstatement from inability to obtain sufficient appropriate evidence. For misstatement, material but non-pervasive effects lead to a qualified opinion; material and pervasive effects lead to an adverse opinion. For insufficient evidence, material but non-pervasive possible effects lead to qualification; material and pervasive possible effects lead to disclaimer. Pervasiveness concerns spread, substantial proportion or fundamental importance to users' understanding, not a universal numerical percentage. Explain the matter in the appropriate basis section and use wording consistent with whether effects are known or merely possible.
Worked example: Supported evidence establishes a material, isolated inventory overstatement, so qualification for misstatement is appropriate. If inventory records are unavailable instead, the auditor evaluates possible effects and qualifies for insufficient evidence when those effects are material but not pervasive.
Common mistake: Choosing adverse opinion for every serious evidence limitation, or using disclaimer when the auditor has sufficient evidence of pervasive misstatement.
52. Key audit matters, emphasis and other matter paragraphs
Key audit matters explain matters of most significance in the audit when such reporting is required or undertaken; they are not separate opinions. An Emphasis of Matter draws attention to an appropriately presented or disclosed matter fundamental to understanding the statements. An Other Matter concerns information outside the statements relevant to understanding the audit, auditor responsibilities or report. Neither substitutes for a modified opinion, required disclosure or a dedicated going concern uncertainty section. Apply the relevant reporting requirements and avoid assuming that every interesting audit issue belongs in all these sections.
Worked example: A difficult valuation may qualify as a key audit matter where that reporting applies. If the valuation is materially misstated, describing the audit effort does not cure the problem; the opinion and basis section must address the misstatement.
Common mistake: Using an Emphasis of Matter or key audit matter description to compensate for a material error that should modify the opinion.
53. Other information and governance communication
Other information accompanying audited statements may contain material inconsistencies with those statements or with knowledge obtained in the audit. Read and evaluate it under the applicable requirements, distinguishing management's narrative from the audited statements themselves. Seek correction of material misstatements and follow the required communication and reporting process if they remain unresolved. Separately communicate significant audit findings and significant control deficiencies to those charged with governance. A financial statement audit does not ordinarily provide assurance over every annual-report statement, but that boundary does not remove the responsibility to address apparent material inconsistency.
Worked example: The annual report claims that all major facilities were renewed, while audit evidence shows one remains under negotiation. The auditor discusses the contradiction, seeks correction and evaluates any required reporting response without presenting the entire narrative as audited.
Common mistake: Ignoring a material annual-report inconsistency because the narrative is outside the financial statements, or implying that reading it constitutes a full audit.
Other assurance and related professional engagements
54. Reasonable assurance, limited assurance and factual findings
Reasonable assurance reduces engagement risk to an acceptably low level and supports a positive-form conclusion, while limited assurance involves a lower but meaningful assurance level and ordinarily a conclusion expressed in terms of whether matters came to the practitioner's attention. Procedures differ in nature, timing and extent according to the engagement. Agreed-upon procedures provide factual findings without assurance, leaving users to draw conclusions. These are different engagement responsibilities, not interchangeable report labels. Agree the required outcome and applicable standard before selecting procedures or promising a level of comfort.
Worked example: A funder requesting an independent conclusion on a grant statement needs an assurance engagement with suitable criteria. A funder requesting specified invoice matches may instead use agreed-upon procedures, receiving exceptions and findings without an overall conclusion on compliance.
Common mistake: Calling agreed-upon procedures limited assurance merely because fewer procedures are performed than in an audit or reasonable assurance engagement.
55. Suitable criteria and assurance acceptance conditions
An assurance engagement needs appropriate subject matter, suitable criteria, a rational purpose and access to sufficient appropriate evidence. Criteria should be relevant, complete, reliable, neutral and understandable, and available to intended users in an appropriate way. Vague promises such as 'excellent service' do not establish a measurable basis for a conclusion. Assess management responsibilities, practitioner competence, ethics and scope limitations before acceptance. Where criteria are developed for specific users or purposes, explain that context in engagement terms and reporting rather than implying universal applicability.
Worked example: A transport operator requests assurance that service is reliable. The practitioner first defines an available criterion, such as the proportion of scheduled departures within a stated time window, including cancellations and the measurement period, before accepting the engagement.
Common mistake: Accepting a broad performance claim as auditable merely because management supplies a calculation, without evaluating the criteria and intended users.
56. Forecasts, projections and assumption sensitivity
Prospective financial information depends on assumptions and preparation methods rather than observable future results. A forecast uses best-estimate assumptions about expected events and actions; a projection includes hypothetical assumptions, potentially combined with best estimates. Evaluate the basis, internal consistency, arithmetic, supporting evidence and presentation of assumptions under the applicable engagement requirements. Sensitivity analysis identifies dependence on uncertain drivers such as sales volumes, margins or financing. Neither careful examination nor an assurance report guarantees achievement. Distinguish an unsupported optimistic assumption from an explicitly disclosed hypothetical scenario that serves a rational purpose.
Worked example: A projection assumes a new plant opens in July although approval is uncertain. The practitioner checks how that hypothetical assumption is described, tests construction and operating cash-flow consistency and evaluates a delayed-opening sensitivity rather than presenting July commencement as established fact.
Common mistake: Treating all prospective information as a prediction to be guaranteed, or assuming disclosed hypothetical assumptions need no evaluation of consistency and purpose.
57. Due diligence, quality of earnings and net debt
Financial due diligence investigates information relevant to a transaction under an agreed scope; it is not automatically an audit or assurance engagement. Quality-of-earnings analysis distinguishes sustainable trading results from unusual, non-recurring or policy-driven effects, while working-capital and net-debt analyses depend on transaction definitions. Challenge proposed adjustments symmetrically rather than accepting only profit increases. Reconcile analyses to reliable records, investigate trends and explain limitations. Commercial significance can differ from audit materiality, and findings should support buyer decisions without making unsupported legal conclusions or guaranteeing the acquisition's value.
Worked example: A seller adds back €200,000 restructuring costs to earnings. Due diligence finds similar charges in each of three years and questions whether they are genuinely non-recurring, explaining the valuation implication rather than automatically accepting the seller's adjusted profit.
Common mistake: Assuming that every expense described as exceptional should be removed from sustainable earnings or that due diligence provides an audit opinion.
58. Forensic evidence preservation and transaction reconstruction
A forensic assignment investigates specified concerns using an agreed mandate and evidence-preservation approach. Define scope, authority, confidentiality and intended use before collecting records or conducting interviews. Preserve original data and maintain a documented chain of custody so evidence can be traced and assessed. Reconstruct transactions through independent sources, test competing explanations and distinguish facts, inferences and unresolved matters. Digital or legal specialists may be needed, but the practitioner should not pronounce criminal guilt. Investigation procedures differ from a financial statement audit's objective and materiality-focused scope.
Worked example: Suspected procurement diversion is investigated by preserving authorised email exports, supplier records and bank evidence. The team reconstructs approvals and payment destinations, documents custody and corroborates interview accounts before reporting supported findings and remaining uncertainties to the authorised recipient.
Common mistake: Treating an unusual payment pattern as proof of guilt or altering original records while assembling an investigation's working evidence.
59. Sustainability boundaries, measurement and estimation
Sustainability assurance requires a defined reporting boundary, suitable criteria and reliable evidence over both quantitative and narrative information. For emissions or resource metrics, assess included operations, calculation methods, activity data, conversion factors and estimation uncertainty. Changes in organisational boundaries can distort year-on-year comparisons even when calculations are correct. Evaluate competence and specialist needs for technical measurements. Separate assurance over reported information from assurance that targets will be achieved. Applicable reporting and assurance requirements depend on the entity, jurisdiction and period; do not infer universal scope or mandatory assurance levels from general sustainability interest.
Worked example: A group reports lower energy use after outsourcing production. The practitioner examines whether the boundary and methodology changed, reconciles meter and invoice data and evaluates explanatory disclosures before accepting the reduction as comparable with the previous year's figure.
Common mistake: Assuming that a falling sustainability metric necessarily represents improved underlying performance when reporting boundaries, estimation methods or business activities have changed.
60. AI-enabled controls and performance-measure assurance
Assurance over technology-supported controls or performance measures requires an explicit claim, measurable criteria and evidence about how outputs are produced. For AI-enabled processes, examine data lineage, access, version changes, human review and how errors or exceptions are detected. Reproducibility and explainability matter when outputs support reported metrics or control decisions. A successful demonstration does not establish effectiveness throughout a period. Distinguish assurance over a specified system or measure from broad claims that an algorithm is universally accurate, unbiased or compliant; those claims require separately defined criteria and evidence.
Worked example: A company reports that an AI tool resolved 92% of complaints. The practitioner checks what 'resolved' means, reconciles the complaint population, tests reopened cases and examines model changes before concluding on the defined metric rather than on general AI quality.
Common mistake: Assuming a high reported success rate proves system effectiveness without testing population completeness, outcome definitions, exceptions and changes during the reporting period.