1 / 13

Discussant’s comments -

Symposium 2009. Discussant’s comments -. Data Mining Journal Entries for Fraud Detection: A Pilot Study – R S Debreceny & Glen L Gray. Eckhardt Kriel. MOTIVATION - JUSTIFICATION. MOTIVATION - JUSTIFICATION. I want to congratulate the authors on a very interesting and topical paper .

ember
Download Presentation

Discussant’s comments -

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Symposium 2009 Discussant’s comments - Data Mining Journal Entries for Fraud Detection: A Pilot Study – R S Debreceny & Glen L Gray Eckhardt Kriel

  2. MOTIVATION - JUSTIFICATION MOTIVATION - JUSTIFICATION • I want to congratulate the authors on a very interesting and topical paper. • It is well researched, documented and while I agree with the paper and its conclusions I ask myself: • Does it go far enough? • Auditors have been doing this for over 5 years • There is a massive amount of data - results and experiences • Its perhaps time to ask – “How may frauds have been uncovered and how useful really is this exercise”? As the Authors state: “There is, however, very little knowledge of the efficacy of this important class of audit procedures.” • My experiences: • During 2002 to 2006 I led a team who performed JE analysis for roughly 500 listed clients in Canada every year. • Frequent interaction with other areas and firms. • In that period millions of journal entries were analysed. • Spent thousands of hours of work. • Tests complied with SAS 99 and more. • We found many of the strange anomalies described in paper. • We found many control exceptions and issues but; • NO SIGNIFICANT FRAUDS WERE UNCOVERED.

  3. CHALLENGES Challenges in process • ITS NOT EASY! • Tough challenges that are not mentioned in the paper. • Accessing and extracting the data. • Understanding unique client environment and FCP. • Data Completeness verification. • Are the appropriate tests being run?

  4. Standard Procedures Standard Procedures • Our procedures included those mentioned in the paper plus: Data Completeness Trial Balance Roll-Up Data Anomaly Tests Blank Date Fields Zero Dollar Items Blank Account Numbers Unbalanced Journal Entries Blank transaction description Blank Preparer ID Foreign Currency Adjustments Unusual Currencies • Key Transaction Tests • Accounts not in the Chart of Accounts • Line items greater than the absolute value of a dollar threshold • Back Dated Journal Entries greater than the absolute value of a dollar threshold • Digital Filter Tests • Benford Tests on leading and trailing digits • Round Number testing Additional Testing Procedures: • Modified Standard Account/Period/Amount Cross Tabulation • Identify any Journal Entry exceeding the average daily posting amount for that account by x% • Identify any Journal Entry exceeding the average daily number of transactions for that account by x% • Identify Journal Entries with identical dollar amounts • Account Combination Testing Debits to Income Accounts and Credits to Expense Accounts Debits to Liability Accounts and Credits to Income Accounts Debits to Asset Accounts and Credits to Income Accounts Debits to Fixed Assets and Credits to Expenses • Identify Journal Entries with key words in description field – “professional fees”, “litigation”, “reserve”, etc. • Identify journal entries passed by unauthorized personnel etc., etc., etc.

  5. Cross Tabulation Example Cross Tabulation Example • Data Trending by Source Code – Cross Tabulation of key data fields, cross comparison of linked items

  6. Limitations of Journal Entry Testing Limitations SAS 99 details a number of procedures that auditors can follow to respond to the objective of consideration of fraud in F/S audit. Journal entry testing is one of these. I have reservations that, on its own, journal entry testing, is effective. So any paper or article on the subject must include it as one of a combination of tests. To detect potential irregularity in financial statements any analysis must be focused: It must contemplate fraudulent misstatement and profile its characteristics; It must search for the characteristics; It must be broadly based.

  7. Possible future research areas Expanding on SAS 99 Paragraphs 28/29/30

  8. Possible future research Textual Mining Textual Mining

  9. Possible future research Benford on Company results Benford on Listed Company Results – AD Saville1 1. Reference: SAJEMS NS 9 (2006) No 3 341

  10. Possible future research Advanced Financial Reporting Analysis Advanced Financial Reporting Analysis – Example MICROSTRATEGY – Application of Different tests

  11. Conclusion

  12. Too much Information ? Too much Information ? M Gladwell Stephen Few’s2 Commentary on Gladwell: “Modern problems, on the other hand, are not the result of missing or hidden information, Gladwell argues, but the result, in a sense, of too much information and the complicated challenge of understanding it. The problems that we face today do not exist because we lack information, but because we don’t understand it. They can be solved only by developing skills and tools to make sense of information that is often complex. In other words, the major obstacle to solving modern problems isn’t the lack of information, solved by acquiring it, but the lack of understanding, solved by analytics.” 2. Visual Business Intelligence September-21-09

  13. Questions Eckhardt Kriel CA (SA) E Kriel & Associates Inc.1148 Forest Trail Place Oakville ON L6M 3H7 www.krielassoc.com www.d3cifer.com Mobile: +1. 416 451-3919 Direct:   +1. 416 451-3919 Email: ekriel@cogeco.ca

More Related