15.2 Selecting Analytical Techniques for Engagement Objectives

Match the Technique to the Engagement Objective

Section B5b asks you to determine appropriate analytical techniques to achieve engagement objectives. The syllabus does not want a favorite tool. It wants a match. Efficiency, completeness, existence, accuracy, cutoff, and fraud-or-abuse each fail in different ways, so each needs a different analytical lens—or a decision that analytics will not be enough and tests of details must carry the work.

Start from the objective written in the work program, not from the data you happen to have. If the objective is "assess whether warehouse labor is used efficiently," inventory turns and the current ratio are the wrong instruments even if they are easy to compute. If the objective is "assess whether recorded sales are complete," vouching recorded invoices to customer orders tests the wrong direction (occurrence, not completeness). The technique has to be capable of detecting the kind of misstatement or process failure the objective cares about.

Reasonableness Tests

A reasonableness test is the technique CIA items use when the objective is completeness or overall reasonableness of a total. You build an independent estimate of what the recorded amount should be, using data that does not come solely from the same recording process, and you compare that estimate to the book. Classic pattern: independently obtained shipment quantities × average selling price ≈ recorded sales. Other patterns: occupied rooms × average daily rate ≈ room revenue; production units × standard yield ≈ recorded output; badge hours × contractual rates ≈ recorded contract labor; metered usage × tariff ≈ recorded utilities.

Three quality tests decide whether the reasonableness test can actually achieve the objective:

1. Independence of the driver. If you estimate sales from the same invoice file you are testing, you have a circular procedure. Pull quantities from the warehouse-management or transportation system, from bills of lading, or from a third-party logistics feed.
2. Stability of the conversion factor. Average price works if mix is stable or if you stratify. A blended average that hides a shift from high-price to low-price SKUs will miss incompleteness or bury overstatement.
3. Precision versus the threshold. If your estimate can only be good within plus or minus 20 percent, you cannot treat a 8 percent book-to-estimate gap as comfort, and you also cannot treat it as a finding. You do not have a sharp enough instrument. Either improve the model (better drivers, stratification) or move to tests of details.

Related-account relationships are a cousin of reasonableness tests. Sales, COGS, inventory, and freight should move in economically coherent ways. A jump in recorded sales with flat shipments, falling inventory that does not match throughput, or freight that does not move with cartons is an unexpected relationship. Coherence is not proof of completeness, but incoherence is a signal that completeness, cutoff, or classification may have failed.

Precision, Residual Risk, and When Analytics Are Insufficient

Analytics give assurance only to the extent the expectation is precise and independent. A high-assurance objective on a material account with a noisy expectation is a mismatch. In that case the correct technique is not "more ratio analysis." It is tests of details: vouching, tracing, confirmation, inspection, reperformance, and recalculation directed at the population that remains risky.

Treat this as a decision rule, not a vibe:

• If the objective needs only a reasonableness view, and the expectation is tight, and the difference is inside the threshold, analytics can be the primary procedure for that objective.
• If the difference exceeds the threshold, management's explanation must be corroborated with evidence. Vague commentary ("it was a busy quarter") is not corroboration.
• If the explanation is uncorroborated, or only explains part of the gap, analytics are insufficient. Design tests of details for the unexplained portion.
• If you never could build a precise expectation—missing driver data, unstable mix, unreliable system reports—do not pretend the procedure ran. Go to details (or change the approach and document why).
• If the objective is fraud, existence of specific recorded items, or accuracy of individual transactions, start with the assumption that high-level ratios will scope work, not finish it.

North Hub again. Objective A: efficiency of outbound freight. Technique: freight dollars per shipment versus a flexible budget and versus South Hub. Independent inputs: shipment counts from the transportation-management system. If actual is $448,000 versus a $460,000 expectation, analytics can support a no-exception conclusion on efficiency for this procedure.

Objective B: completeness of recorded sales at the same company. Technique: shipments × average selling price, stratified by product family. If the estimate is $18.4 million and recorded sales are $16.1 million, a 12.5 percent shortfall against a 4 percent threshold is not something you "ratio away." Investigate cutoff, unbilled shipments, and missing invoice runs. If inquiry does not close the gap with evidence, trace from shipping documents to recorded sales (a test of details in the completeness direction).

Objective C: whether duplicate vendor payments indicate fraud. AP turnover versus last year can be perfectly stable while duplicates still flow. The matching technique is targeted anomaly work (same invoice number, same amount different invoice, split payments just under approval limits) plus details on the hits. Choosing AP turnover because it is "an analytical procedure" fails B5b: the technique does not achieve the objective.

On the exam, when the stem asks which procedure best achieves the objective, name the technique that could detect the failure mode. When it asks what to do after an unexplained difference, do not lower the criteria, do not call it fraud from the ratio alone, and do not accept an uncorroborated story. Say that analytics are insufficient and move to tests of details.