From Evidence to Audit Opinion: Can You Trace the Reasoning?

An audit opinion is the result of connected judgments. A large evidence folder does not explain those judgments unless a reviewer can follow the link between the risk, the work performed, the evidence evaluated and the conclusion reported.

Consider an original fictional manufacturer. A sale is invoiced just before year-end, while available delivery information points to the following period. That difference raises a question about the recording period. It does not, by itself, establish a misstatement: the contract, transfer-of-control facts and applicable accounting requirements still need examination.

State the risk precisely

The immediate question is whether revenue was recorded in the appropriate period. It is not simply whether the invoice exists. Identify the relevant assertion, the transactions and period to examine, and why the circumstances could lead to a material misstatement.

A generic instruction to check revenue leaves too much unspecified. A defined risk gives the procedure a purpose and makes it possible to assess what the evidence does—and does not—answer.

Design work that addresses the question

Inspect relevant contract terms and evidence of dispatch, delivery, acceptance or other facts relevant to transfer. Consider the reliability and completeness of the information used to identify transactions around the reporting date.

The precise procedures depend on the arrangement and assessed risk. Repeating invoice totals or checking a ledger-to-invoice match alone would not establish the timing of the underlying transfer. If information conflicts, further work is needed to understand the difference.

Obtain evidence with a defined purpose

In the fictional case, an invoice supports a billing record. A dispatch record may support movement of goods. Customer information may help establish receipt or acceptance. None should be assigned a meaning its content and reliability cannot support.

Where IFRS 15 applies, revenue recognition concerns satisfaction of the performance obligation through transfer of control. Neither invoice date nor physical delivery date is a universal answer for every arrangement. Understand the facts and applicable reporting framework before selecting the recognition date.

Evaluate the evidence together

Assess relevance, reliability and sufficiency for the question. Investigate contradictory evidence rather than silently choosing the most convenient document. Consider whether the result changes the risk assessment, calls for more work or suggests other transactions need attention.

More copies of the same weak source do not necessarily close an evidence gap. Conversely, one isolated exception does not automatically determine the audit opinion. The nature, context and implications of the matter must be evaluated.

Write the supported conclusion

State what the procedures establish about the assertion and what remains unresolved. If an error is identified, consider the correction and any remaining effects. If evidence is unavailable, distinguish that limitation from a known misstatement.

An assertion-level conclusion contributes to evaluating the financial statements as a whole. It is not the opinion itself. Materiality, combined effects, presentation, disclosures and other relevant evidence also matter.

Connect the conclusion to reporting

ISA 700 addresses forming an opinion on the financial statements. Where modification is necessary, ISA 705 distinguishes matters involving established misstatement from inability to obtain sufficient appropriate evidence, with materiality and pervasiveness affecting the reporting decision.

This fictional example does not provide enough information to select an opinion. It demonstrates the reasoning trail a reviewer should be able to inspect. An unmodified opinion is not a guarantee that every transaction is correct, nor is a count of exceptions an opinion-selection formula.

The six links describe a reasoning trail, not a one-way production line. New evidence can require the team to revisit an earlier risk assessment or procedure.

Try the six-link exercise with one audit area: risk, procedure, evidence, evaluation, conclusion, report. At each link, ask what supports the next statement. A missing link identifies a question to resolve before the reporting conclusion is treated as supported.

References include the IAASB 2026 Handbook, particularly ISA 200, ISA 330, ISA 500, ISA 700 and ISA 705, and the IFRS Foundation's IFRS 15 overview for the accounting context. This original fictional case is educational; apply engagement-specific standards, effective dates, the relevant reporting framework and local requirements.

Inside Assurance — Beyond the numbers. Inside the business.