Sarbanes-Oxley: What IT managers need to know
Staff
Published: 18 Jan 2005 11:30 GMT
Testing control effectiveness
In general, testing controls boils down to three steps: First, inventory the control activities. Second, write test plans to evaluate the effectiveness of each control activity. Third, relate each activity to an "underlying assertion" in the financial statements.
Once you have an inventory of control activities, you can begin writing your tests of effectiveness. These tests determine whether the control is operating as intended and whether the person performing the control is properly qualified and authorised to do so.
The next step is to classify each control activity by relating it to the underlying financial statement assertions: Existence or Occurrence; Completeness; Valuation or Allocation; Rights and Obligations; and Presentation and Disclosure. Then you'll want to indicate whether your control is manual or automated, and indicate if the control is preventative or detective.
If you're starting to get bogged down by the audit jargon, you can read up on how to apply these terms by going to www.auditnet.org/sbc.htm and downloading the two-volume publication called Standards for Business Controls.
Next, you have to write the test steps, which are also known as audit procedures. Audit procedures consist of a combination of inquiry, observation, and detailed testing through either examination or re-performance. For ideas on how to test your controls, try reviewing existing audit programs. One source of free audit programs is www.auditnet.org.
To ensure coverage on the test of effectiveness, the PricewaterhouseCoopers approach uses four information processing objectives: Completeness, Accuracy, Validity and Restricted Access (CAVR). The CAVR approach gives you a standardised means to measure each control activity. You should select the information processing objective(s) which best relates to your control activity. Ideally, each element of CAVR should be addressed in some combination of control activities for each objective.
If you'll just have faith and follow along with what your project manager asks, your piece of the "control effectiveness" mosaic will eventually fit into place.
Previous
Did you find this article useful?
230 out of 464 people found this useful
Digg
Slashdot
Del.ici.ous
Stumble
Reddit
