Assertions and Designing Substantive Procedures

Learning objectives

By the end of this chapter, you should be able to:

• Explain how financial statement assertions relate to classes of transactions, account balances, and disclosures.
• Link a specific risk of misstatement to the most relevant assertion(s) and the direction of that risk.
• Design substantive procedures that are assertion-led, directionally logical, and capable of detecting material misstatement.
• Distinguish between tests of details and substantive analytical procedures, and select an appropriate mix.
• Evaluate exceptions from substantive work, quantify likely misstatement, and decide appropriate next steps.
• Recognise common assertion–procedure mismatches and correct flawed audit logic.

Overview & key concepts

Financial statements are built from management’s records and estimates. Each line item and disclosure carries an implied claim about what is being reported. These implied claims are commonly described as assertions. Assertions give a practical structure for turning risk into work: what could be wrong, and what evidence would expose it?

Assertions are applied to:

• Classes of transactions and events(for example, sales, purchases, payroll)
• Account balances at the reporting date(for example, inventory, receivables, payables)
• Presentation and disclosures(for example, related party disclosures, accounting policies, commitments)

Assertions and the accounting equation

Most misstatements ultimately distort the accounting equation:

Assets = Liabilities + Equity

• Overstatedassets(for example, receivables not recoverable) usually overstateequitythrough overstated profit.
• Understatedliabilities(for example, missing accruals) usually overstateequitythrough understated expenses.
• Cut-off errors shiftincome/expensesbetween periods and therefore shiftequity(retained earnings) between reporting dates.

Keeping procedures tied to these outcomes makes conclusions more robust.

Core theory and frameworks

Assertion framework used in this chapter

Assertions are often taught as “families” of ideas (existence, completeness, valuation, etc.). Marking, however, typically expects students to show they can apply assertions in three distinct contexts: transactions, balances, and disclosures. The same concepts appear in each context, but with different labels and emphasis.

How the assertion families map to the three contexts

Use the following map to translate the chapter’s language into a format that aligns neatly to exam marking expectations.

Classes of transactions and events

• Occurrence→ “Did the recorded transaction happen and relate to the entity?”
• Completeness→ “Have all transactions that should be recorded been recorded?”
• Accuracy→ “Were amounts and data captured correctly?”
• Cut-off→ “Is the transaction recorded in the correct period?”
• Classification→ “Is it recorded in the correct account/category?”

Account balances at the reporting date

• Existence→ “Does the recorded balance represent something real at the reporting date?”
• Rights and obligations→ “Does the entity control the asset / owe the liability?”
• Completeness→ “Are any balances missing?”
• Valuation (and allocation)→ “Is the balance carried at an appropriate amount (including estimates)?”

Presentation and disclosures

• Occurrence / rights and obligations→ “Do disclosed events/transactions exist and genuinely relate to the entity?”
• Completeness→ “Are all required disclosures included?”
• Classification and understandability→ “Is disclosure appropriately grouped and clear?”
• Accuracy and valuation→ “Are disclosed amounts and narrative explanations consistent with the underlying records and measurement?”

This mapping helps you write answers in whichever terminology you are most comfortable with, while still presenting the categories markers expect.

A one-page map: Assertion ↔ direction ↔ typical procedures

The quickest way to avoid weak audit logic is to match assertion and risk direction to a sensible evidence route.

• Overstatement risks(too high): start from what is recorded andvouch backto supporting evidence.
• Understatement risks(too low): start from source evidence andtrace forwardinto the records.

Common pairings:

• Revenue occurrence (overstatement):ledger invoice → order/terms → dispatch → delivery/acceptance → post year-end returns/credit notes.
• Revenue cut-off (timing):dispatch/delivery around year-end → invoice date/posting date → correct period.
• Revenue measurement (returns/rebates/free goods):promotion terms → pricing/rebate calculations → credit notes/refund activity → liabilities/contra-revenue presentation.
• Payables completeness (understatement):post year-end supplier invoices/GRNs → year-end payables/accruals → general ledger.
• Inventory existence:physical count/third-party confirmation → inventory records.
• Inventory valuation:cost build-up + ageing/obsolescence → selling prices/markdowns/post year-end sales → write-down where needed.
• Receivables valuation:ageing + historical default/recovery + forward-looking factors → post year-end cash/credit notes → allowance adequacy.

Explanations of key assertions (applied, exam-focused)

Existence and occurrence

