Master Data Management для банка

Зачем банку MDM

Customer представлен в 5-10 systems банка с different attributes. Product catalog в АБС не sync с marketing описаниями. Counterparty (для AML) в каждой системе свой record.

Без MDM каждый report contradicts другому. Cross-product analytics невозможен.

Banking domains

Customer master. Retail, SME, corporate. С UBO chain для корпоративных.

Product master. Cards, accounts, loans, deposits, FX, investment. С features, pricing, eligibility rules.

Counterparty master. Suppliers, partners, peer banks. AML profile per counterparty.

Branch / channel master. Locations, capabilities.

Reference data. Currencies, country codes, NACE codes, regulatory categories.

Структурные элементы

Source identification per entity (system of record vs reference).

Golden record builder с survivorship rules.

Identity resolution с probabilistic + deterministic matching.

Distribution layer (event bus push / batch sync).

Stewardship UI per domain.

Audit и data lineage.

Banking-specific concerns

Customer hierarchies (joint accounts, family, corporate group).

Beneficial ownership — multi-level UBO links.

KYC refresh state — per customer, per product.

Regulatory categorisation (PEP, sanctions, high-risk geography).

Data residency — некоторые data must stay in country.

Operating model

Owner — CDO.

Stewards per domain (customer, product, counterparty).

Data quality monitoring weekly.

Quarterly business review.

Связанное

• /architecture/banking-cdp-architecture/ — CDP consumer
• /insights/banking-data-quality/ — data quality
• /architecture/banking-event-bus-architecture/ — event bus
• /expertise/banking-data-discipline/ — data discipline