Annual Audit Manual
COPYRIGHT NOTICE — This document is intended for internal use. It cannot be distributed to or reproduced by third parties without prior written permission from the Copyright Coordinator for the Office of the Auditor General of Canada. This includes email, fax, mail and hand delivery, or use of any other method of distribution or reproduction. CPA Canada Handbook sections and excerpts are reproduced herein for your non-commercial use with the permission of The Chartered Professional Accountants of Canada (“CPA Canada”). These may not be modified, copied or distributed in any form as this would infringe CPA Canada’s copyright. Reproduced, with permission, from the CPA Canada Handbook, The Chartered Professional Accountants of Canada, Toronto, Canada.
Overview
This topic explains:
- What is a computer-assisted audit technique (CAAT)
- Potential uses of CAATs in the audit process
- The most common uses of CAATs in controls testing
- The most common uses of CAATs in substantive testing
- Other examples of using CAATs in substantive testing
- Detailed examples of two common CAAT tests
What is a computer-assisted audit technique
OAG Guidance
A computer-assisted audit technique (CAAT) is the use of computers to automate an audit process or procedure. CAATs are auditing tools that when properly designed can improve the effectiveness and efficiency of audit procedures that would otherwise be performed on a manual basis. A CAAT may be as simple as using the formula function within Excel to test the mathematical accuracy of supporting schedules. This CAAT would be more efficient than manually recalculating the schedule.
CAATs also enable an auditor to analyze large volumes of data and identify anomalies. CAATs can efficiently provide a high volume of information over the entire population. Through CAATs we can review a complete population of transactions and design a test to address specific risks identified. An example of this type of CAAT may be as simple as the use of pivot tables or sorting and filtering functions within Excel to identify items non-standard or risk related items for targeted testing based on criteria established by the engagement team. This could be a more effective and efficient approach to address risk than selecting items based on a haphazard sample.
While many CAATs can be executed by the engagement team, as the nature of the CAAT becomes more complex or there are complexities in obtaining data files, consult a Data Analytics specialist when planning to perform CAATs as part of audit procedures.
Potential uses of
CAATs in the audit process
CAS Guidance
The use of computer-assisted audit techniques (CAATs) may enable more extensive testing of electronic transactions and account files, which may be useful when the auditor decides to modify the extent of testing, for example, in responding to the risks of material misstatement due to fraud. Such techniques can be used to select sample transactions from key electronic files, to sort transactions with specific characteristics, or to test an entire population instead of a sample (CAS 330.A16).
OAG Guidance
In tests of controls
CAATs can support control testing by making a small selection of transactions and walking them through the system or by developing an integrated test facility and processing transactions through the system. The advantage of using CAATs in controls testing is that it is possible to test every transaction (either in a masterfile or a transaction file) to determine whether there were any control failures.
In substantive testing
The most widely used CAATs are in the area of substantive testing. CAATs can identify non-standard transactions in order to execute a targeted test that would be more efficient and effective than large haphazard sampling of transactions.
CAATs are commonly used in executing audit procedures over journal entries and revenue transactions.
To assist in fraud detection
CAATs can also assist in fraud detection by enabling us to sort through large volumes of data. See OAG Audit 5514 for examples of how CAATs can be used to detect fraud.
Examples of the most common uses of CAATs in controls testing
OAG Guidance
The following table details CAATs which are commonly used in controls testing:
|
Examples of CAATs
|
Information Processing—Application Controls
|
The basic approach is to identify the conditions that should not be present in the entity’s data files if the controls were working properly. By analyzing the entity’s data, we can identify where controls may not have been working properly or that they have been overridden. The following are some examples of CAATs that could be used for automated controls:
-
Tests to determine if transactions are authorized based on the user responsible for entering transaction.
-
Tests of transactions that fall outside control parameters, such as:
-
Amounts over specified monetary limit;
-
Null amounts;
-
Negative amounts;
-
Blank fields;
-
Invalid dates, or dates outside specified range;
-
Invalid field data (for example, location codes, product codes);
-
Lack of dual approval, where required;
-
Lack of appropriate approval level;
-
Duplicate transactions;
-
Gaps in transaction numbers;
-
Payments for goods or services to vendors not in the entity’s vendor masterfile.
-
Tests for the following:
-
Purchase order present, where required;
-
Matching of purchase order, invoice and receiving advice;
-
Matching of delivered goods advice with invoice generation.
|
Information Processing—IT General Controls
|
-
Automated testing of access logs.
-
Generate list of failed attempts (compare over time).
-
Compare successful attempts with list of authorized users.
-
Generate list of changes in access from prior periods.
-
Search for unusual activity (needs to be defined on a client by client basis).
-
Extract lists of authorized individuals from system and:
-
Test with employee lists.
-
Compare with terminated employee list.
-
Generate list of users with high level of access (i.e. super-users).
-
Search for multiple levels of access for same user.
-
Search for software developers with access to production systems.
-
Search for non-developers with access to software development systems.
-
Generate report of dormant users (no access for extended period of time).
-
Compare current access lists with previous periods to detect changes.
-
Make selections of program changes for further testing (targeted testing).
-
Compare program changes in tracking software with changes registered in system.
-
Generate report of system interruptions over time.
|
Examples of the most common uses of CAATs in substantive testing
OAG Guidance
The following table details CAATs which are commonly used in substantive testing:
Account or audit area
|
Examples of CAATs
|
Revenue and accounts receivable
|
Note: IDEA is a software tool used to query entity data. It can be used to isolate and extract transactions based on pre-set query parameters.
-
Aging of accounts receivable
-
Testing of aging as at a specified period end by recalculating the age of each individual invoice and confirming it is being reported in the proper aging category. Where the entity has no aging, we can produce one independently for analysis. Also, additional aging categories can be generated where the entities categories are not in sufficient detail. For example, if the client categories only cover 30 days, 60 days and 90 days and older, we might consider producing a report that would include categories for 120 days, 150 days, etc.
-
Testing sales cut-off
-
Listing of non-standard sources of revenue
-
Analyzes all revenue general ledger accounts and generates a report of revenue by source (i.e., the originating billing system). Non-standard sources can be investigated if material. Examples might be revenue generated by previously unknown billing systems, manual revenue adjustments, etc.
-
Producing reports of top monetary accounts receivable balances or invoices
-
Producing reports of credit accounts receivable balances
-
Producing reports of past due accounts receivable balances or invoices
-
Testing accumulation of credit note transactions
-
Stratification of accounts receivable invoices/balances
-
Analytical test that shows how many invoices or balances fall into specific amount categories (i.e. negative, 0 to 100000, 100001 to 500000, 500000 to 1000000, etc.). The report also shows the total amounts per category. This can be used to better understand the nature of the data being tested and also to highlight unusually large or small amounts.
|
Inventories and production costs
|
-
Producing reports of obsolete, excess or slow moving inventory
-
Analytical test that compares inventory quantities on hand at a point in time with actual or projected inventory usage. Resulting report shows number of months or years supply of each particular inventory item assuming the same inventory usage in the future. Report can be sorted to highlight low usage / high value items, and used to assist in the assessment of the adequacy of inventory reserves.
-
Producing reports of unusual inventory quantities, costs or descriptions
-
Identifying old or inactive inventory.
-
Selecting items to be counted during physical inventory observation
-
CAATs can be used either to statistically select inventory items to be counted, or for targeted selection of items. Statistical selections might be necessary if the results of the physical inventory observation need to be extrapolated to the entire population. Targeted selections can be made using CAATs to focus on high value items or items deemed to have a higher risk.
-
Testing mathematical accuracy of perpetual inventory records
-
CAATs can be used to automate the process of testing the accuracy of the various inventory reports. Examples include the report of tags used, unused or voided or report of final valued inventory. In addition, CAATs can be used to identify gaps and duplicate tags used as part of the physical inventory count.
-
Producing reports of products where costs exceed market value
-
Analytical test that compares inventory costs with the most recent market value, either by comparison to recent sales amounts (for finished goods) or by comparison to purchasing data (for raw materials). The report would highlight where inventory items might be recorded at values above their current market value and would help assess the reasonableness of any associated inventory reserves.
-
Inventory valuation testing (LIFO, average cost, etc.)
-
CAATs can be used to test various calculations used by the entity for valuing inventory, whether it uses LIFO, average cost or some other approach. The results of the testing would highlight any errors in the entity’s calculations.
-
Producing reports of changes in unit costs and/or quantities from prior year
-
Analysis of unusual inventory transactions
|
Purchases and payables
|
-
Search for unrecorded liabilities
-
Uses an automated approach to select cash disbursements after the period end being audited and matching those against items recorded in accounts payable at period end. A report is then generated showing all potential unrecorded liabilities, as indicated by disbursements made after the period end that related to costs incurred prior to the period end, but are not recorded in accounts payable. The report can be used to calculate the total amount of potential understatement (including all unmatched items), and can then also be sorted to highlight items that would need to be further tested.
-
See a detailed example of an unrecorded liability test using CAATs below.
-
Producing reports of large or unusual payments
-
Analytical test that can be used to highlight high-risk payments. Payments over specified amounts are listed, as well as any unusual payments. The specification of unusual would be determined on an entity-by-entity basis, but might include non-standard payment types (manual cheques, wire transfers to foreign banks), or unusual vendor names (related parties, employee names, etc.).
-
Generate listing of duplicate payments to vendors
-
Report would show potential duplicate payments to vendors by highlighting multiple similar payments. Payments might be considered similar if they have the same values for some combination of information, including vendor name, vendor number, invoice number, invoice amount, P.O. number, etc. While significant amounts of duplicate payments could have an audit impact, even large but non-material amounts are generally of interest to the entity because they could represent amounts potentially recoverable from vendors.
-
Accounts payable circularization (confirmation)
|
Property and equipment
|
-
Producing reports of large acquisition and disposition transactions
-
Testing mathematical accuracy of depreciation expense by asset
-
CAATs can be used to recalculate depreciation expense by category of asset using information on the entity’s property report (useful lives, acquisition date, asset type, etc.). This can also be used to highlight any unusual components of the calculation (i.e., extremely long useful lives, unusual acquisition dates, items with accumulated depreciation greater than acquisition cost, etc.).
-
Test for improper capitalization of expenditures
-
Report of all items capitalized into property can be generated and then sorted/summarized by type and source of item being capitalized (payroll, purchases, overhead, etc.). The report can be sorted to highlight large items by asset type and source type. In addition, the report can be generated for various time periods (monthly, quarterly, yearly) to identify any unusual trends in amounts being capitalized.
|
Other tests
|
-
Mathematical accuracy testing of reports/balances
-
Evaluate analysis
-
IDEA may be used to run a series of standard analyses, including mathematical accuracy, stratification of amounts, field level pattern analysis, and outlier analysis (items three standard deviations from the mean). This analysis can be performed on any data set as a starting point to identify potential unusual or high-risk items.
-
Review of non-standard journal entries
-
CAATs can be used to generate a list of non-standard journal entries. Non- standard would need to be defined on a client-by-client basis, but might include the following type of entries: manual journal entries, entries with blank or unknown posting sources, entries over a certain amount threshold, entries made by unauthorized users. This list can then be used to select items for further testing. For further guidance on journal entry testing see OAG Audit 5509
-
Audit Sampling
-
A statistical approach may be appropriate in some circumstances. The two most common types of statistical audit sampling used currently are attributes and monetary unit. Attributes sampling involves selecting a random sample of items and testing whether a specific condition is present or absent (e.g., authorization of a purchase order), and extrapolating the results to the entire population to obtain comfort that a specific control is in place. Monetary unit sampling involves selecting a random sample of items and testing the accuracy of monetary amounts, and extrapolating the results to the entire population to obtain comfort on the recorded balances. CAATs can be used to calculate the appropriate sample size, given a specified level of materiality and statistical confidence needed, select the sample, and then evaluate the results of the sample items tested.
-
Targeted testing
-
Targeted testing differs from audit sampling in that items are selected for testing using specific criteria designed to target higher risk items, rather than on a random basis. A simple example using the accounts receivable confirmation process would be to select all balances over a specified monetary amount for sending confirmations. Another example when testing revenue transactions would be to summarize all transactions by type code, then make a selection of transactions with non-standard type codes possibly adding a monetary amount threshold to further refine the test. In many cases, targeted testing is more efficient and more effective than audit sampling. Fewer items will generally need to be tested using a targeted approach, because the focus of the testing is on higher risk transactions and because we are focusing on risk, the test is generally more effective. CAATs are ideal for targeted testing because they allow us to easily make selections from large populations of data using the target criteria. As our knowledge of the data being tested increases, we can quickly modify the target criteria to better focus the testing for the future.
-
Search for related party transactions
-
CAATs can be used to provide substantial coverage to our testing of related party transactions. The software can be designed to search for the names of key related parties (e.g., Board of Directors, affiliates, officers) in specified transaction files. Files that could be searched might include: cash disbursements, cash receipts, sales transactions and other general ledger transactions (particularly manual entries). The report generated can then be sorted by monetary amount and/or by related party and be used to determine whether further follow-up/testing is necessary.
-
Gap and duplicates analyses
|
Additional examples of using CAATs in substantive testing
OAG Guidance
The following table gives additional examples of using CAATs in substantive testing:
Revenue and accounts receivable
|
Revenues
-
Producing reports of large sales transactions.
-
Matching dates of shipping documents and invoices for cut-off tests.
-
Producing reports of unusual prices or discounts.
-
Summarising sales by product line.
-
Producing reports of discrepancies between quantities shipped and quantities billed.
-
Producing reports of disputed customers accounts.
-
Matching dates of goods returned and credit notes for cut-off tests.
-
Testing accumulation of invoices.
-
Testing accumulation of transactions in sales history files.
Receipts from customers
-
Producing reports of large or unusual receipts.
-
Producing reports of duplicate receipts.
-
Producing reports of the volume and amount of receipts per period.
-
Testing accumulation of cash receipts.
Trade accounts receivable
-
Producing reports of credit accounts receivable balances.
-
Producing reports of large or old suspense items.
-
Testing accumulation of receivables balances.
-
Producing reports of credit balances.
-
Producing reports of new customers since confirmation date.
-
Producing reports of unusual interest rates on installment accounts.
-
Producing reports of customer accounts in value order.
-
Producing reports of changes to credit limits.
|
Inventories and production costs
|
Production costing
-
Selecting standard costs for detailed testing.
-
Producing reports of changes in standard costs from prior year.
-
Comparing inventory quantities with production information.
-
Testing accumulation of production costs.
-
Producing reports of unusual usage or costs.
-
Testing mathematical accuracy of variance analyses.
-
Testing mathematical accuracy of overhead cost allocations.
-
Comparing usage data from the manufacturing process to relief from inventories.
-
Comparing total production costs incurred (labour, materials, overhead) to amount applied to inventories.
-
Accumulating detailed cost elements and comparing to company standards.
Cost of goods sold
-
Producing reports of large cost of goods sold transactions.
-
Producing reports of quantities shipped and quantities relieved from inventory.
-
Comparing amounts recorded as cost of goods sold with amounts relieved from inventory.
-
Producing reports of inventory shipments not recorded in the proper period.
-
Summarising sales and cost of goods sold by product or product line.
-
Comparing total cost of goods sold from transaction listings to posting in general ledger control accounts.
-
Testing accumulation of cost of goods sold transactions.
Inventories
-
Producing reports of recent shipments of inventory for cutoff testing.
-
Comparing recent invoice prices to costs on perpetual inventory records.
-
Selecting inventory items for detailed testing.
-
Producing reports of inventory by class in value order.
-
Identifying raw materials related to obsolete finished goods.
-
Testing mathematical accuracy of allocation of over- or under-absorbed overhead costs.
-
Analysing gross margin by product.
-
Testing accumulation of inventory balances.
-
Test for duplication/omission of inventory in transit (recorded in two places).
|
Purchases and payables
|
Purchases of goods and services
-
Producing reports of large purchases of goods and services.
-
Producing reports of purchases of materials or services for each month or the entire year.
-
Comparing data on separate files to identify goods received but not invoiced, goods invoiced but not received or discrepancies between purchase orders, receiving documents and supplier invoices.
-
Producing reports of new suppliers.
-
Producing reports of entries from unusual sources.
Payments for goods and services
Accounts payable
-
Aging of payables balances.
-
Producing reports of debit balances.
-
Producing reports of large or old suspense items.
-
Testing accumulation of payables balances.
-
Producing reports of balances with no scheduled payment date.
-
Producing reports of new suppliers.
-
Producing reports of entries from unusual sources.
|
Property and equipment
|
Acquisitions and disposals
-
Producing reports of significant gain or loss transactions based on original cost, amount or other criteria.
-
Testing mathematical accuracy of gains or losses.
-
Producing reports of assets included in prior year listings and excluded from current year listings.
-
Testing mathematical accuracy of capitalised lease amounts for new leases.
-
Producing reports of maintenance and repairs expenses by department or asset.
-
Accumulating acquisitions and gains, losses and proceeds from disposals for presentation in the statement of changes in financial position.
Depreciation
-
Producing reports of depreciable lives not in accordance with client policies.
-
Producing reports of depreciation expense by type, age and location of assets.
-
Testing accumulation of depreciation amounts.
-
Producing reports of entries from unusual posting sources.
Property and equipment
-
Producing reports of large balances.
-
Producing reports of assets by type, age or location.
-
Producing reports of fully depreciated assets.
|
Employee Costs
|
Employee costs
-
Producing reports of employees receiving net pay over a given amount.
-
Test for duplicate employees (based on name, addresses and other).
-
Producing reports of employees working an abnormal amount of overtime.
-
Producing reports of employees with excessive holiday / vacation time.
-
Producing reports of recent terminations and hirings.
-
Selecting samples for testing.
-
Testing mathematical accuracy of payroll totals.
-
Testing accumulation of payroll totals.
-
Producing reports of large or unusual payments.
-
Testing mathematical accuracy of payment files.
Employee related liabilities
-
Testing accumulation of journal adjustments.
-
Producing reports of large journal adjustments.
-
Producing reports of entries from unusual sources.
|
Cash
|
Cash balances
-
Producing reports of excessive idle cash balances.
-
Determining outstanding cheques.
-
Analysing cash balances.
-
Testing accumulation of cash balances.
|
Investments
|
Investments
-
Selecting investment transactions for testing.
-
Selecting investments for confirmation.
-
Identifying changes in investment carrying values.
-
Testing mathematical accuracy of investment market values;
-
Testing mathematical accuracy of gains or losses on sales of investments.
-
Producing reports of costs in excess of market values.
-
Producing reports of unusual activity.
-
Producing reports of related party transactions.
-
Testing accumulation of investment balances.
-
Net Asset Value (NAV) trend analysis.
-
Generate list of non-income producing securities.
-
Recalculate OID (Original Issuer Discount) accretion.
Investment income (loss)
-
Testing mathematical accuracy of investment income.
-
Testing mathematical accuracy of amortisation of premiums or discounts on investments.
-
Selecting specific transactions for testing.
-
Producing reports of unusual investment income amounts.
-
Producing reports of investment income by type.
-
Producing investment yield analyses.
-
Testing accumulation of investment income (loss).
|
Other Assets
|
Deferred costs and intangibles
-
Testing mathematical accuracy of amortisation.
-
Identifying unusual additions or write- offs of deferred costs.
-
Identifying unusual additions or disposals of intangible assets.
-
Producing reports of unusual posting sources.
-
Testing accumulation of deferred costs and intangibles transactions and balances.
Prepaid Expenses
-
Testing mathematical accuracy of amortisation.
-
Analysing prepaid expenses at period end.
-
Analysing prepaid expenses account activity.
-
Producing reports of unusual posting sources.
-
Testing accumulation of other assets transactions and balances.
|
Other Liabilities
|
Accrued and other liabilities
-
Summarising activity within the various accrued and other liability accounts.
-
Testing mathematical accuracy of an estimated liability for accrued warranty costs.
-
Listing accrued and other liabilities in excess of a certain amount for detailed testing.
-
Identifying the age of accrued and other liabilities.
-
Testing accumulation of accrued and other liability transactions and balances.
Deferred revenue
-
Testing mathematical accuracy of amounts allocated to deferred revenue.
-
Testing mathematical accuracy of deferred revenue amounts recognised in income.
-
Summarising significant account activity.
-
Testing accumulation of deferred revenue transactions and balances.
Leasing
|
Detailed examples of two most common CAAT tests
OAG Guidance
1) Accounts Receivable Liquidation (or Subsequent Cash Receipts Test)
The purpose of this routine is to test for overstatement of accounts receivable by analysing what happened to each open invoice over time. For instance, if we see that most invoices were liquidated by the receipt of cash, it is an indicator that the invoices were collectible, and therefore valid as at the period end. If we see a large number of invoices that were never collected, or we see large amounts of write offs, credit memos and other credit adjustments, it is an indicator of a potential collectability issue. The liquidation test starts with the accounts receivable trial balance (all open invoices) as at each end of period being testing. To that we apply all subsequent transaction activity that affects those invoices. The activity includes cash receipts, credit memos, debit memos, adjustments and write-offs (and any other significant categories affecting accounts receivable). The resulting report shows the beginning open balance, the various activity types in separate columns, and then the remaining (unliquidated) balance at the end of our fieldwork. The major advantages of using CAATs versus a manual process are that we obtain better audit coverage and we can perform the test more quickly than if we used a manual approach. The manual liquidation process is generally performed on only a small sample of balances (usually high monetary amount). Also, the liquidation process is generally a manual-intensive one, involving a significant amount of time to liquidate a relatively small number of accounts. Using CAATs, we are able to liquidate all of the accounts receivable balances, greatly increasing the audit coverage over the sample-based manual approach. As with most CAAT tests, in the succeeding years, we can use the templates developed to achieve even greater savings, because the CAAT routines are already built and only need minor code adjustments.
Typically, accounts receivable is tested at an interim date because of the lag between the date of a sale and the ultimate cash collection on that sale. In these cases, the liquidation is performed at an interim date and then the balance is rolled-forward to the end of the period being audited.
2) Search for Unrecorded Liabilities
The purpose of this routine is to test for potential understatement of liabilities. This is done by analysing cash disbursements subsequent to the period end being tested. Disbursements made subsequent to the period end that related to a cost incurred prior to the period end should be recorded as a liability as of period end. For example, inventory was purchased and received on 20 December 2000, with a value of $500,000. The vendor generates an invoice dated 20 December 2000 and sends the invoice to XYZ Corporation. XYZ Corporation receives the invoice on 12 January 2001. Because the invoice was not received prior to the closing of the December accounts, XYZ Corporation would not have recorded the invoice in the accounts payable system as at 31 December 2000. By analysing cash disbursements subsequent to year-end, we would see that $500,000 was paid for an invoice dated prior to year-end. In reviewing the accounts payable trial balance as at the year-end, we would see that the amount was not recorded as a liability. On the surface, this would indicate an unrecorded liability of $500,000. However, if we also review XYZ Corporations various accrual accounts, we would find the $500,000 recorded in the received not vouchered accrual. Therefore, in this example, XYZ Corporation would not be under-accrued. Using a CAAT, we would automate this otherwise manual process by matching all subsequent cash disbursements with amounts in the accounts payable account as at the year-end. We would generate a report of all unmatched amounts, which might indicate unrecorded liabilities. We could then investigate whether there are other accruals in the accounts to cover the amount of potential understatement, using appropriate materiality guidelines.