Modernizing Overseas Core Banking Systems at Major Japanese Banks: A Five-Layer Architecture Blueprint for Modernization Alongside Legacy Systems

Insight
Nov 17, 2026
  • Banking/Capital Markets
  • Technology Transformation
  • Global
GettyImages-1468025006

In global transaction banking, competition is shifting from the “visibility” of account balances to the “usability” of funds: the ability to move them flexibly whenever and wherever they are needed. Major Japanese banks face growing pressure to modernize the core banking systems that support their overseas operations. Modernization can help them meet these changing customer needs, support 24/7/365 instant payments, and respond to tighter regulation such as DORA and PSD3. Building on the shifts in the competitive landscape and the tokenized-deposit approach discussed in our previous paper, this paper outlines a path to phased transformation built on existing assets. The first half (Chapters 2 and 3) introduces the five-layer architecture model and core use cases that underpin modernization. The second half (Chapters 4 and 5) focuses on the main theme of this paper: three implementation patterns and five execution steps for starting with a limited scope and expanding it in stages.

About the Author

  • Takuya Watanabe

    Takuya Watanabe

    Director
  • Naoki Arita

    Naoki Arita

    Manager

1. Why Now: The Case for Modernizing Overseas Core Banking Architecture

This chapter explains why banks are reviewing their overseas core banking systems as 24/7/365 instant payment networks expand, ISO 20022 migration progresses, and regulatory requirements, including DORA and PSD3, become more stringent.
Client expectations in global transaction banking are changing. Traditionally, banks focused on safeguarding funds and settling payments accurately and on time. Today, however, corporate clients expect their banks to make funds immediately available in the countries and currencies they need, whenever they need them, 24/7. Meeting this expectation requires changes to how banking systems are designed, not only to the services built on them. The shift toward “usable liquidity” discussed in our previous paper is now evident in system design as well.
The expansion of 24/7/365 real-time payment networks, the migration to ISO 20022, and tighter regulation in Europe are adding to this pressure. The regulatory changes include DORA (the Digital Operational Resilience Act) and PSD3 (the Third Payment Services Directive, which was not yet in force at the time of writing). Reconciling the books through daily batch processing is no longer sufficient for real-time liquidity management.
Yet major Japanese banks’ overseas operations are still running on legacy systems introduced at different times and with different specifications across countries and regions. A simultaneous, worldwide “big-bang” replacement is difficult to justify given the cost and risk involved. Some leading European and U.S. banks have taken an approach that retains existing core systems and adds a real-time processing layer around them as a way to contain costs and risks. In our view, major Japanese banks do not need to rebuild their systems from scratch. We recommend that they assess the strengths of their existing assets and decide which functions to separate out and which to redesign. Delaying modernization can have consequences beyond technical debt: it may limit how efficiently funds can be used, increase regulatory compliance costs, and make it harder to meet the needs of customers who expect instant payments.

2. The Architecture of Overseas Core Banking Systems: A Five-Layer View

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.

Modernizing all five layers at once is not the objective. To improve return on investment, we recommend that banks assess each layer independently and clearly distinguish which layers to retain and which to separate out.

3. Representative Use Cases Driving “Usable Liquidity”

This chapter uses two representative use cases, Virtual Account Management and multi-currency notional pooling, to illustrate services that banks can offer customers when the five layers work together.
The five layers described in the previous chapter need to work together to deliver these services to customers in global transaction banking. The following two use cases show how this works in practice.

  • Virtual Account Management (VAM)
    A large number of virtual accounts are organized in a hierarchy beneath the parent company’s physical account, with incoming and outgoing payments routed instantly to that account. The subledger records entries at the virtual-account level, allowing the group to centralize liquidity management while maintaining detailed accounting records for each participating entity.
    Note: How This Differs from Conventional Virtual Accounts in Japan (Collection-Only Accounts)
    In Japan, virtual accounts are often understood as disposable accounts used for receivables reconciliation and payment-agency services, primarily to identify the source of incoming payments. Hierarchical VAM in global transaction banking is fundamentally different. It is a cash management platform that supports complex intra-group treasury activities, such as in-house banking and intercompany loan management, through virtual account structures to optimize liquidity.
  • Multi-Currency Notional Pooling
    Balances across multiple currencies are notionally combined into a net position to optimize interest costs and returns, without physically moving funds. This requires real-time conversion into a base currency, a rules engine to calculate net interest, and records of each participant’s credit and debit positions in the pool. These processes must be coordinated in real time through APIs and the subledger.

