Unlocking the Secrets of Bank Core Systems: Architecture, Modules, and Evolution

Dissecting the Global View of Bank Core Systems

From Definition and Evolution to Architecture, Account System, Customer Management, Deposit Core, Loan Core, Payments & Settlement, Card‑Account Relations, and Batch Processing

1. Definition and Development

Bank core systems originated in the mid‑20th century as the "digital hub" of banking operations. Initially simple accounting tools, they have evolved alongside technology into the foundational infrastructure that supports financial innovation.

These systems are not single‑function applications; they stem from centralized, online, real‑time interaction architectures.

Since IBM introduced CICS in the 1960s, banks built comprehensive systems capable of processing transactions centrally, updating data in real time, and supporting multi‑terminal access—forming the modern core system.

The core’s business scope covers traditional deposit and loan services, while modern systems increasingly integrate wealth‑management sales, insurance distribution, and other value‑added services. Technological shifts have driven a transition from monolithic, centralized designs to distributed, micro‑service architectures.

Manual bookkeeping era (pre‑20th century) : Early banks relied on paper ledgers and manual entry, resulting in low efficiency and high error rates. For example, 19th‑century banks managed deposits and loans via handwritten ledgers, with settlement requiring painstaking manual reconciliation.

Mechanization and early computerization (1950s‑1960s) : Electro‑mechanical accounting machines using punched cards improved efficiency. In the 1960s, large mainframes like IBM System/360 introduced batch processing and centralized architectures, laying the groundwork for modern core systems.

Real‑time processing and networking (1970s‑1980s) : The maturation of relational databases and network infrastructure enabled online transaction processing, allowing instantaneous data updates. Japan’s Mitsubishi Bank pioneered cross‑branch real‑time deposits and withdrawals in the 1970s.

Standardization and modularization (post‑1990s) : Growing business complexity led to modular designs. Products such as Flexcube and Temenos T24 support flexible combinations of deposit, loan, and payment functions, and provide standardized interfaces for seamless integration with peripheral systems.

Modern technological evolution : Cloud computing and micro‑service architectures—exemplified by Ant Group’s OceanBase—are replacing traditional monolithic systems, enhancing elasticity and scalability. APIs enable deep integration with third‑party services (payments, credit, e‑commerce), fostering open financial platforms and scenario‑driven innovation.

2. Bank Core Overall Architecture

The core system underpins the most fundamental banking transactions and customer services. The diagram below (illustrative) shows the overall architecture, which has gradually shifted from a centralized to a distributed model, moving from a "big‑and‑all" approach to a "thin core" focused on account services, core services, and accounting.

Account Management : Handles the full lifecycle of customer information, deposit accounts, and loan accounts.

Transaction Processing : Supports real‑time deposits, withdrawals, transfers, and settlements, ensuring timeliness and accuracy.

General Ledger & Accounting : Automatically generates statutory financial statements (balance sheet, profit & loss) and ensures data consistency through accounting checks.

The following sections dissect each functional module to provide a complete view of the core system’s business scope and implementation.

3. Customer Information Management

This foundational module centralizes storage and management of customer basic data, account relationships, and transaction behavior. It enables precise customer identification, dynamic risk control, personalized product recommendation, and efficient operations.

3.1 Main Functions and Roles : The module comprises four core capabilities—master data management, customer relationship maintenance, customer segmentation, and risk/compliance control. The table below (illustrative) details these functions.

3.2 Customer Data Entities

3.3 Business Example : Using a fictional customer “Chen Tianyu” opening an account and applying for a loan, the workflow demonstrates registration, account linking, loan application, marketing recommendation, and risk monitoring.

(1) Registration : The customer applies via mobile banking; the CIF system validates identity, checks anti‑money‑laundering blacklists, and generates a unique customer ID.

(2) Account Linking : A savings account is automatically linked to the customer ID; subsequent credit‑card applications reuse CIF data for rapid approval.

(3) Loan Application : The system retrieves basic info, account flow, and credit score, automatically calculates the loan limit, and proposes repayment plans.

(4) Marketing Recommendation : Based on income tier and activity, the system pushes high‑yield wealth products and offers credit‑loan discounts.

(5) Risk Monitoring : Large outbound transfers trigger anti‑money‑laundering rules, prompting risk‑control investigation.

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

4. Three Types of Bank Accounts

Accounts are the core data entities that carry funds. Their status changes directly affect deposits, loans, payments, and settlement processes.

Accounts record ownership information, support deposit/withdrawal, transfer, interest calculation, and risk control. Each transaction triggers dual‑track processing to update both account balances and accounting entries, ensuring consistency.

The three main categories are:

4.1 Deposit Accounts

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

4.2 Loan Accounts

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

4.3 Internal Accounts

These accounts handle intra‑bank fund transfers and financial accounting, providing fund allocation, precise profit‑and‑loss accounting, and settlement buffering mechanisms.

5. Deposit Core

