Backend interview prep

Start Learning

Core Banking Systems

Learn Core Banking Systems from a software engineer's perspective. This guide explains CBS architecture, customer onboarding, account management, deposits, withdrawals, fund transfers, ledger updates, batch jobs, integrations, security, and real-world banking workflows.

Introduction

Core Banking System, commonly called CBS, is the heart of every bank.

It is the central platform that manages:

  • Customers
  • Accounts
  • Deposits
  • Withdrawals
  • Fund Transfers
  • Loans
  • Interest Calculation
  • Ledger Posting
  • Statements
  • Branch Operations

Whenever a customer opens a mobile banking app, uses an ATM, visits a branch, transfers money, or checks account balance, the request usually reaches the Core Banking System directly or indirectly.

For software engineers, understanding Core Banking is very important because many enterprise banking applications integrate with CBS.

Learning Objectives

After completing this article, you will understand:

  • What is a Core Banking System?
  • Why banks need CBS
  • CBS architecture
  • Customer and account management
  • Transaction processing
  • Ledger posting
  • Batch processing
  • Channel integrations
  • Security and compliance
  • Real-world banking workflows
  • Developer best practices

What is a Core Banking System?

A Core Banking System is a centralized banking platform that allows customers to access banking services from any branch or digital channel.

CBS stands for:

Centralized Online Real-time Exchange

In simple words:

One customer account

↓

Available across all branches and channels

Before CBS, customer data was often branch-specific.

After CBS, a customer can:

  • Deposit money in one branch
  • Withdraw from another branch
  • Use ATM
  • Transfer using mobile app
  • Receive salary
  • Pay bills online

All through the same centralized system.

Why Core Banking is Important

Core Banking provides:

  • Centralized customer data
  • Real-time account balance
  • Accurate transaction processing
  • Branch interoperability
  • Digital banking enablement
  • Compliance reporting
  • Auditability
  • High availability

Without CBS, modern digital banking cannot function.

Core Banking High-Level Architecture

flowchart TD
    Customer[Customer]
    Mobile[Mobile Banking]
    Internet[Internet Banking]
    ATM[ATM]
    Branch[Branch Teller]
    API[API Gateway]
    CBS[Core Banking System]
    CustomerDB[(Customer Database)]
    AccountDB[(Account Database)]
    TransactionDB[(Transaction Database)]
    GL[(General Ledger)]
    Notify[Notification Service]

    Customer --> Mobile
    Customer --> Internet
    Customer --> ATM
    Customer --> Branch

    Mobile --> API
    Internet --> API
    ATM --> API
    Branch --> API

    API --> CBS
    CBS --> CustomerDB
    CBS --> AccountDB
    CBS --> TransactionDB
    CBS --> GL
    CBS --> Notify

Core Banking Main Modules

Module Purpose
Customer Information File Stores customer profile
Account Management Manages accounts and balances
Deposit Management Handles savings, current, FD, RD
Loan Management Handles loan accounts
Transaction Processing Handles debit, credit, transfer
General Ledger Accounting and financial posting
Interest Processing Interest calculation and posting
Statement Generation Account statements
Charges and Fees Service charges, penalties
Reporting Regulatory and operational reports

Customer Information File

Customer Information File is commonly called CIF.

CIF stores customer master information.

Example:

Customer ID: CUST1001
Name: Venu Reddy
Mobile: 9999999999
Email: [email protected]
KYC Status: Verified
Risk Category: Low

A customer can have multiple accounts.

flowchart LR
    Customer[CIF Customer]
    Savings[Savings Account]
    Current[Current Account]
    Loan[Loan Account]
    Card[Credit Card]

    Customer --> Savings
    Customer --> Current
    Customer --> Loan
    Customer --> Card

Account Management

Account module manages:

  • Account number
  • Account type
  • Account status
  • Available balance
  • Ledger balance
  • Holds
  • Overdraft limits
  • Interest rules
  • Account ownership

Common account statuses:

