Chapter 6 Test of Controls
Chapter 6 Test of Controls
Ch # 6: Test of Controls
Any technique that enables auditor to use IT systems as a source of generating audit evidence.
Test data
Involves the auditor processing a sample of data through the IT system and comparing the results
obtained from the processing with pre-determined results.
Procedures may be written into client’s computer information systems that will generate data for audit
purposes every time the process is run.
Normally, to avoid corrupting client’s data files, an extra ‘dummy’ department is stablished, to which the
test data results are allocated. Only the auditor should have access to the data stored in this dummy
department.
CAATs can be expensive, and the use of CAATs should be evaluated on a cost benefit basis.
▪ Purpose is to allow the auditor to carry out tests at the time that transactions are being processed, in
‘real time’.
▪ This can be very useful for the audit of online systems where:
- Data is continually processed and master files are being continually updated, and/or
- It is difficult for system to provide a satisfactory audit trail.
▪ An embedded audit facility may also keep record of the transactions it has monitored so that the
auditor can study those.
6. Test of Controls Page 48
Audit software may need to be compatible with the client entity’s IT system, and can therefore be
expensive to use, especially:
▪ When used for the first time for a client (set-up costs)
▪ Client entity changes its accounting system
(New audit software is needed)
▪ When client has an old purpose-written IT accounting system for which there is incomplete system
documentation.
Auditor should also be aware of the possibility that if he uses copies of the client’s files for carrying out tests
with audit software that the client may provide a file that is not actually a copy of the current ‘live’ files.
When using such files, auditor should insist on being present to observe the copying of the files, to make sure
that they are ‘genuine’.
With auditing around the computer, the client’s internal software is not audited. Instead, inputs to the
system are checked and agreed with the outputs from the system.
Auditing around the computer has greater audit risk than auditing of the client’s internal software,
because:
▪ If the actual files or programs are not tested, there will be no evidence that programs are functioning
properly, as documented
▪ Where auditor finds discrepancies between input and output, there is no way of finding out how the
discrepancy has occurred.
6. Test of Controls Page 49
SALES System
▪ Orders may be accepted ▪ There should be segregation of ▪ Check that proper segregation of
from new customers; or duties between duties is present between these
they may be given credit, ✓ Processing of orders functions
without authorisation ✓ Checking credit reference on ▪ Check that new customer have been
▪ Orders of more than new customers or checking limit approved by looking for the
credit limit may be on existing. signature of the manager giving the
accepted. ▪ New customers, and credit limit, authorisation
▪ Overlooking of orders should be authorised. ▪ Look at lists of customer orders,
▪ Orders may be processed ▪ Sequentially-numbered documents sequentially numbered, and
twice. should be used. confirm that for every customer
▪ Price discount is given ▪ Goods should not be dispatched to order there is a dispatch note
without authorisation. customers without a dispatch note. number.
6. Test of Controls Page 50
▪ Goods are not dispatched ▪ Goods Delivery Notes (GDNs) ▪ Check some delivery notes to
▪ Goods are dispatched should be numbered sequentially confirm that customers do sign
twice. ▪ GRN should be attached to copy of them.
▪ Goods dispatched to customer order. ▪ Check that the segregation of duties
customers who do not ▪ GDN should be signed by an does exist.
have sufficient credit authorised dispatch staff. ▪ Check that all GDNs are serially
▪ Invoices not produced for ▪ Customers should sign a delivery numbered
goods dispatched. note for the receipt ▪ Check that (sequential) lists of
▪ Customers may claim not ▪ Signed delivery note should be invoices show a customer order
receiving the goods attached to a copy of GDN and number and a dispatch note
▪ Sales return are not customer order. number.
properly recorded ▪ Copies of documents should be ▪ Check a list of credit notes to make
transferred to accounts department sure that they cross-refer to sales
after dispatch. invoice number
▪ Each sales invoice should be linked ▪ Check authorization of relevant
to these documents. staff on credit notes
▪ Sales invoices should be ▪ Observe the dispatch process in
sequentially numbered operation.
▪ Segregation of duties between
✓ Dispatching goods
✓ Preparing sales invoice.
▪ Credit notes should be properly
authorised.
▪ There should be periodic checks on
accuracy of invoices
▪ Invoices and credit notes ▪ Invoices and credit notes should be ▪ Check for the sequential numbering
may not be recorded in sequentially numbered. of invoices and credit notes
the system. ▪ Regular statements should be sent ▪ Check that statements are produced
▪ Invoices and credit notes to customers. and dispatched to customers.
are recorded in the ▪ Control account reconciliations ▪ Look for documentary evidence for
wrong customer ▪ Bad debts must be authorised. control total checks
▪ Debts may be written off ▪ Procedures for identification and ▪ Check authorization for bad debt.
as without proper follow-up of overdue accounts etc ▪ Check that exception report is
consideration. regularly produced by system,
listing all overdue debts, and check
that this is followed up.
6. Test of Controls Page 51
PURCHASES System
PAYROLL
Petty cash
Control objectives
▪ To avoid or reduce the risk of petty cash being stolen.
▪ To ensure that all spending out of petty cash is properly authorised.
▪ To ensure that only correct amounts of cash are withdrawn from bank to go into petty cash.
▪ To ensure that all spending out of petty cash is accounted for.
Controls
▪ Maximum amount held in petty cash should be restricted to about 1 month spending.
▪ Petty cash should be kept in a locked cash box in the office safe, or if there is no safe in a locked drawer
in the accountant’s desk. This is a basic physical control over cash.
▪ All withdrawals of petty cash should be recorded on a petty cash voucher and vouchers must be
sequentially numbered.
▪ All petty cash spending should be authorised in advance by a properly authorised person (and not by
the person withdrawing the cash).
▪ Receipts should be provided for petty cash spending and attached to petty cash voucher.
▪ When money is withdrawn from bank to ‘top up’ petty cash, the amount of cheque for cash withdrawal
should be checked against total of petty cash vouchers in the petty cash box.
▪ There should be occasional checks of petty cash by a senior person (not the person responsible for
holding and issuing petty cash) .
▪ There should be a system for the regular recording of petty cash expenses in the petty cash book. Each
entry in the petty cash book should include the voucher number
6. Test of Controls Page 57
Note: The above given controls are only related to the maintenance of the inventory. Controls relating to receipt and
dispatch of inventory are discussed earlier in Sales and Purchase system.
6. Test of Controls Page 58
Non-current assets
▪ Control systems in smaller entities are often less sophisticated than larger organisations.
▪ This is largely due to a lack of resources.
▪ A proper segregation of duties is often very difficult in small entities.
▪ Most probably there will be extensive involvement in control activity by senior management or the
entity’s owner.
▪ Auditor will look for the existence of ‘minimum business controls’.
▪ Auditor is unlikely to be able to use controls as a basis for using a systems-based approach.
▪ A large amount of substantive testing is likely to be adopted.