# ACL Tutorial 1 Solution

Topics: Invoice, Audit, Natural number Pages: 5 (489 words) Published: November 26, 2013
﻿ACL 9
Tutorial 1 Solution

COMMANDS:
ANALYZE -> TOTAL
ANALYZE -> PROFILE
ANALYZE -> STATISTICS
SAMPLING -> SAMPLE
ANALYZE -> SEQUENCE
DATA -> SORT
ANALYZE -> DUPLICATES
ANALYZE -> GAPS

AP_TRANS

1. Using the TOTAL command, develop a hash control total and an amount control total for AP-TRANS.

What recommendation would you make to develop a field for hash control total?

TOTAL command: Invoice Amount plus one of the other number fields. The total of Invoice_Amount is: \$278,641.33
The total of Quantity is: 37,107
The total of Unit_Cost is: 1,522.29

I recommend changing Invoice Number to a number field (vs. string) if possible.

2. Run PROFILE on the file, Invoice Amount.

Can you determine if there are any negative transactions? Explain.

There are none because total = absolute total (\$278,641.33)

3. Run STATISTICS on each of the four available fields with the Std Dev box checked.

Describe your audit direction to specific invoices based on the results of STATISTICS.

The statistics on Invoice_Amount reveal the following data of interest to the auditor:

As of: 08/25/2013 12:23:54
Produced with ACL by: Lehigh University
Command: STATISTICS ON Invoice_Amount STD TO SCREEN NUMBER 5 Table: Ap_Trans.
Invoice Amount
Number
Total
Average
Range
-
56,752.32
-
Positive
102
278,641.33
2,731.78
Negative
0
0.00
0.00
Zeros
0
-
-
Totals
102
278,641.33
2,731.78
Abs Value
-
278,641.33
-
Std. Dev.
-
6,609.23
-

Highest
Lowest
56,767.20
14.88
20,386.19
21.12
18,883.34
31.68
16,642.56
46.08
15,444.80
49.68

There are no zeros or negative invoices, quantity, or cost. This minimizes the need to look for that kind of error.

One transaction is an outlier - \$56,767.20. This item needs to be audited thoroughly.
Other than that, a reasonable statistical (random selection) approach to the other 101 transactions is required. This result gives an auditor the necessary input to calculate the number of samples to take. 4. Run SAMPLE (Sampling -> Sample) for the AP_TRANS file, using the data from step 3. Sample Invoice Amount, Interval of \$6,609, Begin \$14.88 (minimum invoice) and Cutoff \$56,767.20. Save results as AP_Trans_Sample.

AR

5. Run SEQUENCE on AR, using Invoice Number (Ref_No). Make sure to use only Invoice Type Transactions (“IN”); use Expression Builder to filter out other transaction types.

What do you notice about the invoice numbers?

As of: 08/27/2013 10:51:15
Produced with ACL by: Lehigh University
Command: DUPLICATES ON Ref TO SCREEN
Table: Ar

Filter:
Type = "IN" (588 records matched)

10 sequence errors detected
0 gaps and/or duplicates detected
Sequence:
Record
Number
Ref No
22
213184
26
213248
32
213277
35
213264
40
213327
41
213326
42
213325
43
213318
44
213317
48
213354

6. Re-run SEQUENCE on the same file but this time check “Duplicates” and “Gaps” (filter Invoice type transactions only).

What information is provided the auditor about testing invoices?

a. There are 162 gaps and 0 duplicates in the list in the LOG. 162 total problem invoice numbers. b. The LOG / SEQUENCE provides auditors with key information about missing invoice numbers, something that must be investigated.

7. SORT AR by Invoice Amount in descending order. Use Sort On to specify descending order. Specify TYPE “IN”. Use Output File name AR_SortAmount.

What sort of anomalies is the auditor looking for?

The auditor is looking for redundant amounts, large amounts, or other abnormal amounts.