SymSure Framework Concept

Enterprise Wide Controls Portal

Efficiently monitoring internal controls has been a long standing objective for the internal audit, controls and compliance professions. SymSure Monitor delivers the best framework for achieving this in all businesses and across all processes.

Being able to determine the state of internal controls across the enterprise through a single portal is one key component of SymSure™ Monitor’s value proposition. Controls at remote locations can be examined centrally, including activities taken to mitigate risks. The solution is designed to meet the requirements of any business ranging from small businesses to Fortune 500 companies with diverse global operations across multiple languages.

SymSure_Concept

Open Design, Universal Application

Consider a Group of Companies with global operations in telecommunications, manufacturing, banking and insurance. These are diverse businesses with their own controls and compliance needs requiring a monitoring framework that is universally applicable. SymSure™ Monitor is perfectly suited to access and monitor data from Telecom switches, to ERPs, to bespoke applications and core banking and insurance applications. Regardless of the databases being used, SymSure can monitor all these business processes and effectively improve compliance and controls.

SymSure™ Monitor’s open design allows users to build customized monitors using established scripting tools such as ACL™, IDEA®, Arbutus™ and SQL Scripts. With these scripting tools and SymSure™ Monitor’s framework, customers can monitor any control in any business process.

This approach allows the customer to focus on scripting the basic logic and having the framework handle everything else. For example, to monitor the creation of overtime claims in excess of the number of work hours in the period, the script writer can apply a simple logic of OvertimeClaim > HoursInPeriod.

The remaining stages of the process are handled by SymSure including:

  • when and how often the data is to be monitored
  • who is to be notified
  • how they are to be notified (e-mail, SMS, dashboards, etc.)
  • the risk level associated with the control exception
  • who is responsible for resolving the issue and the turnaround time
  • who the exception is to be escalated to, if unresolved

    •