Special Purpose Financial Statements

What are special purpose financial statements?

A mid-tier firm picks up a new client whose lender requires cash-basis FS prepared under a loan covenant. The engagement partner signs off on the terms, the team plans the audit like any other statutory job, and nobody notices the report shipped without an Emphasis of Matter paragraph until the lender's compliance officer phones to ask why it's missing. That phone call is entirely preventable, but it happens often enough to be a running joke at quality review panels.

Special purpose financial statements (SPFS) are prepared under a framework designed for specific users rather than the general public. ISA 800 (Revised) governs their audit. The frameworks include tax bases, cash bases, contractual provisions, and regulatory requirements ( ISA 800 .A2). The file should tell a story about why this particular framework was chosen and who the intended readers are, because if the report ends up in front of someone outside that audience, confusion follows quickly.

ISA 800.6 is clear: all requirements of ISA 200 through 700 apply in full, with only the specific adaptations set out in ISA 800 . What changes is the framework against which the FS are evaluated, not the rigour of the audit itself.

ISA 800.14 requires a mandatory Emphasis of Matter (EoM) paragraph in the auditor's report. This paragraph alerts readers that the FS are prepared under a special purpose framework and may not be suitable for other purposes. It is required on every special purpose engagement. The auditor must also assess the acceptability of the applicable financial reporting framework under ISA 210.6 (a). A contract may specify any framework, but the auditor must independently evaluate whether that framework is acceptable before accepting the engagement.

Worked example: Mertens Bau GmbH

Client: German construction company, FY2025, revenue EUR 38M. Mertens has a syndicated loan facility with BayernLB requiring annual cash-basis FS restricted to the lending syndicate.

Step 1: assess framework acceptability

The engagement partner reviews the loan covenant (clause 14.2) specifying cash-basis presentation with no accruals adjustments. Under ISA 210.6 (a), the team confirms that the framework is acceptable for its intended purpose: the syndicate uses these FS solely to monitor covenant compliance on debt-service coverage and minimum cash balances. The framework would not be acceptable for general purpose reporting, but the intended users do not need IFRS-level disclosure.

Step 2: plan the audit under ISA 800.6

All ISA 200 through 700 requirements apply. The team performs a risk assessment, tests cash receipts and disbursements against bank statements (EUR 26.4M in operating cash flows), and evaluates management's presentation of the cash-basis balance sheet showing net cash of EUR 4.1M. Performance materiality is set at EUR 190,000 (50% of overall mat at EUR 380,000).

Step 3: draft the auditor's report

The report includes the mandatory EoM paragraph under ISA 800.14 , stating that the FS are prepared under the cash basis of accounting specified in the BayernLB loan agreement and are not intended for any other purpose. A restriction on distribution paragraph follows, limiting use to the lending syndicate.

Result: the report clears the lender's compliance review on first submission. Had the EoM paragraph been omitted, the lender would have rejected the report and required reissuance (a situation that, on prior engagements with this syndicate, has triggered a EUR 15,000 rush fee from the auditor's own firm).

Why it matters in practice

The most common error on special purpose engagements is omitting the EoM paragraph required by ISA 800.14 . Teams treat it as optional or forget it entirely. Every special purpose audit report must include this paragraph, regardless of how familiar the intended users are with the framework. On busy desks, the standard report template gets copied from a general purpose engagement and nobody swaps in the ISA 800 wording. That is an engagement quality control failure waiting to surface at the next cold file review.

Teams also fail to evaluate framework acceptability. A contract can specify any financial reporting framework. A loan covenant might require cash-basis statements, or a regulator might prescribe its own reporting format. But the auditor must still assess under ISA 210.6 (a) whether the framework produces FS that meet the needs of the intended users. Accepting a framework without this assessment is an engagement acceptance failure.

Restricted distribution is another area where practice diverges from the standard. When SPFS are intended for a limited group of users, the report should note this restriction. If the statements end up being distributed more broadly than intended, the EoM paragraph becomes even more critical because general users may not understand the framework's limitations. In one engagement we're aware of, a lender-restricted set of cash-basis statements was forwarded to a potential equity investor who read them as IFRS statements and badly mispriced the deal.

Key standard references

• ISA 800.6 (application of ISAs): all requirements of ISA 200 through 700 apply with ISA 800 adaptations only.
• ISA 800.14 (EoM requirement): mandatory paragraph alerting users to the special purpose framework.
• ISA 800 .A2 (framework examples): tax basis, cash basis, contractual provisions, regulatory requirements.
• ISA 210.6 (a) (framework acceptability): the auditor must assess whether the framework is acceptable before accepting the engagement.

Related terms

Related reading

Frequently asked questions