Launch offer — 25% off with code LAUNCH-25 See plans →
Microlesson · 5-min read

Assertions in Auditing

## Assertions

### Definition

Assertions are representations by management, explicit or implicit, that are embodied in the financial statements. The auditor uses them to identify the different types of potential misstatements that may occur.

### Key characteristics

  • Can be positive ("This asset exists") or negative (absence of something, e.g., no contingent liability exists).
  • Can be explicit (directly stated in the notes) or implicit (inherent in presenting an item).
  • Every figure and disclosure in the financial statements carries multiple assertions simultaneously.

### Why assertions matter

Audit procedures are designed to address specific assertions. The direction and nature of testing must match the assertion being tested (see Relevance topic).

### Common assertion categories

#### For classes of transactions and events (Income Statement items)

AssertionWhat it means
OccurrenceRecorded transactions actually happened
CompletenessAll transactions that should be recorded have been recorded
AccuracyAmounts and data are recorded correctly
CutoffTransactions are recorded in the correct period
ClassificationTransactions are in the right accounts

#### For account balances (Balance Sheet items)

AssertionWhat it means
ExistenceAssets/liabilities actually exist at period end
Rights and ObligationsEntity owns assets / owes liabilities
CompletenessAll balances that should be recorded are recorded
Valuation and AllocationBalances are at appropriate amounts

#### For presentation and disclosure

AssertionWhat it means
Occurrence and rights/obligationsDisclosed events have occurred
CompletenessAll required disclosures are included
Classification and understandabilityInformation is clearly presented
Accuracy and valuationDisclosures are accurate and at appropriate amounts

Worked example

### Example 1

Existence assertion (Balance Sheet): Debtor balance of ₹20 lakh is shown. The assertion is that this customer actually owes money. The auditor sends a confirmation letter to test existence.

### Example 2

Completeness assertion (Income Statement): Management asserts that all sales for the year are recorded. The auditor tests completeness by examining dispatch records for the last few days of the year and checking they are included in revenue.

### Example 3

Cutoff assertion: A sales invoice dated 31 March is recorded as revenue. The assertion is that the sale occurred before year-end. The auditor checks the delivery date to confirm the risks and rewards transferred before year-end.

### Example 4

Valuation assertion: Inventory is stated at ₹50 lakh (lower of cost and NRV). The assertion is that it is correctly valued. The auditor reviews NRV by checking post year-end selling prices.

⚠️ Common exam mistakes

  • Treating 'Existence' and 'Completeness' as the same — Existence tests for overstatement (testing from books outward); Completeness tests for understatement (testing from outside inward).
  • Applying the same procedure to test all assertions — each assertion requires a specifically designed procedure.
  • Forgetting that assertions apply to disclosures and presentation, not just numbers on the face of the statements.
  • Confusing 'Occurrence' (transactions) with 'Existence' (balances) — they are analogous concepts but apply to different financial statement elements.
Reference:
Now that you've read this — what's next?
Move from understanding → mastery in 3 clicks. Each option below picks up from this lesson's topic.
Start 15-min diagnostic