• Existence (balances):items recorded at the reporting date are real.
• Occurrence (transactions):recorded transactions/events actually happened and relate to the entity.

Typical risk pattern: overstatement (fictitious revenue, inventory that does not exist, receivables that are not real).

Completeness

Everything that should be recorded or disclosed has been included.

Typical risk pattern: understatement (missing payables/accruals, omitted provisions, incomplete disclosures).

Accuracy

Amounts and other data are correctly captured (prices, quantities, dates, customer/supplier, calculations).

Classification

Items are recorded in the correct account/category.

Example:

• Repairs are expensed rather than capitalised(unless they meet capitalisation criteria). Misclassification can distort profit and asset balances.

Valuation

Balances are carried at supportable amounts, including estimates and adjustments.

Valuation work often involves:

• assessing whether assumptions are reasonable,
• checking calculations,
• comparing to subsequent events that provide evidence (cash receipts, sales, write-offs).

Rights and obligations

The entity controls the recorded assets and is responsible for recorded liabilities.

Cut-off

Transactions are recorded in the correct period. Cut-off is about timing, but the correct period often depends on terms, acceptance, and return arrangements, not simply an invoice date.

Presentation and disclosure

Items are properly described, grouped, and disclosed so that users can understand them.

From risk to work: writing the “audit story”

A good procedure starts with a specific worry, not a generic test. Describe the item you are auditing, then write the risk as a short story:

1. What could be misstated?(state the misstatement plainly)
2. Which assertion does that misstatement attack?(for example, completeness for missing liabilities, occurrence for fictitious revenue)
3. Why is this entity exposed to that misstatement?(incentives, complexity, estimates, manual processing, weak oversight)
4. What evidence would make the misstatement hard to sustain?(third-party confirmation, records generated outside finance, subsequent cash/returns behaviour)

If you cannot explain how the evidence would “corner” the misstatement, the procedure is not aimed tightly enough.

Directional testing (choosing the right evidence route)

Directional testing is a logic check:

• If the risk isoverstatement, start with what is recorded andvouch backto independent support.
• If the risk isunderstatement, start with what should exist (source evidence) andtrace forwardinto the records.

This is especially important for:

• Revenue (overstatement)vspayables (understatement),
• assets (overstatement)vsliabilities (understatement).

Writing a procedure that earns marks

A strong substantive procedure is specific enough that another auditor could perform it and reach a defendable conclusion. Use five headings:

• Risk target:the item, period/date, and the assertion you are trying to prove or disprove.
• Evidence route:whether you will vouch back from recorded items (overstatement risk) or trace forward from source evidence (understatement risk).
• What you will test:define the population and what makes items high risk (value, manual processing, unusual terms, proximity to year-end).
• What counts as proof:identify the documents or outputs that directly address the assertion (and what would be unacceptable).
• How you will evaluate results:how you will quantify errors, decide whether they are isolated/systemic, and what extra work you would do if exceptions arise.

Substantive procedures

Substantive procedures are designed to detect material misstatement at the assertion level. They are commonly grouped into:

Tests of details

Direct checking of transactions, balances, or disclosures.

Examples:

• Vouch invoices to dispatch documentation (revenue occurrence).
• Confirm receivable balances with customers (existence).
• Inspect post year-end invoices and match to pre year-end receipts (payables completeness).

Substantive analytical procedures

Using relationships in data to develop expectations and identify differences that require investigation.

For analytical work to be persuasive, it needs:

• a predictable relationship(a sensible basis for expectation),
• reliable data(inputs that can be trusted),
• corroborated investigationof variances.

Explanations must be supported (for example, by source records or independent evidence); otherwise the variance remains an unresolved risk.

Worked example

Narrative scenario

ABC Ltd has a year-end of 31 December 2025.

The records show:

• Revenue: £1,430,000
• Gross margin: 18.4%
• Trade receivables at year-end: £500,000
• Allowance for expected credit losses recorded: £12,000
• Inventory at year-end: £900,000
• Trade payables at year-end: £300,000
• Accrued expenses at year-end: £85,000
• Capital expenditures during the year: £103,000
• Tax rate: 16.1%
• Discount rate: 8.0%

Additional background:

• A bonus scheme is linked to sales growth.
• Sales returns are increasing.
• Manual credit notes are issued after year-end.
• A major promotion ran near year-end: “Buy 10, get 2 free” plus a 5% rebate if annual purchases exceed a threshold.
• Goods were shipped on the last day of the year, with a 30-day return policy.

