ISA 805: Single-Statement Audits

Financial statement audits usually cover a complete set — statement of financial position, statement of profit or loss, cash flows, changes in equity, notes. ISA 805 (Revised) covers everything smaller: an audit of a single financial statement (a balance sheet on its own, an income statement on its own) or of a specific element, account, or item of a financial statement (a schedule of revenue, a trade-receivables balance, a provision, a statement of compliance with contractual covenants).

The standard’s premise is that assurance should be available at the granularity users actually need. A bank whose covenant turns on a single computed figure does not need — and will not pay for — a full audit; it needs a credible opinion on that figure. A franchisor auditing the royalty base, a grantor verifying eligible project expenditure, a regulator checking one prudential schedule: all are slice-sized questions, and ISA 805 gives auditors a complete methodology for answering them.

What ISA 805 is not: it is not a review, not an agreed-upon-procedures engagement, and not a shortcut. It is a full audit — reasonable assurance, opinion, the ISAs applied — of a smaller subject matter. The assurance level does not shrink with the subject matter; if anything, the tolerances tighten, because materiality is measured against the slice.

ISA 805’s core instruction is compact: apply the ISAs in the 100–700 series as necessary, adapting them to the circumstances. In practice, adaptation concentrates in a few areas. Risk assessment focuses on the assertions relevant to the element — for a revenue schedule, occurrence, completeness, accuracy, and cut-off dominate, while rights and obligations barely feature. The understanding of the entity and its environment narrows to what drives the element, though the auditor cannot ignore the wider business where it affects the slice.

Internal control work targets the controls over the element: the revenue controls for a revenue schedule, the payroll controls for a payroll element. But the auditor stays alert to entity-level weaknesses — a broken control environment contaminates everything, including the slice — and to the interrelationships ISA 805 explicitly calls out: the element’s connections to the rest of the statements.

Evidence procedures are the familiar ISA 500 toolkit aimed at a smaller target: confirmations of the receivables balance, recalculation of the covenant computation, inspection of the contracts behind the revenue schedule. The audit is smaller, not softer — every procedure must still be sufficient and appropriate for a reasonable-assurance opinion on the slice.

This is ISA 805’s most consequential adaptation, and the one that most surprises newcomers. Materiality for the engagement is determined in relation to the single financial statement, element, account, or item being audited — not in relation to the financial statements as a whole. A revenue schedule of AED 40 million is audited to a materiality appropriate to AED 40 million of revenue, which will be a fraction of the materiality for a full audit of the company.

The consequences flow straight into the audit plan. Lower materiality means larger samples, lower tolerable misstatement, more precise analytical procedures, and a lower threshold for accumulating uncorrected misstatements. An element audit can easily involve more intensive testing per dirham of subject matter than a full audit — the slice is small, but the microscope is stronger.

Performance materiality and the clearly-trivial threshold follow the same logic, set against the element. And where the element is itself volatile or judgmental — a provision, a fair-valued item — the auditor sets materiality with that volatility in mind. Companies commissioning element audits should understand this dynamic before negotiating fees: the narrow scope does not automatically mean a narrow price, because the precision demanded is higher.

ISA 805 specifically requires the auditor to consider the element’s interrelationship with the rest of the financial statements, and this is where slice audits most often find their misstatements. Revenue interrelates with receivables, cash, and deferred revenue; a provision interrelates with the events and contracts that created it; a covenant computation interrelates with every input that feeds the ratio.

The practical effect is that the auditor must obtain evidence about related items to the extent necessary to support the opinion on the element. Auditing a revenue schedule properly means getting comfortable with cut-off (which implicates receivables), with refunds and credit notes (which implicate liabilities), and with the contracts that define what counts as revenue. The boundary of ‘the element’ is therefore drawn generously in the planning — the schedule plus everything that could materially misstate it.

Allocations deserve special attention. Where shared costs, central overheads, or group charges are apportioned into the element, the apportionment methodology itself becomes audit subject matter: is the basis reasonable, consistently applied, and adequately disclosed? An element opinion that rests on an arbitrary allocation is an opinion built on sand, and auditors test the allocation as rigorously as the underlying transactions.

ISA 805 engagements often sit alongside a full-statement audit — sometimes by the same firm, sometimes not — and the standards require the two opinions to be reconciled where they interact. The sharpest case: the auditor has audited the complete set of financial statements and modified that opinion (qualified, adverse, or disclaimer). What does that mean for the separate opinion on the element?

The answer turns on relatedness. If the modification relates to the element — the full-set qualification was about revenue recognition and the ISA 805 engagement is a revenue schedule — the auditor must consider whether the element opinion must also be modified, and will typically conclude it must. If the modification is unrelated to the element — the qualification was about inventory valuation and the element is a covenant computation unaffected by inventory — a clean element opinion can stand, but the report should handle the coexistence transparently so readers are not misled.

There is a mirror-image caution for users: a clean ISA 805 opinion on one element is not a clean bill of health for the whole. A bank that receives an unmodified opinion on the covenant computation should not infer the financial statements are unmodified. The report identifies its subject matter precisely to prevent exactly that inference — and readers should respect the boundary the auditor drew.

