Control Testing for Client Audits 2026
Test whether a client’s stated controls operate in practice. Plan audit work from the reporting risk, document exceptions and evaluate reliance.
- Published
- Updated
Control testing checks whether a client’s controls operate effectively against assessed financial-reporting risks. Tie each test to an assertion and use evidence beyond enquiry.
Start with the misstatement the control is meant to prevent or detect. A signed checklist can show that someone signed it. Your test must establish whether the person performed the review that addresses the risk.
From Reporting Risk to a Test
A control test needs a clear connection between the reporting risk and the evidence examined. ASA 315 risk-assessment requirements distinguish evaluating design and determining implementation from testing operating effectiveness.
Design asks whether the control can address the risk. Implementation establishes whether the client has put it into use. A walkthrough can support that understanding, but one transaction does not establish consistent operation throughout the period of intended reliance.
Consider this fictional client. The accounts clerk prepares a monthly bank reconciliation. The finance manager reviews reconciling items against supporting records and documents how unresolved items are followed up.
The assessed risk is that unsupported reconciling items conceal an overstated cash balance. Existence and accuracy of cash are relevant assertions. The test therefore examines what the finance manager checked and how exceptions were resolved.
Use this test objective: determine whether the finance manager reviewed each reconciliation and investigated unsupported reconciling items before approving it. Define what counts as timely review for this client’s control.
Under ASA 330 audit responses, test controls when you intend to rely on their effectiveness. Testing is also required where substantive procedures alone cannot provide sufficient appropriate evidence at assertion level.
Control reliance does not remove substantive procedures for material transaction classes, balances and disclosures.
If the documented review cannot detect the assessed misstatement, change the audit response before selecting items. A larger sample cannot repair an ineffective control design.
Choose the Procedure and Extent
Choose procedures that reveal how the control operated over the period of reliance. Ask the owner to explain the work, then corroborate that explanation with evidence of actual performance.
Evidence for the Monthly Review
| Procedure | What you do | What the evidence can establish | Limit |
|---|---|---|---|
| Enquiry | Ask the finance manager how unusual reconciling items are challenged | Expected practice and explanations for exceptions | An explanation alone does not prove effective operation |
| Observation | Watch the manager perform a review | How the review operates while observed | It covers that occasion and behaviour can change under observation |
| Inspection | Examine reconciliations, supporting records and review comments | Who reviewed the work, when and what they investigated | A signature alone can leave review quality unclear |
| Reperformance | Independently perform the relevant reconciliation checks | Whether the checks identify the items they are meant to detect | Your successful check does not prove the manager performed it |
Combine procedures to answer the objective. For example, inspect evidence of the manager’s challenge to an old reconciling item, then reperform the check using its supporting records.
When the control uses a system report, assess whether that report is sufficiently complete and accurate for the test. Review evidence loses meaning if the underlying report leaves out transactions the control must cover.
Set the Period and Selection
- Define the population. For the fictional monthly review, it comprises the 12 reconciliations for the period under audit. Reconcile that list to the client’s records before selecting work.
- Record the intended reliance and risk addressed. Specify the review attributes to test, including investigation of unsupported items and the authority of the reviewer.
- Choose the extent and selection approach. Consider frequency, expected deviations and the persuasiveness of evidence. Explain how the selection covers the relevant period and changes in staff or systems.
- Perform the procedures and retain the identifying details. Trace each conclusion back to the reconciliation, review record and supporting item examined.
- Evaluate whether the evidence supports the planned reliance. If testing ends before the reporting period ends, address the remaining period before extending that conclusion.
ASA 530 Audit Sampling addresses sample design and evaluation. It requires a sample size sufficient to reduce sampling risk to an acceptably low level. It does not supply one universal number for every control.
For sampling, document the tolerable deviation rate and expected deviation rate alongside the intended reliance. Select items so each sampling unit has a chance of selection.
Testing every reconciliation in a small population is another possible approach. Distinguish that decision from sampling. For automated controls, assess the relevant information-technology dependencies as well as evidence that the automated rule operates.
Evaluate Exceptions
A deviation changes the evidence supporting reliance. Investigate its cause and consider whether the planned audit response remains appropriate. A later explanation or a clean substantive test does not automatically remove the deviation.
In the fictional engagement, the auditor inspects all 12 monthly review packs. One pack has a reviewer’s signature but no evidence of investigation into an old reconciling item. The control requires documented follow-up before approval.
The finance manager says a delegate reviewed the item during an absence. The auditor inspects the delegate’s permissions and searches the retained review correspondence. Neither provides evidence that the required follow-up occurred.
Record a deviation for that review. The auditor then examines reviews performed during other absences and finds the same delegation arrangement lacked documented review duties. The issue can affect more than the first missing comment.
The team concludes that the evidence does not support its planned reliance on this review control. It revises the cash audit work, including procedures over unresolved reconciling items, and considers whether another control can support reliance after testing.
The underlying item can still be correct. Keep the control deviation separate from any monetary misstatement found during further work. Evaluate whether the deficiency needs communication under the applicable auditing requirements.
If evidence instead establishes that the required review occurred and was retained elsewhere, document that evidence and evaluate it against the test attributes. Do not treat an unsupported oral explanation as equivalent evidence.
Document the Conclusion
ASA 230 Audit Documentation requires a record that lets an experienced auditor understand the work and its results. Identify the items tested and record who performed and reviewed the work.
Fictional Workpaper Extract
| Field | Recorded work |
|---|---|
| Objective and assertion | Determine whether review detects unsupported reconciling items that could overstate cash; existence and accuracy |
| Control and owner | Finance manager reviews monthly bank reconciliations and documents investigation before approval |
| Population | All 12 monthly reconciliations, reconciled to the period’s reconciliation register |
| Selection | All 12 inspected; full-population inspection, not a sample |
| Work performed | Inspected approval timing and authority; traced review comments to supporting records; reperformed selected checks of reconciling items |
| Evidence references | Retained reconciliation packs BR-01 to BR-12, supporting-item checks and delegation correspondence |
| Exception | One pack lacks required follow-up evidence; corroborating enquiry and correspondence do not establish performance |
| Evaluation | Delegation duties were unclear during absences; planned reliance is unsupported |
| Further work | Cash procedures revised and cross-referenced to the substantive workpaper; deficiency communication assessed |
| Preparation and review | Record the preparer, completion date, reviewer and review date in the engagement file |
The full file must identify which checks were reperformed and why, with their results. This extract does not substitute for those underlying records or the engagement’s judgement about test extent.
Before signing off, trace the conclusion back to the assertion and assessed risk. Check that the revised audit programme reflects the reliance decision and that every unresolved exception has an owner and a recorded response.
One client form. One finished return.
Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.
Made for Australian accounting firms