ACTIVE
DORMANT
CLOSED
FROZEN
BLOCKED

Account Types

Account Type Usage
Savings Account Personal banking
Current Account Business banking
Salary Account Employee salary
Fixed Deposit Term deposit
Recurring Deposit Monthly deposit
Loan Account Borrowed money tracking
NRI Account Non-resident banking

Available Balance vs Ledger Balance

This is very important in banking.

Ledger Balance

Ledger balance is the actual posted balance after confirmed transactions.

Available Balance

Available balance is the amount the customer can use immediately.

Example:

Ledger Balance: $1,000
Pending Card Hold: $100
Available Balance: $900

Transaction Processing

A transaction is any financial movement.

Examples:

  • Deposit
  • Withdrawal
  • Transfer
  • Card payment
  • Loan EMI payment
  • Interest posting
  • Fee deduction

Every transaction must be:

  • Accurate
  • Atomic
  • Auditable
  • Reversible if required
  • Posted to ledger

Fund Transfer Flow

flowchart LR
    Sender[Sender Account]
    Validate[Validate Balance]
    Debit[Debit Sender]
    Ledger1[Post Debit Ledger]
    Credit[Credit Receiver]
    Ledger2[Post Credit Ledger]
    Notify[Send Notification]

    Sender --> Validate
    Validate --> Debit
    Debit --> Ledger1
    Ledger1 --> Credit
    Credit --> Ledger2
    Ledger2 --> Notify

Double Entry Accounting

Banks use double-entry accounting.

Every transaction has:

  • One debit entry
  • One credit entry

Example:

Customer transfers $100 from Account A to Account B.

Debit Account A:  $100
Credit Account B: $100

Total accounting balance remains consistent.

General Ledger

General Ledger, also called GL, is the official accounting book of the bank.

CBS posts every financial transaction into GL.

Example:

Customer Deposit
Debit: Cash Account
Credit: Customer Deposit Account

GL is used for:

  • Bank accounting
  • Financial reporting
  • Regulatory reports
  • Trial balance
  • Profit and loss
  • Balance sheet

Deposit Flow

flowchart TD
    Customer[Customer Deposits Cash]
    Teller[Branch Teller]
    CBS[Core Banking System]
    Validate[Validate Account]
    Update[Update Balance]
    GL[Post General Ledger]
    Receipt[Generate Receipt]
    SMS[Send SMS Alert]

    Customer --> Teller
    Teller --> CBS
    CBS --> Validate
    Validate --> Update
    Update --> GL
    GL --> Receipt
    Receipt --> SMS

Withdrawal Flow

flowchart TD
    Customer[Customer Requests Withdrawal]
    Channel[ATM or Branch]
    CBS[Core Banking System]
    Validate[Validate Account Status]
    Balance[Check Available Balance]
    Debit[Debit Account]
    Ledger[Post Ledger]
    Cash[Dispense Cash]
    Notify[Send Notification]

    Customer --> Channel
    Channel --> CBS
    CBS --> Validate
    Validate --> Balance
    Balance --> Debit
    Debit --> Ledger
    Ledger --> Cash
    Cash --> Notify

Customer Onboarding Flow

flowchart LR
    Lead[Customer Lead]
    KYC[KYC Verification]
    CIF[Create CIF]
    Account[Open Account]
    Card[Issue Debit Card]
    Digital[Enable Digital Banking]

    Lead --> KYC
    KYC --> CIF
    CIF --> Account
    Account --> Card
    Card --> Digital

Customer onboarding usually includes:

  • Identity verification
  • Address verification
  • Risk classification
  • KYC completion
  • Account opening
  • Debit card issuance
  • Mobile banking activation

Channel Integration

CBS receives requests from many channels.

flowchart TD
    CBS[Core Banking System]
    Mobile[Mobile App]
    Web[Internet Banking]
    ATM[ATM Switch]
    Branch[Branch System]
    IVR[Contact Center]
    Payments[Payment Gateway]
    Cards[Card System]

    Mobile --> CBS
    Web --> CBS
    ATM --> CBS
    Branch --> CBS
    IVR --> CBS
    Payments --> CBS
    Cards --> CBS

