Skip to main content

Managing Legal Entities on the Fenergo SaaS Platform

The target outcome for using the Fenergo SaaS platform is to manage and work with Legal Entity Data.

Core Objectives
  • Clients to Store and have access to their LE data
  • Create and Update that LE Data
  • Validate that the data on the platform is accurate.

Doing the above means that Fenergo clients have have processes that ensure they are doing business with their clients in a safe, efficient and compliant manner. So how are these activities supported by the Fenergo platform?

Store and Access LE data​

The Fenergo SaaS platform is a software product provided as a service to our clients. Part of that service offering includes the shifting of responsibility to us (the vendor), for provisioning and managing the infrastructure required to make the software available / accessible. We use AWS (Amazon Web Services) as a cloud provider upon which we deploy the platform and have built on top of their Cloud Native products.

Fenergo store client data in Cloud Native tenant isolated data stores, protected by industry best practice encryption and security. We commit to SLAs at a contractual level to guarantee client access to their data and the platform. Clients can use the User Interface or APIs to interact with their data in a manner that suits their business needs.

Cloud Native

Is a a term used to describe a style of cloud resources which take full advantage of the best the cloud has to offer. Using Native Storage and Compute services let fenergo focus on the platform without handling infrastructure (Virtual Servers & Operating Systems). Read more about AWS Cloud Native Here

Create and Update LE Data​

Any system is only as good as the data it depends upon and Fenergo offer multiple ways for clients to get data onto the platform.

UI Journeys​

The most organic way to create data on the Fenergo platform is to use the New Request and Journey functionality to create a new Legal Entity and gather the configured data across the various stage and tasks within that Journey.

Clients begin with a Duplicate Search to establish if an Entity already exists. Then if not found, users can elect to create a new Entity. This will automatically perform all the following steps on the platform:

  • A New basic Verified Record is created and a new identifier created for the new LE.
  • The Journey Logic Engine is queried to establish which Journeys are in Scope for the new Legal Entity (based of course on the data already saved)
  • Once identified, the system will create a New Journey of the type found and the user can access them from the LE Profile page.

Direct APIs​

Another option open to clients is to use the Fenergo Direct APIs to replicate the user activity above. Clients can build a system to system integration where they call the Entity Data and Journey APIs which will result in the same outcome as above. This option allows a fine grained granular control over the process and can work well where another business process acts as a source for the data and clients wish to have data created and managed on Fenergo as a next step.

Event Ingress​

A different API to the Direct APIs is the Event Ingress functionality. This simplifies the task of having an integration replicate the UI steps and reduces the interaction to a single API message. Ingress shifts the Orchestration of identifying a Journey and initiating it over into Fenergo. So clients can send a single message which will create or update data and also create and initiate a journey.

Data Migration​

Where a client needs to load a large volume of data onto the Fenergo Platform, they can use the Data Migration APIs to push that data via CSV files into the system. Fenergo will validate the content of the files and create the LE data. Unlike traditional platforms, the fenergo platform can stay fully operational during this activity, users do not need to be logged off or restricted from accessing the UI. Clients can of course choose a strategy that best fits their needs but the APIs allow clients to operate autonomously and without any direct assistance from Fenergo to perform a Data Migration. Reach out to your Fenergo partner if you require any further assistance or direction with this activity.

Validate data is accurate​

Clients define their business / operational processes on the Fenergo platform to reflect how they run and manage client data.

  • When a new LE Record is created, it is typical to perform an Onboarding activity that identifies and gathers all the required client data so clients can do business with them.
  • Equally if clients are exiting from doing business with a LE, they would perform an Offboarding where client data might be flagged to be deleted or removed.
  • Then in between, frequent Maintenance operations that refine and update data.

Any variation or combination of the above can be configured to reflect standard operational processes of a business, but more importantly, the different tasks can be allocated to different teams and enforce 4-eye review steps to make sure responsibility for capturing accuracy of data is correctly spread across multiple persons / roles.