Required

1. Compute the expected allowance for credit losses using the ageing information provided below.
2. Design substantive procedures for:
   • revenue occurrence and cut-off, and
   • revenue measurement/presentation risks arising from returns, rebates, and free goods.
3. Evaluate inventory valuation work that would be appropriate given the scenario.
4. Assess payables completeness work that would be appropriate given the scenario.
5. Identify and correct assertion–procedure mismatches.

Ageing profile and expected loss rates:

• Current: £280,000 at 1%
• 31–60 days: £120,000 at 3%
• 61–90 days: £60,000 at 8%
• 90+ days: £40,000 at 25%

Solution

1) Expected allowance for credit losses (ageing approach)

Expected allowance = Σ (balance in band × expected loss rate)

• Current: £280,000 × 1% = £2,800
• 31–60 days: £120,000 × 3% = £3,600
• 61–90 days: £60,000 × 8% = £4,800
• 90+ days: £40,000 × 25% = £10,000

Total expected allowance = £21,200

Recorded allowance = £12,000
Potential shortfall = £21,200 − £12,000 = £9,200

Financial statement impact (accounting equation):

• Increasing the allowance by £9,200:
  • reduces assets (receivables net of allowance) by £9,200,
  • reduces profit by £9,200 (higher impairment expense),
  • reduces equity by £9,200 via retained earnings.

Illustrative adjusting entry:

• Dr Impairment loss (profit or loss) £9,200
• Cr Allowance for expected credit losses (contra receivable) £9,200

Exam-safe realism point: An ageing matrix is a useful audit expectation tool, but it should be challenged. Consider whether the loss rates reflect current conditions, include forward-looking factors, and reconcile sensibly to actual write-offs and recoveries.

2) Revenue: procedures split by (a) occurrence/cut-off and (b) measurement/presentation

The scenario contains strong risk indicators: sales-linked bonuses, rising returns, manual credit notes after year-end, complex promotions, and shipments on the last day of the year with return rights. Procedures should address both whether revenue is genuine/timely and whether it is measured and presented correctly.

(a) Occurrence and cut-off (genuineness and timing)

Risk target: Revenue near year-end overstated by recording sales that did not occur, or by recognising revenue in the wrong period.

Evidence route: Overstatement risk → vouch from recorded revenue to independent support.

What you will test (population and selection):

• Sales invoices posted from 18–31 December and 1–7 January.
• Test all invoices abovetolerable misstatement(or another risk-based cut-off linked to performance materiality) and a targeted sample of the remainder focusing on:
  • manual invoices/adjustments,
  • unusual customers,
  • transactions close to rebate thresholds,
  • promotional lines.

What counts as proof (tests of details):

• Agree invoice to customer order/terms (including shipping terms and acceptance points).
• Agree to dispatch documentation (goods-out record/dispatch note).
• Obtain delivery confirmation or customer acknowledgement where available.
• For shipments on 31 December, evaluate whether the terms and evidence support recognition before year-end rather than in the next period.

How you will evaluate results:

• Missing dispatch/delivery/acceptance evidence is an exception.
• Quantify the misstatement per item and assess whether it indicates a wider pattern (especially around 31 December).
• Extend testing if exceptions cluster around specific customers, promotional sales, or manual postings.

Cut-off test using dispatch records (source → ledger for timing accuracy):

• Select dispatches in the last 7–10 days before year-end and first 7–10 days after year-end.
• Trace to sales invoice and posting date to confirm revenue is recorded in the correct period given the shipping/acceptance terms.
• Investigate any invoices dated pre year-end where dispatch/delivery occurred after year-end.

(b) Measurement and presentation (returns, rebates, free goods)

Risk target: Revenue and related liabilities misstated because returns, rebates, and “free goods” are not reflected appropriately in the transaction price, contra-revenue, or refund/contract liabilities.

Evidence route: Measurement/presentation risk → test calculations, terms, and subsequent behaviour (returns/credit notes).

Returns and right-of-return risks:

• Analyse January returns and credit notes and match significant items back to late-December sales.
• For goods shipped on 31 December with a 30-day return policy:
  • calculate return rates for late-December shipments compared with earlier periods,
  • investigate spikes and assess whether the year-end position reflects appropriate reductions/ liabilities based on return patterns.