Each channel may have different protocols:

  • REST API
  • SOAP
  • ISO 8583
  • MQ
  • Kafka
  • File-based batch
  • SFTP

Real-Time vs Batch Processing

Core banking systems use both real-time and batch processing.

Real-Time Processing

Examples:

  • Balance inquiry
  • Fund transfer
  • ATM withdrawal
  • Card authorization

Batch Processing

Examples:

  • Interest calculation
  • Monthly statement generation
  • End-of-day processing
  • Fee deduction
  • Report generation

End of Day Processing

End of Day is commonly called EOD.

EOD jobs perform:

  • Interest accrual
  • Fee posting
  • GL reconciliation
  • Statement generation
  • Dormancy checks
  • Regulatory report preparation
  • Batch settlement
flowchart LR
    Start[Start EOD]
    Freeze[Freeze Business Date]
    Interest[Calculate Interest]
    Fees[Post Fees]
    GL[Reconcile GL]
    Reports[Generate Reports]
    Close[Close Business Date]

    Start --> Freeze
    Freeze --> Interest
    Interest --> Fees
    Fees --> GL
    GL --> Reports
    Reports --> Close

CBS Integration with Payment Systems

Core banking integrates with payment networks.

Examples:

  • ACH
  • Wire Transfer
  • SWIFT
  • NEFT
  • RTGS
  • IMPS
  • UPI
  • Card Networks

Payment flow:

flowchart LR
    Customer[Customer]
    Channel[Mobile or Branch]
    PaymentService[Payment Service]
    CBS[Core Banking]
    Network[Payment Network]
    Beneficiary[Beneficiary Bank]

    Customer --> Channel
    Channel --> PaymentService
    PaymentService --> CBS
    CBS --> Network
    Network --> Beneficiary

CBS Integration with Cards

Card systems authorize card transactions.

Flow:

flowchart LR
    Merchant[Merchant]
    CardNetwork[Visa or Mastercard]
    CardSystem[Card Management System]
    CBS[Core Banking]
    Account[Customer Account]

    Merchant --> CardNetwork
    CardNetwork --> CardSystem
    CardSystem --> CBS
    CBS --> Account

CBS may update:

  • Holds
  • Available balance
  • Posted transactions
  • Settlement entries

CBS Data Model

Common entities:

Customer
Account
Transaction
LedgerEntry
Product
Branch
Currency
Loan
Deposit
Statement

Relationship:

flowchart TD
    Customer[Customer]
    Account[Account]
    Transaction[Transaction]
    Ledger[Ledger Entry]
    Statement[Statement]

    Customer --> Account
    Account --> Transaction
    Transaction --> Ledger
    Account --> Statement

Example Java Domain Model

public class Customer {
    private String customerId;
    private String fullName;
    private String mobileNumber;
    private String email;
    private String kycStatus;
}

public class Account {
    private String accountNumber;
    private String customerId;
    private String accountType;
    private BigDecimal ledgerBalance;
    private BigDecimal availableBalance;
    private String status;
}

public class BankingTransaction {
    private String transactionId;
    private String fromAccount;
    private String toAccount;
    private BigDecimal amount;
    private String transactionType;
    private String status;
}

Fund Transfer API Example

POST /api/transfers
Content-Type: application/json

{
  "fromAccount": "10000001",
  "toAccount": "10000002",
  "amount": 100.00,
  "currency": "USD",
  "remarks": "Rent payment"
}

Response:

{
  "transactionId": "TXN123456",
  "status": "SUCCESS",
  "message": "Transfer completed successfully"
}

Transaction Statuses

Common statuses:

INITIATED
VALIDATED
PROCESSING
SUCCESS
FAILED
REVERSED
PENDING_APPROVAL

Why Idempotency is Important

If a customer clicks transfer twice or network retry happens, the bank should not debit twice.

