External Audit Substantive Testing Plan: Step-by-Step Template
A substantive testing plan translates audit risk into practical procedures. Use this step-by-step template to document what you will test, why you will test it, and how you will evaluate results.
Step 1: Define objectives and scope
Start from what “good” looks like for the financial statement line items you will test. Identify the population, boundaries (cutoff date, frequency), and the specific account balances, classes of transactions, and disclosures included in scope.
Step 2: Map assertions to key risks
For each line item, link audit risk considerations to financial statement assertions (existence, completeness, valuation, accuracy, cut-off, rights/obligations, presentation/disclosure). Your goal is to ensure substantive procedures are not generic. They should be targeted.
For each assertion, write the expected failure mode, the observable indicator, and how your procedures would detect it.
Step 3: Choose procedures and evidence
Select procedures that produce sufficient appropriate audit evidence. Typically, you combine a mix: tests of details and substantive analytical procedures. Tie each procedure to a specific assertion and expected evidence type.
Step 4: Plan sampling and testing approach
Define whether you will test all items or use sampling for details and for controls-supported reliance (where relevant). State how you will address non-sampling risk and document how you will treat exceptions.
Step 5: Set performance materiality and tolerable misstatement
Your substantive testing plan should be consistent with materiality decisions. Record how performance materiality informs procedure selection and tolerable misstatement thresholds used to evaluate results.
Translate totals of identified misstatements into conclusions for each assertion and the affected line item, then roll up to overall financial statement impact.
Step 6: Document expected results and evaluation criteria
Write clear decision rules before you test. For analytical procedures, define expected ranges and thresholds for investigation. For tests of details, define reconciliation and verification expectations and what documentation will be required for exceptions.
- Expected ranges: basis for comparisons, time-series considerations, and independent data checks.
- Investigation triggers: how far variance can deviate before follow-up is mandatory.
- Conclusion structure: how you will support “no exceptions,” “exceptions corrected,” and “exceptions not corrected.”
Step 7: Execute, reconcile, and communicate outcomes
During execution, record who performed the work, how evidence was captured, and how exceptions were resolved. After testing, reconcile results to balances, document the impact of misstatements, and link conclusions back to the assertions and risks that drove the plan.
Why this template works
A strong substantive testing plan keeps you disciplined: it starts with risk and assertions, it chooses procedures that create the right evidence, and it ends with documented evaluation criteria. That approach makes your conclusions defensible and easier to review.