Specialized Areas and Audit-Related Services
Why this chapter matters: the audit is not the only engagement type
Every chapter so far has assumed the engagement in question is an ordinary audit of general purpose financial statements. This chapter steps outside that assumption entirely, covering engagements that either audit a genuinely different kind of financial information (special purpose frameworks, single financial statements, summary financial statements) or provide a fundamentally different, lower level of assurance than an audit at all (reviews, compilations, agreed-upon procedures) — and the single organising question this whole chapter is built around is: what level of assurance, if any, is this specific engagement providing, and how does that level shape everything about how the engagement is planned, performed, and reported?
SA 800 series: special considerations for audits of special purpose frameworks and specific elements
SA 800: special purpose frameworks. Financial statements can be prepared under a special purpose framework — a financial reporting framework designed to meet the specific financial information needs of specific users, distinct from a general purpose framework designed to meet the common needs of a wide range of users — such as financial statements prepared specifically for tax purposes, or on a cash basis for a specific regulatory return. The auditor's overall objectives when auditing such statements remain the same as for a general purpose audit, but SA 800 requires the auditor to obtain an understanding of the purpose for which the financial statements are prepared, the intended users, and the steps taken by management to determine that the applicable framework is acceptable in the circumstances, and the auditor's report must specifically alert readers that the statements are prepared under a special purpose framework, since a reader unfamiliar with this distinction could otherwise mistakenly assume the statements meet the same broad, general purpose standard an ordinary financial statement audit provides.
SA 805: single financial statements and specific elements. Where the auditor is engaged to report on a single financial statement (such as only a balance sheet, without the complete set of financial statements) or a specific element of a financial statement (a single account balance, such as accounts receivable, audited in isolation), SA 805 requires the auditor to consider whether the specific engagement is practicable in the first place, given that a single financial statement or specific element is typically deeply interrelated with, and cannot always be meaningfully assessed independently of, other elements of a complete set of financial statements — a receivables balance, for instance, cannot always be fully understood or verified in complete isolation from the revenue recognition policies and practices that give rise to it.
SA 810: summary financial statements. Where an entity prepares summary financial statements derived from a complete set of audited financial statements, and engages the auditor to report on them, SA 810 requires the auditor's opinion to address whether the summary financial statements are consistent, in all material respects, with the audited financial statements from which they were derived — a fundamentally different, narrower opinion than an audit opinion on the underlying financial statements themselves, and this distinction (consistency with an already-audited source, rather than a fresh, independent audit opinion of its own) is precisely what a Final-level question on this standard tests.
Assurance versus non-assurance: agreed-upon procedures and compilations
SRS 4400: agreed-upon procedures. In an agreed-upon procedures engagement, the practitioner performs specific procedures that have been agreed between the practitioner and the engaging party (and, typically, any other intended users), and reports the factual findings from performing those procedures — critically, this is not an assurance engagement at all; the practitioner does not express an opinion or a conclusion of any kind, but simply reports what was found from performing the specifically agreed procedures, leaving the reader to draw their own conclusions from those reported factual findings. This is the single most tested conceptual point in this cluster, precisely because it is the sharpest possible contrast to everything else this paper examines: an audit provides reasonable assurance in the form of an opinion; an agreed-upon procedures engagement provides no assurance conclusion whatsoever, only a factual report of findings.
SRS 4410: compilation engagements. In a compilation engagement, the practitioner applies accounting and financial reporting expertise to assist management in the preparation of financial information, without undertaking to obtain any assurance about whether the information is free from material misstatement at all; the practitioner's report explicitly states that no assurance is expressed on the compiled financial information, and the engagement's purpose is fundamentally different from either an audit or a review — it exists to help management prepare information, not to provide any independent check on that information's reliability to any degree.
Review engagements: a genuinely different level of assurance
SRE 2400: engagements to review historical financial statements. A review engagement provides limited assurance, expressed as a negative form of conclusion ("nothing has come to our attention that causes us to believe the financial statements are not prepared, in all material respects, in accordance with the applicable framework"), a materially weaker form of conclusion than an audit's positive form of opinion ("in our opinion, the financial statements present fairly..."). This difference in conclusion form directly reflects the difference in the underlying work performed: a review consists primarily of inquiry and analytical procedures, without the more extensive corroborative procedures (physical inspection, external confirmation, extensive testing of underlying documentation) an audit performs, meaning a review provides meaningfully less assurance than an audit precisely because meaningfully less evidence has been gathered to support it.
SRE 2410: review of interim financial information by the entity's independent auditor. Where the entity's own auditor (not merely any practitioner) performs a review of the entity's interim financial information, SRE 2410 permits this review to draw on the auditor's existing knowledge of the entity obtained through auditing its annual financial statements, allowing a genuinely more efficient interim review than an entirely fresh review engagement with no prior knowledge of the entity would permit, while still providing only the same limited, negative-form assurance conclusion a review inherently provides, regardless of how much prior knowledge the auditor brings to it.
SAE 3400, 3402 and 3420: assurance on prospective information and controls
SAE 3400: examination of prospective financial information. Prospective financial information — forecasts or projections about future periods — inherently carries a level of uncertainty an audit of historical financial statements does not, since it depends on future events and management's own assumptions about what those future events will be, and SAE 3400 accordingly requires the practitioner's report to explicitly state that actual results are likely to differ from the prospective information, since some events and circumstances frequently do not occur as expected, and this uncertainty typically increases the further into the future the prospective period being examined extends.
SAE 3402: assurance reports on controls at a service organisation. This standard governs the report a service organisation's own auditor provides (the Type 1 or Type 2 report already introduced in the earlier planning chapter's discussion of SA 402) — the user auditor relies on this report as evidence about the service organisation's controls, while the service auditor issuing the report under SAE 3402 is providing direct assurance about the service organisation's own control description and, for a Type 2 report, the operating effectiveness of those controls over the specified period.
SAE 3420: assurance engagements to report on the compilation of pro forma financial information in a prospectus. Where a prospectus includes pro forma financial information — illustrating the effect of a significant transaction (such as an acquisition) as if it had occurred at an earlier date, for illustrative purposes — SAE 3420 requires the practitioner to report on whether this pro forma information has been properly compiled on the stated basis, a narrower assurance objective than opining on whether the pro forma figures themselves are "correct" in any absolute sense, since pro forma information is, by its hypothetical, illustrative nature, not something that can be assessed as simply true or false the way historical financial statements can.
The organising theme across this entire chapter
Every engagement type in this chapter differs from an ordinary audit along exactly one, or both, of two dimensions: the subject matter being reported on (a special purpose framework, a single element, summary statements, prospective information, pro forma information, rather than a complete set of general purpose historical financial statements), or the level of assurance provided (limited assurance for a review, no assurance conclusion at all for agreed-upon procedures or compilations, rather than the reasonable assurance an audit provides). A Final-level question testing this cluster is, at its core, always asking you to correctly place a described engagement along these two dimensions before addressing anything else about how it should be planned, performed or reported — precisely the same discipline of settling the right classification before proceeding that has organised nearly every chapter in this qualification.