The deposit core is the primary source of bank liabilities, managing customer deposit assets and tightly integrating with loan, payment, and settlement modules. Its core functions include:

Fund collection and utilization to build a loan‑fund pool supporting asset‑side expansion.

Providing flexible deposit/withdrawal services with configurable interest rules, and value‑added features such as automatic rollover and customized large‑deposit certificates.

Multi‑level risk controls (freeze, stop‑payment, limits) to prevent abnormal fund flows, and compliance functions (deposit insurance reporting, AML monitoring).

Generating profit through interest spread, account fees, and transaction fees.

High‑concurrency handling (e.g., batch interest calculation at quarter‑end), real‑time interest simulation before withdrawal, and real‑time synchronization with the general ledger ensure accounting consistency.

6. Loan Core

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

Key capabilities include credit execution, loan issuance, repayment scheduling, exception monitoring, loan extensions, and asset recovery.

7. Payments & Settlement

This module acts as the "high‑speed highway" for funds, linking customers, banks, central banks, and third‑party payment institutions. Core functions are:

All‑scenario fund flow : Supports personal‑to‑enterprise payments, inter‑bank clearing, and cross‑border remittance.

Cross‑business collaboration : Provides real‑time fund transfer for deposits, loans, and wealth management, breaking data silos.

Intelligent compliance clearing : Uses transaction‑level verification, AML monitoring, and large‑transaction reporting.

Exceptional customer experience : Offers 24/7 real‑time settlement, batch auto‑debit, multi‑currency settlement, and cross‑border tracking.

7.1 In‑house Payments (On‑Us)

Funds move between accounts within the same bank, involving only the payer and payee accounts without external intermediaries.

Process flow: customer initiates payment via online/mobile banking or counter; the payment gateway performs risk checks; the core updates payer balance and generates accounting entries (debit payer, credit payee).

Account source: entire transaction stays within a single bank’s account system (e.g., ICBC A → ICBC B).

Instant settlement: typically seconds.

Zero external cost: no inter‑bank fees.

Implementation relies on account source verification, real‑time balance update, and accounting entry generation.

Example: a customer transfers ¥10,000 via mobile banking; the system validates, updates balances, and records the debit/credit entries.

7.2 Cross‑Bank Payments

Funds move between different banks or financial institutions, requiring balance adjustments on both sides and inter‑bank settlement.

The payment flow involves the paying bank (initiates debit), the receiving bank (credits the beneficiary), the central bank clearing system (net settlement), and possibly an intermediary or correspondent bank for non‑direct connections.

Example: a customer transfers ¥10,000 from Bank A to Bank B via the CNAPS real‑time clearing system.

7.3 Settlement & Reconciliation

Settlement : The process of transferring funds and settling positions between the bank and external entities (central bank, other banks, payment platforms) to ensure balanced accounts.

Reconciliation : Comparing internal records with external data to identify and resolve discrepancies, guaranteeing data integrity.

Settlement generates standard files (e.g., CNAPS format) for inter‑bank fund movement; reconciliation engines automatically match internal and external records, flagging differences for manual or automated correction.

8. General Ledger Module

The General Ledger (GL) serves as the financial hub, recording all banking transactions in standardized accounting entries, ensuring accuracy, compliance, and providing authoritative data for management and regulators.

The GL aggregates data from deposit, loan, and payment modules, performs daily balance reconciliation, and produces financial statements (balance sheet, cash flow). Core functions include posting, trial balance, period closing, and report generation.

Typical GL accounts cover assets, liabilities, equity, income, and expenses. Consistency checks ensure that shared‑account balances are zero after day‑end clearing; any non‑zero balances indicate errors requiring investigation.

Example: a cross‑bank transfer generates GL entries—debiting the customer’s deposit account and crediting the settlement account, followed by a corresponding settlement entry crediting the central bank reserve.

9. Card Business Management

This module manages the full lifecycle of debit, credit, and prepaid cards, covering issuance, transaction processing, clearing, and risk management—linking customer accounts with payment channels.

Features include POS consumption, ATM cash withdrawal, online payments, and card‑account binding (e.g., debit cards linked to checking accounts).

During issuance, the CRM provides customer data, the card system generates a card number and binds it to an account. Transactions are processed through UnionPay or third‑party gateways, instantly deducting balances. End‑of‑day clearing reconciles with card networks, and the GL records fees and commissions.

Example: a credit‑card purchase of ¥1,000 incurs a ¥6 merchant fee and a 0.75 % installment fee; the accounting flow records the purchase, fee, and installment revenue.

Card management bridges accounts, channels, and merchants, enhancing profitability through credit limits and installment pricing, while improving customer experience with features like one‑click binding and real‑time alerts.

Conclusion

The bank core system is the backbone of banking operations. Understanding its definition, evolution, overall architecture, functional modules, batch processing, and integration points enables banks to plan and implement core system projects scientifically, providing solid support for business growth. As fintech advances, core systems will continue to evolve to meet new business demands and technological challenges.