Architecture

Master Data Management for the bank

Customer master, product master, counterparty master — single source of truth for critical entities. Distribution to downstream systems.

Discuss Your Challenge

Why the bank needs MDM

Customer is represented in 5-10 systems with different attributes. Product catalog in ABS not synced with marketing descriptions. Counterparty (for AML) has a separate record in each system.

Without MDM every report contradicts another. Cross-product analytics is impossible.

Banking domains

Customer master. Retail, SME, corporate. With UBO chain for corporates.

Product master. Cards, accounts, loans, deposits, FX, investment. With 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.

Structural elements

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

Golden record builder with survivorship rules.

Identity resolution with probabilistic + deterministic matching.

Distribution layer (event bus push / batch sync).

Stewardship UI per domain.

Audit and 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 — some data must stay in country.

Operating model

Owner — CDO.

Stewards per domain (customer, product, counterparty).

Data quality monitoring weekly.

Quarterly business review.

← Back

Ready to discuss your challenge?

Tell me what's not working or what needs to be built. First conversation — no obligations.

Usually respond within a few hours

Discuss a challenge
Choose a convenient way to connect
Telegram
Fast reply
Fast
WhatsApp
Voice and documents
📞
Call
+998 99 838-11-88