## Test of Controls (TOC) — Concept and Objectives
### What is TOC?
Test of Controls is a procedure to evaluate whether internal controls are operating effectively (not just whether they exist — that is covered under understanding of IC via SA 315).
```
Understanding of IC (SA 315)
↓
Evaluation & Risk Assessment
↓
Testing Operating Effectiveness of IC (SA 330 — TOC)
```
### Objective of TOC
To obtain Sufficient Appropriate Audit Evidence (SAAE) about the operating effectiveness of controls.
### When Must the Auditor Perform TOC?
TOC is required in two situations:
Situation (a):
The auditor's assessment of ROMM includes an expectation that controls are operating effectively — i.e., the auditor intends to rely on those controls to reduce the extent of substantive work.
Situation (b):
Substantive procedures alone cannot provide SAAE at the assertion level (this often occurs in IT-heavy environments where a paper trail is absent).
### Nature of TOC Procedures
When performing TOC, the auditor must go beyond mere inquiry and combine procedures to obtain evidence about:
1. How controls were applied at relevant times
2. Consistency with which they were applied during the period
3. By whom or by what means they were applied
Specific procedures used in TOC:
| Procedure | Application in TOC |
|---|---|
| Inquiry + Observation | Together confirm whether a control was actually performed |
| Inspection of Documents | Verify that transactions were authorised (e.g., signature on voucher) |
| Re-performance | Independently re-execute a control originally done by the entity (e.g., re-doing bank reconciliation) |
| Testing on computerised IT applications | When controls operate through IT systems |
Indirect Controls: If a control depends on another control, the auditor must also test that indirect (supporting) control.
> Example: If the system auto-posts journal entries based on a master-file setting, the auditor must also test the access controls over that master file.