Manual credit notes issued after year-end:

• Obtain a listing of manual credit notes issued in January/February.
• For a risk-focused sample (and all significant items), inspect:
  • the reason and authorisation,
  • linkage to original invoice,
  • whether the credit note relates to pricing, returns, rebates, or non-delivery.
• Consider whether the pattern indicates aggressive year-end revenue recognition.

Promotion: “Buy 10, get 2 free”

• Inspect promotion terms and how “free” units are processed in the system.
• Test a sample of promotional sales to confirm:
  • quantities shipped agree to order and dispatch records,
  • pricing reflects the promotion consistently,
  • the accounting treatment does not artificially inflate revenue (for example, by invoicing “free” items at list price without an offset).

5% rebate above an annual threshold

• Identify customers close to or exceeding the threshold near year-end.
• Recalculate rebate accruals (or credit notes issued) based on:
  • annual purchase totals,
  • the agreed rebate percentage,
  • timing of recognition (accrue where the obligation arises under the terms).
• Assess whether rebates are presented appropriately (revenue reduction and/or liability, depending on how the entity settles the rebate).

How you will evaluate results:

• Reperformance differences are quantified as misstatement.
• If measurement errors are systematic (for example, threshold rebates not accrued), extend testing to additional customers and reassess the overall estimate.

3) Inventory valuation (cost and recoverability)

Risk target: Inventory overstated and cost of sales understated due to slow-moving stock, promotional pricing pressure, or returns-related effects.

Evidence route: Test cost build-up and then test recoverability using selling evidence.

What you will test:

• Stratify inventory by value and risk: slow-moving lines, promotional items, and high-return categories.
• Select all significant lines (by value) plus targeted items with long ageing or poor margins.

What counts as proof:

• For cost: agree a sample to purchase invoices and costing records; check consistent costing method application.
• For recoverability:
  • compare recorded cost to post year-end sales prices (net of expected discounts/rebates),
  • review markdowns and aged stock reports,
  • inspect evidence of obsolescence or damage.

How you will evaluate results:

• Where selling prices achieved after year-end are below cost (or stock remains unsold with persistent markdowns), quantify a write-down and assess whether it is material.

4) Payables completeness (unrecorded liabilities)

Risk target: Liabilities understated and expenses understated by missing invoices, missing accruals, or delayed recording of goods/services received.

Evidence route: Understatement risk → trace from source evidence into the records.

What you will test:

• Post year-end supplier invoices received in January/early February.
• Unmatched goods received notes at year-end.
• Significant payments made after year-end.

What counts as proof:

• Match post year-end invoices to evidence of receipt/service before year-end.
• Where receipt/service is pre year-end, trace into year-end payables or accruals.
• For payments after year-end, inspect the invoice and receipt date to assess whether the liability should have existed at year-end.

How you will evaluate results:

• Quantify each missing liability and assess whether omissions are isolated or indicate a wider cut-off/completeness weakness.
• Extend testing if multiple exceptions arise in the same supplier group or around year-end.

5) Assertion–procedure mismatches (and corrected approaches)

• Mismatch:Testing revenue overstatement mainly by tracing from customer orders to invoices.
• Why flawed:Orders can exist even if goods were not dispatched or accepted; it does not directly prove recorded revenue is genuine.
• Correct approach:Start with recorded sales and vouch to dispatch and delivery/acceptance evidence (occurrence), then corroborate with post year-end returns/credit notes.
• Mismatch:Concluding revenue is correct based only on gross margin analytics.
• Why flawed:Analytics highlight risk but rarely settle it where incentives, returns, and manual adjustments exist.
• Correct approach:Use analytics to direct attention, then perform targeted tests of details and corroborate explanations with records.
• Mismatch:Testing payables completeness by vouching recorded payables to invoices.
• Why flawed:That supports existence of what is recorded, not whether liabilities are missing.
• Correct approach:Inspect post year-end invoices/GRNs and trace relevant items into year-end payables/accruals.
• Mismatch (common trap in this scenario):Testing revenue occurrence and cut-off but ignoring returns, rebates, and free goods effects.
• Why flawed:Revenue can be genuine and timely but still overstated if the transaction price is not adjusted for expected returns/rebates, or if promotional mechanics inflate invoiced amounts.
• Correct approach:Add procedures that reperform rebate calculations, analyse post year-end returns, and test promotional transactions to ensure measurement and presentation are appropriate.