Use an idempotency key.

Example:

Idempotency-Key: 9f4c4b61-1234-4567-8901

Flow:

flowchart LR
    Request[Transfer Request]
    Check[Check Idempotency Key]
    Existing[Return Existing Result]
    Process[Process New Transaction]

    Request --> Check
    Check --> Existing
    Check --> Process

Security in CBS

CBS must enforce:

  • Authentication
  • Authorization
  • Role-based access
  • Encryption
  • Audit logging
  • Maker-checker approval
  • Fraud checks
  • Transaction limits
  • Session timeout

Maker-Checker Pattern

In banking, sensitive actions often require two people.

Maker creates the request.

Checker approves it.

Example:

flowchart LR
    Maker[Maker Creates Request]
    Pending[Pending Approval]
    Checker[Checker Reviews]
    Approved[Approved]
    Executed[Executed]

    Maker --> Pending
    Pending --> Checker
    Checker --> Approved
    Approved --> Executed

Used for:

  • Large fund transfers
  • Beneficiary addition
  • Corporate payments
  • Account closure
  • Limit changes

Audit Logging

Every important action should be logged.

Audit fields:

Who performed action
When action happened
What changed
Old value
New value
Source IP
Device ID
Channel
Correlation ID

Audit logs are critical for:

  • Compliance
  • Fraud investigation
  • Customer disputes
  • Regulatory reporting

Reliability Requirements

CBS must support:

  • High availability
  • Disaster recovery
  • Data backup
  • Transaction consistency
  • Low latency
  • Zero data loss
  • Strong monitoring

Banking systems commonly use:

  • Active-passive DR
  • Multi-AZ databases
  • Message queues
  • Batch restartability
  • Reconciliation jobs

Common Banking Developer Challenges

  • Duplicate transactions
  • Timeout handling
  • Reversal processing
  • Partial failures
  • Ledger mismatch
  • Payment retries
  • Batch job failures
  • Data reconciliation
  • Performance bottlenecks
  • Compliance changes

Best Practices for Developers

  • Use BigDecimal for money
  • Never use double or float for currency
  • Use idempotency keys for payment APIs
  • Keep audit logs for critical actions
  • Use transaction boundaries carefully
  • Implement retry with caution
  • Design reversal flows
  • Validate account status before debit
  • Check available balance, not only ledger balance
  • Use maker-checker for sensitive operations
  • Encrypt sensitive customer data
  • Monitor transaction failure rates

Common Interview Questions

What is a Core Banking System?

A Core Banking System is the central platform that manages customer accounts, transactions, deposits, withdrawals, loans, ledgers, and financial records across all banking channels.

What is CIF?

CIF stands for Customer Information File. It stores customer master data such as name, contact details, KYC status, risk category, and customer relationships.

What is the difference between available balance and ledger balance?

Ledger balance is the posted account balance. Available balance is the amount available for immediate use after considering holds, pending transactions, overdraft limits, and restrictions.

What is EOD in banking?

EOD stands for End of Day processing. It includes interest calculation, fee posting, ledger reconciliation, statement generation, reporting, and business date closure.

Why is idempotency important in banking?

Idempotency prevents duplicate processing of the same transaction when retries or duplicate requests occur.

What is maker-checker?

Maker-checker is an approval pattern where one user creates a request and another user reviews and approves it before execution.

Summary

In this article, we learned Core Banking Systems from a software engineer's perspective.

We covered:

  • What CBS is
  • CBS architecture
  • Customer Information File
  • Account management
  • Transaction processing
  • General ledger
  • Deposits and withdrawals
  • Customer onboarding
  • Channel integration
  • Real-time and batch processing
  • EOD jobs
  • Payment and card integrations
  • CBS data model
  • Idempotency
  • Maker-checker
  • Security
  • Developer best practices

Core Banking is the foundation of the banking domain. Once you understand CBS, it becomes easier to learn payments, cards, lending, fraud detection, regulatory reporting, and enterprise banking architecture.