Keep ITGC testing tied to financial reporting risk
IT general controls support the systems and processes that financial reporting relies on. Access administration, change management and computer operations involve different evidence and testing questions. Treating all three as the same checklist can obscure the control objective and leave important attributes untested. Scope should follow the relevant system and risk, not merely the existence of an available data export.
walktru brings control information, evidence classification and testing results with reasoning into a connected workflow. Its existing ITGC articles describe procedures for change management and computer operations, including population reliability and traceable decision criteria. IT Audit teams can use a focused evaluation to determine which steps fit their methodology and where additional evidence or manual review is required.
Organize the evidence before applying criteria
For change management, useful evidence may include change records, approvals, testing support and deployment details. For computer operations, it may include job logs, incident records or backup reports. An access test may require account data, request documentation and review evidence. Each source needs to reflect the relevant period and population; an export from the right application can still contain the wrong scope.
Define the attributes needed to support the control conclusion. Then classify evidence, check relevant completeness and accuracy considerations and connect observations to the test. walktru’s deterministic approach is designed to make execution repeatable and the reasoning reviewable. An exception should remain visible with its supporting evidence and the reviewer’s evaluation, rather than disappear into a summarized status.
Testing checklist
- Confirm the financially relevant system and control.
- Establish the period and reliability of the population.
- Apply the control’s specific approval, timing or execution criteria.
- Document follow-up and the final evaluation.
Example: change approval before deployment
Consider a control requiring approval before a production change. The test may compare the approval record with the deployment timestamp and verify the approver’s role under the documented policy. A ticket marked closed does not, by itself, demonstrate timely approval. A complete testing record should distinguish an approval that exists from one that occurred in the required sequence.
Emergency changes may follow different procedures. If the policy allows retrospective approval, document that pathway and test against its requirements rather than apply the routine-change rule indiscriminately. This is an illustrative example of criteria-based testing, not a claim that every ticketing or deployment system is integrated. Confirm supported sources and the evidence needed for your environment during a demo.
Broader coverage still requires reliable inputs
Where a complete and reliable population is available, automation can apply appropriate procedures across more records than a manual review would ordinarily handle. Coverage must still be described accurately. Testing every row of one export does not prove that every relevant system, event or attribute was included. The underlying population and the suitability of each automated procedure remain central to the conclusion.
SOX TRAIL® helps connect evidence, test activity, exceptions and conclusions. Use that record to evaluate what was tested and what remains unresolved. ITGC testing also connects to IPE reliability and application controls, since reliance on automated financial processes can depend on both the general control environment and the specific control logic.