My WebLink
|
Help
|
About
|
Sign Out
Home
2010-01-AU Limited Scope Performance Audit of Department of Water Supply's Internal Controls for Cash Handling and Financial IT Systems
PublicDocuments
>
Legislative Auditor
>
Audit Reports
>
County Auditor Reports
>
2010-01-AU Limited Scope Performance Audit of Department of Water Supply's Internal Controls for Cash Handling and Financial IT Systems
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/19/2011 3:41:19 PM
Creation date
7/19/2011 1:34:39 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
70
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
CHAPTER 4: CASH HANDLING SYSTEMS <br />FINDING Water billing transactions are not submitted to a "real <br />time" financial system to ensure efficient recording, <br />processing, reconciling, monitoring, and reporting of all <br />customer payments. <br />The Public Utility Billing System (PUBS) is set up as a batch <br />processing system. As walk -in and mail -in payments are received <br />for water bills, they are entered into the PUBS application as a <br />"batch" or a sort of suspense account rather than being posted to <br />customer accounts in "real time ". At a certain time each day, all <br />transactions that have been entered since the last "batch" was <br />posted are grouped (batched) and posted to the appropriate <br />customer accounts. Reports are run showing summaries of all <br />customer transactions included in the batch as well as details of <br />the amounts of cash, checks, and credit cards associated with <br />those transactions. Each office has its own cut -off time to ensure <br />that its deposits are made by the end of each work day. Any <br />water bill payments that are processed after the cut -off time are <br />processed in a new batch, which is carried over to the bank <br />deposit for the following work day. An average of 750 daily <br />transactions is contained in a daily "batch" and deposit for the Hilo <br />office. <br />Batch processing is considered outdated in current accounting <br />practice, since it holds a number of transactions in limbo until the <br />"batch" is posted (routinely on the next work day). Among the <br />risks associated with batch processing is the manipulation of <br />batch data and the misappropriation of assets in the absence of <br />sufficient controls. For example, until the recent revision of <br />Finance Division procedures, daily batch reports (incoming totals <br />by payment type) were not reconciled to daily bank deposits (total <br />deposits by payment type). Thus, a Cashier could accept a walk - <br />in cash payment, enter it as a check payment in PUBS, and <br />replace the cash with a subsequent mail -in check payment before <br />posting of the next batch report. This is a common embezzlement <br />scheme that in the absence of adequate controls can continue <br />undetected for an extended period of time. The fact that DWS has <br />still not implemented sufficient cash handling controls — from <br />segregation of duties for mail -in payments to the sharing of Cash <br />Cans, logins, and passwords — perpetuates an environment <br />susceptible to the mishandling or misappropriation of customer <br />payments that can escape early detection. <br />RECOMMENDATION DWS management should conduct an analysis of all of its cash <br />handling activities, control processes, and financial systems to <br />identify areas of significant risk and their potential impact on <br />operations as well as an analysis of improved cost - effective <br />controls to reduce risks to acceptable levels. For example, if batch <br />processing is still to be used, management needs to ensure that <br />reports are generated for each Cashier and each financial system <br />36 <br />
The URL can be used to link to this page
Your browser does not support the video tag.