CPA AUD Task-Based Simulations

What an AUD simulation asks you to do

A task-based simulation (TBS) is a case, not a longer multiple-choice question. It gives you a situation and asks you to use information in exhibits to complete one or more tasks. Depending on the case, you may select documents, reconcile amounts, identify an assertion, evaluate an exception, choose an audit procedure, or determine the reporting consequence. The point is to apply audit judgment to the facts supplied.

The AICPA blueprint lists seven AUD simulations, split into three testlets containing 2, 3, and 2 TBSs. TBSs count for 50 percent of the AUD score. A single simulation may have multiple response fields. That makes practice with evidence and task instructions essential: knowing a standard in isolation does not show that you can apply it to a messy file.

A case often contains information that is relevant to the overall scenario but not every task. Do not assume every exhibit must be used in each response. Start from what the task asks, then decide which records help answer it. A spreadsheet with many rows is not automatically the most important evidence; a short contract clause may determine the accounting conclusion.

A four-step method

1. Read the requested output

Before studying the exhibits, look at the task requirements. Are you being asked for an amount, a classification, a procedure, a conclusion, or a report effect? Underline the verb mentally. “Calculate” needs a number and method. “Select the most appropriate procedure” needs a procedure aimed at the stated risk. “Determine whether an adjustment is needed” calls for an accounting conclusion supported by the facts.

Also notice the response format. A dropdown requires a choice from the given labels. A selection task may allow more than one response. A numeric entry may specify dollars, units, or rounding. A narrative field may ask you to explain a finding. Answer in the requested form; extra words do not fix an incorrect classification.

2. Identify the audit question

Translate the task into the underlying issue. Is it about existence, completeness, cutoff, valuation, rights and obligations, or presentation? Is it about control design, operating effectiveness, substantive evidence, fraud risk, an estimate, subsequent events, or reporting? Naming the issue helps you avoid being distracted by a true but unrelated fact in another exhibit.

For account testing, keep the direction of the procedure in view. Starting with recorded items and tracing to source support can test occurrence or existence. Starting with source documents outside the ledger and tracing them into the books can test completeness. Confirming a recorded receivable can support existence and some aspects of rights, but does not by itself establish valuation or cutoff.

3. Build an evidence trail

Read the relevant exhibits and write a short chain: source, fact, assertion or risk, conclusion. Ask who created the document, when it was created, what it actually establishes, and whether something else corroborates it. A bank confirmation may provide external evidence about a balance at a date. A client reconciliation explains how the balance is presented. You may need both, but they do not answer identical questions.

When information conflicts, do not choose the exhibit with the neatest formatting. Identify the conflict and determine which source is more reliable for that fact. A signed contract may establish a delivery term; a sales listing shows how management recorded a transaction; a carrier record shows a movement or delivery date. Their evidential roles differ.

4. Respond and verify

Make the requested response and check it against the facts. Recalculate amounts independently, confirm that debits and credits run in the right direction, and verify dates and units. For a procedure, name what to inspect, compare, confirm, recalculate, or observe and what evidence the action should produce. “Review the transaction” is usually too vague unless the task asks for a broad response.

Original worked simulation: year-end revenue cutoff

The following is an original teaching case. The names, amounts, and documents are fictional. It is not an AICPA question and does not reproduce a retired or live exam item.

You are auditing the December 31 financial statements of Northstar Office Supply, a nonissuer. Management recorded a $47,000 sale on December 30 and removed the related inventory. The sale is large enough to be material to the account being tested. The audit team selected the transaction from the year-end sales journal because it was posted during the final days of the reporting period.

Exhibit A: contract excerpt

The customer order says the goods remain the seller’s responsibility until receipt at the customer’s location. The customer’s signed acceptance is dated January 3. The invoice is dated December 30.

Exhibit B: carrier record

The carrier picked up the shipment on December 30. Its delivery record shows arrival at the customer’s dock on January 3. The customer signed the receipt that day.

Exhibit C: ledger detail

The December 30 entry debits accounts receivable and credits sales revenue for $47,000. Inventory of $29,000 is credited and cost of goods sold is debited on the same date. No separate entry reverses the transaction in January.

Task 1: identify the issue

