39.1 Document Review Simulation Method
Key Takeaways
- Each Core and Discipline section serves three task-based simulation (TBS) testlets after two multiple-choice testlets, so document review skill is tested on every CPA section, not just one.
- A document review TBS should begin with the requirement and the response grid, not with a full read of every exhibit.
- Source reliability ranks evidence: executed agreements, external confirmations, and authoritative excerpts outrank informal management narratives.
- Dates, entity type, measurement basis, taxpayer status, control frequency, and reporting period are the high-value facts that flip CPA answers.
- Most document review errors come from trusting background narratives, missing exceptions, using the wrong period, or entering a correct amount in the wrong format.
Why document review is different from reading
A task-based simulation (TBS) on the Uniform CPA Examination often looks like a small client file. You may see a prompt, an answer grid, a trial balance, emails, invoices, board minutes, tax schedules, audit workpapers, policy excerpts, or system reports. The exam is not asking whether you can read all of it. It is asking whether you can identify which documents answer the requirement and enter a defensible response.
The stakes are structural. Every section of the post-CPA-Evolution exam runs four hours across five testlets: two multiple-choice testlets, then three TBS testlets. Most sections weight multiple-choice questions (MCQs) and TBSs at 50 percent each; Information Systems and Controls (ISC) is the exception at 60 percent MCQ and 40 percent TBS. A passing scaled score is 75, which is not a percentage correct. Because TBSs carry roughly half your score on AUD, FAR, REG, BAR, and TCP, weak document review can sink an otherwise strong candidate.
Read the requirement before the exhibits
The first discipline is to read the requirement before the exhibits. The requirement tells you the decision type: calculate an adjustment, identify a control exception, classify a transaction, select an authoritative conclusion, reconcile source data, or evaluate whether a statement is supported. Once you know the decision type, the exhibits stop being a pile of documents and become evidence with different levels of relevance.
The CPA document review frame
Use this frame before opening the first exhibit in detail:
| Question | What you are looking for | Common CPA example |
|---|---|---|
| What is the response format? | Number, drop-down, checkbox, date, journal entry, or short conclusion | FAR adjustment cell or AUD exception label |
| What period is tested? | Year-end, interim date, filing year, taxable year, audit period, or service period | REG basis at sale date, AUD control period |
| What source should be trusted? | Executed agreement, authoritative excerpt, external document, system report, or reconciled schedule | Lease contract over a management summary |
| What fact can change the answer? | Threshold, exception, ownership percent, assertion, effective date, frequency, or limitation | TCP passive activity rule, ISC access-review frequency |
| What should be ignored? | Background, duplicated amounts, old drafts, client opinions, or unrelated exhibits | Narrative memo that conflicts with invoice detail |
Five-step workflow and section signals
- Read the requirement and grid. Write a tiny map: cells 1-3 are revenue cutoffs, cells 4-5 are disclosure conclusions, cell 6 is a correcting entry.
- Open each exhibit once for labeling. Tag it as contract, policy, source data, reconciliation, correspondence, authority excerpt, or distractor. Do not deep-read yet.
- Rank the exhibits. Put executed agreements, original source documents, and authoritative excerpts above informal summaries; put dated drafts below final versions.
- Solve one response group at a time. Pull only the exhibits tied to the current answer cells; note the fact, rule, and response in a compact workpaper.
- Review only high-risk cells. Check signs, dates, entity names, taxable-versus-book amounts, blank-entry instructions, and whether the grid wants zero or no entry.
Section-specific document signals
- AUD review turns on evidence quality, assertions, control design, operating effectiveness, exception patterns, report dates, and required communications. If a receiving log contradicts management's cutoff claim, the independent transaction detail outweighs the narrative.
- FAR and BAR simulations tie financial-statement amounts to contracts, schedules, journal entries, or trial-balance data. The decisive document defines recognition, measurement, classification, or presentation: a lease, debt agreement, grant restriction, or investment schedule.
- REG and TCP make dates and taxpayer identity dangerous. The same property fact pattern changes when the taxpayer is an individual, C corporation, S-corp shareholder, partner, estate, or trust. Track basis, holding period, ownership percentage, filing status, and tax-versus-book reporting.
- ISC asks whether system behavior or evidence matches a stated policy or service-organization criterion. A control that exists on paper but is not performed at the required frequency is not operating as described.
A practical review habit
Your scratch work should be short but traceable. For each answer group, capture document name, key fact, rule or criterion, and response. That habit prevents the most common TBS spiral: rereading every exhibit because you cannot remember why you entered an answer. On exam day, perfect notes are unnecessary; a reliable evidence trail is enough.
A worked document-review example
A FAR cutoff TBS gives a December trial balance, a shipping log, three sales invoices, and a memo stating "all December sales were recorded." The grid wants a year-end revenue adjustment. Walk the frame: the response format is a number with a sign; the period is the fiscal year ending December 31; the most reliable source for shipment timing is the independent shipping log, not the memo. The log shows invoice 1042 shipped January 2 but was booked December 31. Free-on-board (FOB) shipping point means control transfers at shipment, so the sale belongs in January.
The adjustment reverses revenue and the related receivable in the current year. The memo is the distractor; the log is decisive.
Common document-review traps
- Sign and direction errors. A correct dollar amount entered as a debit instead of a credit, or as a positive instead of a negative, scores zero in most cells.
- Wrong period. Using a prior-year basis, an interim balance, or a forecast figure where year-end is required.
- Trusting the narrative. Accepting a management memo over an executed contract or external confirmation.
- Blank vs zero. Some grids require a typed 0; others require the cell left empty. Read the instruction line.
- Format mismatch. Entering a percentage where the cell wants a dollar amount, or a label where it wants a date.
A FAR simulation includes a signed lease agreement, an email from the controller summarizing the lease, a preliminary rent schedule, and a final amortization schedule tied to the signed agreement. The requirement asks for the year-end lease liability. Which source should receive the most weight?
In an AUD document review TBS, management says inventory counts were observed at all locations, but the count sheets show one warehouse was not observed until three days after year-end. What is the best next step?