Build practical audit judgment through twenty original written tasks and sixty substantive concepts covering assurance, ethics, planning, controls, evidence and reporting. Three linked five-task cases repeat the facts needed for independent use; further tasks develop evidence evaluation, reporting and spreadsheet presentation. This representative preview follows the supplied September 2026–June 2027 ACCA AA study allocation, current for 17 October 2026, rather than official domain weightings. The examination itself mixes objective tests and constructed responses; this package uses written and practical responses. It concerns AA International, not AAA or the redesigned qualification launching in 2027. Citations establish syllabus relevance; technical explanations apply established audit knowledge.
What this guide covers
Build ACCA AA skills with 20 original written tasks, worked answers and 60 focused audit study concepts.
Audit framework and regulation
1. The five elements of an assurance engagement
An assurance engagement connects a practitioner, a responsible party and intended users through an evaluation of subject matter against suitable criteria. Its five elements are that three-party relationship, appropriate underlying subject matter, suitable criteria, sufficient appropriate evidence and a written assurance report. Criteria make the conclusion meaningful: users need a benchmark against which performance or information has been assessed. An engagement cannot deliver useful assurance merely by collecting documents. Identify what is being evaluated, who is responsible, which criteria apply and whether evidence can support the promised conclusion.
Worked example: A charity asks an accountant to assess a grant expenditure statement against the funder's published eligibility rules. Trustees prepare the statement, the funder uses the report, and invoices and payment records provide evidence against those specific criteria.
Common mistake: Treating the engagement letter as the subject matter confuses the contract for the work with the information actually being evaluated.
Official syllabus reference: [1]
2. Reasonable assurance versus limited assurance
Reasonable assurance reduces engagement risk to an acceptably low level and supports a positive-form conclusion, such as an audit opinion on financial statements. Limited assurance involves less extensive evidence gathering and supports a conclusion framed around whether anything has come to the practitioner's attention indicating material misstatement. Both require meaningful evidence; neither provides certainty. A review commonly emphasizes enquiry and analytical procedures, with further work when concerns arise. The distinction concerns the engagement's assurance level and procedures, rather than whether the practitioner believes the client is generally trustworthy or commercially successful.
Worked example: An auditor tests transactions, controls and estimates before expressing a financial statement opinion. A review practitioner performs a narrower engagement and reports whether anything has come to attention suggesting the statements fail to comply materially with the specified framework.
Common mistake: Limited assurance is not permission to ignore contradictory evidence, and reasonable assurance does not mean every transaction has been independently verified.
Official syllabus reference: [1]
3. Agency, stewardship and the expectation gap
Agency arises when owners delegate management of resources to directors whose incentives and information may differ from theirs. Stewardship reporting allows directors to explain how they used those resources. Independent audit increases the credibility of that reporting and helps reduce information asymmetry, but it does not transfer directors' responsibilities to auditors. The expectation gap includes differences between what users believe auditors do and the audit's actual responsibilities and limitations. Apply these ideas when explaining why audits exist, why independence matters and why an opinion cannot guarantee solvency or detect every instance of fraud.
Worked example: Shareholders cannot inspect every overseas branch, while directors control the accounting records and earn profit-related bonuses. Audited statements provide more credible stewardship information, but shareholders must still assess strategy and commercial risk when deciding whether to retain their investment.
Common mistake: Assuming that appointment by shareholders makes the auditor responsible for managing the business replaces independent evaluation with an incompatible executive role.
Official syllabus reference: [1]
4. ISAs, national law and statutory audit rights
International Standards on Auditing establish requirements and application guidance for conducting financial statement audits. National adoption and legislation determine how those standards interact with local appointment, eligibility, access, removal and reporting requirements. An international syllabus does not establish one universal company law. Distinguish professional audit requirements from jurisdiction-specific statutory rights and duties. Where both apply, understand their relationship rather than assuming one automatically displaces the other. In a scenario, use the stated jurisdictional facts and recognize when a legal requirement needs clarification before deciding whether an engagement can be accepted or continued.
Worked example: An appointment scenario states that local legislation gives the auditor access to accounting records. Management proposes withholding a subsidiary ledger. The auditor considers both the legal access right and the evidence implications, rather than treating the restriction as an ordinary contractual preference.
Common mistake: Quoting one country's appointment or removal procedure as a universal ISA requirement confuses legislation with international professional auditing standards.
Official syllabus reference: [1]
5. Audit committee oversight and executive responsibility
An effective audit committee supports governance by overseeing financial reporting, internal control, internal audit and the relationship with external auditors. Independence from executive management helps members challenge judgments, discuss unresolved findings and oversee auditor appointment and independence. Management still prepares statements and operates controls; the committee oversees rather than processes transactions. Governance codes provide best-practice reference points, but their legal status and detailed provisions depend on the jurisdiction and entity. Evaluate whether membership, expertise, access and reporting arrangements allow genuine challenge instead of merely checking that a committee formally exists on paper.
Worked example: A committee receives internal audit reports only after the finance director removes disputed findings. Direct access to the head of internal audit and private meetings with external auditors would improve oversight by allowing members to hear unresolved concerns without executive filtering.
Common mistake: A committee is not effective merely because it meets frequently; executive dominance and restricted access can still prevent meaningful independent challenge.
Official syllabus reference: [1]
6. Ethical principles and the conceptual framework
The fundamental ethical principles are integrity, objectivity, professional competence and due care, confidentiality, and professional behavior. The conceptual framework requires identifying, evaluating and addressing threats to compliance. Evaluate threats using the perspective of a reasonable and informed third party rather than the accountant's confidence in personal honesty. Responses may remove the circumstance, apply effective safeguards or require declining or ending the activity. A measure counts as a safeguard only when it actually reduces the threat to an acceptable level. Apply this sequence to specific facts before choosing a practical response.
Worked example: A manager is asked to sign off complex inventory valuation without relevant experience or time for review. The concern involves competence and due care. Assigning a suitably skilled reviewer and adequate time addresses the cause more effectively than a generic ethics reminder.
Common mistake: Listing ethical principles without connecting them to the facts does not explain the threat or establish that a proposed safeguard works.
Official syllabus reference: [1]
7. Independence threats and effective safeguards
Independence includes independence of mind and independence in appearance. Common threat categories are self-interest, self-review, advocacy, familiarity and intimidation. Identify the mechanism: financial dependence may discourage challenge, preparing information may lead to reviewing one's own judgments, and close relationships may weaken skepticism. The response must fit that mechanism. Removing an affected team member can address a personal relationship, while an independent review may address some judgment threats. Some circumstances are prohibited or cannot be made acceptable through safeguards. Avoid assuming that disclosure or a separate team automatically solves every independence problem.
Worked example: An audit senior's spouse becomes responsible for the client's revenue estimates. Replacing the senior removes that relationship from the engagement's evidence decisions. Merely asking the senior to document extra skepticism leaves the underlying influence over the audit work intact.
Common mistake: Calling every ethical problem self-interest obscures the actual mechanism and can lead to a safeguard that does not address the threat.
Official syllabus reference: [1]
8. Confidentiality and authorized disclosure
Confidentiality protects information obtained through professional relationships and continues after those relationships end. An accountant should not use such information for personal advantage or disclose it without proper authority, unless a legal or professional right or duty permits or requires disclosure. The analysis therefore considers the recipient, purpose, authority and applicable obligations. Confidentiality does not mean concealing matters from appropriate engagement personnel or refusing every lawful reporting duty. When disclosure is justified, limit it to relevant information through an appropriate channel and document the basis rather than spreading allegations informally.
Worked example: A prospective investor asks an audit employee about a client's unpublished cash shortage. The employee should not disclose the information merely because the investor might benefit. Any separate duty to report suspected wrongdoing requires analysis through the appropriate legal and professional framework.
Common mistake: Assuming that public interest automatically authorizes disclosure to anyone bypasses the need to establish an appropriate right, duty and recipient.
Official syllabus reference: [1]
9. Quality management through resources and review
Audit quality depends on a system that assigns competent people, sufficient time, suitable technological resources and clear direction, supervision and review. The engagement partner remains responsible for managing and achieving quality on the engagement. Work should be reviewed by people with appropriate experience, with significant judgments discussed and unresolved differences addressed before reporting. Consultation and any required engagement quality review support, rather than replace, the engagement team's responsibilities. Apply quality management by linking a deficiency to its cause: an inexperienced team confronting complex estimates needs expertise and supervision, not simply a longer checklist.
Worked example: A junior auditor completes a specialist valuation section without review because the manager is reassigned. The firm should provide competent review and access to expertise before the report is issued, then address the staffing process that allowed the gap to arise.
Common mistake: A completed checklist does not demonstrate audit quality when reviewers lack competence, significant judgments remain unresolved or necessary evidence is missing.
Official syllabus reference: [1]
10. Monitoring, root causes and remediation
Monitoring evaluates whether quality management arrangements are designed appropriately and operate effectively. Findings must be evaluated to identify deficiencies, understand their severity and pervasiveness, and determine root causes. Remediation should address those causes and be assessed for effectiveness rather than ending when a policy is issued. Distinguish an isolated file error from a recurring system weakness, while recognizing that one serious finding can still matter. Useful evidence includes inspection results, recurring review points, staffing patterns and consultation records. Correcting an affected engagement and improving the wider system may both be necessary.
Worked example: Several files contain late revenue testing. Investigation shows that budgets allocate too little final-stage time and managers discourage overruns. Adding another revenue checklist would miss the cause; revising budgets, supervision and escalation arrangements directly addresses the repeated scheduling pressure.
Common mistake: Treating training as the answer to every inspection finding ignores causes such as incentives, workload, access restrictions and ineffective supervision.
Official syllabus reference: [1]
Planning and risk assessment
11. Acceptance preconditions and engagement letters
Before accepting an audit, assess ethical compliance, independence, competence, resources and relevant information about management integrity. Audit preconditions include an acceptable reporting framework and management's acknowledgment of responsibility for the statements, necessary internal control and access to information and people. An engagement letter records the agreed objective, scope, responsibilities, framework and expected reporting arrangements. It clarifies expectations but cannot cure unacceptable preconditions. With appropriate permission, communication with a predecessor can inform acceptance. Reassess continuance when circumstances change, including serious integrity concerns, unpaid fees or new restrictions on evidence access.
Worked example: A company offers a lucrative audit but refuses access to its legal correspondence and overseas accountant. The firm first assesses the evidence restriction and management's acknowledgment of responsibilities; signing a standard engagement letter would not make the restricted engagement acceptable.
Common mistake: An engagement letter records an acceptable agreement; it does not transform an unacceptable reporting framework or severe access restriction into an acceptable audit.
Official syllabus reference: [1]
12. Overall audit strategy versus detailed audit plan
The overall audit strategy establishes the engagement's scope, timing and direction, including significant reporting deadlines, locations, resources and areas requiring attention. The audit plan translates that direction into the nature, timing and extent of risk assessment procedures and further audit procedures. Both evolve as evidence changes. Strategy might require specialist involvement and year-end attendance at several warehouses; the plan specifies the actual procedures and selections. Planning is therefore iterative rather than a one-time administrative document. Changes should be documented with reasons so reviewers can understand how new information altered the audit approach.
Worked example: An initial strategy anticipates relying on automated sales controls. Testing reveals unauthorized configuration changes. The team revises the strategy toward greater substantive work and updates the plan with expanded revenue testing and additional procedures over the affected period.
Common mistake: A list of detailed invoice tests is not the overall strategy, and an unchanged plan is not evidence of effective planning.
Official syllabus reference: [1]
13. Audit risk and the detection-risk response
Audit risk is the risk of expressing an inappropriate opinion when the financial statements are materially misstated. Risk of material misstatement comprises inherent risk and control risk; detection risk concerns audit procedures failing to detect an existing material misstatement. The model helps explain the audit response rather than demanding arbitrary numerical probabilities. When assessed misstatement risk rises, acceptable detection risk falls, requiring more persuasive evidence or changes in procedure nature, timing or extent. Auditors assess client-side risks but manage detection risk through their work. More samples alone may not solve an inappropriate procedure design.
Worked example: A complex warranty estimate lacks effective management review. Higher inherent and control risks lead the auditor to use more experienced staff, test assumptions against claims data and consider specialist input rather than relying on management's spreadsheet arithmetic alone.
Common mistake: Auditors cannot reduce inherent risk by performing extra tests; extra work changes detection risk and the evidence supporting the audit conclusion.
Official syllabus reference: [1]
14. From business risk to assertion-level misstatement
Business risk threatens an entity's objectives, while audit risk focuses on material misstatement. Translate a scenario fact into an affected balance, a possible accounting error and the relevant assertion. A failed product launch may create obsolete inventory, overstated recoverability and an inventory valuation risk. A new sales channel may create incomplete interfaces or incorrect revenue cutoff. Not every business difficulty creates the same accounting effect. Assertion-level analysis makes the response specific and avoids describing only commercial consequences such as falling profits. Consider whether the matter also has pervasive financial statement-level implications.
Worked example: A retailer loses its largest customer. The commercial risk is reduced future sales. Audit implications include potentially overstated customer receivables, slow-moving inventory and pressure to accelerate revenue, each requiring different evidence and potentially different procedures.
Common mistake: Writing that a company may lose money identifies a business concern but does not explain which financial statement amount could be misstated.
Official syllabus reference: [1]
15. Materiality, performance materiality and aggregation
Materiality concerns whether misstatements could reasonably influence users' decisions, individually or together. It depends on size, nature and circumstances, so a percentage is a starting judgment rather than a universal rule. Performance materiality is lower than overall materiality to address aggregation and undetected misstatements when planning work. A clearly trivial threshold serves a different purpose in accumulating identified misstatements. Reassess materiality when actual results or other information differ from planning assumptions. Qualitatively sensitive matters, such as disclosures affecting management accountability, may deserve attention even when their monetary amount is relatively small.
Worked example: An exercise sets overall materiality at $200,000 and performance materiality at $120,000. Three unrelated $80,000 errors cannot each be dismissed as below overall materiality: together they total $240,000, before considering undetected errors or qualitative factors.
Common mistake: Performance materiality is not the maximum acceptable error in every individual account, and smaller identified errors are not automatically irrelevant.
Official syllabus reference: [1]
16. Ratio analysis as a risk-assessment tool
Planning analytics compare plausible relationships across periods, budgets and non-financial information to identify unusual movements. Gross margin, receivables days, inventory days and liquidity ratios answer different questions and require consistent definitions. A movement creates an investigation lead rather than proof of error. Break the ratio into numerator and denominator, consider commercial explanations and identify possible accounting effects. Closing balances can distort ratios where seasonality is strong, so average balances or monthly analysis may be more informative. Corroborate explanations with underlying evidence instead of accepting a convenient narrative that merely fits the numbers.
Worked example: Revenue rises 10% while closing receivables rise 50%, increasing receivables days. Longer contractual terms could explain the change, but disputed invoices or premature sales could also contribute. The auditor examines terms, ageing and subsequent collections before deciding the implication.
Common mistake: A deteriorating ratio does not prove fraud, and a stable ratio can conceal offsetting errors or changes in the business mix.
Official syllabus reference: [1]
17. Fraud responsibilities and management override
Management and those charged with governance have primary responsibility for preventing and detecting fraud. Auditors seek reasonable assurance that statements are free from material misstatement caused by fraud or error. Fraud can be harder to detect because concealment, collusion and override may defeat ordinary controls. Management override requires specific attention, including journal entry testing, consideration of bias in estimates and examination of significant unusual transactions. Assess incentives, opportunities and attitudes without treating indicators as proof. When concerns arise, obtain corroborating evidence, reconsider risk and communicate through appropriate channels.
Worked example: A finance director posts large manual sales journals after normal processing closes and reverses them immediately in January. The auditor investigates authorization, contracts, dispatch evidence and the complete journal population, rather than accepting a description of 'routine year-end adjustments'.
Common mistake: Management's primary fraud responsibility does not remove the auditor's duty to assess fraud risks and design an appropriate evidence-based response.
Official syllabus reference: [1]
18. Laws and regulations with different financial effects
Some laws and regulations directly determine financial statement amounts or disclosures, while others govern operations and may affect statements through penalties, provisions or going concern. The auditor's procedures reflect this distinction and do not constitute a legal compliance audit of every activity. Understand the relevant regulatory environment, inspect appropriate correspondence and remain alert to indications of non-compliance. If suspected non-compliance arises, investigate its nature and financial effects, consider communication and reporting duties and obtain suitable expertise where needed. Confidentiality and external reporting obligations depend on the applicable professional and legal framework.
Worked example: A manufacturer receives a regulator's letter alleging environmental permit breaches. The auditor inspects the correspondence and legal assessment to evaluate potential fines, remediation obligations and operational consequences, rather than assuming that environmental rules are irrelevant because they do not directly calculate revenue.
Common mistake: Calling a regulation operational does not make it financially irrelevant; breaches may create liabilities, disclosures or threats to continued operations.
Official syllabus reference: [1]
19. Professional skepticism and contradictory evidence
Professional skepticism combines a questioning mind, alertness to possible misstatement and critical assessment of evidence. It requires neither automatic distrust nor passive acceptance. Consider evidence that contradicts management's explanation, assess document reliability and investigate inconsistencies. Professional judgment applies relevant training and experience to decisions such as materiality, procedure selection and evidence sufficiency; it must be supported by reasons. A skeptical response changes the work when facts demand it. Recording that management is experienced or honest cannot replace corroboration where estimates, incentives or unusual transactions create a meaningful risk.
Worked example: Management attributes falling warranty claims to improved quality, but customer complaints and repair backlogs have increased. The auditor investigates delayed claim processing and tests the completeness of claims data before accepting a lower warranty provision.
Common mistake: Skepticism is not demonstrated by hostile language or a standard file statement; it is demonstrated by how evidence is challenged and resolved.
Official syllabus reference: [1]
20. Working papers that support a reproducible conclusion
Audit documentation should allow an experienced auditor with no previous connection to understand the work performed, evidence obtained, significant matters and conclusions reached. Record the procedure's purpose, population or items tested, results, exceptions, preparer and review information. Link conclusions to evidence and explain significant judgments or changes in approach. Documentation supports supervision, accountability and subsequent inspection, but cannot substitute for procedures never performed. Secure custody and controlled access protect confidentiality and integrity; retention and file assembly follow applicable requirements rather than an invented universal timetable. Later changes should preserve a clear amendment trail.
Worked example: A receivables paper identifies selected invoices, confirmation results, alternative procedures for non-responses and resolution of a disputed balance. A reviewer can follow why the remaining allowance is reasonable without asking the original preparer to reconstruct the work from memory.
Common mistake: A tick beside an account balance does not explain the procedure, evidence or conclusion and cannot establish that adequate audit work occurred.
Official syllabus reference: [1]
21. Interim testing and the untested remaining period
Interim audit work can improve scheduling and identify issues early, but evidence obtained before year end does not automatically cover the remaining period. Interim work may include understanding systems, testing controls and examining selected transactions. At final audit, assess changes in controls, personnel and systems, then obtain evidence over the intervening period. The extent of additional work depends on risk, elapsed time and the evidence already obtained. Year-end balances, cutoff and subsequent events often require final-stage attention. Distinguish the timing of a procedure from whether it is a control test or substantive procedure.
Worked example: Controls are tested through September, but a new payroll system begins in November. The auditor cannot simply extend September's conclusion to December; the new system's implementation and relevant controls require assessment, with additional substantive work where necessary.
Common mistake: An interim visit does not reduce final work automatically; its value depends on what was tested and whether later changes undermine reliance.
Official syllabus reference: [1]
22. Understanding the entity through corroborated enquiries
Understanding the entity includes its business model, ownership, governance, industry, financing, reporting framework, performance measures and internal control. Risk assessment uses enquiry, analytical procedures, observation and inspection together. Enquiry explains how management says activities work; inspection and observation test whether that description fits reality. Consider external developments and internal changes, including technology and incentives, because they can alter risks without changing the chart of accounts. The purpose is to identify and assess misstatement risks and design responsive work, not to produce a lengthy company profile with no audit implications.
Worked example: Management says a new online marketplace only introduces customers. Inspection of contracts shows the entity controls pricing, accepts returns and bears inventory risk. That understanding changes the auditor's assessment of the revenue model and the evidence needed for presentation and recognition.
Common mistake: Copying last year's business description misses changed contracts, systems and incentives that may materially alter this year's financial reporting risks.
Official syllabus reference: [1]
Internal control
23. The five components of internal control
Internal control comprises the control environment, the entity's risk assessment process, its monitoring process, the information system and communication, and control activities. These components interact: ethical leadership influences behavior, risk assessment identifies threats, information systems process transactions, specific activities address risks, and monitoring identifies deterioration. Understanding all five prevents an audit from focusing only on transaction signatures. Controls provide reasonable rather than absolute assurance because judgment, error, collusion and management override remain possible. Evaluate whether the components fit the entity's size and complexity and support reliable financial reporting in practice.
Worked example: A company has invoice approval signatures but rewards managers who bypass checks to meet dispatch targets. The approval activity exists, yet the control environment undermines it. Repeated bypasses also indicate that monitoring has failed to identify or correct the problem.
Common mistake: A strong accounting software package is only part of internal control; it cannot compensate automatically for weak leadership, access governance or monitoring.
Official syllabus reference: [1]
24. Segregation of duties and compensating reviews
Segregation separates incompatible responsibilities such as authorization, asset custody, transaction recording and reconciliation. Its purpose is to reduce the opportunity for one person to both cause and conceal an error or fraud. Small entities may lack enough staff for complete separation, making precise independent reviews important. A compensating control must detect the relevant error promptly using reliable information; a vague statement that the owner watches everything is insufficient. Collusion and override limit segregation's protection. Evaluate actual system permissions and workflow, because different job titles do not prove that incompatible capabilities are separated.
Worked example: One employee creates suppliers and prepares payment files. An owner independently checks new suppliers against original contracts and reviews bank-file beneficiaries before release. This targeted review is more persuasive than an owner approving only the total payment amount.
Common mistake: Two signatures do not establish segregation when both signers rely on the same unchecked schedule or can alter payments after approval.
Official syllabus reference: [1]
25. Walkthroughs, narratives and flowcharts
Narratives describe processing in words, flowcharts show document and system flows, and questionnaires prompt structured enquiries about control objectives and activities. A walkthrough follows a transaction through its initiation, processing, recording and reporting to check understanding and establish whether relevant controls have been implemented. It may reveal missing handoffs or inconsistent descriptions. A walkthrough of one transaction does not usually establish operating effectiveness throughout the year. Choose a recording method that makes responsibilities, documents, interfaces and exceptions clear, and corroborate staff explanations with observation and inspection rather than treating questionnaire answers as verified evidence.
Worked example: A sales walkthrough traces an order through credit approval, dispatch, invoicing and ledger posting. The flowchart reveals that dispatches entered after 5 p.m. bypass the daily invoice interface, prompting consideration of revenue completeness and cutoff risks.
Common mistake: A completed internal control questionnaire records answers; it does not by itself prove that controls exist or operated effectively throughout the period.
Official syllabus reference: [1]
26. Design, implementation and operating effectiveness
Control design asks whether a control could prevent, detect or correct the relevant misstatement if performed properly. Implementation asks whether it exists and is being used. Operating effectiveness asks whether it functioned consistently, by appropriate people or systems, during the relevant period. Enquiry alone is insufficient to establish operating effectiveness. Inspection, observation and reperformance provide different evidence, each with limitations. Test controls when planning reliance or when substantive procedures alone cannot provide sufficient appropriate evidence. Deviations require investigation and reassessment of reliance, considering their cause, frequency and possible financial statement effects.
Worked example: A monthly bank reconciliation is well designed and January's reconciliation exists. To rely on it throughout the year, the auditor examines selected months, timely independent review and resolution of differences, and reperforms relevant calculations rather than relying on the January example.
Common mistake: Finding a control document proves neither consistent operation nor effective review, especially when signatures were added late or exceptions remain unresolved.
Official syllabus reference: [1]
27. Sales controls from dispatch to ledger
Sales controls should address authorized customers and terms, complete and accurate invoicing, correct recording and collection. Credit approval reduces exposure to unsuitable customers but does not establish that revenue occurred. Sequential dispatch records reconciled to invoices help address completeness, while matching invoices to dispatch evidence supports occurrence and quantity accuracy. Price-master access and approval affect accuracy. Cutoff controls connect dispatch and contractual performance dates to the accounting period. Control tests should specify the source population and attribute tested, because tracing invoices backward answers a different question from tracing dispatches forward.
Worked example: An auditor selects dispatch notes and checks that each produced an invoice in the correct period. For selected invoices, the auditor separately checks dispatch evidence and approved prices. The two directions address different risks despite using some of the same documents.
Common mistake: Credit approval is not evidence that goods were delivered, and a complete invoice sequence cannot reveal dispatches that were never invoiced.
Official syllabus reference: [1]
28. Purchasing controls and capital expenditure authorization
Purchasing controls connect genuine business needs, authorized orders, receipt of goods, valid invoices and approved payment. Three-way matching compares orders, goods received records and invoices, while unmatched receipt reports help identify liabilities not yet invoiced. Supplier-master changes need independent authorization to reduce diversion risk. Capital expenditure adds controls over investment approval, asset-register updates and authorized disposals, because ordinary purchase approval may not address long-term asset accountability. Test authorization before commitment and evidence of receipt before payment. Distinguish control recommendations from substantive procedures that independently verify recorded purchases or asset balances.
Worked example: A factory buys machinery through its normal purchasing system. Besides matching the invoice to delivery and the order, controls require approval within the capital budget, entry into the fixed asset register and separate authorization before an old machine is sold.
Common mistake: An approved invoice does not prove receipt, appropriate capital authorization or correct recording of the asset in the fixed asset register.
Official syllabus reference: [1]
29. Payroll master-file controls and authorized changes
Payroll controls address genuine employees, authorized pay rates, accurate time or output data, correct calculations and valid payments. Human resources should authorize starters, leavers and contractual changes independently of payroll processing where feasible. Restricted master-file access, change reports and independent review reduce ghost-employee and unauthorized-rate risks. Reconciliations between personnel records, payroll and bank payment files address different stages of the process. Test changes against approved source documents and inspect timely exception resolution. A stable monthly total does not establish accuracy because offsetting changes or small recurring unauthorized payments may remain hidden.
Worked example: A payroll clerk changes an employee's bank account. A control requires independent verification using established contact details and approval before the next payment file. The auditor tests selected changes against verification records and checks that review occurred before payment release.
Common mistake: Recalculating net pay tests arithmetic but does not establish that the employee exists, the salary is authorized or the bank account is valid.
Official syllabus reference: [1]
30. Inventory custody, movements and count controls
Inventory controls protect physical stock and maintain reliable quantity records. Restricted access, documented receipts and issues, authorized adjustments and reconciliations between perpetual records and counts address different risks. Count instructions should define responsibilities, movement control, identification of damaged or third-party goods and procedures for resolving differences. Independent counting reduces the risk that custodians conceal shortages. Goods in transit and stock held externally require clear ownership and recording arrangements. A well-run count supports quantities but does not alone establish ownership or recoverable value, which require additional records and evaluation.
Worked example: During a count, warehouse dispatches continue without a movement log. The same pallets could be counted twice or omitted. Freezing movements or recording and reconciling every movement would improve count reliability, while independent investigation is needed for unexplained differences.
Common mistake: A stock count can support physical existence while leaving ownership, obsolete items and goods moving around the count date unresolved.
Official syllabus reference: [1]
31. Bank reconciliations and payment release controls
Bank reconciliations compare the cash book with independent bank information and explain timing differences and errors. Effective controls include timely preparation, independent review, investigation of unusual reconciling items and correction of genuine errors. Payment controls separately address authorized beneficiaries, amounts and release permissions. A reconciliation cannot prevent every unauthorized payment if the reviewer accepts it as a valid cash-book entry. Inspect whether old outstanding items clear and whether review is sufficiently detailed. Bank access, payment preparation and reconciliation should be separated or supported by targeted compensating review.
Worked example: A reconciliation contains an outstanding deposit for three months. A reviewer should inspect the original receipt and later bank entries rather than repeatedly carrying it forward. The item could reflect an error, misappropriation or an unsupported cash balance.
Common mistake: A reconciliation that mathematically agrees is not necessarily effective when stale items are unexplained or unauthorized payments are accepted without challenge.
Official syllabus reference: [1]
32. General IT controls and processing controls
General IT controls support the reliable operation of systems through areas such as access management, program changes and IT operations. Information processing controls address transactions directly, including validation, authorization, calculations and interface reconciliations. An automated processing control may operate consistently only if relevant access and change controls protect its configuration. Assess the dependency rather than assuming all IT weaknesses affect every application equally. Test who can change the control, whether changes are approved and whether it operated during the reliance period. One successful test today does not establish uninterrupted operation throughout the year.
Worked example: A system rejects invoices above approved purchase-order quantities. If purchasing staff can alter the tolerance without review, the auditor examines configuration history and access rights before relying on the rejection control, even when a demonstration currently rejects an excessive invoice.
Common mistake: Automation reduces some manual errors but does not remove risks from unauthorized configuration changes, incomplete interfaces or excessive privileged access.
Official syllabus reference: [1]
33. Communicating deficiencies with consequences and remedies
A useful control finding states the observed deficiency, explains the risk or consequence and recommends a proportionate remedy. Significant deficiencies merit timely written communication to those charged with governance, with other appropriate communication to management. Significance depends on the likelihood and potential magnitude of misstatement and the importance of the control, not merely whether an error has already occurred. Recommendations should identify a workable responsibility, action and timing. Avoid promising that implementing recommendations will eliminate all fraud. A financial statement audit evaluates controls for audit purposes rather than expressing an overall control opinion unless separately engaged.
Worked example: A report states that supplier bank changes lack independent review, allowing payments to be redirected. It recommends verification through established supplier contacts and approval by someone outside payment preparation before changes become effective, rather than vaguely requesting 'stronger supplier controls'.
Common mistake: A recommendation without a stated deficiency and consequence leaves governance unable to judge why the change matters or how urgently to act.
Official syllabus reference: [1]
34. Internal audit scope, objectivity and outsourcing
Internal audit evaluates and helps improve governance, risk management and control, with work that can include financial, operational, compliance and value-for-money assignments. Its scope differs from external audit's financial statement opinion. Organizational status, unrestricted access and direct communication with appropriate governance bodies support objectivity. Outsourcing can provide expertise and flexibility but introduces provider independence, confidentiality, continuity and cost considerations. Management retains responsibility for controls and decisions. An internal auditor should not evaluate operational responsibilities it owns without addressing the resulting conflict. Terms of reference should define scope, authority, reporting and follow-up arrangements.
Worked example: Trustees commission an economy, efficiency and effectiveness review of a community transport service. The internal auditor compares procurement costs, vehicle use and achieved service outcomes, reports directly to trustees and recommends improvements without taking over daily dispatch decisions.
Common mistake: Outsourcing internal audit does not transfer governance accountability to the provider or make it acceptable for the provider to audit its own decisions.
Official syllabus reference: [1]
Audit evidence
35. Assertions determine the direction of testing
Assertions express the claims embedded in financial statements, including occurrence or existence, completeness, accuracy or valuation, rights and obligations, cutoff, classification and presentation. Procedure direction matters. Starting with recorded assets and inspecting them mainly addresses existence; starting with independently identified assets and tracing them into records mainly addresses completeness. One procedure may support several assertions but rarely all equally. Select evidence that can reveal the suspected error rather than merely producing documents related to the account. Rights and valuation often need contracts or estimates beyond physical inspection.
Worked example: An auditor selects machines from the asset register and locates them on the factory floor to test existence. To identify unrecorded machines, the auditor selects items observed on the floor and traces them back into the register.
Common mistake: Inspecting a physical asset does not automatically establish ownership, correct valuation or completeness of the entire asset population in the records.
Official syllabus reference: [1]
36. Sufficiency, appropriateness and evidence reliability
Sufficiency concerns evidence quantity; appropriateness concerns relevance and reliability. Higher risk generally requires more persuasive evidence, but obtaining more poor-quality evidence cannot necessarily compensate for its weakness. Independent external evidence and evidence obtained directly by the auditor are often more reliable, subject to circumstances and authenticity. Inspection, observation, enquiry, confirmation, recalculation, reperformance and analytics support different conclusions. Observation is limited to the time observed, and enquiry usually needs corroboration. Evaluate entity-produced information for accuracy, completeness and suitable detail before relying on it to perform an audit procedure.
Worked example: A manager's verbal assurance that all bank accounts are disclosed is less persuasive than auditor-controlled bank confirmation supported by ledger review and account-opening records. Yet the confirmation process must still use reliable contact details and investigate unexpected responses.
Common mistake: An external-looking document is not automatically reliable, and collecting many copies of the same unsupported claim does not create independent corroboration.
Official syllabus reference: [1]
37. Sampling, selection risk and projected errors
Audit sampling applies procedures to less than the whole relevant population so that selections support conclusions about that population. Define the population, sampling unit, objective and selection method before choosing items. Sampling risk means the sample conclusion may differ from the conclusion from testing everything; non-sampling risk includes inappropriate procedures or misinterpreting evidence. Specific-item selection is useful but does not automatically support projection to untested items. Investigate errors, project where appropriate and evaluate sampling risk and tolerable misstatement. Stratification can improve efficiency when populations contain different value or risk groups.
Worked example: A representative sample contains $6,000 overstatement in $120,000 of recorded expenditure. Under an explicitly chosen ratio method, the 5% rate projects to $30,000 in a $600,000 population, with further evaluation needed for sampling risk and error causes.
Common mistake: Testing only the largest invoices does not produce a representative sample of all remaining invoices or justify projecting its results indiscriminately.
Official syllabus reference: [1]
38. Substantive analytical procedures need precise expectations
A substantive analytical procedure can provide evidence when a sufficiently predictable relationship supports a precise expectation and the underlying data are reliable. Develop the expectation, decide an acceptable difference, compare recorded amounts and investigate unexplained differences with corroborating evidence. Disaggregated monthly or product-level analysis may reveal issues hidden in annual totals. Predictability differs by account: payroll for stable salaried staff may be more predictable than litigation expense. Planning analytics identify risk, whereas substantive analytics are deliberately designed to obtain evidence about assertions. Management's explanation alone does not resolve a significant variance.
Worked example: A business has 40 employees each earning $3,000 monthly for all twelve months, with no bonuses or other payroll costs. Expected salary expense is $1,440,000. A recorded $1,500,000 requires investigation of the $60,000 difference using reliable personnel and payroll records.
Common mistake: Comparing this year with last year is not automatically substantive evidence when no precise expectation, reliable data or variance investigation exists.
Official syllabus reference: [1]
39. Inventory attendance separates quantity from valuation
At inventory attendance, auditors evaluate count instructions, observe procedures, inspect stock and perform test counts. Record-to-floor selections address existence, while floor-to-record selections help address completeness. Record identifying details so test counts can be reconciled to final inventory records. Consider movements, third-party stock and damaged or obsolete items. Attendance primarily supports quantities and condition; ownership and valuation require additional evidence. Under a lower-of-cost-and-net-realizable-value policy, compare cost with selling price less relevant completion and selling costs. Counts at a different date require evidence connecting quantities to the reporting date.
Worked example: A product costs $50 and is expected to sell for $57, but requires $4 completion and $6 selling costs. Net realizable value is $47, so a $3 write-down per unit is needed under the stated policy despite the price exceeding cost.
Common mistake: Observing that stock exists does not show that its recorded cost is recoverable or that all stock on site belongs to the entity.
Official syllabus reference: [1]
40. Receivables confirmations and recoverability
Auditor-controlled confirmations can support receivable existence and aspects of accuracy, but responses and exceptions require evaluation. Maintain control over request preparation, dispatch and receipt to reduce interception risk. A non-response provides no agreement and needs alternative procedures, such as matching subsequent receipts to specific year-end invoices and inspecting delivery records. Confirmation does not by itself establish recoverability. Evaluate ageing, disputes, credit notes, customer difficulties and relevant forward-looking information when assessing expected losses under the applicable framework. Distinguish a genuine collection risk from a pricing error that requires adjustment to revenue or the receivable.
Worked example: A customer confirms $90,000 but pays only $60,000 after entering financial difficulty. The confirmation supports the balance's existence, while the remaining $30,000 still requires a recoverability assessment using liquidation information, security and expected distributions.
Common mistake: A confirmed receivable is not necessarily collectible, and a later receipt must be matched to the relevant invoices before it supports year-end amounts.
Official syllabus reference: [1]
41. Searching for unrecorded payables and accruals
Liability testing often emphasizes completeness because omitted obligations overstate profit and net assets. Search outside the year-end payable listing using subsequent payments, invoices received later, unmatched goods received notes and supplier statements. Determine whether the underlying goods or services were received before year end; payment date alone does not decide recognition. Reconcile supplier statements and investigate differences rather than assuming the client's ledger is complete. Accrual estimates need evidence of the service period and amount. Procedures should also identify cutoff errors and double counting between invoices and accrued liabilities.
Worked example: A February payment settles repairs completed in December, but no payable or accrual appears at year end. Inspection of the service report and invoice supports a December obligation, so the auditor evaluates an adjustment despite the later invoice and payment dates.
Common mistake: Selecting only recorded payables cannot reliably identify omitted liabilities, and a post-year-end payment is not automatically a current-year expense.
Official syllabus reference: [1]
42. Non-current asset recognition, depreciation and impairment
Audit non-current assets by distinguishing valid additions, repairs, disposals, depreciation or amortization, and impairment. Inspect invoices and the nature of expenditure rather than accepting management's account coding. Physical inspection supports tangible asset existence, while contracts and title records support rights. Recalculate depreciation using supported cost, residual value, useful life and availability for use. Intangible asset recognition requires the relevant framework's criteria; a budget or management intention alone is insufficient. Impairment indicators require assessment of recoverability, not simply continued application of the original useful life. Reconcile movements to the opening and closing register.
Worked example: A machine costs $120,000, has a supported $20,000 residual value and a five-year straight-line useful life. Annual depreciation is $20,000 before considering timing. A separate routine servicing invoice is examined as an expense rather than added automatically to machine cost.
Common mistake: A large payment is not necessarily capital expenditure, and an asset's physical presence does not prove that its carrying amount remains recoverable.
Official syllabus reference: [1]
43. Bank balances, borrowings and equity movements
Cash work combines bank confirmations, bank reconciliations and testing of reconciling items, with attention to restrictions and undisclosed accounts. Confirmations can also identify loans, security and guarantees. Borrowing work includes agreements, interest recalculation, covenant assessment and appropriate presentation under the applicable framework. Equity movements require evidence such as authorized resolutions, issue documentation, statutory records where applicable and receipt of proceeds. Trace transactions across records rather than relying on a single balance confirmation. Distinguish a genuine timing difference from an error requiring correction, and assess whether financing terms create disclosure or going concern implications.
Worked example: A bank confirms a $500,000 loan secured on property. The auditor inspects the agreement, recalculates interest, tests covenant compliance and checks presentation and security disclosures. The confirmation alone does not establish that every financing-related disclosure is complete.
Common mistake: Agreement between bank and ledger balances does not establish correct borrowing classification, covenant compliance or complete disclosure of guarantees and security.
Official syllabus reference: [1]
44. Accounting estimates, provisions and contingent liabilities
Accounting estimates require evaluating management's method, significant assumptions and data, with attention to uncertainty and possible bias. Auditors may test management's process, use relevant subsequent events or develop an independent estimate or range. Provisions and contingent liabilities require distinguishing recognized obligations from matters needing disclosure under the applicable framework. Legal correspondence, contracts and claims histories help evaluate completeness and measurement. A reasonable estimate is not necessarily the single most likely number an auditor prefers. Consider whether disclosures adequately explain uncertainty and whether patterns of optimistic assumptions suggest management bias across multiple estimates.
Worked example: A warranty provision assumes 2% of units will need a $40 repair. For 10,000 units, the base calculation is $8,000. The auditor also tests unit data, recent claim rates, repair costs and product changes before accepting the estimate.
Common mistake: Correct spreadsheet arithmetic cannot make an estimate reasonable when its claim rate, population, repair cost or underlying obligation is unsupported.
Official syllabus reference: [1]
45. Automated tools, population integrity and exceptions
Automated tools and techniques can examine full populations for duplicate payments, unusual journals, sequence gaps and unexpected relationships. Their value depends on an appropriate objective and complete, accurate input data. Reconcile extracted totals to source systems, inspect field definitions and assess transformations before trusting results. An exception is a lead requiring investigation, not automatically a misstatement. Full-population analysis can remove sampling risk for the specific attribute tested, while leaving risks from missing data, poor rules and interpretation. Test data used to assess controls must be authorized and designed to avoid corrupting live records.
Worked example: A duplicate-payment query matches supplier ID, invoice number and amount. It flags a repeated invoice, but inspection shows one entry is a reversal. The auditor investigates document and posting references before deciding whether the exception represents an actual overpayment.
Common mistake: Testing every row does not establish that every relevant transaction was extracted or that the programmed rule addresses the intended audit assertion.
Official syllabus reference: [1]
46. Using experts without transferring audit responsibility
Specialist knowledge may be needed for valuations, actuarial calculations or other technical matters outside ordinary audit expertise. Distinguish management's expert, whose work supports management's accounting, from an auditor's expert assisting the audit. Evaluate relevant competence, capabilities and objectivity, understand the scope and assess the work's adequacy for the audit purpose. Examine significant assumptions, methods and source data where relevant. A qualification does not establish that a particular report addresses the correct asset or restrictions. The auditor remains responsible for the audit opinion and cannot resolve contradictory evidence merely by citing the specialist.
Worked example: A property valuer assumes unrestricted commercial use, but a deed limits the building to education. The auditor questions the assumption and seeks appropriate revised evidence, even though the valuer is qualified and the report appears professionally prepared.
Common mistake: An expert's reputation does not remove the need to assess the report's scope, assumptions and consistency with other available audit evidence.
Official syllabus reference: [1]
47. Internal auditors and service-organization evidence
When considering internal audit work, evaluate the function's objectivity, competence and systematic, disciplined approach, then assess the specific work's relevance and quality. The external auditor retains responsibility and performs sufficient evaluation rather than copying conclusions. Service organizations create a different evidence issue: outsourced processing remains part of the user entity's reporting system. Understand the services and relevant user controls, and assess whether available service-auditor reporting addresses design alone or operating effectiveness over a suitable period. Neither outsourcing nor another auditor's report automatically supplies evidence over the client's complete financial statement assertions.
Worked example: Payroll is processed externally. A report describes the provider's controls at one date, but the client relies on operation throughout the year. The auditor considers the report's coverage, additional evidence and the client's own approval and reconciliation controls before deciding reliance.
Common mistake: A service provider's assurance report is not an audit opinion on the client's payroll expense, and internal audit work does not eliminate external audit responsibility.
Official syllabus reference: [1]
48. Not-for-profit income completeness and restrictions
Not-for-profit audits apply normal assurance principles to funding structures that may make completeness difficult. Cash donations can disappear before recording, so testing recorded income to deposits may miss the main risk. Use independent event records, sequential receipts, collection logs and reconciliations where available. Grants and restricted donations also require examination of agreements, eligibility conditions, recognition and presentation under the applicable framework. Consider whether funds are restricted to particular purposes and whether expenditure meets those terms. Volunteer staffing or a charitable mission does not remove fraud risk, documentation needs or the requirement for sufficient appropriate evidence.
Worked example: A charity records only amounts collectors deposit. The auditor traces independently recorded fundraising events and signed collection sheets to bankings and the ledger, then inspects a restricted education grant to determine whether its conditions and presentation have been handled appropriately.
Common mistake: A bank deposit proves that cash reached the bank; it does not establish that every donation collected was deposited or recorded.
Official syllabus reference: [1]
Review and reporting
49. Subsequent events and the conditions-at-year-end test
Subsequent events work identifies events requiring adjustment or disclosure between the reporting date and the auditor's report date. Under the usual accounting distinction, adjusting events provide evidence about conditions existing at year end; non-adjusting events concern conditions arising later, with material disclosure considered. Procedures include enquiries, minutes, interim financial information and legal or financing developments. Responsibilities change after the report date: there is no general duty to keep performing procedures indefinitely, but relevant facts becoming known require consideration and appropriate action. Separate the event's discovery date from the date of the underlying condition.
Worked example: A customer becomes insolvent in February after severe December financial difficulties, providing evidence about the year-end receivable. By contrast, a factory destroyed by a wholly new February incident generally raises a later-event disclosure issue rather than a December asset adjustment.
Common mistake: Classifying every event after year end as non-adjusting ignores whether it reveals a condition that already existed at the reporting date.
Official syllabus reference: [1]
50. Going concern basis, uncertainty and forecast evidence
Management assesses whether the going concern basis is appropriate and prepares relevant disclosures; the auditor evaluates that assessment and the supporting evidence. Distinguish an inappropriate basis from an appropriate basis accompanied by a material uncertainty. Test cash forecasts, financing availability, covenant compliance and the feasibility of management's plans, considering downside scenarios and contradictory evidence. An intention to obtain finance is weaker than an enforceable available facility. Use the assessment period required by the applicable framework and examinable requirements. Reporting depends on the basis, evidence and disclosure conclusions rather than on a single liquidity ratio.
Worked example: A forecast shows a $70,000 shortfall after available facilities. Management proposes selling equipment, but no buyer exists and the equipment is essential to production. The auditor challenges both the timing and feasibility of the plan and evaluates the resulting uncertainty and disclosures.
Common mistake: A disclosed material uncertainty does not automatically require an adverse opinion, while disclosure cannot repair an inappropriate going concern accounting basis.
Official syllabus reference: [1]
51. Written representations support but do not replace evidence
Written representations confirm specified management responsibilities and relevant statements made during the audit. Obtain them from people with appropriate responsibility and knowledge, covering the relevant financial statements and period and dated appropriately in relation to the report. They are necessary evidence for specified matters but are insufficient alone where other evidence should reasonably exist. Contradictions require investigation, and refusal or doubts about management integrity can affect evidence reliability and the audit opinion. A representation that all liabilities are recorded cannot replace a search for unrecorded liabilities or evaluation of legal claims.
Worked example: Management signs a statement that there are no undisclosed guarantees. Board minutes mention support for a subsidiary's bank loan. The auditor inspects the agreement and investigates the inconsistency rather than treating the signed letter as stronger than the contradictory documentary evidence.
Common mistake: A representation letter does not transfer management's responsibilities to the auditor or compensate automatically for missing contracts, confirmations or other necessary evidence.
Official syllabus reference: [1]
52. Final review and accumulated uncorrected misstatements
Final review evaluates whether sufficient appropriate evidence supports the conclusions and whether the financial statements as a whole are consistent with the auditor's understanding. Perform overall analytical review, inspect presentation and disclosures, reassess materiality and evaluate accumulated uncorrected misstatements individually and together. Consider qualitative effects, prior-period matters and patterns suggesting bias, not only net arithmetic. Request correction and communicate relevant uncorrected matters appropriately. Review unresolved points and evidence contradictions before reporting. A collection of individually small errors may be material in aggregate, and errors affecting different disclosures cannot always be sensibly offset.
Worked example: Three uncorrected errors overstate profit by $45,000, $55,000 and $60,000. Their $160,000 aggregate exceeds the scenario's $150,000 overall materiality, even though each is smaller. The auditor also considers whether the errors share a biased accounting approach.
Common mistake: Signing off each account separately does not establish that the financial statements as a whole are fairly presented or free from aggregate material misstatement.
Official syllabus reference: [1]
53. The unmodified auditor's report and its responsibilities
An unmodified report communicates the auditor's opinion on the financial statements under the applicable framework. Its structure identifies the audited statements, opinion and basis, and explains management's and the auditor's respective responsibilities, with additional sections as applicable. Independence and compliance with relevant ethical requirements support the basis for opinion. The auditor's responsibilities explain reasonable assurance, material misstatement and the nature of an audit rather than promising certainty. Understand each section's function so scenario facts can be placed correctly. An unmodified opinion does not imply that no findings were reported privately to governance.
Worked example: An audit finds a corrected inventory error and a control deficiency communicated to the audit committee. If sufficient evidence supports the corrected statements, an unmodified opinion may still be appropriate; the control finding does not automatically modify the financial statement opinion.
Common mistake: An unmodified opinion does not certify that controls are flawless, every accounting entry is correct or the entity will remain commercially successful.
Official syllabus reference: [1]
54. Qualified, adverse and disclaimer decisions
First distinguish an identified material misstatement from an inability to obtain sufficient appropriate evidence. For identified misstatement, material but non-pervasive effects lead to qualification, while material and pervasive effects lead to an adverse opinion. For insufficient evidence, material but non-pervasive possible effects lead to qualification, while material and pervasive possible effects lead to disclaimer. Pervasiveness concerns breadth or fundamental significance, not a universal percentage. Explain the matter in the relevant basis section. A modification is not selected merely because management is difficult or because an audit issue required extensive work.
Worked example: A material inventory valuation error confined to one balance may justify qualification. If records are unavailable across dominant assets and related results, the possible effects may be pervasive, leading to disclaimer because the problem is insufficient evidence rather than proven misstatement.
Common mistake: Adverse and disclaimer are not interchangeable stronger qualifications: one concerns established pervasive misstatement, while the other concerns pervasive possible effects of missing evidence.
Official syllabus reference: [1]
55. Key audit matters, emphasis of matter and other matter
Key audit matters, where reporting is required or otherwise applicable, are selected from matters communicated to governance that required significant auditor attention and were of most significance in the audit. An emphasis of matter draws attention to a matter appropriately presented or disclosed in the statements that is fundamental to users' understanding. An other matter concerns understanding the audit, auditor's responsibilities or report and is outside the statements. None substitutes for a necessary modification or required going concern reporting. Distinguish why the communication is needed before choosing a report section.
Worked example: A complex revenue estimate demanded substantial audit attention and may be a key audit matter where applicable. A separately disclosed exceptional event might warrant emphasis if fundamental to understanding, but neither section can repair a materially misstated revenue figure.
Common mistake: A key audit matter is not a separate opinion, and emphasis of matter cannot be used to avoid qualifying materially misstated statements.
Official syllabus reference: [1]
56. Other information and material inconsistency
Other information, such as narrative sections of an annual report, may contain statements inconsistent with the audited financial statements or the auditor's knowledge. The auditor reads and considers that information; this does not ordinarily extend the financial statement opinion to all narrative content. Investigate apparent material misstatements and determine whether the problem lies in the statements, other information or the auditor's understanding. Discuss correction with management and governance and consider the appropriate reporting consequences. A discrepancy should not be dismissed merely because it appears outside the financial statement notes.
Worked example: The annual report claims revenue increased 25%, while the audited statements show 8%. The auditor checks definitions and source data, then requests correction if the narrative is materially misleading rather than automatically modifying the financial statement opinion.
Common mistake: Reading other information is not an audit of every narrative claim, but it still creates responsibilities when material inconsistencies or misstatements appear.
Official syllabus reference: [1]
Employability and technology skills
57. Exhibit navigation and requirement-to-evidence mapping
Digital audit tasks require extracting relevant facts from multiple exhibits without losing the relationship between a requirement and its evidence. Identify the required output, entity, period and requested perspective before selecting material. Keep source labels and distinguish facts from assumptions so conclusions can be traced. Navigate between exhibits and response tools deliberately, checking whether later information changes an earlier interpretation. This mirrors workplace evidence management: a well-written conclusion can still be wrong if it uses the wrong period, entity or draft document. Preserve unresolved inconsistencies rather than silently choosing the most convenient version.
Worked example: A loan exhibit shows a revised repayment date, while an earlier management memo uses the original date. The candidate identifies the signed amendment, uses it in the liquidity analysis and explains the discrepancy instead of combining incompatible assumptions from both documents.
Common mistake: Copying every exhibit fact into a response does not demonstrate analysis and can conceal that the answer addresses the wrong requirement or period.
Official syllabus reference: [1]
58. Spreadsheet formulas, references and controlled filtering
Spreadsheet analysis should preserve source data, use transparent formulas and reconcile results to control totals. Relative references change when copied; absolute references anchor a fixed cell or range. Multi-field tests, such as supplier plus invoice number, often identify exceptions more accurately than a single field. Sorting must keep complete rows together, and filters must not silently exclude relevant records from totals or conclusions. Test formulas on known cases and inspect blanks, text-formatted numbers and sign conventions. A correct formula applied to an incomplete range still produces a misleading result.
Worked example: A duplicate test uses COUNTIFS on both supplier ID and invoice number, with absolute source ranges and relative row criteria. The analyst checks a known duplicate and a same-number invoice from another supplier, then reconciles row counts before and after filtering.
Common mistake: A plausible spreadsheet total is not enough: omitted rows, broken sorting and copied formulas with shifting ranges can all create convincing but incorrect results.
Official syllabus reference: [1]
59. Professional written responses with assessable procedures
A professional audit response connects the relevant fact to its implication and the action or conclusion required. For procedures, specify the action, evidence source and purpose: 'inspect subsequent bank receipts and match them to year-end invoices' is assessable, while 'check receivables' is not. Use concise paragraphs or tables where they improve comparison, and avoid repeating the same point in different words. Recommendations should be practicable and assigned to an appropriate role. Digital editing should improve clarity without removing necessary qualifications about assumptions, incomplete evidence or matters requiring further investigation.
Worked example: Instead of writing 'investigate payroll', a response states: 'Select leavers from approved HR records, trace them to payroll removal dates and inspect the next payment run to identify payments after employment ended.' The procedure has a defined source, action and objective.
Common mistake: Long answers do not earn substance through length when they repeat scenario facts or use vague verbs without identifying evidence and purpose.
Official syllabus reference: [1]
60. Presenting reconciliations and exception conclusions
Effective presentation makes calculations and judgments reproducible. Label currency, units, dates and populations; show the bridge from source totals through adjustments to the reported result. Separate confirmed errors from potential exceptions and explain whether figures include or exclude sample items, credits or duplicates. Tables help compare consistent categories, while concise prose explains the decision. Preserve an audit trail to original records and state meaningful limitations without burying the conclusion. Presentation is part of technical accuracy because an unlabeled total or ambiguous sign can cause a correct calculation to support the wrong decision.
Worked example: An exception report shows original purchases of $250,000, one potential duplicate of $8,000 and an investigative total of $242,000. It labels the $8,000 as unconfirmed and identifies the source records, preventing readers from treating the analysis as an approved accounting adjustment.
Common mistake: Removing exceptions from a displayed total without explaining their status can turn a useful investigation schedule into an unsupported assertion of corrected accounts.
Official syllabus reference: [1]