Audit Findings vs Observations: What's the Difference?

An exception is a test result

An exception is what a procedure returned: three of twenty-five payments lacked approval. It lives in the workpaper. Exceptions are evidence, not conclusions — several exceptions may roll into one finding, and some exceptions turn out to be explainable and roll into none.

A finding is a control failure with consequence

A finding asserts that a control is missing, poorly designed, or not operating, and that this matters. It carries a rating, a recommendation, an owner, and a due date — and it is tracked to closure.

An observation is an improvement opportunity

An observation notes something worth improving that is not a control failure: an inefficiency, a manual step that could be automated, an inconsistency between sites. It is offered, not required, and typically not tracked to closure with the same discipline.

Why the distinction matters

Everything raised as a finding enters the follow-up register and consumes management attention. Teams that label improvement ideas as findings inflate their issue counts, dilute the serious items, and lose credibility when the register fills with things nobody intends to fix. Teams that label real control failures as observations create the opposite problem — no one has to act.

One useful test: if you would be uncomfortable seeing it closed without evidence, it is a finding.