Computer-Assisted Audit Techniques (CAATs)
Computer-Assisted Audit Techniques (CAATs)
The overall objectives and scope of an audit do not change when an audit is conducted in a computerised
environment. However, the application of auditing procedures may require auditors to consider techniques
that use the computer as an audit tool. These uses of the computer for audit work are known as CAATs.
CAATs may be used in performing various auditing procedures, including the following.
Setting up the software needed for CAATs can be time consuming and expensive.
Audit staff will need to be trained so they have a sufficient level of IT knowledge to apply CAATs.
Not all client systems will be compatible with the software used with CAATs.
There is a risk that live client data is corrupted and lost during the use of CAATs.
The major steps to be undertaken by the auditors in the application of a CAAT are as follows.
Set the objective of the CAAT application
Determine the content and accessibility of the entity's files
Define the transaction types to be tested
Define the procedures to be performed on the data
Define the output requirements
Identify the audit and computer personnel who may participate in the design and application of the
CAAT
Refine the estimates of costs and benefits
Ensure that the use of the CAAT is properly controlled and documented
Arrange the administrative activities, including the necessary skills and computer facilities
Execute the CAAT application
Evaluate the results
1
There are two particularly common types of CAAT, audit software and test data.
Audit software
Audit software consists of computer programs used by the auditors, as part of their auditing procedures,
to process data of audit significance from the entity's accounting system. It may consist of generalised
audit software or custom audit software. Audit software is used for substantive procedures.
Generalised audit software allows auditors to perform tests on computer files and databases, such as
reading and extracting data from a client's systems for further testing, selecting data that meets certain
criteria, performing arithmetic calculations on data, facilitating audit sampling and producing documents
and reports. Examples of generalised audit software are ACT and IDEA.
Custom audit software is written by auditors for specific tasks when generalised audit software cannot be
used.
The following table provides some examples of the use of audit software in the course of an audit.
2
Using audit software is likely to be cost-effective in the long term if the
client does not change its systems.
Difficulties of using audit software
The costs of designing tests using audit software can be substantial, as
a great deal of planning time will be needed in order to gain an in-depth
understanding of the client's systems so that appropriate software can be
produced.
The audit costs in general may increase because experienced and specially trained staff will be
required to design the software, perform the testing and review the results of the testing.
If errors are made in the design of the audit software, audit time, and therefore costs,
can be wasted in investigating anomalies that have arisen because of flaws in how the
software was put together rather than by errors in the client's processing.
If audit software has been designed to carry out procedures during live running of the client's
system, there is a risk that this disrupts the client's systems. If the procedures are to be run when
the system is not live, extra costs will be incurred by carrying out procedures to verify that the
version of the system being tested is identical to that used by the client in live situations.
Test data
Examples include:
Test data used to test specific controls in computer programs, such as online password
and data access controls.
Test transactions selected from previously processed transactions or created by the auditors to
test specific processing characteristics of an entity's computer system. Such transactions are
generally processed separately from the entity's normal processing.
Test data can for example be used to check the controls that prevent the processing of invalid
data by entering data with, say, a non-existent customer code or worth an unreasonable
amount, or a transaction which may if processed break customer credit limits.
Test transactions used in an integrated test facility. This is where a 'dummy' unit (eg a department or
employee) is established, and to which test transactions are posted during the normal processing cycle.
3
A significant problem with test data is that any resulting corruption of data files has to be
corrected. This is difficult with modern real-time systems, which often have built-in (and highly
desirable) controls to ensure that data entered cannot be easily removed without leaving a mark.
Test data only tests the operation of the system at a single point of time and therefore the results do not
prove that the program was in use throughout the period under review.
Initial computer time and costs can be high and the client may change its programs in
subsequent years.
Professional audit staff are highly trained and educated, but their experience and training is limited to
accountancy and audit matters. In certain situations it will therefore be necessary to employ an uditor's
expert.
Examples of areas in which an auditor's expert may be needed to help gain audit evidence include:
Valuations of land and buildings
Valuation of inventory or work in progress, including the determination of the physical condition of
inventory
Legal opinions, including expert opinions on the possible outcomes of litigation or disputes
Guidance on this area is provided by ISA 620 Using the work of an auditor's expert.
An auditor's expert could be employed by the auditor to assist in:
Obtaining an understanding of the entity and its environment, including its internal control
Identifying and assessing the risks of material misstatement
Determining and implementing overall responses to assessed risks at the financial statement level
Designing and performing further audit procedures to respond to assessed risks at the
assertion level
Evaluating the sufficiency and appropriateness of audit evidence obtained in forming an
opinion on the financial statements
4
Personal experience with previous work done by the expert
Discussions with the expert
Discussions with other people who are familiar with the expert's work
Knowledge of the expert's qualifications, membership of a professional body or
industry association, licence to practise etc
Published papers or books by the expert
The auditor's firm's quality control policies and procedures
Agreement
ISA 620 requires the auditor to agree in writing the following with the auditor's expert.
Nature, scope and objectives of the work
Respective roles and responsibilities of the auditor and the auditor's expert
Nature, timing and extent of communication between the auditor and the
auditor's expert, including the form of any report
Confidentiality requirements
The agreement between the auditor and the auditor's expert is often in the form of an engagement letter.
The Appendix to ISA 620 lists matters to consider for inclusion in the engagement letter.