Beyond adding functionality, these two use cases give corporate treasury teams visibility of group-wide funds that they can use to decide where to concentrate or deploy cash. Greater visibility into group funds and centralized cash management can help corporate clients reduce idle cash and external borrowing. For banks, these capabilities can help differentiate their services and may support both fee income and the deposit base.

4. Modernizing Alongside Existing Core Systems: Three Implementation Patterns

This chapter presents three implementation patterns identified from our analysis of modernization initiatives at leading European and U.S. banks, and sets out our recommended approach for major Japanese banks.
We now turn to the central theme of this paper: putting transformation into practice. Our analysis of these banks’ approaches identifies three broad patterns for transforming the architecture of major banks.

  1. Progressive Modernization
    Banks migrate functions to a cloud-native platform in stages, starting with new products and digital channels, while continuing to run the existing core. For major banks with large portfolios, this approach can allow them to continue using existing assets while limiting migration risk and expanding the scope in stages.
  2. Sidecar (Overlay)
    Banks add a new ledger or payment platform alongside the existing core banking system while keeping changes to the core itself to a minimum. A representative example is the blockchain-based sidecar model, including applications using tokenized deposits, described in our insight paper “Tokenized Deposits and the Shift to 24/7 Bank Payment Infrastructure: Toward an Era of Immediately Usable Liquidity.” This approach can be particularly effective for services that need to reach the market quickly, such as 24/7 payments, because it limits the scope of changes required in the existing core.
  3. Full Replacement
    At smaller locations or newly established overseas subsidiaries, banks shut down the existing system and switch to a next-generation, cloud-native platform in a single cutover. Because migration affects the entire operation, this approach is limited to small or newly established locations that can tolerate the risk of business interruption. It allows banks to implement their target architecture without the constraints of legacy assets or the burden and cost of running old and new systems in parallel.

Banks should choose a pattern based on three criteria: the size of the location, the maintainability of existing systems, and how quickly new services need to reach the market. We recommend using Progressive Modernization as the foundation for large locations, the Sidecar pattern for new services such as 24/7 payments, and Full Replacement for small or newly established locations.
Given the scale of their businesses, we believe a hybrid strategy combining Progressive Modernization and the Sidecar pattern can allow major Japanese banks to modernize their core in stages while launching new services such as 24/7 payments quickly. To put this strategy into practice, we recommend that banks move away from relying entirely on a single product from one vendor and adopt a composable approach that combines selected legacy assets with modern modules.

5. Approach to Transformation and Five Execution Steps

This chapter sets out five steps for putting this architecture into practice and identifies the stakeholders who should be involved in each.
The architecture modernization outlined in the previous chapter needs to be translated into specific initiatives, owners, and deliverables. To make the most of existing assets, banks need to start with validation in a limited scope and then expand in stages. We propose five execution steps that involve everyone from senior management to frontline teams.

Step 1: Current-State Assessment (All Stakeholders)
For each overseas location, identify where funds remain idle, constraints on operating hours, operational workloads, and structural bottlenecks in legacy systems.

Step 2: Selection of Priority Use Cases (Led by Business Units)
Identify the target customer segments, currencies, and transaction flows based on customer needs and return on investment, for example, U.S. dollar payments in a particular region.

Step 3: Identification of Technology Application Areas (Led by IT)
Use the five-layer model in Chapter 2 to review current systems and identify which functions to retain in the existing core and which to separate out through a sidecar or decoupling approach.

Step 4: Design and Execution of a Proof of Concept (PoC) (Led by the CIO)
Deploy a new platform within a limited scope. Test how the subledger and data integration with the existing core perform in day-to-day operations, and whether the platform meets security requirements.

Step 5: Development of a Phased Implementation Roadmap (Executive Management)
Use the PoC results to develop a medium- to long-term investment plan and a phased rollout roadmap, with a cross-functional team spanning business, IT, risk, and finance.

Each step should produce a concrete deliverable. For Steps 1 through 5, these are a current-state assessment report, a priority use case definition document, an application area map, PoC evaluation results, and a phased implementation roadmap, respectively. Defining these deliverables makes it clear what to hand over to the next phase and what evidence supports investment decisions.

6. Conclusion: ABeam Consulting’s Support

Modernizing overseas core banking systems is not just an IT system modernization project. It is a cross-functional program that spans business strategy, operational processes, regulatory and accounting requirements, and organizational culture change.
This modernization can enable banks to move from making funds “visible” to making them “usable,” ready to move whenever needed. ABeam Consulting combines practical expertise in global transaction banking with architecture design capabilities to support banks from current-state assessment through PoC and phased implementation, within their existing system, regulatory, and organizational constraints. We work alongside banks to determine which customers’ funding challenges to address and in what order.


Contact

Click here for inquiries and consultations