AUD substantive-testing coverage for major transaction cycles, inventory, fixed assets, and investments.
This chapter covers substantive testing at the account and transaction level. It is where assertion-level audit work becomes concrete through direct testing of cycles, balances, and specific financial statement areas.
Substantive-testing questions should begin with the assertion, not the procedure. Confirmation, inspection, recalculation, observation, analytical procedures, and cutoff work are useful only when they respond to the specific misstatement risk being tested.
| Account or cycle | Assertion focus | Common AUD trap |
|---|---|---|
| Revenue and cash receipts | Occurrence, cutoff, completeness, and collectibility. | Testing sales volume without addressing premature revenue recognition. |
| Purchases, expenditures, and payroll | Completeness, authorization, cutoff, and accuracy. | Overlooking unrecorded liabilities or unauthorized payroll changes. |
| Inventory | Existence, condition, rights, valuation, and cutoff. | Treating attendance at the count as sufficient for costing and valuation. |
| Fixed assets | Existence, ownership, depreciation, impairment, and classification. | Testing additions without considering useful lives, disposals, or impairment indicators. |
| Investments and fair value | Existence, valuation, classification, and disclosure. | Accepting fair value inputs without evaluating hierarchy, support, and management bias. |
| Step | What to do | Why it matters on AUD |
|---|---|---|
| 1. Start with the assertion | Identify whether the risk concerns existence, completeness, cutoff, valuation, rights, obligations, presentation, or disclosure. | The correct substantive procedure depends on the assertion being tested. |
| 2. Match the procedure to the risk | Choose confirmation, inspection, recalculation, reperformance, observation, inquiry, analytics, or cutoff testing based on the misstatement risk. | A procedure can be valid in general but weak for the specific assertion. |
| 3. Define the population and timing | Determine what records, transactions, balances, locations, or periods must be tested. | Many AUD traps involve testing the wrong population or ignoring period-end cutoff. |
| 4. Evaluate exceptions | Decide whether deviations are isolated, systematic, projected, or indicators of a broader misstatement. | Exceptions affect both the account conclusion and the need for additional work. |
| 5. Revise the audit response | Adjust sample size, perform alternative procedures, expand testing, or reconsider risk assessment when evidence is insufficient. | Substantive testing is iterative when results do not support the planned conclusion. |
| Checkpoint | Exam use | What to avoid |
|---|---|---|
| Assertion target | Identify existence, completeness, cutoff, valuation, rights, obligations, presentation, or disclosure. | Choosing a procedure because it is familiar rather than assertion-responsive. |
| Procedure fit | Match confirmation, inspection, recalculation, observation, analytics, reperformance, or cutoff work to the risk. | Using a valid procedure for the wrong assertion. |
| Population and timing | Define records, transactions, balances, locations, cutoff period, and testing date. | Testing the wrong population or missing period-end exposure. |
| Exception meaning | Decide whether exceptions are isolated, projected, systematic, fraud-related, or evidence of broader risk. | Treating all exceptions as clerical without evaluating implication. |
| Response revision | Expand testing, perform alternative procedures, adjust sample size, or revisit risk assessment when evidence is weak. | Keeping the original audit plan after results no longer support it. |