Retail Bank Business Information Model

This Business Information Model maps the data entities behind a retail banking business — customers, accounts, products, and transactions — organized into foundational, transactional, and informational categories. It lays out how those entities relate across the party, account, and product structure of the bank, and it's delivered as an editable Word document you can adapt to your own product set and organizational structure.

Why Customer and Account Aren't the Same Entity

Retail banking looks like the textbook case for a customer/account model, but the relationship between the two is where generic templates fall apart. A single account can have multiple owners, authorized signers, and beneficiaries, while a single customer can be linked to accounts they don't fully own — power of attorney, custodial accounts, trust relationships — so party-to-account role has to be modeled as its own many-to-many entity, not a simple owner field. "Household" is another entity that doesn't exist as a natural record in the source data — it's inferred from account relationships, yet it drives relationship pricing and cross-sell, so it has to be modeled deliberately. Compliance entities like KYC records, beneficial ownership, and sanctions screening attach to the customer but run on their own independent lifecycle, not as metadata bolted onto the account. And a loan is really three linked entities, not one — origination, servicing, and collateral each have distinct lifecycles, and a single piece of collateral can secure more than one loan.

What's Inside

• Foundational entities — Customer/Party, Household, Account, Product, Branch/Channel
• Transactional entities — Transaction, Loan, Card, Deposit, Loan Collateral
• Informational entities — Party-to-Account Role, KYC/Compliance Record, Statement, Relationship Pricing
• Entity relationships spanning the party, account, and product structure
• Delivered as a fully editable Word document

Where Teams Apply It

• Scoping the data model for a core banking, CRM, or digital banking platform implementation
• Aligning retail, risk, and compliance teams on shared definitions of customer, household, and account before a data governance initiative
• Structuring master data management for party and account records across deposit, lending, and card systems
• Mapping compliance and KYC data requirements independent of the account relationship

Who It's For

Data architects and business architects at retail and community banks, IT leaders scoping core banking or CRM platforms, and MDM or compliance leaders standardizing customer and account data.