Auditing in Oracle Fusion doesn’t (have to) ruin system performance

Auditing in Oracle Fusion doesn’t (have to) ruin system performance

A number of organisations have contacted us recently saying that their auditors have reported that the organisation hasn’t set up auditing on high risk activities in their Oracle ERP Cloud or HCM Cloud system. The organisation has then read scare stories about the impact of auditing on system performance and become worried about how they can address the audit point.

We’d be happy to introduce you to some of our clients who would confirm that auditing, when done well, has no noticeable impact on system performance in Oracle ERP Cloud or Oracle HCM Cloud. Auditing in the Oracle SaaS systems is like a dimmer switch – you choose how much to turn it on. Whilst it’s possible to switch it all the way up and start recording high frequency transactions such as changes to GL Journals or AP Invoices, this may well impact on performance, but we would argue that nobody is going to review every single one of these changes and you’d be better off implementing preventative approval controls and then building other risk-based exception reports such as identifying manual GL journals that have avoided approval or where the same user has created or amended suppliers and then recorded invoices to the same supplier.

Over the past year we’ve helped organisations record high risk changes such as those for configuration and key master data. Turning this on within Fusion itself is the easy part. More important is to define the policy of *what* is to be audited and *why* (and to document ‘why not’ for some areas), along with defining the processes and operating model for actually identifying the changes and reviewing these, along with amending Fusion Roles to prevent users from amending auditing settings. Two common challenges we’ve noted previously are that:

  • There are many users that can amend auditing configuration as well as perform changes to business process configuration or master data – increasing the risk that users disable auditing, make unlogged changes and then turn auditing back on again, and
  • Audit report reviewers also have access to make changes to business process configuration or master data, increasing the risk of ‘self-review’

We make sure our work addresses both of these key auditing risks.

If this sounds like this would help address your auditor’s challenges, please contact us for more information.

As for our clients – calculating the exact system impact is almost impossible, but as one of our contacts told us “none of the end users has even noticed that we’ve turned it on”!