Timedora

Developing a Well-Supported Audit Finding

How to develop and review an evidence-based audit finding that answers its objective, explains its scope and implications, and avoids overstating what is known.

Build and Review the Finding

Build and Review the Finding

A well-supported audit finding explains the difference between an expectation and what the audit found, then communicates why the difference matters. Four elements can help organize that explanation:

  • Criteria: What should happen, and the source of that expectation.

  • Condition: What the audit found, including the scope and extent of the testing.

  • Cause: Why the difference occurred, if established.

  • Effect: The actual or potential impact of the difference.

These elements are useful links in the explanation, not a formula that every finding must fill out in the same way. Include what is needed to answer the audit objective. A finding is complete when its conclusion answers that objective and is supported by evidence.

Work through the payment example

The example finding states that the payment policy requires documented approval before payment. This gives the criterion and identifies its source: the policy. It then reports the condition precisely: 6 of 40 payments tested had no approval record. The number and tested group show the finding’s scope; they do not establish that all payments lacked approval.

Next, interviews and process records indicate that the workflow does not consistently require staff to retain approval. This offers an explanation for the gap, but the wording does not claim the cause has been proven. The effect is framed as increased risk: unauthorized payments may not be detected promptly. It does not say that an unauthorized payment occurred or went undetected. The conclusion is expressly limited to the items tested.

Review before finalizing

Check that the criterion is clear and applies to the activity; the condition is factual; and the evidence supports both the stated extent and the conclusion. Keep cause and effect within what the evidence establishes: use cautious language for an indicated but unverified cause, and distinguish potential impact from an observed outcome. State important limitations so readers can understand what the finding does—and does not—cover.

If a recommendation or action plan is included, it should address the underlying cause when that cause is known. If it is not established, do not present it as fact. The aim is a finding whose reasoning is understandable, whose scope is clear, and whose implications do not exceed the evidence.