The main issue is cutoff, with a related risk to occurrence for the recorded sale and existence for the receivable. The contract says responsibility continues until receipt, and the customer accepted the goods after year end. The invoice date and carrier pickup date show that a transaction was initiated, but they do not establish that the contract’s transfer condition was met by December 31.

Task 2: calculate the proposed correction

On the stated facts, reverse the premature sale from the December statements: debit sales revenue $47,000 and credit accounts receivable $47,000. Restore the inventory by debiting inventory $29,000 and crediting cost of goods sold $29,000. The first entry removes the overstated revenue and receivable. The second reverses the cost entry so inventory is not understated and cost of goods sold is not overstated.

Do not report a net $18,000 revenue adjustment simply because the gross sale and cost differ by that amount. Revenue and cost of goods sold are separate accounts, and the inventory assertion is also affected. The task asks for the correction to financial statement accounts, so show each effect rather than netting unrelated lines.

Task 3: choose further work

Inspect a sample of sales recorded near year end and compare contract terms with carrier delivery and customer acceptance evidence. This responds to cutoff risk and can identify a pattern beyond the selected item. The auditor should evaluate the error, project it when appropriate under the sampling plan, and consider whether the tested population or risk assessment needs to change.

If management refuses to correct the identified misstatement, accumulate it with other uncorrected misstatements and evaluate materiality individually and in aggregate. The auditor also considers qualitative factors. Whether an opinion modification is needed depends on the final statements and the size and pervasiveness of the uncorrected effect; do not jump from one exception straight to an adverse opinion.

Second example: a liability completeness search

Suppose a January cash disbursement of $18,600 pays an invoice for services completed in December. The invoice arrived after year end and is absent from the accounts payable listing. The payment record alone does not tell you whether the obligation belonged in the prior-year statements. Inspect the invoice, service period, contract, and approval evidence. If the work was received by year end and the obligation existed then, the liability and expense may be understated.

This search begins with later evidence and traces toward the year-end books. It is designed to find liabilities that should have been recorded but were omitted. A search limited to recorded payables could miss the very items the procedure is meant to find. The sample illustrates how procedure direction follows the completeness assertion.

Common simulation traps

Confusing an invoice date with the date a sale is earned is a common cutoff error. A document’s date matters only in context. Contract terms, delivery, acceptance, and the reporting framework determine what it supports.

Treating every exhibit as equally reliable is another mistake. Management reports can be useful but may contain untested data. External documents may corroborate a fact but can be incomplete or relate to a different population. Evaluate evidence for the claim the task asks you to assess.

Choosing a procedure because it sounds technical can also miss the point. A physical inventory observation does not directly test whether a December sale was recorded in the correct period. Confirming a receivable does not necessarily test every valuation issue. Tie the procedure to the risk and assertion.

Finally, do not assume a control deficiency proves the financial statements are misstated. It may raise risk and require more work. The auditor needs evidence about whether a misstatement occurred, its amount, and its materiality. Likewise, a clean control test does not eliminate substantive procedures for material balances and disclosures.

How to practise without memorizing cases

Use a fresh fact pattern after you learn a case. Change the direction of evidence, the transaction date, the contract condition, or the assertion under test. Ask yourself which new fact changes the answer and why. If your method still works when details change, you have learned a principle rather than the answer key.

Keep an error log with four fields: the requested decision, the evidence that mattered, the reasoning mistake, and a new question to test the correction. A short label such as “wrong assertion” is not enough. Write the distinction you missed: for example, “I traced from the ledger outward, so I tested whether recorded sales occurred, not whether all shipments were recorded.”

Use the AICPA’s retired AUD simulation as a demonstration of how a simulation can combine data analytics, data completeness, visualizations, and substantive audit responses. It is public retired material. Study the reasoning process, but do not copy its prompt or transform its response into a supposedly original practice item. Your learning bank should use new entities, exhibits, facts, and questions.

The AICPA sample test serves a different purpose: it familiarizes you with software and tools. It is shorter, unscored, and includes questions from all exam sections. Use it to learn how to navigate and enter responses. For content development, follow the current AUD blueprint and practise original cases across ethics, risk, evidence, and reporting.

A strong simulation response is usually economical. State the relevant fact, connect it to the audit issue, and answer the task. Do not add a broad lecture on every assertion when the task asks for one adjustment. Do not omit a short rationale where the response field asks for one. Precision comes from selecting the right evidence, not from using the most words.