Fenergo: client lifecycle, KYC and governed compliance workflows

Fenergo supplies configurable software for client onboarding and continuing compliance work. Its SaaS platform brings together information collection, policy requirements, workflow and risk assessment, with interfaces that let other business systems use the same capabilities. For a brokerage, the relevant role is maintaining the client and counterparty record and coordinating due diligence across teams and products. Fenergo’s offering is aimed at financial institutions, including banks, asset managers, wealth businesses and fintechs.[1]

The CLM product page identifies onboarding/operations, client and related-party data management, KYC and product enablement as standard modules. It presents Regulatory Compliance and Risk Management as additions. That distinction matters when comparing a full platform proposal with a narrower KYC deployment: a product catalogue does not establish that every module is included in one subscription.[2]

Fenergo says its KYC content covers more than 120 jurisdictions and includes rules for natural persons, legal entities and ownership/control. The rules engine determines which information is required at a particular lifecycle stage. Continuing monitoring is designed to distinguish material changes that need review from lower-impact updates that can proceed under configured policy.[3]

Identity verification can extend to beneficial owners, directors and other related parties through invitation links. It produces an outcome for the institution’s workflow rather than merely storing a copy of an identity document. Transaction Monitoring separately offers configurable detection scenarios and back-testing, so an institution can examine proposed rule behaviour before using it in its monitoring process.[4][6]

The developer documentation separates APIs that change records from APIs that retrieve them and publishes OpenAPI specifications. Integrations can therefore use individual functions without reproducing the entire Fenergo interface. For breaking changes, the documented policy is a new version with the old version supported for two major releases. Non-breaking additions can still introduce new response fields or event types; integrations are expected to tolerate these rather than assume an unchanging payload.[7]

CLM for Salesforce lets relationship managers search existing entities, initiate onboarding and track progress from Salesforce. Chatter notifications carry journey updates, while document and related-party outreach connects the relationship manager with the compliance workflow. This is a documented application integration, with data-field mapping for migration, rather than a claim that any CRM can connect without implementation work.[8]

Machine credentials need separate access design. The Tenant Access guide states that the interface’s access layers and field-level restrictions do not apply to the client-credentials grant: an entity-data read scope can read all entity data within the relevant tenant. Tokens last 900 seconds, and API calls carry the tenant identifier. This makes a narrowly scoped integration credential a different control from an employee’s screen permissions.[21]

Fenergo conducts AWS Marketplace purchases through private offers. Its own EULA page says terms are not publicised, although the current Marketplace listing links an unsigned subscription template. The published figures and template below therefore describe an available procurement reference; the customer-specific offer and signed agreement establish the purchased scope.[11]

The linked template bills annually in advance, payable within 30 days of invoice. Training, implementation and configuration require a separate agreement. It renews for the original term length unless either party gives non-renewal notice at least 30 days before term-end.[12]

Fenergo manages the underlying AWS platform. Its architecture documentation describes a shared SaaS codebase deployed across three availability zones within a selected region, with independently operating functional domains. Updates enter an event-based system and propagate to the relevant stores; a successful change request and every downstream view becoming current are separate stages. The documented architecture concerns resilience within a deployment, rather than an unconditional guarantee that no active transaction can ever be lost.[14]

The migration guide calls for extraction rights, data-quality assessment, mapping to the future data model and a cutover strategy for records that continue changing. APIs support the transfer, with Fenergo specialists advising on preparation. This is more substantial than uploading a client list: existing related-party structures, approved data and work already in progress affect how the new system behaves on its first operating day.[13]

Transaction Monitoring has its own environment mapping. Its published deployment guide lists Frankfurt, Stockholm, Ohio and Sydney AWS regions and explains that CLM environments do not map one-for-one to monitoring environments. Recovery is supported across availability zones within a region; cross-region disaster recovery is not supported. A whole-region outage would require manual intervention and redeployment to another region. That boundary is material when a firm connects CLM to monitoring.[15]

The template provides 24/7 telephone handling for Severity 1 incidents; a ticket alone remains Severity 2 until the required call. Other support hours are 09:00–17:30 Dublin time, Monday–Friday excluding Irish public holidays. Response clocks require a completed report during support hours and pause while requested information is outstanding.[12]

