AUD · Performing Further Procedures and Obtaining Evidence · 8 practice questions
Audit Data Suitability: Relevance and Precision
Accurate, complete data must also fit the measure and level of detail needed for the audit procedure. Below, one net-sales scenario changes one fact at a time to show what makes a report suitable.
Try one first
Hint
Ask whether the dataset measures net sales (actual transaction prices less discounts and returns) or a different metric (e.g., units × current list price).
Answer A. Analytical evidence must be relevant to and sufficiently precise for the asserted amount. The report uses current list prices and omits actual transaction prices, discounts, and returns, so its measurement basis does not match recorded net sales. The auditor should obtain suitably detailed data (transaction-level prices, discounts, returns) or redesign the substantive procedures to address these gaps before relying on the analytical procedure.
Why not B: Tempting because auditors sometimes use reasonable estimates to bridge data gaps. But the stem indicates discounts vary significantly and prices changed during the year, so applying unvalidated average adjustments risks material misstatement; such estimates would themselves require validation or separate substantive procedures.
Why not C: Tempting because testing completeness and accuracy of internally produced data is a key reliability step. However, even accurate unit counts are not relevant if the pricing/adjustments differ from the recorded net sales measurement basis; list prices × units will not reflect actual net sales when discounts, returns, and multiple price changes are material.
Why not D: Tempting for candidates who favor a conservative approach, but overly broad. Internally produced information is not inherently unusable; the auditor should evaluate and, where possible, obtain or derive appropriate transaction-level data or redesign procedures rather than categorically discarding all client-generated reports.
Same scenario, one fact changes
Base case
During Alder Co.'s Year 2 audit, the auditor plans monthly net-sales analytics. An ERP report provides transaction-level units shipped and actual sales amounts net of discounts and returns, grouped by month. Prices and discounts vary during the year. The auditor has tested the report's logic, completeness, and accuracy.
Answer: Suitable as an input to the monthly net-sales analytics.
The tested report measures actual net sales and provides the monthly detail the procedure needs. Suitability as an input does not, by itself, establish that the analytical procedure provides sufficient evidence.
Before you open each one, predict the answer.
Change 1The report substitutes units multiplied by current list prices for actual sales amounts net of discounts and returns.
Answer: Not suitable without adjustment or redesigned procedures.
Current list prices omit actual pricing differences, discounts, and returns. Tested unit counts do not make that measure suitable for net-sales analytics.
Change 2The report is aggregated to annual totals, with no monthly or transaction detail.
Answer: Not suitable for the planned monthly analytics.
Accurate annual totals cannot supply the monthly amounts needed for monthly expectations. Obtain monthly detail or redesign the procedure.
Change 3The report comes from a spreadsheet rather than the ERP; all other facts remain unchanged.
Answer: Still suitable as an input to the monthly net-sales analytics.
The source change does not defeat suitability. The stated testing still supports the report, and its measure and monthly detail still fit.
Key points
- Remember: accurate data can still be the wrong data for the procedure.
- Net-sales analytics need actual sales amounts after discounts and returns, not units multiplied by current list prices.
- Monthly expectations require monthly information; annual totals hide the detail needed.
- A spreadsheet is not automatically unsuitable, just as an ERP report is not automatically suitable.
How the exam traps you
- Treating tested completeness and accuracy as proof that current list prices measure net sales. Check whether the amounts reflect actual transaction prices, discounts, and returns.
- Using accurate annual totals to develop monthly expectations. Obtain monthly detail before using the report for monthly analytics.
- Rejecting a tested report solely because it comes from a spreadsheet. Evaluate its evidence and fitness for the procedure, not just its source.
Now the same facts as questions
Each question changes one fact from the one before. Watch which change flips the answer.
Question 1
Answer A. The tested report matches net sales and provides the needed monthly detail.
Why not B: Price variation does not prohibit analytics when suitable data support the expectation.
Why not C: System origin alone does not establish accuracy, completeness, or fitness for purpose.
Why not D: Monthly expectations require monthly information.
Question 2
Answer B. The auditor must address actual transaction pricing, discounts, and returns before relying on the procedure.
Why not A: Accurate units do not correct the mismatch between list-price sales and actual net sales.
Why not C: The problem concerns this report's measure, not all internally generated information.
Why not D: Current list prices do not capture those adjustments.
Question 3
Answer C. Monthly expectations need monthly information, which this report lacks.
Why not A: Reliability testing does not supply missing monthly detail.
Why not B: The correct measure is not enough when the reporting period does not fit.
Why not D: An annual report may fit another purpose; it does not fit this monthly procedure.
Question 4
Answer D. The report remains tested, relevant, and sufficiently detailed for the planned analytics.
Why not A: A spreadsheet is not automatically unsuitable.
Why not B: List prices would remove the actual net-sales measure needed for this procedure.
Why not C: Standards do not require ERP origin when appropriate evidence supports the information.
Question 2
Hint
Separate two questions: Is the data reliable, and is it granular enough for the way the auditor plans to use it?
Answer B. The facts in the stem address reliability: the report is a standard system output, controls were tested and effective, there were no manual edits, and the total ties to the general ledger. The remaining primary concern is suitability for the auditor's intended analytic, specifically whether the data are sufficiently granular and timely. Because rebate rates vary by customer tier and significant contract changes occurred mid-quarter, aggregation by product family and quarter may prevent a meaningful expectation for the rebate liability.
Why not A: This distractor is tempting because candidates recall that entity-generated information requires evaluation. However, the stem already provides strong evidence of reliability (standard report, tested controls, no manual edits, GL tie). Standards do not mandate source-document tracing when other appropriate evidence supports reliability.
Why not C: This is appealing if a candidate overgeneralizes the risk from contract changes, but it's incorrect: auditing standards do not categorically prohibit analytical procedures due to contract changes. The issue is whether the data and expectation can be made sufficiently precise despite the changes.
Why not D: Tying the report to the general ledger supports high-level completeness and accuracy but does not address whether the report's level of aggregation is adequate for the specific assertion being tested. Suitability depends on precision and granularity as well as basic reliability.
Question 3
Hint
Separate two questions: Is the information reliable enough, and is it fit for this exact audit purpose? A report can pass some reliability testing and still be unusable if its timing or coverage does not match the assertion being tested.
Answer A. The auditor must evaluate not only general reliability but fitness for the specific purpose. The internal report's timing (invoice date versus shipment date) and return-period treatment do not match the entity's recognition basis, and the external statistics cover only part of the population (62% domestic retail). Those misalignments mean the data are unsuitable, without additional adjustment, for developing a monthly expectation of total recognized revenue.
Why not B: This is tempting because direct testing can sometimes compensate for weak controls. But the auditor's reperformance revealed substantive basis mismatches (invoice date vs. shipment date and differing return timing) that affect the measurement the auditor needs; the external data's limited coverage (only one channel) does not resolve those mismatches.
Why not C: This is tempting because candidates often overvalue a successful reconciliation to the general ledger. However, an annual tie-out does not establish that monthly figures are accurate on the correct recognition basis or that the report's timing and return handling match the assertion being tested; the external data also does not cover the full population.
Why not D: This distractor appeals to candidates who treat ineffective IT controls as an absolute bar. In practice, deficient controls do not automatically render internally produced information unusable if sufficient evidence about accuracy and completeness can be obtained; the problem here is that the information is not aligned to the intended monthly recognition basis and coverage.
Question 4
Hint
Focus on what the auditor must establish about entity-produced information before relying on it, not just who reviewed it or how it was produced.
Answer B. The controlling consideration is the reliability of entity-produced information for the auditor's intended purpose. The auditor must obtain evidence about the report's accuracy and completeness and judge whether it is sufficiently precise and detailed for the planned test. Routine review by management, agreement of totals, or the report's system origin do not, by themselves, establish that reliability.
Why not A: Tempting because management review suggests the report is used and monitored, but review alone does not provide direct evidence that the underlying data are accurate, complete, or sufficiently detailed for the auditor's procedure.
Why not C: Tempting because reconciling totals offers some assurance, but agreement of a total does not ensure the report's completeness or accuracy at the monthly or transactional level, nor that it is precise enough for testing monthly warranty expense.
Why not D: Tempting because system-generated reports often seem more reliable, but the source alone is not decisive; the auditor still needs evidence that the information is accurate, complete, and appropriate for the specific audit test.
Common questions
What makes audit data relevant and sufficiently precise?
The data must match what the procedure tests and provide enough detail. For monthly net-sales analytics, that means actual net sales amounts and monthly information.
Why aren't accurate units shipped and list prices enough to test net sales?
Current list prices do not capture changing transaction prices, discounts, and returns. Accurate unit counts do not fix that measurement mismatch.
Can an auditor use a spreadsheet as audit evidence?
Yes. In this scenario, the spreadsheet remains a suitable input because its logic, completeness, and accuracy were tested, and its measure and monthly detail fit the procedure.
Watch it solved
A full CPA AUD task-based simulation on Use of Data and Information, worked step by step.
Data Extract Reliability & Duplicate Payments | CPA AUD TBS on YouTube
Practice AUD like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Use of Data and Information
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.