Skip to content

Case study Energy & utilities

How growing energy company selected SafePaaS and Oracle ERP Cloud for scalable growth

A rapidly growing energy company selected Oracle ERP Cloud to support scalable growth, and its auditors required a full review of every ERP Cloud role to prove SoD risk was mitigated before production roll-out.

3 daysto deliver role and user violation reports across 100+ SoD policies
30% lowerimplementation cost
300+ configurationsreviewed across GL, AP, FA, AR, INV, PO and TNE
30+ defectsfound in SDLC controls
IndustryEnergy & utilities
RegionGlobal operations
SizeRapidly growing through acquisition of other energy companies
Primary ERPOracle ERP Cloud

Challenges

  • Auditors required a full review of all ERP Cloud roles to ensure SoD risks were mitigated before production roll-out
  • IT Security needed assurance that roles given to users did not violate the company's security policy or access controls
  • Business users needed assurance that process controls such as 3-way match, approval hierarchy and cross-validation rules were configured accurately in ERP Cloud
  • Finance management needed to prevent financial misstatement risk in GL, AP, FA and AR modules

Results

  • Within three days, delivered role and user violation reports with over 100 SoD policies tested
  • Reviewed over 300 configurations across the GL, AP, FA, AR, INV, PO and TNE modules
  • Gave internal audit and control owners access to a Cloud ERP risk repository of over 500 access, transactional and configuration risks to map against their risk and control matrices
  • Created more than 100 unique Oracle ERP roles
  • Identified more than 30 SDLC control defects
  • Reduced implementation cost by 30%

See it on your ERP

A 30-minute walkthrough against the systems you actually run.

See how this model applies to the systems sitting inside your own estate.

What this story shows

  • Over 100 SoD policies tested and reported within three days
  • Role and configuration risk was proven before production roll-out, not after
  • Implementation cost fell 30% while 30+ SDLC control defects were found