15 posts tagged with "Agency"

The Agency Associations step now previews your agency data as a nested, three-tier view — Investment Managers, their Underlying Principals and Managed Relationships, and the Managed Products beneath them — with each identifier shown alongside its resolved name. This makes it easy to spot-check that the combinations are structured correctly before loading, and you can search for a specific record to preview it in its agency context. This is available on all agency-enabled tenants.

Agency Bulk Upload no longer requires a Managed Relationship file. Where customers don't hold Managed Relationship data, the Managed Relationship data type can be de-selected on the Agency ETL task, and the system will find or create the Managed Relationship between the Investment Manager and each Underlying Principal during Load. A new Autoname MRs setting gives those Managed Relationships a meaningful name automatically. This is available now on non-live tenants and will be enabled on live tenants from 5 October 2026.

ETL Agency Migration can now automatically name new Managed Relationships that are created without a name, using the format "MR - [Investment Manager Legal Entity Name] - [Underlying Principal Legal Entity Name]". Managed Relationships created by the system no longer display as a generic "Managed Relationship", making them easy to tell apart where an Underlying Principal has several. This is available now on non-live tenants and will be enabled on live tenants from 5 October 2026.

ETL Agency Migration can now automatically launch Fenergo journeys for migrated Investment Managers and Underlying Principals once they have loaded, so that follow-up activity such as onboarding, Risk Assessment, Screening or Due Diligence can begin without launching each journey manually. Journey Launch is available now on non-live tenants and will be enabled on live tenants from 2 October 2026.

ETL Agency Migration is a new and separate capability, leveraging ETL to migrate agency objects. It exists for a single purpose: to build the Agency Data Model. It migrates Investment Managers, Underlying Principals, Managed Relationships and Managed Products, and constructs the relationships between them automatically.

ETL Agency Migration brings agency migration into the same self-service, preview-and-validate experience clients already use for standard ETL. It complements standard ETL rather than replacing it — where an Investment Manager or Underlying Principal is also a client, its full client record is still migrated through a standard ETL project.

Agency Bulk Upload introduces a new Agency ETL task within the Agency Request journey, allowing customers to onboard large volumes of Underlying Principals, Managed Relationships and Products for an Investment Manager using CSV files instead of manual UI entry.

By embedding our Extract Transform Load (ETL) capabilities directly into Agency Requests, customers can process high-volume agency onboarding while still using the standard Agency data model, connected journeys and policy-driven validation.

Managed Relationships entities are integral to the agency data model. They are optional and can be left unnamed or can be manually named. We've added an option to automatically apply a "Legal Entity Name" value that follows the format: "MR - [Agent Legal Entity Name] - [UP Legal Enttity Name]".

Conflict Resolution was previously updated to retain resolved conflicts for review as a completed task. We've enhanced this to also retain resolved conflicts for Managed Relationships. No configuration or enablement is required. When the Conflict Resolution task is completed with MR conflicts, they will be available for review in the completed task.

We are pleased to announce the release of our new KYC Reliance enhancement. This provides a powerful framework for you to configure how KYC Reliance is applied during your Underlying Principal onboarding journeys.

We've enhanced the Managed Relationship Details task wtih the same UX we recently release for Agency Request Details. This will make it clearer for users when there are mandatory Data or Document requirements outstanding and guide them to the area requiring action by highlighting the Managed Relationship, tab (data/docs) and requirements that still need to be captured.