This chapter breaks overseas core banking systems down into five layers that support “usable liquidity,” providing a common language for deciding where existing assets should be retained and where redesign is needed.
To modernize while continuing to use existing core banking systems, banks need to understand the role of each function rather than treat the system as a black box. As a first step, this paper organizes overseas core banking systems into five layers that support “usable liquidity.”
Core banking solutions are selected to meet the needs of individual countries, making it difficult to discuss all systems in the same terms. However, practical considerations such as consolidated accounting mean that treating the General Ledger (GL) layer separately better reflects how Japanese banks operate. This paper therefore discusses the Core Banking and GL layers separately.
① Channel Layer
This layer connects customers and external systems, such as enterprise resource planning (ERP) systems and treasury management systems (TMS), to the bank. Traditionally, it consisted of screens for balance inquiries and payment instructions. Today, it is evolving into an operational platform that controls fund movements based on real-time balances.
② API / Integration Layer
This layer controls external and internal connectivity and is designed to enforce zero-trust security principles. An API gateway handles traffic between external networks and internal systems (north-south traffic). A service mesh controls traffic between internal functions, or microservices (east-west traffic). This architecture allows banks to expand external connectivity, including through open APIs, while maintaining appropriate security, traffic-control, and service-resilience measures.
③ Business Logic Layer
This layer contains the core logic of banking functions, including deposits, lending, payments, and liquidity management. This layer brings together functions that directly support “usability,” such as target balancing and the rules for calculating interest in notional pooling. Whether this layer can be decoupled into independent services is a key factor in how quickly banks can change products and business rules.
④ Core Banking Layer
This layer holds balances and transaction records. The design of the subledger is particularly important. More recently, models have emerged in which the subledger operates independently of the core system through APIs, as Ledger-as-a-Service (LaaS). Event sourcing and CQRS (Command Query Responsibility Segregation) are two design approaches that can support real-time processing. Event sourcing continually appends events rather than overwriting state. CQRS separates the responsibilities and models for data updates (commands) and data retrieval (queries), supporting both frequent updates and fast queries. This design can support real-time processing while limiting changes to the core banking system. In practice, banks can add real-time capabilities without shutting down existing systems.
⑤ Data / General Ledger (GL) Layer
This layer combines the GL, which maintains the integrity of the official books, with a data platform that supports decision-making. Real-time liquidity forecasting requires an architecture that can aggregate and analyze data from the preceding four layers with minimal latency.