Substantive analytical procedures

Substantive analytical procedures

Published September 28, 2026

Substantive analytical procedures

On this page

Expectation, comparison and investigation

A rent draft lists 3 sites, monthly rent of $8,000 per site, and recorded annual rent of $360,000. It has no expected amount or acceptable difference, yet it says “no exception.” The finished schedule must show the expectation, comparison, acceptable difference, and follow-up.

A substantive analytical procedure compares recorded information with an independently developed expectation. The comparison must be precise enough to identify a possible misstatement. A significant difference needs support before a conclusion is reached.

Observation, inspection and reperformance checks records directly. Sending external confirmations and Evaluating confirmation results use different evidence paths.

Choosing, building and evaluating the procedure

AU-C 520.05-.06 provides the order for building and evaluating the procedure.

  1. Select the account, assertion, and relationship. Judge whether a substantive analytical procedure is suitable given assessed risk and any tests of details.
  2. Evaluate the source, comparability, nature, relevance, and controls over the data.
  3. Develop an expectation from a plausible and predictable relationship.
  4. Decide whether the expectation is sufficiently precise. Set the acceptable difference before comparing amounts.
  5. Compare the recorded amount with the expectation. State the direction and size of the difference.
  6. For a difference that exceeds the acceptable amount or is otherwise inconsistent, inquire of management, obtain corroborating evidence, perform other procedures as needed, and document the conclusion.

🔑 RULE: AU-C 520 does not prescribe a fixed dollar or percentage threshold. The auditor sets the acceptable difference using risk, materiality, desired precision, and other planned procedures.

Suitability and data reliability come before the calculation. Investigation comes after the comparison and requires evidence beyond inquiry alone.

Expected payroll includes the bonus

Payroll expense provides a predictable relationship between employees, monthly pay, and annual payroll. The headcount report, approved salary master, and payroll register are reliable and reconciled. The assessed risk is moderate. The initial expectation excludes a separately identified year-end bonus, so the difference must be investigated.

LineAmountWhy
Suitability judgmentSuitable for payroll expense amountHeadcount and pay have a plausible, predictable relationship, and the data is reliable at the assessed risk.
Employees40 employeesPayroll register and HR headcount report provide the activity driver.
Average monthly salary$2,500 per employeeApproved salary master provides a comparable rate.
Annual period12 monthsThe expectation covers the full reporting period.
Expected base payroll$1,200,00040 employees × $2,500 × 12 months.
Recorded payroll$1,248,000Amount in the general ledger.
Initial difference, recorded minus expected+$48,000A positive amount means recorded payroll exceeds the base expectation.
Acceptable difference$24,000Set by the auditor before comparison; AU-C 520 supplies no fixed dollar threshold.
Management explanation$48,000 year-end bonus accrualInquiry identifies a possible reason but does not prove it.
Corroborating evidence$48,000 agrees to approved bonus listing and payroll evidenceEvidence supports the response and the amount.
Revised expected payroll$1,248,000$1,200,000 base payroll + $48,000 supported bonus.
Final tie-out$1,248,000 recorded - $1,248,000 revised expectation = $0The initial $48,000 difference exceeded $24,000 and was investigated; no unexplained difference remains.

The base expectation comes from reliable operating data. The supported bonus changes the expectation and produces a zero final difference.

Utility cost from machine hours

Utility cost has a predictable relationship with machine hours and a supported vendor rate. The general ledger reports $120,000 of utility cost. The auditor has set an acceptable difference of $6,000.

LineAmountWhy
Reliable activity data18,000 machine hoursProduction logs are the operating driver.
Supported cost rate$6.00 per machine hourVendor rate agreement supports the input.
Expected utility cost?Multiply hours by the supported rate.
Recorded utility cost$120,000General ledger amount.
Difference, recorded minus expected?Compute the recorded amount less the expectation.
Acceptable difference$6,000Auditor-set amount for this procedure.
Action?Compare the difference with the acceptable amount and apply the investigation rule.

The same sequence applies to a different operating driver. Recorded amount minus expected amount gives the direction, while the size is compared with the acceptable difference.

Practice

Using 18,000 machine hours and a supported rate of $6.00 per hour, expected utility cost is _____.

Recorded utility cost is $120,000. Using the expectation, the difference recorded minus expected is _____.

The acceptable difference is $6,000. Which conclusion follows?

Suitability, reliability, differences and evidence

These cases test suitability, data reliability, difference direction, acceptable differences, and follow-up evidence. The sign describes the possible direction of error, but it does not by itself establish an adjustment.

Practice

Which fact most strongly supports using a substantive analytical procedure for payroll expense amount?

Which statement about the acceptable difference is correct?

Recorded utility cost is $120,000 and expected utility cost is $108,000. What is the correct difference and direction?

A payroll difference exceeds the acceptable amount, and management says it is caused by bonuses. What should the auditor do next?

Payroll expectation and acceptable difference

The records keep the original payroll drivers, supported bonus, and acceptable difference. Only the recorded payroll amount changes to $1,270,000. Fill the expectation, difference, and conclusion cells.