The ISA 805 report follows the ISA 700 architecture adapted to the slice. It identifies the subject matter with precision — not ‘the financial statements’ but ‘the schedule of revenue of X Company for the year ended...’ or ‘the statement of financial position of Y as at...’ — because precise identification is what stops readers mistaking an element opinion for a full opinion. The opinion paragraph then states whether the subject matter is prepared, in all material respects, in accordance with the applicable financial reporting framework.

The basis-of-preparation description gets more prominence than in a full-set report: the framework (IFRS, or the contractual/regulatory basis) is named, and where the framework is special-purpose, ISA 800’s considerations join the engagement — including the alert that the information may not be suitable for another purpose. Management’s and the auditor’s responsibilities are described in element terms.

Modified opinions work exactly as in ISA 705, applied to the slice: a material misstatement of the element yields a qualified or adverse opinion on the element; inability to obtain sufficient evidence about the element yields a qualification or disclaimer. The Basis for Opinion explains the modification in element terms, quantifying the effect where practicable.

The UAE’s commercial landscape generates slice-sized assurance needs constantly. Bank covenant compliance statements are the most common: a facility agreement requires the borrower to demonstrate, periodically, that financial covenants are met, computed on the agreement’s definitions — and the bank wants an auditor’s opinion on that computation, not a full audit. Royalty and commission audits under franchise, distribution, and agency agreements are close behind: the counterparty’s economics turn on one revenue-like figure.

Project and grant accounting produces more: schedules of eligible expenditure for government or development funding, project cost statements for joint operations, service-charge accounts for jointly owned property. Free-zone entities meet ISA 805 where an authority or a counterparty wants assurance on a single schedule — a revenue declaration, a payroll listing — rather than full statements.

For companies, the commissioning logic is economic: assurance where the decision turns, at a fee proportionate to the question. For auditors, these engagements demand crisp engagement letters — the subject matter, the framework, the intended users, and any use restrictions spelled out — because the narrower the subject matter, the more precisely the boundaries must be drawn. A vague element definition is how slice engagements become disputes.

Evidence in an ISA 805 engagement is the ISA 500 toolkit with the spotlight narrowed and the tolerances tightened. Confirmations go to the element’s counterparties — customers for a receivables element, banks for a cash element. Inspection targets the contracts, agreements, and source documents that define the element. Recalculation verifies computed elements like covenant ratios and royalty bases from first principles. Analytical procedures are sharper than in a full audit because the expectation can be built precisely around the element’s drivers.

Two evidence challenges recur. First, completeness of the element: is the revenue schedule really all the revenue? Completeness assertions are inherently harder than existence ones, and slice engagements must design procedures — reconciliations to the general ledger, to tax filings, to operational data — that address completeness directly rather than assuming it. Second, cut-off: elements measured over a period (revenue, expenditure) live or die on period boundaries, and cut-off testing gets priority commensurate with that risk.

Management’s written representations are tailored to the element: responsibility for the element’s preparation, completeness of information provided about it, and the specific judgments (allocations, estimates) that shape it. Generic representation letters, copied from full audits, miss the element-specific assertions the standard needs evidenced.

ISA 805 acceptance work has a distinctive focus: defining the slice. The engagement letter must identify the single financial statement, element, account, or item with a precision that leaves no room for later argument — ‘the schedule of gross revenue as defined in clause 7 of the franchise agreement’, not ‘the revenue audit’. It names the applicable financial reporting framework (and, where special-purpose, records the ISA 800 acceptability judgment), identifies the intended users, and states any restriction on distribution or use.

Preconditions follow ISA 210 with slice adaptations: management must acknowledge responsibility for preparing the element in accordance with the framework and for the internal control necessary to do so, and must provide the auditor with access to all information relevant to the element — including the related items the interrelationship analysis will reach into. An engagement where management wants the revenue schedule audited but will not open the receivables ledger is not acceptable.

Independence and competence are assessed against the slice: the firm needs the expertise the element demands (a royalty-base audit in a complex licensing structure is not junior work), and threats to independence are evaluated in the engagement’s context. Firms also consider the relationship with any full-set audit — same firm or another — and plan the information-sharing the standards expect.

Users of ISA 805 reports — bankers, franchisors, grantors, regulators — should read them with the slice firmly in mind. The opinion answers one question: is this element prepared, in all material respects, in accordance with the stated framework? It does not answer whether the company is healthy, whether the full statements are fairly presented, or whether the underlying business is sound. Treat the opinion as a precise instrument, not a general character reference.

Check three things beyond the opinion paragraph. First, the subject-matter identification: make sure the element described is the element you care about, defined the way your agreement defines it — a covenant computation on the wrong definition is worse than no computation. Second, the framework: is the basis of preparation the one your decision needs? Third, any emphasis or restriction: an SPF alert or a use restriction tells you the opinion’s travel limits; respect them.

And where the report is modified, read the Basis for Opinion before reacting: a qualification about the element’s measurement may or may not affect your decision, depending on what you needed the element for. A qualified royalty base still tells the franchisor most of what they need; a disclaimed covenant computation tells the bank it needs another way to monitor the facility. The report’s precision is a feature — use it.