Interpretation of results

The ageing-based expectation indicates a potential allowance shortfall of £9,200. If uncorrected, receivables (net), profit, and equity would all be overstated by £9,200.

Revenue risk is heightened by incentive pressure and post year-end adjustments (returns and manual credit notes). Effective substantive work therefore needs two strands: (1) evidence that recorded year-end sales are genuine and in the correct period, and (2) evidence that revenue has been measured and presented appropriately after considering returns, rebates, and promotional terms.

Inventory valuation and payables completeness work support the balance sheet by ensuring assets are not overstated and liabilities are not understated, both of which feed directly into profit and equity.

Common pitfalls and misunderstandings

• Confusing occurrence and completeness:Occurrence asks whether recorded items are genuine; completeness asks whether items are missing.
• Ignoring direction:Vouching supports overstatement risks; tracing supports understatement risks.
• Blurring objectives:Keep each procedure focused and ensure evidence directly targets the assertion.
• Accepting explanations without corroboration:Variance explanations must be supported by evidence, otherwise the risk remains.
• Over-reliance on analytics in high-risk areas:Use analytics to identify where to test; do not use it as the only basis for conclusions where incentives and manual processing exist.
• Neglecting returns/rebates/free goods mechanics:These frequently drive measurement and presentation misstatements in revenue.

Summary and further reading

Assertions convert broad audit aims into clear, testable questions about transactions, balances, and disclosures. High-scoring substantive procedures are assertion-led, directionally logical, and supported by evidence that would reasonably expose the stated misstatement. Tests of details and analytical procedures work best together: analytics flags risk and builds expectations; detailed testing validates or corrects the figures.

Where exceptions arise, quantify the impact, investigate the cause, extend procedures where necessary, and conclude whether sufficient appropriate evidence has been obtained.

For wider study, focus on revenue features that create measurement complexity (returns, rebates, free goods), estimation areas (credit losses, inventory write-downs), and common completeness risks (unrecorded liabilities and accruals), as these frequently underpin substantive testing requirements.

FAQ

What are financial statement assertions, and why do they matter?

Assertions are the implied claims behind each figure and disclosure—such as whether it is real, complete, correctly measured, and properly described. They matter because they help convert risks into targeted procedures capable of detecting misstatement.

How do you decide which substantive procedures to perform?

Start with the risk: describe the misstatement, identify the assertion it affects, explain why it could occur, then choose evidence that would make that misstatement difficult to maintain. Match the direction of the procedure to whether the risk is overstatement or understatement.

What makes substantive analytical procedures persuasive?

A predictable relationship, reliable data, and investigation that produces evidence. Explanations must be corroborated to records or independent sources; otherwise the variance remains unresolved.

Why split revenue work into (a) occurrence/cut-off and (b) measurement/presentation?

Because revenue can be genuine and in the correct period, yet still misstated if returns, rebates, or promotional terms are not reflected properly. Separating these strands ensures the audit response matches the real risk.

What do you do when exceptions are found?

Quantify the misstatement, identify the root cause, assess whether it indicates a broader problem, extend testing or perform alternative procedures, and consider whether an adjustment is needed.

Glossary

Assertions
Implied claims that figures and disclosures are genuine, complete, correctly measured, and properly presented.

Existence
A balance recorded at the reporting date represents something real.

Occurrence
A recorded transaction or event took place and relates to the entity.

Completeness
All transactions, balances, and disclosures that should be recorded are included.

Accuracy
Amounts and related data are captured correctly.

Classification
Items are recorded in the correct accounts and categories.

Valuation
Balances are carried at appropriate amounts, including estimates and necessary adjustments.

Rights and obligations
The entity controls recorded assets and is responsible for recorded liabilities.

Cut-off
Transactions are recorded in the correct accounting period.

Presentation and disclosure
Items are appropriately described, grouped, and disclosed so users can understand them.

Substantive procedures
Procedures designed to detect material misstatement at the assertion level, including tests of details and analytical procedures.

Tests of details
Direct checking of transactions, balances, or disclosures using underlying evidence.

Substantive analytical procedures
Developing expectations from data relationships and investigating significant differences to obtain evidence.

Directional testing
Selecting evidence routes that match risk direction: vouching for overstatement risks and tracing for understatement risks.

Corroborative evidence
Evidence from independent or multiple sources that supports the same conclusion and strengthens reliability.