Schedule lineAmountStatus
Expected base payroll____Fill from Exhibit 1.
Supported bonus____Fill from Exhibit 2.
Expected total payroll____Add the two expectation components.
Recorded payroll$1,270,000Given in Exhibit 3.
Difference, recorded minus expected____Fill and state the sign.
Acceptable difference$24,000Given in Exhibit 3.
Conclusion____State whether this difference exceeds the acceptable amount.

The supported bonus remains part of the expectation because its evidence did not change. The new difference is compared with the same $24,000 acceptable amount.

Developing expectations and investigating differences

  1. Judge whether the relationship and data make the procedure suitable for the assertion and assessed risk.
  2. Evaluate the source, comparability, relevance, and controls over the data.
  3. Develop an expectation that is sufficiently precise.
  4. Set the acceptable difference before comparison.
  5. Compare recorded with expected and state the direction.
  6. Investigate differences beyond the acceptable amount with management inquiry, corroborating evidence, and other procedures as needed.

Tie-out: $1,248,000 - $1,248,000 = $0.

The tie-out works because reliable drivers built the expectation and evidence supported the initial difference. A zero final difference does not remove the need to consider assessed risk and other planned audit procedures.

Unlock the full lesson and continue reading

Signup to continue reading this lesson and unlimited access questions, flashcards, AI notes, and more

Scan to download app

Scan to download
UNLOCK FREE ACCESS

