Audit Assertions Explained: How to Map Risks to Procedures Under SA 315

Audit assertions are the bridge between a financial statement line item and the audit work performed on it. They help the auditor move from a broad balance such as revenue, inventory or trade payables to a more precise question: what could be materially wrong, and what evidence would address that risk?

ICAI lists SA 315 in its current Engagement and Quality Control Standards repository. The official SA 315 text explains that management, in representing that financial statements comply with the applicable financial reporting framework, implicitly or explicitly makes assertions about recognition, measurement, presentation and disclosure. The auditor uses those assertions to consider the types of potential misstatement that may occur.

Why assertions matter in a risk-based audit

SA 315 requires risks of material misstatement to be identified and assessed at both the financial-statement level and the assertion level for classes of transactions, account balances and disclosures. Assertion-level assessment matters because it helps determine the nature, timing and extent of further audit procedures.

That means an audit programme should not stop at “test inventory” or “verify revenue.” The useful question is narrower: is the main risk that recorded inventory does not exist, that some inventory is omitted, that it is valued incorrectly, or that ownership is unclear? Each risk points to different evidence.

The three assertion groups under SA 315

1. Classes of transactions and events

• Occurrence: recorded transactions and events actually occurred and pertain to the entity.
• Completeness: transactions and events that should have been recorded were recorded.
• Accuracy: amounts and other data relating to recorded transactions and events were recorded appropriately.
• Cut-off: transactions and events were recorded in the correct accounting period.
• Classification: transactions and events were recorded in the proper accounts.

2. Account balances at period end

• Existence: assets, liabilities and equity interests exist.
• Rights and obligations: the entity holds or controls rights to assets, and liabilities are obligations of the entity.
• Completeness: all assets, liabilities and equity interests that should have been recorded were recorded.
• Valuation and allocation: balances are included at appropriate amounts and related valuation or allocation adjustments are appropriately recorded.

3. Presentation and disclosure

• Occurrence and rights and obligations: disclosed events, transactions and other matters occurred and pertain to the entity.
• Completeness: required disclosures are included.
• Classification and understandability: information is appropriately presented and described and disclosures are clearly expressed.
• Accuracy and valuation: financial and other information is disclosed fairly and at appropriate amounts.

Existence and completeness: the direction of testing matters

One of the most useful practical distinctions is between testing for overstatement and testing for understatement. To address existence or occurrence, an auditor often starts with something already recorded in the books and traces it to supporting evidence. To address completeness, the auditor often starts outside the recorded ledger population and traces source evidence into the books.

For example, selecting trade receivables from the ledger and obtaining external evidence may help address existence. It does not, by itself, prove that every receivable that should have been recorded is present. Similarly, selecting invoices already recorded in the purchases ledger and vouching them may provide evidence about occurrence or accuracy, but it is weak evidence for unrecorded liabilities because omitted items are not in the population being selected.

How to map assertions to practical procedures

Revenue

If the risk is fictitious sales, occurrence is central. Procedures may connect recorded sales to customer orders, dispatch or service evidence, invoices and other relevant evidence. If the risk is recording sales in the wrong period, cut-off becomes important and the auditor may examine transactions around year-end together with the underlying dispatch, delivery or service completion evidence.

Trade receivables

Existence may be addressed through confirmations or other evidence such as subsequent receipts, depending on the circumstances. But a receivable can exist and still be overstated. Valuation and allocation therefore requires separate attention to collectability, ageing, disputes, subsequent receipts and the applicable financial reporting requirements for impairment or allowances.

Trade payables

For payables, completeness is often a major concern because an omitted liability can overstate profit and net assets. A search for unrecorded liabilities may use evidence such as subsequent payments, supplier statements, unmatched receiving records, invoices received after year-end and other source documents to identify obligations that should have been recorded.

Inventory

Physical count work can provide evidence relevant to existence, but physical presence does not prove ownership or correct valuation. Goods held on consignment, third-party stock, damaged items or slow-moving goods may require separate work on rights and obligations and valuation and allocation.

Worked example: a year-end purchase

Assume goods are received on 29 March but the supplier invoice is entered on 3 April. If the reporting date is 31 March, the audit issue is not simply whether the invoice is genuine. The auditor should consider whether the goods and related liability belong in the March year-end financial statements. That brings together cut-off for the purchase transaction and completeness of the closing payable, with the accounting treatment determined under the applicable reporting framework and the underlying facts.

A practical assertion-mapping workflow

1. Start with the financial statement area: identify the class of transactions, balance or disclosure being audited.
2. Write what could go wrong: describe the potential misstatement rather than ticking every assertion automatically.
3. Choose the relevant assertion: map the risk to occurrence, completeness, valuation, cut-off or another applicable assertion.
4. Design the procedure: specify what evidence will be obtained, from which population and in which direction the test will run.
5. Separate assertions when necessary: do not assume one procedure proves existence, rights, completeness and valuation at the same time.
6. Evaluate the result: conclude whether the evidence obtained actually addresses the identified risk and revise the risk assessment or procedures if new information changes the picture.

Common assertion mistakes

• Using the same procedure for every assertion without explaining why it is relevant.
• Vouching items from the ledger and calling that a completeness test.
• Obtaining evidence that a receivable exists but ignoring whether it is recoverable.
• Observing inventory physically but ignoring ownership, condition or valuation.
• Testing numbers in a disclosure but not whether all required disclosures are present or understandable.
• Ticking every assertion for every line item instead of linking procedures to specific risks of material misstatement.

Practical takeaway

Assertions make audit work precise. Identify what could go wrong, map that risk to the relevant assertion, and then choose evidence that directly addresses it. The biggest practical improvement is to stop treating existence, completeness, valuation, cut-off and presentation as interchangeable labels. When the assertion is clear, the direction and purpose of the audit procedure become much easier to defend and document.