# Banking Data Model

**URL:** https://forum.data-community.org/t/banking-data-model/730
**Category:** Data Vault 2.0
**Created:** [April 3, 2023, 7:55am UTC](https://forum.data-community.org/t/banking-data-model/730 "2023-04-03T07:55:02Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![shubhankarsharma](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@shubhankarsharma](https://forum.data-community.org/u/shubhankarsharma)
#### Post date: [April 3, 2023, 7:55am UTC](https://forum.data-community.org/t/banking-data-model/730/1 "2023-04-03T07:55:02Z")

</div>

Hello Group, Thank you for some great discussion.  
I am trying to build a DV2.0 based on a bank domain.  
Business Entities 🙂

1. Customer
2. Account : Account is further broken into following sub-types  
a. Savings  
a. Checking  
a. Loans

The source has as of date values for each of the account sub-types and prepares a **full load everyday**.

Based on DV2.0 principles, I have been able to create the following DV objects:

1. Hub\_Customer . BK : CUSTOMER\_KEY  
a. Sat\_customer\_pii : To isolate PII attributes  
a. Sat\_customer\_attribute : For non-pii attributes
2. Hub\_Account : BK : ACCOUNT\_NUMBER  
a. Sat\_account\_attributes (these are not account sub\_types)
3. Link\_Customer\_Account

**Question**

- I am unable to model the account sub-types. Should these be satellities on the Link\_Customer\_Account ?
- The account sub-types have Primary & Seconday Customers that are similar to Primary & Seconday account holders. How should these be modelled ?

| ACCOUNT\_NUMBER | JOINT\_ACCOUNT | CUSTOMER\_KEY\_OF\_ACCOUNT\_OWNER | CUSTOMER\_KEY\_OF\_JOINT\_ACCOUNT\_OWNER\_1 | CURRENT\_BALANCE | DATE\_UPDATED\_LAST |
| --- | --- | --- | --- | --- | --- |
| 508787686 | Y | VIS1460787878 | VIS14600545454 | 2,598.16 | 2023-03-24 00:00:00.000 |
| 508787121 | Y | VIS1460566565 | VIS14600222112 | 3,498.16 | 2023-03-24 00:00:00.000 |

Will appreciate your thoughts on this ?

---

<div class="post-metadata">

### Author: ![shubhankarsharma](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@shubhankarsharma](https://forum.data-community.org/u/shubhankarsharma)
#### Post date: [April 6, 2023, 2:24pm UTC](https://forum.data-community.org/t/banking-data-model/730/2 "2023-04-06T14:24:37Z")

</div>

Hello team, Any recommendations on the following 🙂

- How should the account sub-types be modeled ?

- The account sub-types have Primary & Seconday Customers that are similar to Primary & Seconday account holders. How should these be modelled ?

---

<div class="post-metadata">

### Author: ![shubhankarsharma](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@shubhankarsharma](https://forum.data-community.org/u/shubhankarsharma)
#### Post date: [April 11, 2023, 1:21am UTC](https://forum.data-community.org/t/banking-data-model/730/3 "2023-04-11T01:21:31Z")

</div>

@patrickcuba or other Data Vault greats. Looking for some guidance on this. Thank you in advance

---

<div class="post-metadata">

### Author: ![FrenkLoonen](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/frenkloonen/32/119_2.png) [@FrenkLoonen](https://forum.data-community.org/u/FrenkLoonen)
#### Post date: [April 11, 2023, 8:26am UTC](https://forum.data-community.org/t/banking-data-model/730/4 "2023-04-11T08:26:10Z")

</div>

I’m in a (credit risk) banking domain currently too. I’m following our LDM where current (/checking) accounts have been separated from financing products (loans) and deposit products. All have an account number as a BK, but because the business concepts are so different, I created three separate hubs.

For the primary and secondary customers, I would create two links

- Link\_Account\_Customer\_Primary
- Link\_Account\_Customer\_Secondary

Both will reference the same Hubs. And you can create two Effectivity Satellites, one for each link.

For the account holders, you can take the same approach.

---

<div class="post-metadata">

### Author: ![patrickcuba](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/patrickcuba/32/19_2.png) [@patrickcuba](https://forum.data-community.org/u/patrickcuba)
#### Post date: [April 16, 2023, 10:25pm UTC](https://forum.data-community.org/t/banking-data-model/730/5 "2023-04-16T22:25:34Z")

</div>

Greats? 😃

The link looks fine, some thoughts

Is the hub table at the right grain? How do you tell the account type? Should you have one account hub or several account hubs?  
**Separate grain** : does the source supply these as seperate landed content or combined?  
Separate — win-win, combined — can they split it? No, then you should split them in pre-staging

**Same grain** (if you have decided to do so): would it make sense to deploy views by account type? hub\_savings\_account, hub\_checking\_account, hub\_loan\_account. They are essentially different things, but, up to you of course!

How do you identify the primary/secondary account owner? Is it key\_1 and key\_2 as you have depicted? If so then your link will contain:

- dv\_hashkey\_(ACCOUNT\_NUMBER) — hub\_account (or hub\_loan\_account… etc.)
- dv\_hashkey\_(CUSTOMER\_KEY\_OF\_ACCOUNT\_OWNER) — hub\_customer
- dv\_hashkey\_(CUSTOMER\_KEY\_OF\_ACCOUNT\_OWNER\_1) — hub\_customer  
If the source supplies it this way then this link maintains the Unit of Work

More specifically to your questions:

- Should these be satellites on the Link\_Customer\_Account? — depends, are the details describing the relationship or the account? If the account then hang them off the hub\_account
- How should these be modelled? With as fewest tables as possible!

---

<div class="post-metadata">

### Author: ![RhysHanscombe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.data-community.org/rhyshanscombe/32/394_2.png) [@RhysHanscombe](https://forum.data-community.org/u/RhysHanscombe)
#### Post date: [December 1, 2025, 2:50pm UTC](https://forum.data-community.org/t/banking-data-model/730/6 "2025-12-01T14:50:31Z")

</div>


