Whitepaper · Financial Services · Informatica Customer 360
KYC, householding and counterparty hierarchy on one party record.
KYC and AML party masters, member and customer householding, commercial and legal-entity hierarchies, and security reference data.
01 · Executive summary
The short version
- PDI delivers 69 financial-services use cases on Informatica Customer 360 with its accelerators. The use cases are drawn from 23 anonymized account profiles.
- Each use case arrives pre-mapped: the 12 entities it can land on, the 21 source-system families it draws from, and the match and data-quality rules for those entities.
- Design decisions are captured in adaptive-card workshops: 132 cards across 10 data-model workshops, so every answer becomes a configuration input.
- The entry point is a $50,000 fixed-fee MDM implementation for any two source systems. Informatica licensing is procured separately.
02 · The master-data problem
Where the records disagree.
Banks, credit unions, lenders and asset managers keep the same party in the core banking system, the AML platform, the loan origination system and the CRM. Know-your-customer, householding and exposure views each need that party once, with its relationships and hierarchy intact.
Financial Services is the deepest vertical in the accelerator, with 69 mapped use cases. KYC and AML party masters land on the Person and Organization model. Counterparty and legal-entity hierarchies land on Legal Entity 360 for Banking with its ownership relationships. Security masters land on Securities 360. Loan and collateral instruments are modeled as well.
03 · What is prepackaged for this industry
The accelerator, before day one.
Data model in play
- Person45 use cases
- Legal Entity42 use cases
- Organization28 use cases
- Household10 use cases
- Bond5 use cases
- Equity5 use cases
- Loan4 use cases
- Agreement3 use cases
- Payer3 use cases
- Asset3 use cases
- +2 moreStructure, Supplier
Source-to-target mappings
- Salesforce Sales and Service CloudColumn-level mappings with page-level evidence
- Dun & BradstreetElement-level mappings, confirmed per implementation
- GLEIF LEIColumn-level mappings with page-level evidence
- GDS property codesElement-level mappings, confirmed per implementation
- IATA / ARC / CLIA registriesElement-level mappings, confirmed per implementation
- 16 enterprise system familiesCore banking platform, CRM, BSA/AML platform, Loan origination, E-commerce / web accounts, Contract / bid / co-op pricing systems, ERP item / customer / vendor master, nCino / Salesforce FSC…. Mapped at attribute-family level; column names confirmed from the data dictionary.
Rules and workshops
- 25 match rulesIn the library for the entity types in play, ranked from exact keys to fuzzy name-and-address matching.
- 35 standardization rulesAcross 23 attribute families: names, addresses, phones, emails, identifiers and more.
- 132 adaptive cards10 data-model workshops, from party sub-types to stewardship.
04 · Use-case accelerator map
50 patterns, each with a landing.
Every pattern below is delivered on Informatica Customer 360 with PDI's accelerators. Patterns are anonymized from account profiles; a count such as 3× means the pattern recurs across profiles. Source systems are shown as system families.
| Use case pattern | Typical source systems | Lands on |
|---|---|---|
| KYC / AML Party MDM8× | BSA/AML platform, Core banking platform, Contract / bid / co-op pricing systems, Loan origination | Person, Legal Entity |
| Customer 360 / Householding3× | Core banking platform, E-commerce / web accounts, CRM, Salesforce Sales and Service Cloud | Hierarchy relationships, Person, Organization, Household, Legal Entity |
| Indirect Lending Dealer MDM3× | Dealertrack / RouteOne, Loan origination | Organization |
| KYC / Account Party MDM3× | Core banking platform, BSA/AML platform | Person, Legal Entity |
| Member 360 / Householding3× | Core banking platform, E-commerce / web accounts, CRM, Salesforce Sales and Service Cloud | Hierarchy relationships, Payer, Person, Organization, Household |
| Security Master / Reference Data MDM3× | Market data, ERP item / customer / vendor master, E-commerce / web accounts | Bond, Equity |
| Commercial Relationship Hierarchy MDM2× | Loan origination, Core banking platform, Dun & Bradstreet | Hierarchy relationships, Legal Entity |
| Customer 360 / Householding (post-merger)2× | Core banking platform, E-commerce / web accounts, CRM, Salesforce Sales and Service Cloud | Hierarchy relationships, Person, Organization, Household, Legal Entity |
| Account Party MDM | Core banking platform, BSA/AML platform | Person, Legal Entity |
| Account/Card hierarchy MDM | Core banking platform, BSA/AML platform, E-commerce / web accounts, CDP / marketing automation | Hierarchy relationships, Agreement, Legal Entity |
| Borrower / Obligor Legal Entity & Hierarchy MDM | Fund administration / investor portal / loan admin, Salesforce Sales and Service Cloud, CRM, GLEIF LEI | Hierarchy relationships, Legal Entity |
| Borrower 360 | Loan origination, Salesforce Sales and Service Cloud, CRM | Person, Organization |
| Client & Counterparty Legal Entity MDM (KYC, LEI) | BSA/AML platform, CRM, GLEIF LEI | Hierarchy relationships, Person, Legal Entity |
| Client & Intermediary 360 (advisors, platforms, institutions) | Salesforce Sales and Service Cloud, Fund administration / investor portal / loan admin | Hierarchy relationships, Legal Entity, Person, Organization |
| Client (Fund Manager) Hierarchy MDM | CRM, Licensing / provisioning / billing | Hierarchy relationships, Legal Entity, Person |
| Collateral / Equipment Asset MDM (aircraft, trucks, construction) | Loan origination | Loan, Asset |
| Collections Contact Data Quality | Confirmed in discovery | Person |
| Commercial & Government Depositor MDM | Core banking platform | Organization, Person, Agreement |
| Commercial Client Legal Entity & Hierarchy MDM | Salesforce Sales and Service Cloud, nCino / Salesforce FSC, Loan origination, Dun & Bradstreet | Hierarchy relationships, Legal Entity |
| Commercial Relationship & Trust Client MDM | Loan origination, Trust / escrow administration, Core banking platform | Organization, Person |
| Customer 360 | Core banking platform, E-commerce / web accounts | Person, Organization |
| Customer 360 / Householding (post-M&A) | Core banking platform, Salesforce Sales and Service Cloud, nCino / Salesforce FSC, E-commerce / web accounts | Hierarchy relationships, Person, Organization, Household, Legal Entity |
| Customer 360 / Identity Resolution | Confirmed in discovery | Person, Organization, Legal Entity |
| Customer 360 / KYC | Core banking platform, E-commerce / web accounts | Person, Organization, Legal Entity |
| Customer 360 / KYC identity resolution | Regulatory / registry feeds, BSA/AML platform, Salesforce Sales and Service Cloud, CDP / marketing automation | Person, Organization, Legal Entity |
| Customer 360 across bank, insurance agency & wealth | Core banking platform, Agency management, CRM | Person, Organization |
| Dealer / Vendor Partner MDM (office equipment dealers) | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Organization, Supplier, Person, Asset |
| Fund & Security Reference Data MDM | Fund administration / investor portal / loan admin, ERP item / customer / vendor master, Market data | Bond, Equity |
| Holdings & Portfolio MDM across affiliates | Confirmed in discovery | Hierarchy relationships, Legal Entity |
| Hotel / Property & Chain MDM | GDS property codes, Agency management | Structure |
| Household & Relationship MDM | Core banking platform, CRM | Hierarchy relationships, Household |
| Insurer Client Legal Entity MDM | CRM | Hierarchy relationships, Legal Entity |
| Investor & Legal Entity MDM (KYC/AML) | BSA/AML platform, Fund administration / investor portal / loan admin, GLEIF LEI | Hierarchy relationships, Person, Legal Entity |
| Investor / LP 360 | Fund administration / investor portal / loan admin, CRM | Legal Entity, Hierarchy relationships, Person |
| KYC / AML & Fraud Party MDM | BSA/AML platform | Person, Legal Entity |
| LP / Investor 360 | Fund administration / investor portal / loan admin, CRM | Legal Entity, Hierarchy relationships, Person |
| Leased Equipment Asset MDM (serial numbers) | Confirmed in discovery | Asset |
| Legal Entity & Counterparty MDM | GLEIF LEI, BSA/AML platform | Hierarchy relationships, Person, Legal Entity |
| Lessee Customer 360 | Dun & Bradstreet | Person, Organization |
| Loan & Instrument Reference Data MDM | Fund administration / investor portal / loan admin, Market data, ERP item / customer / vendor master | Bond, Equity, Loan |
| Loan Officer, Broker & Realtor Partner MDM | CRM | Organization, Hierarchy relationships, Loan, Person |
| Partner & Program Manager MDM (BaaS/embedded finance partners) | Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud, Licensing / provisioning / billing, ERP item / customer / vendor master | Organization, Agreement |
| Payee & Bank Account MDM | ERP item / customer / vendor master | Organization, Person |
| Portfolio Company & Legal Entity MDM | Salesforce Sales and Service Cloud, CRM | Hierarchy relationships, Legal Entity |
| Property & Loan MDM | Loan origination, Contract / bid / co-op pricing systems, Licensing / provisioning / billing | Loan, Structure |
| Regulatory Reporting Data Quality (CAT, etc.) | ERP item / customer / vendor master | Data-quality rules |
| Relationship & Contact MDM (founders, co-investors) | CRM | Legal Entity, Hierarchy relationships, Person |
| Travel Agency / Advisor MDM (IATA, ARC, CLIA IDs) | IATA / ARC / CLIA registries, Agency management, Contract / bid / co-op pricing systems, Salesforce Sales and Service Cloud | Organization, Person |
| Trust & Wealth Client Legal Entity MDM | Trust / escrow administration | Hierarchy relationships, Legal Entity |
| Wealth Client MDM | Trust / escrow administration | Organization, Person |
05 · How it deploys
Five steps, each already built.
The accelerator replaces blank-page design with decisions, a drawn model and pre-built mappings.
- Decide
Adaptive-card workshops capture the design. 10 data-model workshops, 132 cards. Each card asks one decision with two to four mutually exclusive options, and each answer is logged as a configuration input.
- Model
The financial-services model is already drawn: 12 entities, with their relationships and hierarchies, selected for the use cases in this paper.
- Map
The two sources arrive pre-mapped. 364 column-level mappings cover NPPES, MedPro, GLEIF, SAP, Salesforce and GS1, and 60 source-system families are catalogued in all.
- Match
Match, merge and quality rules start from a library: 20 match models with 65 rules, and 35 standardization rules across 23 attribute families.
- Prove
Tenant checks and acceptance. 80 documentation discrepancies are confirmed on the tenant before configuration is generated, and the acceptance measures agreed in discovery are tested.
This Customer 360 industry entry offer is distinct from the separately scoped Informatica MDM MVP.
06 · The two-source entry point
How a $50K MVP lands here.
A fixed-fee MDM implementation for two source systems. The model, the mappings, the match and data-quality rules and the workshop cards exist before the engagement starts.
- Starting pattern
- KYC / AML party master
- Source system 1
- Core banking platform
- Source system 2
- AML platform or CRM
- Lands on
- Person and Organization from the core model; Legal Entity with Parent and Ultimate Parent relationships where commercial hierarchy is in scope
- What it proves
- One party record per real-world customer across core banking and the AML platform, with match and survivorship rules the compliance team can inspect.
The $50,000 covers PDI professional services only. Informatica licensing is procured separately through Informatica. Additional sources, domains or scope changes after configuration begins are estimated separately. The example sources are illustrative; any two source systems qualify, and the pair is confirmed in discovery.
07 · Confirmed in discovery
What each engagement settles first.
- The two source systems. 16 enterprise system families appear in this industry. Their column names are confirmed from the customer's data dictionary before mappings are finalized.
- The tenant. 80 documentation discrepancies across the model are confirmed on the customer's tenant before configuration is generated, including field-group internal IDs that are read from tenant metadata.
- Package order. Industry packages are imported before any customization, because importing an industry package overwrites existing Customer 360 customization.
- Acceptance. Acceptance measures are agreed in discovery, before the fee is committed.
08 · Method
How this paper was built.
The use-case map, data model, mappings and rules come from PDI's accelerator, built on Informatica's published Customer 360 and Industry 360 documentation (April and July 2026 releases) and extended for each industry. Use cases are anonymized from 124 account profiles; no account is named. Adaptive-card counts come from PDI's Customer 360 data-model workshop set. The paper states no project durations or outcome figures; those are set as acceptance measures in discovery.