Ch09 - Auditing Revenue Cycle
Ch09 - Auditing Revenue Cycle
IT Auditing
& Assurance, 2e, Hall & Singleton
Singleton
MANUAL PROCEDURES
Follow Figure 9-1
Obtaining & recording customers
orders
Document = SALES ORDER [Figure 9-2]
One copy in Open Order File
Approving credit
One copy of sales order went to credit
dept.
Returned authorized copy triggers
release of sales order into system
IT Auditing & Assurance, 2e, Hall
MANUAL PROCEDURES
Processing shipping orders
4 copies of Sales Order to warehouse; packing slip,
Field checks
Limit tests
Range tests
Price times quantity extensions
usually tape
Next process is to post individual shipping notices to
appropriate individual AR accounts
Items
remittance list
Prepares batch for transactions
remittance list
IT Auditing & Assurance, 2e, Hall
Shipping procedures
Reconciles goods, stock release, packing slip from
system.
Online, IS prepares Bill of Lading for shipment, and
shipping notice for DP Dept.
Select carrier and prepare goods for shipment, along
with packing slip and Bill of Lading
Stock release form is filed
IT Auditing & Assurance, 2e, Hall
FEATURES OF REAL-TIME
PROCESSING
Events Database
Advantages
Completeness
Accuracy
VERIFY revenue transactions are accurately computed, based on correct prices and
quantities
Ensure AR subsidiary ledger, sales invoice file, remittance file are mathematically
correct .. And agree with GL accounts
Valuation or Allocation
VERIFY AR and revenues for period are properly described and classified
INPUT CONTROLS
Purpose
Ensure creditworthiness of customers
Control techniques vary considerably between batch systems and
real-time systems
Credit authorization procedures
Credit worthiness of customer
Batch and manual systems use credit dept.
Real-time systems use programmed decision rules
INPUT CONTROLS
Data Validation Controls
To detect transcription errors in data as it is processed
Batch: after shipment of goods
Error logs
Error correction computer processes
Transaction resubmission procedures
If Controls over system development and maintenance are NOT weak, testing
data editing/programming logic more efficient than substantive tests of details
(test data, ITF)
Some assurance can be gained through the testing of error lists and error logs
(detected errors only)
INPUT CONTROLS
Batch controls
Manage high volumes of similar transactions
Purpose: Reconcile output produced by system with the original
input
Controls continue through all computer (data) processes
Batch transmittal sheet:
Unique batch number
Batch date
Transaction code
Record count
Batch control total (amount)
Hast totals (e.g., account numbers)
PROCESS CONTROLS
Computerized procedures for file updating
Restricting access to data
Techniques:
File update controls -- Run-to-run batch control data to monitor
ACCESS CONTROLS
Prevent and detect unauthorized and illegal access to
firms systems and/or assets
Warehouse security
Depositing cash daily
Use safe deposit box, night box, lock cash drawers and safes
Accounting records
Removal of an account from books
Unauthorized shipments of goods using blank sales orders
Removal of cash, covered by adjustments to cash account
Theft of products/inventory, covered by adjustments to inventory or
cash accounts
PHYSICAL CONTROLS
Segregation of duties
transaction processing
Rule 2: Asset custody separate from record-keeping
tasks
Rule 3: Organization structured such that fraud requires
collusion between two or more people
Supervision
functions
Compensates for inherent exposure from incompatible
functions
Can be supplement when duties are properly segregated
Prevention vs. detection of fraud and crime is objective:
supervision can be effective preventive control
PHYSICAL CONTROLS
Independent verification
Review the work of others at critical points in business processes
Purpose: Identify errors or possible fraud
Examples:
Shipping dept. verifies goods sent from warehouse dept. are correct in
type and quantity
Billing dept. reconciles shipping notice with sales notice to ensure
customers billed correctly
DP systems.
Duties of design, maintenance, and operations for computers need
to be separated
Programmers should not be responsible for subsequent program
changes.
OUTPUT CONTROLS
PURPOSE: Information is not lost, misdirected, or corrupted; that the
system output processes function properly
Controls are designed to identify potential problems
Reconciling GL to subsidiary ledgers
Maintenance of the audit trail that is the primary way to trace the source
of detected errors
Details of transactions processed at intermediate points
AR change report
Transaction logs: permanent record of valid transactions
Transaction listings successfully posted transactions
Log of automatic transactions
Unique transaction identifiers
Error listings
exceptions
AR is immaterial
Assessed Control Risk is low
Confirmation process will be ineffective
Steps:
Select accounts to confirm
Consolidate invoices (not AR subsidiary) using CLASSIFY (filter) and
SUMMARIZE (amount) [see Tables 9-3 and 9-4]
Why?
JOIN the CUSTOMER file with the new consolidated invoice file
Realizable Value
AGING AR
Chapter 9:
Auditing the Revenue Cycle
IT Auditing
Singleton& Assurance, 2e, Hall & Singleton