How to Verify Inter-System Transaction Completeness?
Which test approach provides the GREATEST assurance of the completeness of transactions transferred between systems?
Community Votes
56% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the fundamental audit distinction between tracing and vouching, with the common trap being reliance on aggregate total reconciliation instead of record-level verification.
This CISA question evaluates methods for verifying inter-system transaction completeness. While candidates often debate aggregate reconciliation, the consensus and official guidance favor direct source-to-destination tracing for maximum assurance.
Option A is frequently selected because reconciling totals appears comprehensive, but it only confirms numerical balance rather than proving every individual transaction successfully transferred.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Directly tracing a sample of transactions from the source system to the destination system is the definitive audit procedure for testing completeness. This approach verifies that every recorded event originating in the source environment actually arrived at the receiving system without omission. By cross-referencing the master source list against destination records, auditors eliminate guesswork and obtain tangible evidence of successful data migration.
Why the Other Options Are Wrong
Option A relies on aggregating transaction totals, which can easily mask missing or duplicated individual records due to offsetting errors. Option B reverses the direction by sampling from the destination back to the source, which primarily tests existence or occurrence rather than completeness. Option C focuses on exception handling workflows, which are valuable for operational monitoring but do not provide direct substantive evidence of transfer accuracy.
Community Comment Notes
The voting split highlights a classic certification dilemma, with several users initially favoring aggregate reconciliation. Comment [2] correctly identifies that total reconciliation differs fundamentally from individual transaction verification, explaining why it acts as a distractor. Comments [3] and [4] accurately emphasize that direct source-to-destination sampling aligns with ISACA’s standard for completeness assurance, reinforcing why tracing outperforms summary-level checks.
Exam Strategy
Always distinguish between tracing (source → destination for completeness) and vouching (destination → source for existence). When asked for greatest assurance on data transfer integrity, prioritize direct record-level verification over aggregate summaries.
Frequently Asked Questions
Why is reconciling totals insufficient for completeness?
Aggregate reconciliation only verifies mathematical balance, allowing individual missing or duplicated transactions to mask discrepancies. Direct tracing catches these gaps at the record level.
Does sampling reduce the assurance level for completeness testing?
Sampling is acceptable when populations are large, provided the statistical method targets high-risk transfers. Full population testing is ideal but often impractical in live environments.
Related Analysis
Practice All CISA Questions
Access 400 questions with complete answers and detailed explanations.
View Full CISA Practice Test →