The foundations of balance sheet management are inherently cross-functional. Asset & Liability Management (ALM), Funds Transfer Pricing (FTP), Regulatory Reporting, and Financial Planning each examine a different dimension of the same economic reality.
This article examines the economics of balance sheet management, exploring how fragmentation develops across interconnected functions, how it affects operational efficiency and governance, and why operating model design becomes a significant driver of long-term cost.
Audio Article
ALM focuses on interest rate risk, liquidity, and the behavior of assets and liabilities over time, while FTP translates funding and liquidity economics into internal pricing mechanisms. Regulatory Reporting turns financial and risk information into formal regulatory outputs, and Financial Planning projects the future evolution of the institution under changing business and market assumptions.
These organizational boundaries serve a clear purpose, although the underlying economics remain closely connected. A deposit portfolio can influence liquidity assumptions, interest rate sensitivity and internal transfer prices, while the same evolution of the balance sheet can flow into financial forecasts and regulatory indicators. Behavioral assumptions developed within one function may also influence conclusions reached elsewhere.
This interdependence creates a natural need for consistency across the financial institution, as information moves between functions and connected methodologies need to support a common understanding of the balance sheet. When these activities rely on independent systems, that consistency requires additional effort. The same information may be extracted and maintained through different processes, methodologies may evolve through separate development cycles, and similar calculations can be reproduced across platforms while interfaces carry information between environments that were never designed to operate as one.
Much of the complexity lives in the connections between systems and in the work required to preserve coherence across them.
The real cost of fragmentation shows up in daily operations, not in technology architecture.
Fragmentation is often viewed through the lens of technology architecture, while many of its most significant consequences appear in the daily operation of the institution. Every additional environment brings its own requirements for maintenance and specialized expertise, and connected balance sheet activities require institutions to preserve consistency across all of them.
The result is a recurring set of operational activities:
Maintaining parallel data feeds and transformation processes.
Reconciling results produced through different analytical environments.
Coordinating methodological changes across several platforms.
Preserving specialized expertise for individual systems.
Managing independent upgrade cycles and external support relationships.
Adapting integrations as the surrounding architecture evolves.
Although each activity may appear manageable in isolation, the cumulative effort becomes substantial once it is replicated across several systems and sustained over many years, particularly as the institution continues to evolve.
A new product may require adjustments across several analytical environments, while regulatory developments can affect data structures and reporting logic in different parts of the architecture.
Changes in behavioral assumptions may also travel through ALM and planning processes, requiring each affected platform to interpret and implement the same methodological development within its own structure. Operational complexity increases with every additional platform involved, as the institution continues to manage a single balance sheet while the operational consequences of change are distributed across multiple environments and development cycles.
The cost of maintaining coherence is largely invisible in a budget; it is absorbed by the specialist capacity spent reconciling differences across systems.
Some of the most significant effects of fragmentation are difficult to locate in a budget because they are embedded in the everyday use of specialist capacity.
When Finance, Risk and Treasury functions operate through separate systems, considerable effort can be devoted to resolving differences between metrics before the information reaches management discussions. The challenge often lies in determining whether outputs produced through different environments can be understood together and whether apparent inconsistencies reflect genuine economic differences or variations in data and methodology.
This creates a recurring form of operational friction, where time that could be devoted to understanding the balance sheet is redirected toward maintaining coherence between platforms. Teams investigate data lineage, compare assumptions and resolve differences across systems before meaningful analysis can begin.
One of the greatest inefficiencies, and one of the highest hidden costs of fragmentation, is the specialist capacity absorbed by this work.
ALM specialists, regulatory experts and finance professionals create greater value when their time is focused on interpretation and on understanding the consequences of changing conditions. Operating models that continuously redirect this capacity toward reconciliation carry an economic cost that extends well beyond technology expenditure.
The same dynamic can influence the institution’s ability to retain specialized talent. Highly qualified professionals are drawn to complex analytical questions and meaningful decisions, while environments dominated by repetitive reconciliation and operational maintenance leave less room for the work that requires their expertise. Over time, the quality of the operating environment becomes part of the institution’s ability to use and retain specialist knowledge.
The consequences of fragmentation also reach governance, particularly when management decisions depend on information produced across different areas of the institution.
Funding strategy and balance sheet composition can draw on metrics generated by several teams, each operating with its own responsibilities and analytical perspective. Differences in data sources or methodological implementation may require additional validation before information reaches governance forums, leaving decision-makers to understand the origin of those differences before they can evaluate their implications.
Integrated operating environments reduce this friction by providing a more common foundation for information and analytical processes. This creates several useful conditions:
Key metrics can be evaluated within a more consistent view of the balance sheet.
Connected functions can work from shared analytical foundations.
Less time is required to explain differences created by separate operational environments.
Management discussions can devote greater attention to interpretation and action.
The resulting alignment also corresponds closely with supervisory expectations around the integration of key metrics into governance frameworks and management processes.
The relevance of a metric extends beyond its calculation, as supervisors also consider how information enters planning and risk management and how it ultimately informs management discussions. An institution that can demonstrate a coherent relationship between analytical outputs and decisions provides a clearer view of how the balance sheet is understood and managed.
Cloud migration reduces infrastructure costs, but it does not remove the operational fragmentation across systems.
Technology modernization has changed the infrastructure landscape across banking, and many institutions have migrated specialized applications to cloud environments, reducing their dependence on traditional on-premises infrastructure.
The economic benefits can be meaningful. Cloud migration can reduce hardware investment cycles, change the way infrastructure capacity is managed, and provide greater flexibility in the deployment of computing resources. The application landscape, however, can preserve many of its existing operational characteristics after migration.
A cloud-hosted legacy system may continue to require its own support structure and specialized expertise, while major version upgrades can still involve migration planning, integration adaptations and extensive output validation. Institutions may also continue to manage independent interfaces and maintain consistency across separate environments.
This distinction is frequently discussed in the context of cloud-enabled and cloud-native architectures. Moving an application to cloud infrastructure changes where it runs, while the underlying architecture continues to shape its maintenance and integration requirements.
The distinction becomes clearer when examining representative situations that many institutions will recognize. To illustrate how fragmentation translates into measurable economic outcomes, the following section presents two five-year use cases based on different technology starting points:
Use Case 1: Four specialized on-premises systems are consolidated into a single integrated SaaS operating environment.
Use Case 2: Four specialized systems that have already migrated to cloud infrastructure are consolidated into the same integrated SaaS environment.
Together, these scenarios make it possible to distinguish the value created through infrastructure modernization from the broader economic impact of simplifying the operating model. Although both institutions perform the same balance sheet activities across ALM, Regulatory Reporting, FTP and Financial Planning, they begin from different infrastructure landscapes, providing a clearer view of where the savings actually originate.
The financial analysis that follows shows how much of the cost of fragmentation remains after infrastructure has already been modernized, and why operating model consolidation continues to generate substantial long-term value.
Mirai ALM & Liquidity is designed around this principle: a single, cloud-native environment where ALM, FTP, and regulatory reporting share the same data and modeling foundation, removing the need to reconcile outputs across separate systems.
The two use cases are evaluated over a five-year period using a representative institution operating separate systems for ALM, Regulatory Reporting, FTP and Financial Planning. The fragmented environment incorporates the principal cost categories associated with infrastructure and licensing, together with the support resources and data management activities required to maintain multiple platforms. Regulatory adaptation and major version upgrades are also included where applicable.
Each scenario is then compared with the same functional landscape operating within a single integrated SaaS environment, allowing the economic impact of operating model consolidation to be evaluated across different technology starting points.
In the first scenario, four specialized on-premises systems are consolidated into a single integrated environment. The results are significant:
€21.54M reduction in five-year total cost of ownership
€16.22M Net Present Value (NPV)
229% ROI
Payback within the first year
The scale of the result reflects the full economic burden of the fragmented operating model. Infrastructure is an important component, particularly in systems with demanding availability and computational requirements, while a substantial part of the long-term cost also originates from maintaining several platforms and the operational structures surrounding them.
Support capacity and data management continue year after year, licensing costs accumulate across systems, and periodic upgrades introduce additional investment. The five-year view brings these costs together and makes visible an economic burden that is often distributed across different functions and budgets.
H3 - Use Case 2: Fragmented Cloud-Based Environment
The second scenario begins from a more modern infrastructure position, with the four specialized legacy systems already hosted in the cloud. The integrated operating model still generates:
€15.19M reduction in five-year total cost of ownership
€11.41M Net Present Value (NPV)
Payback within the first year
The difference in NPV between the two scenarios is €4.81M, representing the value created by eliminating on-premises infrastructure investment cycles through cloud migration.
That improvement is meaningful, while the comparison also reveals how much of the cost structure remains after infrastructure modernization. Support resources and data management activities continue to represent major cost drivers, alongside the software licensing required to maintain several specialized systems.
The two scenarios illustrate different layers of the same economic problem. Cloud migration addresses infrastructure expenditure, while operating model consolidation reaches the broader structure created around multiple systems and the operational effort required to keep them working together.
Much of the value comes from reduced duplication across technology and operations, and from freeing specialist capacity for higher-value work.
When ALM, FTP, and Regulatory Reporting operate within a more integrated environment, institutions can reduce duplication across technology and operational activities. A common data foundation lowers the need to maintain parallel information flows, while greater consistency across connected metrics reduces the effort required to preserve coherence between functions. Changes can also move through a more unified environment instead of being reproduced across multiple platforms.
Some of the most important benefits remain difficult to express through a traditional financial model:
Greater analytical capacity among specialized teams.
A closer connection between balance sheet metrics and management discussions.
More coherent governance across connected functions.
A stronger foundation for adapting to future requirements.
These outcomes matter because the economic value of integration continues beyond direct technology savings. A more coherent operating model changes the way information moves through the institution and allows specialist expertise to be used where it creates greater value.
The financial results are the measurable expression of that broader effect.
The two use cases reach the same conclusion from different starting points. Institutions operating traditional on-premises environments benefit from both infrastructure modernization and operating model simplification, while those that have already migrated legacy applications to the cloud continue to unlock significant value by consolidating fragmented systems and processes.
ALM, FTP and Regulatory Reporting already share many of the same data, assumptions and analytical foundations. An integrated operating environment allows the operating model to reflect those relationships more naturally, reducing duplication while creating a more consistent foundation for governance, analysis and future change.
This is the principle behind Mirai RiskTech: Balance Sheet Management & ALM Software for Banks. By unifying ALM, FTP, and regulatory reporting within a single AI-powered platform, Mirai enables institutions to simplify their operating model and devote more time to understanding the balance sheet rather than maintaining coherence across platforms.
Download the whitepaper: The Cost of Balance Sheet Management Fragmentation in Banking
What is Balance Sheet Management fragmentation?
It refers to ALM, FTP, Regulatory Reporting, and Financial Planning operating on separate systems, requiring institutions to manually maintain consistency across economically connected data, methodologies, and outputs.
Does cloud migration solve the cost of Balance Sheet Management fragmentation?
Partially. Cloud migration reduces infrastructure investment cycles, but support resources, data management, and licensing across multiple specialized systems continue to drive high costs even after migration.
What is the financial impact of consolidating ALM, FTP, and Regulatory Reporting?
A five-year Mirai analysis of a representative institution found a €21.54M TCO reduction and 229% ROI when consolidating four on-premises systems, and a €15.19M reduction when consolidating already cloud-based systems.
Why does fragmentation affect balance sheet governance, not just operations?
When management decisions rely on metrics from separate systems, additional validation is needed to reconcile differences, which can slow governance discussions and obscure whether variances reflect genuine economic differences or methodology gaps.
How does an integrated operating model change specialist team capacity?
It reduces time spent on reconciliation and platform maintenance, freeing ALM, regulatory, and finance specialists to focus on interpretation and decision support rather than data-coherence work.