CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
🌙☀️
Log inStart free
Home/Templates/Finance & Banking

🏦 Finance & Banking · Database ERD

Banking Database Schema

A relational schema for retail banking: customers, accounts, transactions, cards, loans and beneficiaries.

More Finance & Banking templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • A customer can hold several accounts, and accounts can be joint
  • Every transaction records debit and credit accounts
  • Loans have an EMI schedule

Prompt used

ERD for retail banking: Customer holds Accounts through AccountHolder (supporting joint accounts), each Account belongs to a Branch and has Transactions and Cards; Customer has Beneficiaries for transfers; Loan belongs to a Customer and has EmiSchedule rows.

Mermaid code
erDiagram
  CUSTOMER ||--o{ ACCOUNT_HOLDER : holds
  ACCOUNT ||--|{ ACCOUNT_HOLDER : "held by"
  BRANCH ||--o{ ACCOUNT : manages
  ACCOUNT ||--o{ TRANSACTION : records
  ACCOUNT ||--o{ CARD : issues
  CUSTOMER ||--o{ BENEFICIARY : adds
  CUSTOMER ||--o{ LOAN : takes
  LOAN ||--|{ EMI_SCHEDULE : "repaid by"
  CUSTOMER {
    int id PK
    string cif_no
    string name
    string pan
  }
  ACCOUNT {
    int id PK
    string account_no
    string type
    decimal balance
    int branch_id FK
  }
  TRANSACTION {
    int id PK
    int account_id FK
    string type
    decimal amount
    datetime posted_at
  }
  LOAN {
    int id PK
    int customer_id FK
    decimal principal
    decimal rate
  }
  EMI_SCHEDULE {
    int id PK
    int loan_id FK
    date due_date
    decimal amount
  }

Inside this diagram

An entity relationship diagram with 9 tables, 22 columns and 8 relationships.

Tables and their columns

  • CUSTOMER: id (PK), cif_no, name, pan
  • ACCOUNT_HOLDER
  • ACCOUNT: id (PK), account_no, type, balance, branch_id (FK)
  • BRANCH
  • TRANSACTION: id (PK), account_id (FK), type, amount, posted_at
  • CARD
  • BENEFICIARY
  • LOAN: id (PK), customer_id (FK), principal, rate
  • EMI_SCHEDULE: id (PK), loan_id (FK), due_date, amount

Relationships

  • CUSTOMER holds ACCOUNT_HOLDER: each CUSTOMER has zero or more ACCOUNT_HOLDER, each ACCOUNT_HOLDER belongs to exactly one CUSTOMER
  • ACCOUNT held by ACCOUNT_HOLDER: each ACCOUNT has one or more ACCOUNT_HOLDER, each ACCOUNT_HOLDER belongs to exactly one ACCOUNT
  • BRANCH manages ACCOUNT: each BRANCH has zero or more ACCOUNT, each ACCOUNT belongs to exactly one BRANCH
  • ACCOUNT records TRANSACTION: each ACCOUNT has zero or more TRANSACTION, each TRANSACTION belongs to exactly one ACCOUNT
  • ACCOUNT issues CARD: each ACCOUNT has zero or more CARD, each CARD belongs to exactly one ACCOUNT
  • CUSTOMER adds BENEFICIARY: each CUSTOMER has zero or more BENEFICIARY, each BENEFICIARY belongs to exactly one CUSTOMER
  • CUSTOMER takes LOAN: each CUSTOMER has zero or more LOAN, each LOAN belongs to exactly one CUSTOMER
  • LOAN repaid by EMI_SCHEDULE: each LOAN has one or more EMI_SCHEDULE, each EMI_SCHEDULE belongs to exactly one LOAN

Make your own diagram like this

Describe your own system in plain English and the AI ER diagram generator draws it in seconds, in the same style as this template.

Related templates

SequenceFinance & Banking

UPI Payment Flow

The steps behind a UPI payment: the payer's app, the payer's bank, NPCI's UPI switch and the payee's bank, from entering a UPI ID to the money arriving.

C4 ArchitectureProFinance & Banking

Payment Gateway Architecture

A payment gateway that lets online merchants accept cards and UPI: the checkout, the payment core with fraud checks, and the card networks and banks it connects to.

FlowchartFinance & Banking

Loan Origination Workflow

A personal loan from application to disbursal: KYC, credit bureau check, underwriting rules, manual review for borderline cases, and the final agreement.

SequenceFinance & Banking

Card Payment Authorisation

What happens in the second after a card is tapped or entered online: the acquirer, card network and issuing bank authorise the payment, with 3-D Secure for online payments.

Data FlowFinance & Banking

Real-Time Fraud Detection Data Flow

How a bank scores every transaction for fraud in milliseconds: features from history, an ML model, rules, and a case queue for analysts.

C4 ArchitectureProFinance & Banking

Core Banking System Architecture

The main building blocks of a bank's core platform: accounts, deposits, loans, payments and the general ledger, used by branches, internet banking and mobile.