Unlocking the Secrets of Bank Core Systems: A Comprehensive Overview

1. Overview Diagram

The diagram below shows the overall architecture of a bank's core system.

Its functional scope covers the most fundamental and critical financial transaction processing and customer service management. With technological evolution, the core system architecture has gradually shifted from centralized to distributed, and its functional positioning has moved from an early "big‑and‑all" model to a "thin core" model, focusing on three core capabilities: account services, central basic services, and accounting processing.

Account Management: Implements full‑lifecycle management of customer information, deposit accounts, and loan accounts.

Transaction Processing: Supports real‑time deposits, transfers, and fund clearing, ensuring timeliness and accuracy.

General Ledger and Accounting: Automatically generates statutory financial statements such as balance sheets and profit‑and‑loss statements, ensuring data consistency through reconciliation mechanisms.

Next, we will dissect the core system's main functional units from a business‑module perspective to fully understand its scope and implementation.

2. Definition and Evolution

The bank core system originated in the mid‑20th century as the "digital hub" of banking operations. Over time, its definition expanded from a simple accounting tool to the foundational infrastructure supporting financial innovation.

It was not designed for a single business function but emerged from centralized online real‑time interactive systems. Since IBM introduced CICS in the 1960s, banks have built comprehensive systems capable of centralized transaction processing, real‑time data updates, and multi‑terminal access.

The core’s basic business areas include traditional deposit‑loan services and payment settlement, with modern systems gradually integrating wealth‑management and insurance distribution. Technological advances have driven a transition from centralized to distributed architectures and from monolithic to micro‑service designs.

Manual Accounting Era (pre‑20th century): Paper ledgers and manual records were inefficient and error‑prone.

Mechanization & Early Computing (1950s‑1960s): Electromechanical accounting machines and mainframes like IBM System/360 introduced batch processing.

Real‑Time Processing & Networking (1970s‑1980s): Relational databases and networks enabled online transaction processing, e.g., Mitsubishi Bank’s early core system.

Standardization & Modularity (post‑1990s): Products like Flexcube and Temenos T24 offered modular, quickly deployable functionalities.

Modern Technological Evolution: Cloud computing and micro‑services (e.g., Ant Group’s OceanBase) replace traditional centralized systems, enhancing elasticity and integration with third‑party services.

3. Customer Information Management

This foundational module stores and manages customer basic data, account relationships, and transaction behavior, enabling precise identification, dynamic risk control, personalized product recommendation, and efficient operations.

3.1 Main Functions and Roles include master data management, customer relationship maintenance, segmentation, and compliance control (see table).

Example: Customer Chen Tianyu opens an account via mobile banking, the CIF system validates identity, checks AML blacklists, and generates a unique customer ID.

Account linking: After opening a savings account, the CIF automatically associates it with the customer ID; subsequent credit‑card applications retrieve CIF data for rapid approval.

Loan application: The system pulls basic info, account statements, and credit scores, automatically calculates loan limits, and proposes repayment plans.

Marketing recommendation: Based on risk level and activity, the system pushes high‑yield wealth products or credit‑loan discounts.

Risk monitoring: Large outbound transfers trigger AML rules, prompting investigation.

In summary, the customer information module is the operational nucleus, supporting identification, risk control, personalized services, and data integration, while tightly collaborating with account, payment, and risk modules.

4. Three Types of Bank Accounts

Accounts are the core data entities of a bank, carrying funds and influencing all business processes.

4.1 Deposit Accounts

This module manages the full lifecycle of deposit accounts, covering fund custody, interest calculation for demand and term deposits, and account control (withdrawal, freeze, unfreeze).

4.2 Loan Accounts

This module handles the entire loan lifecycle, including credit execution, disbursement, repayment management, and post‑loan operations such as extensions and asset recovery.

4.3 Internal Accounts

This module manages intra‑bank fund transfers and accounting, providing fund allocation, precise profit‑and‑loss accounting, and pre‑settlement buffering.

5. Deposit Core

The deposit core is the primary liability source, managing customer deposits, supporting loan funding, and offering flexible products and high‑concurrency processing such as quarterly interest posting.

Key values: enhance customer stickiness through structured deposits, control risk via account freezes, and improve net interest margin through efficient liability management.

6. Loan Core

The loan core manages the full lifecycle of credit assets, from disbursement to recovery and risk control, directly influencing interest income and asset quality.

It supports end‑to‑end loan processing, with batch jobs handling large‑scale operations.

7. Payments and Settlement

This module acts as the "highway" for fund flows, linking customers, banks, central banks, and third‑party payment institutions.

7.1 In‑house Payments

Funds move between accounts within the same bank, incurring no external fees.

Same‑source funds: transfers stay within the bank (e.g., ICBC A → ICBC B).

Instant settlement: seconds‑level processing.

Zero cost: no interbank or third‑party fees.

Process example: Customer transfers ¥10,000 via mobile banking; the payment gateway performs risk checks, updates balances, and generates accounting entries (debit A, credit B).

7.2 Interbank Payments

Funds move between different banks, requiring settlement through central bank systems (e.g., CNAPS).

Example flow: Bank A initiates payment, debits the payer, Bank B credits the payee, and the central bank clears the net positions.

7.2 Settlement and Reconciliation

Settlement: Funds are transferred between the bank and external entities (central bank, other banks, payment platforms) to ensure balanced accounts.

Reconciliation: Internal records are matched against external data to resolve discrepancies.

8. General Ledger Module

The GL serves as the financial hub, recording all transactions, ensuring compliance, and providing data for management and regulators.

It aggregates data from deposit, loan, and payment modules, performs daily/monthly/yearly balance checks, and outputs financial statements.

Typical GL accounts include assets, liabilities, equity, income, and expenses, with automated posting ensuring that each transaction is accurately reflected.

9. Card Business Management

This module handles the full lifecycle of debit, credit, and prepaid cards, covering issuance, transaction processing, settlement, and risk management.

Cards enable POS purchases, ATM withdrawals, and online payments, linking card numbers to settlement accounts.

Example: A credit‑card purchase of ¥1,000 generates merchant fees and installment charges, which are reflected in the GL.

12. Customer, Account, Card

Customers are the root entity; accounts hold funds; cards and passbooks provide access. Account numbers are public identifiers, while internal account IDs remain hidden for security and flexibility.

13. Batch Processing Overview

Batch processing handles non‑real‑time tasks such as end‑of‑day clearing, interest calculation, and report generation during low‑traffic periods, reducing load on online systems and minimizing manual errors.

Conclusion

The bank core system is the backbone of banking operations, and its construction and optimization are crucial for a bank's growth. By deeply understanding the core system's essence, evolution, architecture, requirements, project organization, service decomposition, and batch processing, banks can plan and implement core system projects more scientifically and rationally, providing solid support for business development. As fintech continues to evolve, core systems will keep advancing to meet new business needs and technological challenges.