Its monthly availability commitment is 99.9%, measured across core API health checks and login criteria, with maintenance, integration, network and customer-related exclusions. These template provisions are separate from the negotiated support level.[12]

The current third-party list identifies a phased move from Jira to Intercom for support and expressly says customer personal data should not be placed in assistant prompts. It distinguishes support relationship details from the production customer data processed by hosting and selected service providers. It also offers change notifications and, unless a written agreement says otherwise, a 30-day objection period after third-party-list updates.[19]

Fenergo’s compliance functions organise institutional decisions; the SaaS privacy notice says it does not independently make business or regulatory decisions for clients. Institutions control how identity outcomes, policies and workflow approvals are used, including the legal basis for biometric processing. Fenergo primarily processes their customer personal data on documented instructions, while its separate corporate notice describes controller activity for business contacts and its own relationship administration.[18][17]

API credential management is now a customer task: the guide says the service-request process for Fenergo-created client IDs ended in May 2026. The self-service tools retain audit trails and permit credential creation and removal under separate permissions. This change affects responsibility for maintaining integrations when a credential expires or a connection is retired.[22]

The SaaS notice effective 15 October 2026 says customer personal data is not used to train AI models. Clients choose the hosting region and determine retention and deletion of customer personal data within their tenancy; technical, audit and backup records may follow separate periods. Termination disposal follows contractual obligations and established procedures. Selecting a hosting region does not exclude every international transfer through an approved subprocessor.[18]

The subscription template identifies Fenergo Limited as the supplier.[12]

Fenergo was founded in 2009 and is headquartered in Dublin. Enterprise Ireland’s November 2025 company account describes a EUR 100 million research, development and innovation expansion announced that year, including plans for 300 additional Dublin jobs. Those are dated investment and hiring plans, rather than a current completed-headcount measure.[26]

Astorg’s current portfolio page continues to list Fenergo and records completion of the Astorg/Bridgepoint acquisition on 28 July 2021. The ownership context is therefore a privately held software business backed by those investors.[25]

Operator

Fenergo Limited

Service scope

SaaS client lifecycle, KYC, identity verification, regulatory workflows and transaction monitoring; institutional decisions remain with the client.

Customer types

Banks; Asset managers; Wealth managers; Fintechs; Other financial institutions

Delivery

SaaS; API

Pricing publication

Public and quoted pricing

Headquarters

Dublin, Ireland

Platforms

Fenergo CLM; Fenergo KYC; Fenergo Transaction Monitoring; Fenergo ID&V; CLM for Salesforce; Fen-AI / KYRA

Integrations

OpenAPI-based APIs; Salesforce application; SSO and SCIM; Read-only Supergraph GraphQL

Pricing scope

AWS Marketplace publishes deployment entry points; all purchases use negotiated private offers.

Implementation

Configurable journeys and policies, API integrations and migration of entity records; responsibility for the authoritative data source must be defined.

Support

Official support email and contract-specific incident processes; critical incidents require the documented escalation route.

Permissions and regulatory scope

Compliance software supports client institutions; it does not independently make their business or regulatory decisions.

Provider metadata checked 20 Oct 2026Source 28Source 2Source 16Source 12Source 11Source 3Source 27Source 10Source 13Source 25Source 7Source 1Source 18Source 8Source 24Source 20

Fenergo’s July 2026 Fen-AI announcement identifies six KYRA Automation agents as available to customers globally and introduces an interface for approved external agents. Its wider agent-class roadmap should not be read as proof that every described future capability is included in today’s subscription.[27]

Advanced Reporting supplies a schema for entity, journey and related-party data, with SQL reports requested through the interface or APIs. Execution is asynchronous: a client checks whether the report is still running and retrieves the secure download location after completion. This makes report generation a managed workflow, rather than direct database access or an immediate response containing every historical record.[23]

Supergraph provides a separate GraphQL route for selecting related information across domains in one query. The documentation explicitly limits it to reading: mutations that update records are not supported. It still requires an access token and tenant identifier. A data-warehouse export can therefore request a targeted combined view without acquiring a write capability through that query interface.[24]

The template requires a data-return request before termination and offers a free standard-format download for up to 30 days after term-end. Afterwards, retention or continued provision is not assured, and deletion is permitted subject to law.[12]