A Comprehensive Overview of Modern Bank Core Systems Architecture

Bank Core System Overview

The bank core system is the central platform for processing financial transactions and managing customer services. Modern architectures have shifted from monolithic mainframe designs to distributed, micro‑service and cloud‑native deployments, focusing on three core capabilities: account services, central services, and accounting.

Historical Evolution

1960s: IBM CICS introduced real‑time online transaction processing on mainframes.

1970s‑80s: Relational databases enabled instant account updates.

1990s‑present: Modular products (e.g., Flexcube, Temenos T24) and standardized APIs promoted flexibility.

Recent years: Cloud computing and micro‑services (e.g., Ant Group OceanBase) provide elasticity and open‑API integration with fintech.

Customer Information Management (CIF)

CIF stores master data for customers, their accounts, and transaction histories. Core functions include:

Master data management.

Customer relationship maintenance.

Segmentation and targeted operations.

Risk and compliance control (e.g., AML blacklist checks).

Typical workflow: a mobile‑banking registration triggers identity verification, blacklist screening, and generation of a unique customer ID. Subsequent account opening, credit‑card issuance, loan applications, marketing recommendations, and risk monitoring all reference the CIF data.

Bank Account Types

Deposit accounts : custody of funds, interest calculation, and status control (freeze/unfreeze).

Loan accounts : credit issuance, repayment scheduling, delinquency handling, and post‑loan asset disposal.

Internal accounts : intra‑bank fund transfers, profit‑loss accounting, and settlement buffering.

Deposit Core

Manages the liability side of the balance sheet. Key capabilities:

Real‑time deposit posting and high‑concurrency interest accrual (e.g., quarterly posting, on‑demand interest estimation).

Account control features such as freeze, stop‑payment, and limit enforcement.

Compliance functions including deposit insurance reporting and AML monitoring.

Integration with the General Ledger to ensure accounting consistency.

Loan Core

Handles the asset side of the balance sheet. Core processes cover the full loan lifecycle:

Credit approval and loan disbursement.

Repayment scheduling, principal/interest posting, and exception handling.

Post‑loan activities: extensions, collections, and asset disposal.

Risk metrics (e.g., exposure, delinquency rates) feed directly into profitability analysis.

Payment & Settlement

Acts as the “high‑speed highway” for fund movements, linking customers, banks, central banks, and third‑party providers.

On‑Us (intra‑bank) Payments

Funds move between accounts within the same bank.

Instant settlement (seconds) with zero inter‑bank fees.

Cross‑Bank Payments

Involve multiple participants (payer bank, clearing system, central bank, intermediary banks) and follow national standards such as CNAPS in China. The process typically includes:

Payment instruction from the payer bank reduces the payer’s balance.

Central clearing system (e.g., CNAPS) nets positions and generates settlement files.

Recipient bank credits the beneficiary account.

Reconciliation engine matches internal records with external settlement data; discrepancies are resolved via adjustment or refund workflows.

General Ledger (GL)

The GL records every transaction as standardized debit/credit entries, producing balance sheets, income statements, and cash‑flow statements. Typical GL accounts include assets, liabilities, equity, income, and expenses. Daily reconciliation ensures that transaction‑level balances equal aggregated GL balances.

Card Business Management

Manages the full lifecycle of debit, credit, and prepaid cards:

Card issuance and binding to underlying accounts.

Real‑time transaction processing for POS, ATM, and online payments.

Daily clearing with card networks and fee settlement.

Risk controls such as credit limits, fraud detection, and dispute handling.

Example accounting for a credit‑card purchase of 1,000 CNY with a 6 CNY merchant fee and a 0.75 % installment fee:

Debit: Customer account      1,000.00
Credit: Merchant settlement   994.00
Credit: Merchant fee           6.00
Debit: Installment receivable  7.50
Credit: Installment revenue    7.50

Batch Processing

Batch jobs run during off‑peak windows to handle non‑real‑time workloads such as end‑of‑day clearing, interest calculation, regulatory reporting, and data archiving. They process millions of records automatically, reducing manual effort and ensuring timely, accurate outputs.

Data Model Relationships

Key entities and their relationships:

Customer ↔ Account : 1‑to‑N; a customer can own multiple accounts.

Account ↔ Card / Passbook : 1‑to‑N or 1‑to‑1; a card or passbook is linked to a specific account.

Account ↔ GL Account : Automatic mapping; e.g., a personal deposit account maps to a liability GL account, while a corporate loan maps to an asset GL account.

Separating the public account number (used for external transactions) from the internal account ID enhances security and allows a single account to be accessed via multiple media (cards, passbooks, mobile numbers).

Conclusion

The bank core system integrates customer master data, account management, deposit and loan processing, payment clearing, accounting, risk control, and batch operations. Understanding its modular architecture, evolution path, and inter‑module data flows enables banks to design, implement, and optimize core‑system projects that support current business needs and future fintech innovations.