Management Assertions: What Are We Actually Testing?

An audit procedure is useful when it answers a defined question about a possible misstatement. “We tested inventory” is less informative than explaining which assertion was at risk and what the evidence addressed.

Start with the statement being made

Assertions describe different ways financial information could be wrong. For transactions, the questions concern occurrence, completeness, accuracy, cut-off, classification and presentation. For period-end balances, they concern existence, rights and obligations, completeness, accuracy/valuation/allocation, classification and presentation. Related disclosures form part of those categories. ASA 315, A188–A191

The infographic groups these into six learning prompts. It is a navigation aid; it does not make every category identical for transactions and balances or replace the applicable financial reporting framework.

One item can raise several different questions

Consider an illustrative inventory item seen in a warehouse. The observation addresses a physical question: is an item present? It does not, on its own, establish that the entity owns the item, that all inventory is recorded, or that the carrying amount is appropriate.

A useful workpaper would separate those questions. Ownership might require examination of contractual arrangements. Valuation might require evidence about cost and the relevant measurement considerations. Each conclusion needs a procedure suited to that question.

Choose the direction deliberately

An illustrative transaction test can begin with an entry in the ledger and examine supporting records to investigate whether the recorded event happened. A completeness test may instead begin with a suitable source population and trace items into the accounting records.

Neither direction is a universal recipe. Define the population, explain why it can answer the risk, and consider what it leaves outside the test. A source list missing relevant items cannot establish that the ledger is complete.

When entity-produced information is used, its reliability—including accuracy, completeness and appropriate detail—must be evaluated for the audit purpose. ASA 500, paragraph 9

Turn an assertion into a procedure

Use a short design chain:

• Risk: what specific misstatement could occur?
• Assertion: which statement about the information would then be wrong?
• Population: what items or information could reveal that error?
• Procedure: what action will obtain relevant evidence?
• Conclusion: what does the result support, and what remains unanswered?

For an illustrative period-end purchase, the question could be whether the expense was recorded in the appropriate period. Simply finding an authorised invoice does not resolve that question. The design must consider the relevant transaction circumstances and accounting criteria, then obtain evidence that addresses timing.

Make the conclusion as precise as the test

Do not convert a successful existence test into a conclusion on every inventory assertion. Explain the extent of the work, exceptions identified and the assertion actually addressed. Evaluate conflicting evidence rather than treating one convenient document as decisive.

This discipline also helps reviewers see gaps: a workpaper can contain many documents while leaving the main risk unanswered.

Bring the business context back in

Assertions connect accounting information to how the business operates: goods move, services are delivered, obligations arise and estimates change. Understanding those events helps the team select evidence that answers the reporting question.

This is an educational map using Australian auditing standards as a primary reference, not an entity-specific audit program. Procedure design and the final conclusion require the circumstances and applicable framework.

Name the risk. Name the assertion. Then choose the evidence.