Practice Questions: Substantive analytical procedures

  1. 1. An auditor is designing an attribute sample to test whether purchase orders contain required approval. Assuming other sampling-design factors remain unchanged, which of the following changes ordinarily increases the required sample size?

    • A. Decreasing the acceptable risk of overreliance
    • B. Increasing the tolerable deviation rate
    • C. Decreasing the expected population deviation rate
    • D. Increasing the size of an already large population
    Show answer

    Answer: A. Decreasing the acceptable risk of overreliance

    Decreasing the acceptable risk of overreliance - A lower acceptable risk of overreliance requires stronger evidence before the auditor relies on purchase-order approvals. - With other sampling-design factors unchanged, stronger evidence ordinarily requires a larger attribute sample. Increasing the tolerable deviation rate - A higher tolerable deviation rate allows more purchase orders without required approval before the control is considered unacceptable. - That greater allowance ordinarily decreases, rather than increases, the required sample size. Decreasing the expected population deviation rate - A lower expected deviation rate means the auditor anticipates fewer purchase orders missing required approval. - With other factors unchanged, expecting fewer deviations ordinarily decreases the required sample size. Increasing the size of an already large population - Once the population of purchase orders is already large, further growth has little or no effect on attribute-sampling sample size. - The required sample size is driven principally by the specified risk and deviation rates, not by a further increase in a large population.

  2. 2. Read the passage below describing the auditor's engagement, then answer the question that follows. An auditor plans to rely on a client-generated IT report listing all system-approved changes to the sales order processing application made during the year, in order to assess the risk that unauthorized program changes affected revenue recognition. Which procedure should the auditor perform before relying on the report?

    • A. Select recorded sales from the extract and vouch them to invoices and shipping documentation
    • B. Recalculate the dashboard percentages generated from the individual records included in the extract
    • C. Test the completeness of the change-management report by tracing a sample of actual program changes (identified independently, e.g., from code repository logs) to the report, and evaluate the report's underlying query logic
    • D. Ask information technology personnel whether the standard sales report has changed during the year
    Show answer

    Answer: C. Test the completeness of the change-management report by tracing a sample of actual program changes (identified independently, e.g., from code repository logs) to the report, and evaluate the report's underlying query logic

    Test the completeness of the change-management report by tracing a sample of actual program changes (identified independently, e.g., from code repository logs) to the report, and evaluate the report's underlying query logic - Tracing changes identified independently in code repository logs to the report tests whether it omits actual changes to the sales order processing application. - Evaluating the query logic helps establish whether the client-generated report captures the change activity the auditor needs before relying on it to assess revenue-recognition risk. Select recorded sales from the extract and vouch them to invoices and shipping documentation - Vouching recorded sales to invoices and shipping documents addresses whether those sales transactions occurred, not whether program changes are missing from the change-management report. - The auditor needs evidence about changes to the sales order processing application before relying on the report, rather than support for individual revenue entries. Recalculate the dashboard percentages generated from the individual records included in the extract - Recalculating percentages checks arithmetic based on included records, but cannot reveal program changes omitted from the report. - The relevant risk is that an incomplete change listing could conceal changes affecting revenue recognition, even if calculations using the listed records are correct. Ask information technology personnel whether the standard sales report has changed during the year - Inquiry alone does not test the completeness of the client-generated change-management report or its underlying query logic. - Asking about a standard sales report also does not independently identify changes to the sales order processing application for comparison with the change listing.

  3. 3. A customer does not respond to a positive accounts receivable confirmation after the auditor sends an initial request and a follow-up request. The balance is material, and the client received payment from the customer three weeks after year end. Which procedure should the auditor perform next?

    • A. Treat the lack of a response as a confirmed exception and project it to the population.
    • B. Inspect the subsequent cash receipt and supporting remittance and shipping documentation.
    • C. Replace the positive request with a negative confirmation sent to the same customer.
    • D. Ask the credit manager whether the customer disputed the balance at year end.
    Show answer

    Answer: B. Inspect the subsequent cash receipt and supporting remittance and shipping documentation.

    Inspect the subsequent cash receipt and supporting remittance and shipping documentation. - After two unanswered positive requests, the auditor should perform alternative procedures for the material receivable. - The payment received three weeks after year end and its remittance support collection; shipping documentation helps establish that the recorded sale and receivable existed at year end. Treat the lack of a response as a confirmed exception and project it to the population. - A nonresponse provides no confirmation evidence, but it is not a reported disagreement or an identified misstatement. - The auditor must obtain alternative evidence for this material balance rather than project the unanswered request as an exception. Replace the positive request with a negative confirmation sent to the same customer. - A negative confirmation asks the customer to reply only if they disagree, so another silence would not resolve the unanswered positive request. - The available subsequent payment and supporting documents provide a more appropriate way to test this receivable. Ask the credit manager whether the customer disputed the balance at year end. - Asking the client’s credit manager may provide context, but client inquiry alone is insufficient evidence for this material receivable. - The auditor should inspect the payment, remittance, and shipping records instead of relying solely on what client personnel recall.

  4. 4. An auditor is testing sales recorded from December 20, 20X5 through January 10, 20X6. The population is an export from the client's sales application, produced using a controller-created query, consisting of 4,860 invoices totaling $18,420,000. The controller modified the date-filter logic on December 15, 20X5. The auditor has not tested general information technology controls and has not reconciled the export to the sales ledger. Which procedure should the auditor perform before using the exported sales report as the population for substantive cutoff testing?

    • A. Reconcile the report's record count and total amount to the sales ledger and test the report parameters against the approved query.
    • B. Compare the report's gross margin percentage with the prior-year gross margin percentage and investigate significant fluctuations.
    • C. Ask the controller whether all year-end sales were included and retain the controller's response in the audit documentation.
    • D. Select several report entries and agree each entry to its related sales invoice and customer purchase order.
    Show answer

    Answer: A. Reconcile the report's record count and total amount to the sales ledger and test the report parameters against the approved query.

    Reconcile the report's record count and total amount to the sales ledger and test the report parameters against the approved query. - Before using the 4,860-invoice, $18,420,000 export as a cutoff-testing population, the auditor needs evidence that the client-produced report is complete and accurate. - Reconciliation addresses whether the export agrees with the sales ledger, while testing the parameters addresses the controller’s December 15 change to the date-filter logic. Compare the report's gross margin percentage with the prior-year gross margin percentage and investigate significant fluctuations. - A gross-margin comparison might reveal an unusual sales trend, but it does not establish that the export contains all relevant invoices. - It also does not test whether the modified query extracted sales for December 20, 20X5 through January 10, 20X6. Ask the controller whether all year-end sales were included and retain the controller's response in the audit documentation. - The controller’s answer is inquiry, not sufficient evidence that the export agrees with the sales ledger. - Because the controller created the query and changed its date filter, the auditor must test the report rather than rely on that assurance. Select several report entries and agree each entry to its related sales invoice and customer purchase order. - Agreeing selected entries to source documents can support the accuracy of those entries. - It cannot establish that the export omitted no invoices or that the changed date filter captured the intended cutoff period.

  5. 5. You are completing the audit of Apex Components, Inc., a nonissuer that prepares financial statements in accordance with U.S. GAAP. The financial statements are for the year ended December 31, 20X5. The auditor expects to date the report February 20, 20X6, and the financial statements are expected to be issued March 1, 20X6. Management has agreed to record the litigation adjustment described in the exhibits but refuses to record the other proposed adjustments. Determine the required accounting, audit, communication, and reporting consequences.

    • 6. An audit team is completing the audit of Northstar Equipment, Inc., a nonissuer that prepares financial statements in accordance with U.S. GAAP for the year ended December 31, 20X5. Revenue is recognized when control of equipment transfers to the customer. The auditor selected year-end sales transactions after identifying a risk that revenue could be recorded in the wrong period. Management has not recorded any proposed cutoff adjustments, and the auditor's report has not yet been dated.

      Flashcards: Substantive analytical procedures

      1. 1. What audit approach is associated with a low acceptable detection risk?

        Show answer

        A low acceptable detection risk requires more effective substantive procedures. Depending on the circumstances, the auditor may obtain more reliable or persuasive evidence, increase the sample size or other extent of testing, and perform procedures closer to or at year-end rather than relying only on interim testing.

      2. 2. What does a high acceptable detection risk permit in an audit?

        Show answer

        It permits less extensive substantive procedures—such as smaller samples or less persuasive, but still sufficient and appropriate, evidence—because the auditor accepts a greater risk that the procedures will fail to detect a material misstatement. Strong controls and stable operations may support a higher acceptable detection risk but are not required.

      Everything you need for CPA prep

      Get full Oncourse access with lessons, practice questions, flashcards and AI study tools.

      GET STARTED FOR FREE
      75% OFFLimited time offer
      GET 75% OFF