Habit 6: Synergize – Implement SOD across ERP Solutions

Leen RoeleveldBest Practices

Large companies often arise from various acquisitions and mergers with other companies. Every acquired company typically has its own ERP environment, which cannot simply be replaced. That is why these companies often have multiple ERP systems. However, when processes are integrated, employees may have  access to multiple ERP systems to perform their duties.
If we look at the applications that are used for the detection of SOD conflicts, then almost all of these applications are focused on specific applications, for example for SAP, or Infor LN, or Oracle, etc. Therefore, conflicts that exist across different ERP systems cannot be identified. If these conflicts cannot be identified, a security risk arises because employees can commit fraud without a reasonable chance of even being noticed.
Therefore, when selecting an application for conflict identification, companies with multiple ERP systems should also consider whether this application can detect conflicts across multiple ERP systems. This closes the gap and the conflict identification is conclusive.

Stay tuned! Follow us at LinkedIn or FacebookLeave your e-mail address if you want us to send these blogs straight into your e-mail inbox.

Habit 5: Seek First to Understand, then to be Understood – Investigate Conflicts and apply Mitigating Controls

Habit 4: Think Win-Win – Utilize Existing Libraries for Conflict Identification

Habit 3: Put First Things First – Prioritize SOD Conflicts based on Risk Exposure

Habit 2: Begin with the End in Mind – Include Role Definition in Implementation Project

Habit 1: Be Proactive – Address Compliance Risks Already During Implementation

The 7+1 Habits of Highly Effective Compliance when deploying ERP Systems