Moody’s Analytics: KYC, entity intelligence & onboarding

The current product catalog presents Moody’s for Compliance alongside Entity Verification, Grid and Orbis. Operational documentation continues to use Maxsight, while the contract collection retains Passfort. These names identify related workflow and data capabilities; the current pages do not establish that every product is interchangeable or included in one subscription. Banks, payments businesses, securities firms and other organizations conducting counterparty due diligence can select the combination their process requires.[1][13][19]

Orbis makes company records easier to compare and links entities through ownership trees. Registry verification addresses a different question: what evidence is available from the relevant official record, such as registration details, directors, status or filings. An onboarding team may need both the standardized group view and a dated source document, especially when indirect control or a complex ownership chain requires investigation.[4][3]

Grid organizes adverse media by risk type and stage, allowing analysts to distinguish an allegation or investigation from a later legal outcome. Its PEP information includes relationships such as family members and close associates. Screening should therefore feed an assessment of the specific person, connection and event; a matched name or relationship is not itself a finding of misconduct.[5]

Maxsight’s provider documentation names Moody’s Orbis, GBG ID3global and Kompany KYC API as examples of connected data services. Entity details are sent to the configured provider and the returned result contributes to the check outcome. Multiple providers can be arranged in a fallback sequence. This makes provider selection an operational decision about coverage and returned evidence, rather than simply a count of available connections.[8]

For Salesforce users, Moody’s publishes a managed Maxsight package that brings risk information into front-office workflows. Installation requires Salesforce Administrator access and uses AppExchange. Package installation is one stage: the help collection also separates permission assignment, connecting the systems and configuration. A project should assign responsibility for both the compliance workflow and the Salesforce administration involved.[11][12]

The help guide modified on 9 December 2025 documents a terminology difference that matters during integration. The interface uses Entity, Assessment and Workflow where older terminology used Profile, Product application and Smart policy flow. The API retains the older names. Mapping interface labels to API objects avoids confusing a change in presentation with a changed interface contract.[9][10]

The publicly linked PassFort architecture guide is dated 1 March 2021. It describes a shared SaaS deployment, a separately managed dedicated deployment option, a RESTful JSON API and JSON webhooks. It also describes role-based access and scoped API keys. These are useful architectural reference points for a Passfort-derived implementation; its historical hosting locations and infrastructure details should be replaced by the environment schedule in a current proposal.[17]

The public KYC catalog routes purchases through a demo or sales discussion and does not provide one tariff covering workflow, company data and screening. The linked PassFort Master Subscription Agreement is dated 4 January 2021: it puts charges in order forms and, unless otherwise specified, bases fees on purchased service and content subscriptions rather than actual consumption. That wording is a dated contracting example, not a current price promise for the whole Moody’s portfolio.[1][14]

A useful quotation should identify the workflow subscription, licensed datasets, external-provider checks, relevant volume commitments and implementation work separately. The 2021 agreement distinguishes third-party applications and services from PassFort’s own responsibilities unless an order form says otherwise. That distinction matters when an onboarding workflow depends on a registry, identity provider or other separately supplied data service; a successful platform procurement must also settle who contracts for and supports each connection.[14][8]

Configuration starts with the assessment a customer must complete, the tasks it contains and the checks attached to those tasks. Maxsight distinguishes electronic identity evidence from identity-document verification. Each enabled check needs a variant specifying its provider and configuration. A workflow can use different variants by country or invoke a second provider after a failure, error or partial match, while retaining inputs and returned results for review.[7]

1. Define customer and entity types, the required evidence and the decisions that need analyst approval.
2. Configure task checks, provider variants and country-dependent fallback behavior; distinguish a provider error from a failed verification.
3. Map internal systems to the documented API objects and connect any Salesforce workflow under the appropriate administrator controls.
4. Exercise passing, failing and incomplete assessments with representative cases, then confirm the evidence and decision history that analysts will retain.

Moody’s describes Financial House beginning integration in September 2020 and using Passfort to combine customer onboarding, monitoring and the work of agents and compliance analysts. A separate Penguin Securities case reports a Maxsight implementation in under three months and a 70–80% reduction in onboarding time, with tailored risk thresholds and internal API connections. Those are vendor-published customer outcomes with different starting points; they do not establish a standard implementation duration.[19]

KYC customers have a public support form and regional telephone routes, while Maxsight help provides user and developer documentation. The public form promises a response as soon as possible without a numerical response target. Product-specific contracts matter for operational support: the current Passfort terms page links both Standard and Premium SLAs, each carrying a 1 October 2020 date.[18][13][10]

The GRID privacy notice, updated 9 October 2026, identifies Moody’s Analytics, Inc. as the provider and describes authorized subscriber use for compliance and risk screening. It explicitly excludes using GRID to decide an individual’s eligibility for credit, insurance, employment or other covered consumer purposes. That restriction is material when a firm tries to reuse screening data outside its original compliance workflow.[6]

The notice distinguishes Moody’s role in compiling and distributing GRID data from processing audit-trail information for screening-platform customers. Subscribers determine their own use of the information. This profile covers data and compliance software; the evidence here does not establish a financial-services permission for a customer merely because it uses Moody’s tools.[6][2]

The KYC family reflects both internal development and acquisitions. Moody’s 3 December 2021 release reported that it had acquired PassFort Limited, a UK SaaS workflow business, and had agreed to acquire Vienna-based 360kompany AG. The PassFort acquisition was already completed when announced. A separate release on 1 March 2022 confirmed completion of the kompany acquisition, adding registry-based business-verification technology.[20][21]

Operator

Moody’s Analytics, Inc. (GRID); other products use the contracting Moody’s affiliate

Service scope

KYC and entity intelligence: company and ownership data, registry verification, risk screening, onboarding workflows and ongoing monitoring.

Customer types

Banks; Payments businesses; Securities firms; Compliance teams; Corporations conducting counterparty due diligence

Delivery

SaaS; API

Pricing publication

Quote only

Platforms

Moody’s for Compliance; Maxsight; Passfort; Orbis; Grid; Entity Verification; Kompany KYC API

Integrations

Maxsight API; Moody’s Maxsight for Salesforce; Moody’s Orbis; GBG ID3global; Kompany KYC API

Pricing scope

Product-specific proposal. The linked January 2021 PassFort agreement puts subscription charges and quantities in order forms; it is not a universal current Moody’s tariff.

Implementation

Configure evidence tasks and provider variants, map internal systems to Maxsight API objects, and validate analyst workflows. Salesforce installation requires administrator access.

Support

KYC support form, regional telephone contacts and Maxsight documentation. Applicable support targets depend on the product agreement; linked PassFort SLAs are dated October 2020.

Permissions and regulatory scope

Compliance data and software. The October 2026 GRID notice identifies Moody’s Analytics, Inc. and excludes covered individual credit, insurance and employment eligibility uses. No customer financial-services permission is conferred.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 6Source 7Source 8Source 12Source 14Source 13Source 18Source 20Source 21

The most useful evaluation cases are those where evidence is incomplete: two companies with similar names, an indirect owner, a partial screening match, a provider failure and a customer whose risk changes after approval. Orbis, registry retrieval, Grid and workflow checks address different parts of those cases. Comparing the evidence returned and the analyst actions required gives a clearer view of fit than relying on a single aggregate coverage claim.[4][3][5][7]