Kyle Ashcraft, CPA · 2019 CPA Exam Scores · 95 FAR · 98 BEC · 91 REG · 90 AUD
A test of details is the part of the audit where you stop looking at totals and start looking at the items behind them. You pick a customer balance, an invoice or a shipment, and you check it against evidence outside the books.
Two ideas carry this topic on AUD: which direction you test in, and when a test of details beats a substantive analytical procedure. Here is how I teach both.
Quick answer: a test of details checks individual transactions or balances against evidence, such as confirming a receivable or vouching a sale to a shipping document. A substantive analytical procedure checks whether a total makes sense against an expectation. Both are substantive procedures. Vouching from the books to the documents tests existence or occurrence. Tracing from the documents to the books tests completeness.
On this page
- What is a test of details in auditing?
- Vouching or tracing: which direction tests which assertion?
- What are examples of tests of details by account and assertion?
- How is a test of details different from a substantive analytical procedure?
- How does the auditor decide the mix and extent?
- How does the AUD exam test this?
- Frequently asked questions
Last updated November 2026. Coffee Co. and every figure on this page are illustrative, not a real client. Standards referenced: AICPA AU-C 330, AU-C 500, AU-C 505, AU-C 520 and AU-C 530.
What is a test of details in auditing?
A test of details looks at the source of a balance. It asks: how can I corroborate what the client tells me? Corroborate just means back up a claim. So, let's say the client tells me the bank balance is $100,000. I send a bank confirmation, and the bank tells me whether that is true.
Test of details versus substantive testing is not a real choice. Substantive procedures is the umbrella: any audit procedure that is not a test of controls. Under it sit two categories, tests of details and substantive analytical procedures. "Substantive test of details" is the same thing, said in full.
| Test of details | Substantive analytical procedure | |
|---|---|---|
| The question | Is this item backed up by evidence? | Does the total fit what I expected? |
| What you look at | Individual transactions and balances | Trends, ratios and relationships among amounts |
| Procedures | Confirmation, inspection, vouching, tracing, recalculation, cutoff testing | Set an expectation, set a threshold, investigate differences |
| Works best for | Significant risks, existence of assets, unusual transactions | Large volumes of transactions that are predictable over time |
| Umbrella | Substantive procedure | Substantive procedure |
The other side of the line is a test of controls, which asks whether a control worked. That split is in test of controls vs. substantive test, so this page stays on the substantive side.
The rule: checking individual items against evidence is a test of details. Comparing a total to an expectation is a substantive analytical procedure. Both are substantive procedures.
Vouching or tracing: which direction tests which assertion?
The direction you go in decides it. Let's say Coffee Co. has equipment recorded at $10,000 on its balance sheet. I want to know it is real, so I start at the balance sheet and go to the purchase invoice. That is vouching, and it tests existence. Think of vouching for a person: you are saying they are legitimate.
Now flip it. I want to know Coffee Co. is not leaving vendor invoices out of accounts payable. So I start with the invoices and trace them into the accounts payable listing. That is tracing, and it tests completeness.
| Vouching | Tracing | |
|---|---|---|
| Start at | The books | The source document |
| Go to | The source document | The books |
| Finds | Recorded items that are not real | Real items that were never recorded |
| Catches | Overstatement | Understatement |
| Assertion | Existence or occurrence | Completeness |
Here is why. You cannot find something missing by starting from a list that does not include it. One caution: some questions use "tracing" loosely to mean matching documents, so check which population the sample comes from.
Remember: books to documents is vouching, which tests existence or occurrence. Documents to books is tracing, which tests completeness.
What are examples of tests of details by account and assertion?
Every test of details is aimed at an assertion. Here is the board I draw, using the assertion names from AU-C 315.
| Account | Assertion | Test of details | Type |
|---|---|---|---|
| Cash | Existence, rights and obligations | Send a bank confirmation | Confirmation |
| Cash | Accuracy, valuation and allocation | Recalculate the bank reconciliation, agree items to the cutoff bank statement | Recalculation |
| Accounts receivable | Existence | Send positive confirmations to customers | Confirmation |
| Revenue | Occurrence | Vouch recorded sales to shipping documents | Vouching |
| Revenue | Completeness | Trace shipping documents into the sales journal | Tracing |
| Revenue | Cutoff | Examine shipments just before and after year end | Cutoff testing |
| Accounts payable | Completeness | Search for unrecorded liabilities: payments and invoices after year end | Inspection of documents |
| Fixed assets | Existence | Inspect the asset itself | Inspection of assets |
Confirmations. A confirmation is evidence straight from a third party, and AU-C 500 treats evidence from independent outside sources as more reliable than evidence from the client. For accounts receivable, AU-C 330 says the auditor should confirm unless the balance is immaterial, confirmation would be ineffective, or the assessed risk is low and other planned substantive procedures address it. When a customer never replies, AU-C 505 requires alternative procedures, such as inspecting cash received after year end. The full round trip is in my confirmations example.
Recalculation. Here is the bank reconciliation from my cash lecture: start from the bank statement, add deposits in transit, subtract outstanding checks, compare to the books.
| Bank reconciliation, December 31 | Amount |
|---|---|
| Balance per bank statement | $2,000 |
| Add: deposits in transit | $510 |
| Less: outstanding checks | ($875) |
| Cash balance it should be | $1,635 |
| Cash balance per books | $1,800 |
| Difference: books overstated | $165 |
Then I test each line. I confirm the $2,000 with the bank, check that the reconciling items clear on the January cutoff statement, and ask why the books are $165 too high.
Cutoff testing. Cutoff asks whether a transaction landed in the right period. Coffee Co. ships FOB shipping point, so in this example a sale belongs in the period it ships. I pull shipments on both sides of December 31, 2026.
| Invoice | Shipped | Recorded in | Amount | Result |
|---|---|---|---|---|
| 7101 | Dec 29, 2026 | 2026 | $2,400 | Correct |
| 7102 | Dec 31, 2026 | 2027 | $1,900 | 2026 revenue understated |
| 7103 | Jan 2, 2027 | 2026 | $3,600 | 2026 revenue overstated |
| 7104 | Jan 3, 2027 | 2027 | $1,100 | Correct |
| Net effect on 2026 revenue | $1,700 | Overstated ($3,600 less $1,900) | ||
Pick the test from the assertion. Not sure it is real? Confirm, inspect or vouch it. Something missing? Trace into the books. Wrong period? Test both sides of year end.
How is a test of details different from a substantive analytical procedure?
Analytical procedures are required in planning and again in the overall review at the end. In the middle, as a substantive procedure, they are optional. When I use one, AU-C 520 gives me the steps:
- Decide whether an analytic suits this assertion, given the assessed risk.
- Evaluate whether the data behind the expectation is reliable.
- Develop an expectation precise enough to catch a misstatement that could be material.
- Set the threshold: the difference I will accept without investigating.
- Investigate differences over the threshold: ask management, then get evidence that backs up the answer.
So, let's say Coffee Co.'s revenue has grown 10% a year, and I expect the same this year.
| Revenue analytic | Amount |
|---|---|
| Prior year revenue | $100,000 |
| Expectation: 10% growth | $110,000 |
| Recorded revenue: 40% growth | $140,000 |
| Difference | $30,000 |
| Threshold for investigation | $5,000 |
$30,000 is over the threshold, so I investigate. Management says Coffee Co. won three major new customers, each worth about $10,000. Three times $10,000 is $30,000, which explains the gap. But management's answer is not evidence on its own. I inspect the three contracts and vouch sales to those customers to shipping documents. Notice the follow-up is itself a test of details.
There is a catch. AU-C 240 presumes a fraud risk in revenue recognition, and fraud risks are significant risks. Under AU-C 330, when the response to a significant risk is substantive procedures only, it must include tests of details. So on a real revenue audit, this analytic alone would not be enough.
| A test of details gives better evidence when | An analytic works well when |
|---|---|
| The risk is a significant risk | The assessed risk is lower |
| You need proof an asset exists | The account is high volume and predictable, such as payroll or interest expense |
| Transactions are unusual or one-off | The relationship between amounts is stable |
| The data for an expectation is not reliable | The data is reliable |
In one line: a test of details proves items one at a time. An analytic tests whether the total fits an expectation, and it is only as good as how precise that expectation is.
How does the auditor decide the mix and extent?
Audit risk equals inherent risk times control risk times detection risk. Inherent risk and control risk together are the risk of material misstatement. Detection risk is the only piece the auditor controls, and it moves the opposite way. When the risk of material misstatement goes up, the detection risk I can accept goes down, so I need more persuasive evidence. I get it by changing:
- Nature: more and stronger tests of details, such as a confirmation instead of an inquiry.
- Timing: testing at year end instead of at an interim date.
- Extent: testing more items.
AU-C 330 allows analytics alone, tests of details alone, or a combination. A low-risk, predictable expense with tested controls might need only an analytic. More on the risk side is in detection risk.
Sampling. Tests of details use variables sampling, which looks at dollar amounts. Attribute sampling, which looks at rates, is for tests of controls. In probability proportional to size sampling, each dollar is a sampling unit, so larger balances are more likely to be picked, which suits testing for overstatement. Sample size goes up with higher risk, lower tolerable misstatement or more expected misstatement. It goes down when other substantive procedures, including a good analytic, already give assurance on the same assertion. AU-C 530 then requires me to project what I find to the population.
| Coffee Co. receivables sample | Amount |
|---|---|
| Population: accounts receivable | $1,000,000 |
| Sample tested | $200,000 |
| Overstatement found (1% of the sample) | $2,000 |
| Projected misstatement (1% of the population) | $10,000 |
| Tolerable misstatement | $25,000 |
$10,000 is well under $25,000, so the sample supports the balance. A projection close to or above tolerable misstatement means more testing or an adjustment.
Remember: risk of material misstatement up, detection risk down. That means more tests of details, closer to year end, on bigger samples.
How does the AUD exam test this?
Here is an exam-style question I wrote. An auditor wants evidence that accounts payable at December 31 is complete. Which procedure is most appropriate?
- A. Select balances from the accounts payable listing and vouch them to vendor invoices.
- B. Examine cash disbursements made after year end and, for those that relate to the year under audit, check that they appear on the December 31 accounts payable listing.
- C. Recalculate the total of the accounts payable listing and agree it to the general ledger.
- D. Compare total accounts payable to the prior year and investigate differences over a threshold.
- Answer B is correct. This is the search for unrecorded liabilities. It starts outside the listing, with payments the company actually made, and checks whether the liability was recorded. That direction tests completeness.
- Answer A is the trap. It is a test of details, but it starts from the listing, so it can only tell you the recorded payables are real. That is existence. A missing invoice is never on the list you sampled from.
- Answer C tests the arithmetic. Recalculating the listing proves it adds up, not that every liability is on it.
- Answer D is weaker evidence. An analytic can flag that the total looks low, but it does not identify the unrecorded invoices, so it is not the most appropriate test of completeness here.
Two checks every time: which assertion is being tested, and which population the sample starts from.
For the overview of the umbrella, see substantive procedures. For picking and evaluating samples, see audit sampling. And for tests of details on two accounts end to end, see substantive testing of cash and receivables.
Sources: AICPA AU-C 240, Consideration of Fraud in a Financial Statement Audit; AICPA AU-C 315, Understanding the Entity and Its Environment and Assessing the Risks of Material Misstatement; AICPA AU-C 330, Performing Audit Procedures in Response to Assessed Risks and Evaluating the Audit Evidence Obtained; AICPA AU-C 500, Audit Evidence; AICPA AU-C 505, External Confirmations; AICPA AU-C 520, Analytical Procedures; AICPA AU-C 530, Audit Sampling. Standards checked November 2026. Coffee Co. figures are illustrative.
Frequently asked questions
What is a test of details in auditing?
A substantive procedure that checks individual transactions or balances against evidence, such as confirming a receivable, vouching a sale to a shipping document, or testing cutoff at year end.
What is the difference between a test of details and substantive testing?
Substantive testing is the umbrella: any procedure that is not a test of controls. It has two categories, tests of details and substantive analytical procedures, so a test of details is one kind of substantive test.
How is a test of details different from a substantive analytical procedure?
A test of details proves individual items with evidence. A substantive analytical procedure sets a precise expectation for a total, sets a threshold, and investigates differences over it. Analytics work best on large, predictable accounts.
Does vouching test existence or completeness?
Vouching goes from the books to the documents, so it tests existence or occurrence. Tracing goes from the documents to the books, so it tests completeness.
When is a test of details required?
Under AU-C 330, when the auditor responds to a significant risk with substantive procedures only, those procedures must include tests of details. An analytic alone is not enough.
Start the free AUD 101 course
A full free outline and official AICPA questions you can practice, so you can see whether the explanations work for you. No credit card required.
Kyle Ashcraft, CPA scored 90 or above on every section of the CPA exam in 2019, including a 90 on AUD. He is the founder and sole instructor of Maxwell CPA Review, where he creates every lecture, textbook and study outline himself.
Reach him at MaxwellCPAreview@gmail.com.
Double-click to edit...
