• Home
  • Contact
  • Find a Partner

Contact ACL: 1-888-669-4225
facebook
linkedin
twitter
vimeo
youtube
email

  • SOLUTIONS
    • Products
      • GRC
      • Enterprise Continuous Monitoring
      • Data Analysis
    • Departments
      • Internal Audit
      • External Audit
      • Compliance
      • Finance
      • Shared Services
    • Hot Topics
      • FCPA + UK Bribery Act
      • Fraud
      • Risk
      • SAP® ERP
    • Industry
      • Banking & Finance
      • Business Services
      • Education
      • Government
      • Healthcare
      • Insurance
      • Manufacturing
      • Telecommunications & Utilities
      • Retail
  • SERVICES
    • Training
      • Course Catalog
      • Training Schedule
      • ACDA Certification
    • Services & Support
      • Consulting Services
      • Support Services
  • CUSTOMERS
    • Customer Community
      • Connections Customer Conference
      • User Groups
      • ACL Bootcamp
      • Impact Awards
      • Support Center
      • Social Media
    • Customer Successes
      • Case Studies
      • Customer Reference Program
  • ABOUT ACL
    • Company Overview
      • Contact
      • News Releases
      • Media Coverage
      • Analyst Coverage
      • Careers
      • Management
      • Legal
    • Engage
      • Events
      • ACL Blog
      • Subscribe
      • Education Futures
      • Social Media
    • Partners
      • Find a Partner
      • Associations
  • RESOURCE LIBRARY
    • Case Studies
    • Webinars
    • Videos
    • Podcasts
    • Product Collateral
  • SUPPORT CENTER


Top 25 Analytic Test for Every Organization: Test 1 – Suspicious Journal Entries

February 18, 2013
by Dan Zitting
Analytic Testing, Auditing, Suspicious Journal Entries
5 Comments

Earlier this month, AUDITMAN Dan Zitting shared some insight on the Rules and Tools for effective auditing in Top 25 Analytics Tests Your Organization Should Use, today he shares Test #1 – Suspicious Journal Entries.

When auditing, where else would we start than right in the guts of things, the general ledger. If I can’t find something interesting in the GL to talk about with management, I consider myself a failure as an auditor. So here is one suggested way to get quick and dirty with the journal entries and find at least that next topic of discussion:

RISK:  Posted entries may not be authorized or valid.

TEST:  Identify any journal entries containing descriptions that could indicate an invalid or suspicious entry.

TEST STEPS:

  1. Obtain a dump of all the journal entries from within the audit period you want to review.
    • Get it from someone in IT responsible for your ERP or core financial system.
    • Get it in a delimited text file format, quicker to import into your analysis tool.
    • Include all the key fields, but in particular things like description, date, amount, employee ID, account, etc.
    • *Hulk smash* if IT gives you any trouble – getting the data for this test should actually be quite easy to do.
  2. Import the JE data into ACL Desktop using the import wizard
  3. Filter on the description field for “hot button” words that might indicate a fraudulent, brain-dead, or otherwise suspicious entry
    • Examples: “per [X person]“, “to correct”, “error”, “adjust”, etc.
    • Get creative and think about those words that might be specific to your organization
  4. Consider further refining the results by identifying suspicious descriptions based on the accounts being posted to
    • Example: “land” or “building” showing up in the description field for a short-term asset account
  5. For the exceptions identified, review with management.

 

EXPECTED RESULTS:  You should definitely find some fun entries in any reasonably sized organization. Listen carefully in the discussion. You will certainly identify either errors, fraud, or (at least) the next thing you should have a look at!

Next Time:  We’ll continue our discussion on journal entries with some great tests.

Powered By DT Author Box

Posted by Dan Zitting

Dan Zitting

Dan Zitting, ACL’s Vice President, Product Management & Design, is responsible for product management, design, and user experience for ACL’s industry-leading software products. He is dedicated to the advancement of productivity enhancing technology for the audit profession and is a three-time winner of the CPA Practice Advisor Magazine’s 40 under 40 and Readers’ Choice awards. Dan is a Certified Public Accountant, Certified Information System Auditor and Certified Information Technology Professional. He holds a Bachelor of Science from Colorado State University and a Master of Science from University of Notre Dame.

Social Share
5 Comments
  1. Chelsea Smith March 1, 2013 at 4:34 am Reply
    This is a not my ordinary reading day, but this has brought clear issues to me. You also pointed out many important things about compliance audit. Thanks for sharing this essential information.
  2. Francisco A. Ortiz March 3, 2013 at 5:28 pm Reply
    Looking forward to your next post. Interesting and very simple. Sometimes we know what to do, but we think: "NAH! That's too simple." Those are the jobs that put you through the roof, up, up and away, like you say. Good job and thanks!
  3. Bidyadhar March 12, 2013 at 7:50 am Reply
    Hello Kindly clarify me: 1. Journal entries : We are in SAP environment, so those entries I will take it from "SAP TABLE level" or "FBL3N i.e., General ledger level" ? Thanks Regards
  4. Dan Zitting March 20, 2013 at 7:22 pm Reply
    @Chelsea - I'm interested in what you posted here. How is auditing journal entries related to compliance auditing? General ledger is not something that sticks out to me at all as having compliance implications. @Francisco - Absolutely. I just spoke with a customer yesterday about a similarly simple test. Checking that all journal entries were posted and approved by different individuals. They thought it was too simple a test to find anything - sure enough though, they did! The application was controlling this for individual entries but NOT for batch entries. Simple tests (when using analytics - that is the key) often have findings, and even when they don't, you usually see something interesting that helps you know what to look at next!
  5. Dan Zitting March 20, 2013 at 7:26 pm Reply
    @Bidyadhar - I apologize as I am not a total SAP expert. I have audited it many times, but I don't claim to be the best. That said, I have always done this sort of test by taking the data from the SAP table level. I *believe* (I am NOT sure) that FBL3N command would require you enter an account code. So you if you exported that information, you would only be auditing that one account, correct? I would much prefer to extract all the data at table level and analyze it all at once.

Leave a Reply Cancel reply

*
*

Categories

  • All Blog Articles
    • Auditing
    • Business Assurance
    • Compliance and Risk
    • Continuous Auditing/Monitoring
    • Fraud Detection and Prevention
    • Internal Audit
    • Management
    • Technology

Contact Us

  • Products
    • Enterprise Continuous Monitoring
    • Data Analysis
    • GRC

Latest Tweets

  • Breaking Down Silos and Building Up Enterprise #Compliance bit.ly/10nh2tg @complianceweek #regulations 4 hours ago
  • Q&A with Hal, IT Audit Director at @DnBUS. Hal talks about what it means to be a "controls activist" acl.com/portfolio/qa-w… 4 hours ago

Subscribe

Sign up to receive email updates from ACL.

SUBSCRIBE

Recent Posts

  • "How would you kick start data analytics?" ACL LinkedIn Group
  • ACL Launches ACL™ Analytics 10; Powerful Analysis Software Enables Data-Driven GRC Management
  • ACL Selected As Finalist For BCTIA Technology Impact Awards

t: 1-888-669-4225 e: info@acl.com | Terms and Conditions
© 2013 Copyright ACL Services Ltd.

mongoose

ACL Analytics