AUD Audit Procedures: Vouching, Tracing, and Tests of Details
Choose the procedure from the risk and assertion, then check its direction, population, and evidence.
Quick answer
Vouching moves from a recorded item to supporting evidence and commonly addresses overstatement or existence and occurrence. Tracing moves from source evidence to the recordsand commonly addresses omission or completeness. Those are study shortcuts, not automatic rules. On AUD, name the risk, assertion, starting population, procedure direction, and evidence before choosing an answer.
Vouching vs tracing: the direction map
Recorded item to evidence
Vouching
Start with an item already in the ledger, journal, or report. Move back to an invoice, shipping record, contract, confirmation, or other support. This direction commonly asks whether the recorded item is valid, existed, or occurred.
Example: Select recorded sales and inspect shipping evidence to test whether revenue was recorded before the earning event occurred.
Source evidence to records
Tracing
Start with evidence of an event that should have been recorded. Follow it into the journal, ledger, and financial statements. This direction commonly asks whether anything was omitted or understated.
Example: Select receiving reports and trace them into purchases and accounts payable to look for obligations missing from the records.
Map each assertion to a procedure objective
The same document can support one assertion well and another poorly. Use the table as a starting map, then let the exact risk in the question control the answer.
| Assertion | Typical risk | Useful procedure direction | Example |
|---|---|---|---|
| Existence or occurrence | Recorded item is invalid or overstated | Record to supporting evidence | Vouch recorded sales to shipping evidence |
| Completeness | A valid event or obligation was omitted | Source evidence to accounting records | Trace receiving reports to accounts payable |
| Accuracy or valuation | Amount, estimate, or allocation is wrong | Recalculate, inspect inputs, and test assumptions | Recalculate an allowance using supported inputs |
| Cutoff | Transaction is recorded in the wrong period | Compare event dates around period end | Match shipping dates to recorded sales dates |
| Rights and obligations | Entity does not own an asset or owe a liability | Inspect contracts or obtain external evidence | Inspect title documents for recorded property |
Tests of controls vs substantive procedures
Tests of controls
Evaluate whether a control operated effectively.
Example: Inspect approvals and reperform the control for a sample of transactions.
Tests of details
Directly test transactions, balances, or disclosures.
Example: Confirm receivables, inspect invoices, recalculate amounts, or test cutoff.
Substantive analytical procedures
Evaluate plausible relationships using an expectation precise enough for the assertion.
Example: Develop an independent expectation, compare it with the recorded amount, and investigate differences.
A test of details is not the same as all substantive testing. PCAOB AS 1105 classifies substantive procedures as tests of details plus substantive analytical procedures. The purpose of a procedure, not its label alone, determines its category.
A repeatable AUD decision sequence
- Name the engagement and objective. An issuer audit, nonissuer audit, review, or attestation scenario can change the authority and conclusion.
- Identify the risk and assertion. Decide whether the concern is invalid recording, omission, wrong amount, wrong period, or another misstatement.
- Define the population. State where the auditor begins and what should be represented in that population.
- Choose the procedure and direction. Explain why it responds to the stated risk.
- Evaluate the evidence. Ask whether it is relevant, reliable, and sufficient for the conclusion.
Apply the map to AUD questions
Keep the procedure map beside a mixed AUD set. For every miss, write the risk, assertion, direction, and evidence objective before reading the explanation.
Official sources and scope
Reviewed August 10, 2026. The AICPA Blueprint defines current CPA Exam scope. PCAOB standards support the issuer-audit concepts explained here, but they do not replace the engagement-specific authority in every AUD question.
AICPA: 2026 Uniform CPA Examination Blueprints
Open official sourcePCAOB: AS 1105: Audit Evidence
Open official sourcePCAOB: AS 2301: The Auditor's Responses to the Risks of Material Misstatement
Open official sourcePCAOB: AS 2305: Substantive Analytical Procedures
Open official source
Frequently Asked Questions
- What is the difference between vouching and tracing in an audit?
- Vouching usually starts with a recorded item and moves to supporting evidence, which commonly helps test whether the recorded item exists or occurred. Tracing usually starts with source evidence and moves into the accounting records, which commonly helps test completeness. The assertion, risk, population, and evidence objective control the correct direction.
- Is a test of details the same as substantive testing?
- No. A test of details is one type of substantive procedure. Substantive analytical procedures are the other broad type. Tests of controls are further audit procedures too, but they evaluate whether a control operated effectively rather than directly testing an account balance or transaction.
- Which direction tests completeness?
- A common completeness test starts with source evidence that should have been recorded and traces it into the accounting records. For example, select receiving reports and trace them to the purchases journal and accounts payable records. Always confirm that the question actually asks about omission or understatement risk.
- Does PCAOB guidance control every AUD CPA Exam question?
- No. The AUD Blueprint covers issuer, nonissuer, governmental, attestation, and accounting-and-review-service contexts. PCAOB standards are useful primary sources for issuer-audit concepts, but the engagement type and the authoritative literature named in the question still matter.