Configuring Moody's EVA

Moody's Analytics EVA (Entity Verification API) is an external data service that enables Fenergo clients to automatically retrieve and enrich entity information during onboarding and periodic review.

This guide covers the configuration and operation of the EVA integration within the Fenergo platform.

Overview

What is EVA?

EVA is Moody's Analytics entity data service that aggregates company information from multiple upstream registries and curated data partners, exposed through a single REST API. Within Fenergo, EVA surfaces as two independent External Data Adapters:

• EVA Curated — enriched, curated firmographic data sourced from Orbis (Moody's Analytics), providing financial, ownership and relationship information.
• EVA Register — authoritative data retrieved directly from national company registries (for example, Companies House for UK entities), providing legal, officer, and PSC information.

Both adapters are built and managed through Fenergo Flow Studio, and each is registered as a separate External Data Provider with its own authentication, mapping, and provider priority configuration.

Supported Data Sources

Source	Upstream Data	Primary Use Cases
EVA Curated	Moody's Orbis	Firmographics, financials, ownership structure
EVA Register	National company registries (e.g. Companies House)	Legal name, officers, PSC filings, incorporation details & document retrieval

Integration Scope

The EVA integration covers:

• Import and configuration of two Fenergo Flows (EVA Curated and EVA Register) with an Initiator Type of ExternalData, published in Fenergo Flow Studio.
• Registration of both Flows as named Flow Providers in the Fenergo External Data Providers screen, with API authentication and mapping status.
• Field-level mapping of EVA response attributes to Fenergo Global Policy entity fields across four mapping tabs: Entity Data, Hierarchy Link, Company Related Parties, and Individual Related Parties.
• End-to-end user journey encompassing entity search, profile selection, data review, and import into the Fenergo entity record.

System Configuration

This section describes the steps required to configure the EVA integration in a Fenergo SaaS environment. Configuration must be completed in the following order: Flow import, Flow setup values, Flow publication, Provider registration, Outbound authentication, Callback authentication, Moody's registration, Integration testing, and Field mapping.

Prerequisites

Before beginning configuration, ensure the following are in place:

• A valid Moody's Analytics EVA API subscription with an API key and the EVA endpoint URLs (v1 and v2), provided by Moody's Analytics.
• A Fenergo SaaS tenant with Flow Studio access and External Data configuration permissions.
• Your Fenergo SaaS environment name (e.g. fenergonebula) and tenant ID.
• A system administrator or configuration role in Fenergo.

Importing the EVA Flows and Sub-flows

From the left-hand navigation, go to Management > Integrations > Flow Studio and select the Templates tab. Scroll to the EVA section. The following Flows and sub-flows are available for import:

Flow name	What it does
EVA Register	Registers/searches an entity with Moody's and orders a document
EVA Curated	Searches and retrieves curated entity data from Moody's
EVA Search Request Flow	Supporting flow used internally by EVA Curated
EVA Webhook Setup	One-time setup flow that tells Moody's where to send results
EVA_DocumentsCallback	Receives the finished document from Moody's
EVA_OngoingMonitoring	Receives entity change/monitoring alerts from Moody's
EVA_Callback	Receives finished search results from Moody's

To import:

• Select a Flow — for example, EVA Curated — and click IMPORT.
• The Import Template modal opens with fields pre-populated. Click CONFIRM.
• The Flow is imported in Draft status.
• To publish immediately, click SUBMIT FOR APPROVAL, then APPROVE, and confirm.
• Click the Flows tab to verify the imported flow appears.

note

Importing EVA Curated or EVA Register will also pull in the required sub-flows automatically. If any sub-flow is missing, import it individually by repeating the steps above. Shared dependencies are detected and linked on import.

Configuring Flow Setup Values

Several imported flows contain placeholder values that must be replaced with environment-specific details before the integration will function. Open each flow's draft and update the following variables before publishing:

Flow	Variable	Value
EVA Webhook Setup	ApiUrl	Your Moody's EVA API URL
	AuthValue	A secret value you choose — record it, as it is reused in the Callback Authentication section
	FenergoEnvironmentUrl	Your Fenergo SaaS environment name
	TenantId	Your tenant ID
EVA_DocumentsCallback	Domain	Your Fenergo SaaS environment name
	TenantId	Your tenant ID
	AuthValue	The same secret value chosen above
EVA_Callback	Domain	Your Fenergo SaaS environment name
	TenantId	Your tenant ID
	AuthValue	The same secret value chosen above

EVA Register, EVA Curated, EVA_OngoingMonitoring, and EVA Search Request Flow do not require setup value changes.

warning

Placeholder values will not cause an error at publish time — the flow will publish successfully but will not function correctly at runtime. Verify all values before proceeding.

Publishing EVA Flows in Fenergo Flow Studio

All seven flows must be in Published status before the integration can be used.

To verify and publish:

• Navigate to Flow Studio > Flows.
• Locate all seven EVA flows: EVA Curated, EVA Register, EVA Search Request Flow, EVA Webhook Setup, EVA_DocumentsCallback, EVA_Callback, EVA_OngoingMonitoring.
• For each flow showing Draft in the Current Status column, open it and click SUBMIT FOR APPROVAL, then APPROVE, and confirm.

note

If a flow cannot be published due to validation warnings, open each step tab (Search Request, Search Response, Get Request, Get Response) and resolve any highlighted issues before retrying.

EVA Flow Structure

Each primary EVA Flow (EVA Curated, EVA Register) implements a four-step request lifecycle. All four tabs must show a green tick before the flow is considered fully configured:

Step	Description
Search Request	Constructs the entity search payload from Fenergo attributes (legal name, registered number, country).
Search Response	Parses the list of matching entities returned by the EVA API and presents them for user selection.
Get Request	Fetches the full data profile for the selected entity using its EVA entity identifier.
Get Response	Maps the full profile response to the Fenergo data model. This tab hosts the mapping canvas used during field mapping configuration.

Registering EVA as External Data Providers

Once EVA Curated and EVA Register are published, register them as Flow Providers in the External Data Providers screen. This connects each Flow to the External Data framework and enables authentication and field mapping.

Navigating to External Data Providers

• Navigate to Home > Providers.
• The External Data screen shows two sections: Providers (pre-configured system providers such as Orbis, Kompany, and D&B Direct+) and Flow Providers (Flow Studio-built custom providers).
• EVA Curated and EVA Register appear in the Flow Providers section. If they are not yet listed, click + ADD and select the corresponding Flow from the dropdown.

Provider Status Fields

Each Flow Provider entry displays the following status indicators:

Field	Expected Value	Description
Status	Active	The provider is enabled and available for data requests.
Authentication Status	Verified	The EVA API credentials have been validated successfully.
Mapping Status	Mapped	All required field mappings have been completed and saved.
Active toggle	Enabled	The provider is active for use in journeys and entity profiles.

note

A Mapping Status of "Mapping In Progress" indicates that mapping has been started but not completed. The provider will not function correctly until all mapping tabs are saved and the status updates to Mapped. See the Configuring Field Mapping section for instructions.

Configuring Outbound Authentication (Fenergo to Moody's)

Authentication is configured through a Global Variable in Flow Studio rather than within each individual Flow or Provider. The apiKey is defined once in the Global Variables tab and is shared automatically by both EVA Curated and EVA Register.

warning

Do not set the apiKey within the EVA Curated or EVA Register Flow's own Variables tab. It is managed centrally at the Global Variables level.

The following variables are Flow-specific and must be configured separately for each provider:

• apiUrl — the EVA API v1 base URL (https://api.kyc.moodys.com/eva/api/v1/).
• ApiUrlV2 — the EVA API v2 base URL (https://api.kyc.moodys.com/eva/api/v2/).
• MaxShareholdingLevel — controls how many levels deep the ownership hierarchy is traversed.
• MinShareholdingPercentage — sets the minimum ownership threshold for shareholder inclusion.

To configure the Global API key: Navigate to the Global Variables tab in Flow Studio. Locate the apiKey variable (type: Secret) and enter the EVA API key provided by Moody's Analytics.

To configure the Flow-specific variables: Open the EVA Curated Flow in Flow Studio and navigate to the Variables tab. Set apiUrl and ApiUrlV2 to the correct endpoint URLs. Click + to add a variable if any are missing. Repeat for EVA Register.

Once saved, open the provider record at Home > Providers > EVA Curated. The Data Types section should show Company as Active, with all four steps showing Complete. Click SAVE & TEST to validate connectivity — the provider status badges will update to Authenticated on success.

Configuring Callback Authentication (Inbound — Moody's to Fenergo)

This step authorises Moody's to call back into Fenergo and is separate from the outbound apiKey authentication. It must be completed before running the webhook setup.

Navigate to the Custom Auth tab for each relevant flow and toggle on the Callback Auth switch. Click ADD NEW CALLBACK and fill in the parameters as follows.

a) Authorise Moody's to call into Nebula. Apply to these three flows: EVA_DocumentsCallback, EVA_OngoingMonitoring, EVA_Callback.

PUT /api/authConfiguration/flow/{flowId}
{
  "configurationDetails": [
    {
      "authenticationMethod": "SharedKey",
      "sharedKeyLocation": "QueryParameter",
      "parameterName": "SampleAuth",
      "sharedKey": "<the secret value you chose>"
    }
  ]
}

b) Authorise the callback to resume the original flow. Apply to EVA Register and EVA Curated separately.

For EVA Register:

PUT /api/authConfiguration/flow/{evaRegisterFlowId}
{
  "callbackDetails": [
    {
      "asyncKey": "Default",
      "authDetails": [
        {
          "authenticationMethod": "SharedKey",
          "sharedKeyLocation": "QueryParameter",
          "parameterName": "SampleAuth",
          "sharedKey": "<the secret value you chose>"
        }
      ]
    }
  ]
}

For EVA Curated, use the same payload but with "asyncKey": "AsyncId".

note

If you are unsure how to make these API calls, contact your Fenergo representative for assistance. This is a one-time setup per environment.

Registering the Integration with Moody's

Run the EVA Webhook Setup flow once. This registers your Fenergo environment with Moody's and tells EVA where to send search results, documents, and monitoring alerts. The flow is safe to run more than once — it will not create duplicate registrations.

Testing the Integration

Before proceeding to field mapping, verify that the end-to-end integration is functioning correctly. Trigger a document request via EVA Register and a search via EVA Curated, and confirm the following for each:

• The request completes successfully in Flow Studio.
• The matching callback flow (EVA_DocumentsCallback or EVA_Callback) also runs and completes successfully within a short interval.

If a request does not behave as expected, contact Fenergo Customer Support with the flow name, execution ID, and approximate time of the run.

Configuring Field Mapping

Field mapping connects EVA response attributes to Fenergo Global Policy entity fields. Mapping is configured separately for each provider across four tabs: Entity Data, Hierarchy Link, Company Related Parties, and Individual Related Parties.

Accessing the Mapping Canvas

• From the External Data Providers screen, click the provider name (EVA Curated or EVA Register).
• Select the relevant entity type (for example, Company).
• Navigate to the Get Response tab. The mapping canvas shows two panels: Global Policy External Data Results fields on the left, and EVA response fields on the right. Existing mappings appear as connecting lines between the panels.

Creating and Removing Mappings

• To create a mapping: drag a line from an EVA field on the right panel to the corresponding Global Policy field on the left panel.
• To remove a mapping: click the connecting line and select Delete.
• Click SAVE after completing all mappings on each tab before switching to the next tab.

Related Parties Mapping

The Company Related Parties and Individual Related Parties tabs map EVA shareholder, officer, and beneficial owner data to Fenergo related party fields. Completing these tabs is required for automatic population of director, shareholder, and UBO records during data retrieval.

EVA Curated provides ownership data based on the Orbis shareholding model. EVA Register provides PSC data as filed with the national registry.

Configuring Provider Priorities (Entity Enrichment task only)

Where both EVA Curated and EVA Register return a value for the same Fenergo field, the Provider Priorities tab (Home > Providers > Provider Priorities) determines which source takes precedence. Configure priorities to reflect your organisation's data quality policy — for example, preferring EVA Register for legal name and company status, and EVA Curated for financial data and ownership structure.

Configuration Checklist

• All 7 EVA flows imported
• Setup values configured on EVA Webhook Setup, EVA_DocumentsCallback, EVA_Callback
• All 7 flows published
• EVA Curated and EVA Register registered as Flow Providers
• Outbound authentication configured and SAVE & TEST passed for both providers
• Callback authentication configured on EVA_DocumentsCallback, EVA_OngoingMonitoring, EVA_Callback
• Callback authentication configured on EVA Register and EVA Curated flows
• EVA Webhook Setup flow run once
• Test document request and search request both completed successfully
• Field mapping completed for EVA Curated and EVA Register

Journey Configuration

EVA data retrieval is initiated within Fenergo Journey Schemas through dedicated task types. Two task types support EVA: External Data Combined and External Data Enrichment. Each serves a distinct purpose in the onboarding and review workflow.

EVA Task Types in Journey Schemas

Both task types are added to a Journey stage in the Journey Schema editor under Home > Journey Schemas.

Task Type	Purpose	EVA Providers Used
External Data Combined	Primary data retrieval task. Searches both EVA providers simultaneously, presents results for user profile selection, and imports entity data, related parties, and documents into the Fenergo entity record.	EVA Curated, EVA Register
External Data Enrichment	Data granulation and aggregation task. Used to enrich a new or existing entity record with additional or updated data from EVA, typically applied after initial onboarding or during periodic review. Can be rules-driven natively or through KYRA Source.	EVA Curated, EVA Register

Configuring the External Data Combined Task

The External Data Combined task is the standard EVA data retrieval task used during entity onboarding. It triggers a simultaneous search across EVA Curated and EVA Register and presents the Select Data Profiles screen to the user.

Adding the Task to a Journey Stage

• Navigate to Home > Journey Schemas and open or create the relevant Journey Schema.
• Select the Journey tab and navigate to the stage where EVA data retrieval should occur (for example, New Request).
• Add a new task. Set the Title to External Data Search EVA (or a name appropriate to your configuration).
• In the Task Content section, set Task Type to External Data Combined.
• In the Select External Data Provider field, select both EVA Curated and EVA Register.

Task Properties

Field	Value / Setting	Description
Task Type	External Data Combined	Configures the task to run a combined search across selected providers. (2 max)
Select External Data Provider	EVA Curated, EVA Register	Specifies which providers are queried. Both must be selected for full EVA coverage.
Auto Search Data Provider	EVA Curated, EVA Register (optional)	When set, Fenergo automatically triggers the search without requiring the user to initiate it manually.
Auto Download Profile	EVA Curated, EVA Register (optional)	When set, Fenergo automatically retrieves the full data profile for the top-ranked match, bypassing the profile selection step.
Auto Import From	— (optional)	When set, Fenergo automatically imports data from the specified provider without user review.
Auto Import Related Parties From	— (optional)	When set, related party data (directors, shareholders, UBOs) is automatically imported from the specified provider.
Auto Complete	— (optional)	When enabled, the task completes automatically once all automated steps have run, without requiring user action.

note

The automation fields are optional. When left unset, the user is presented with the full interactive profile selection and review screens. Enable automation selectively based on your organisation's data quality and compliance requirements.

Configuring the External Data Enrichment Task

The External Data Enrichment task supports data granulation — the process of applying conditional logic to determine which specific data attributes should be retrieved or refreshed from EVA based on the current state of the entity record. It is typically applied during onboarding, periodic review, or re-verification stages of a Journey.

The task also integrates with the KYRA Source Agent. When KYRA is active, it can invoke the Enrichment task to retrieve targeted EVA data attributes autonomously as part of an agent-driven data collection workflow, reducing manual intervention and accelerating the data gathering process.

note

Use of the External Data Enrichment task with the KYRA Source Agent requires the KYRA module to be enabled and configured on your Fenergo tenant. Contact Fenergo Customer Support for guidance on enabling KYRA.

Adding the Enrichment Task to a Journey Stage

• In the Journey Schema editor, navigate to the review or re-verification stage.
• Add a new task and set the Task Type to External Data Entity Enrichment.
• In the Select External Data Provider field, select EVA Curated, EVA Register, or both, depending on which data the enrichment should target.
• Configure the automation fields as appropriate for the enrichment use case.

Use Cases

Common use cases for the External Data Enrichment task with EVA include:

• Refreshing ownership and UBO data from EVA Curated during annual KYC review.
• Updating officer and PSC data from EVA Register following a known change event (for example, a director appointment or resignation).
• Aggregating financial data from EVA Curated to supplement an existing entity profile where financial information was not collected at onboarding.
• Standard client onboarding where enrichment is required before risk assessment.

note

The External Data Enrichment task updates existing entity data rather than creating a new profile. Field-level conflict resolution follows the provider priority rules configured at Home > Providers > Provider Priorities.

Configuring Ongoing Monitoring with EVA Register

Fenergo supports ongoing monitoring of configured company data points and shareholders via EVA Register. When a subscribed field changes, Moody's notifies Fenergo through the EVA_OngoingMonitoring callback flow, which can automatically launch an update journey to consume the change.

Supported Monitored Fields

The following fields are available for monitoring. The full list is visible in the EVA Register Flow under the Designer tab, within the Subscribe to EVA HTTP Invoker step:

• content.firmographics.contactInformation.addresses
• content.firmographics.contactInformation.formattedAddress
• content.firmographics.legalInfo.legalForm
• content.firmographics.names.name
• content.companyRelationshipsAndRoles.shareholders
• content.firmographics.statuses.normalizedStatus

Configuring Monitoring Frequency

The frequency of monitoring checks is controlled by the MonitoringFrequency variable in the EVA Register Flow. The default value is 30 days.

To change it:

• Open the EVA Register Flow in Flow Studio and create a new draft.
• Navigate to the Variables tab and locate the MonitoringFrequency variable.
• Update the value to the desired frequency in days.
• Publish the updated flow.

Configuring the Monitoring Task in a Journey

To subscribe an entity to ongoing monitoring:

• In the Journey Schema editor, add an External Data Monitoring Subscription task to the subscribe journey.
• Configure the task to use EVA Register as the provider.
• Place this task directly after the External Data Combined task in the journey stage.

Once an entity is subscribed, a Monitoring Chip appears on the External Data Combined task to indicate that monitoring is active for that entity.

Configuring the Update Journey

When EVA Register detects a change to a subscribed field, an update journey can be automatically launched in Fenergo to consume the update. To configure this, add the following triggers in the Event Triggers section of the update journey:

Trigger 1

Setting	Value
Source	Event Ingress
Field	Event Type
Operator	Equals
Value	External Data

Trigger 2 (add as an AND condition)

Set the Event Subtype to either of the following values depending on your use case:

Setting	Value
Source	Event Ingress
Field	Event Subtype
Operator	Equals
Value	Update Entity

Alternatively:

Setting	Value
Source	Event Ingress
Field	Event Subtype
Operator	Equals
Value	Data Import