Why Intraday Liquidity Should Not Be a Standalone System

When banks discuss intraday liquidity, the conversation often focuses on payment monitoring, account balances, regulatory reporting requirements and real-time dashboards. These capabilities are important, but they can create the impression that intraday liquidity is a separate treasury discipline rather than part of a broader liquidity framework.

The reality is that treasury teams are not managing one liquidity position for intraday purposes and another for liquidity risk, funding or forecasting. They are managing the same underlying liquidity position viewed through different lenses.

Intraday liquidity is not a separate type of liquidity. It is simply liquidity viewed through a different time horizon.

Treasury teams do not manage one liquidity position for intraday purposes and another for funding, forecasting, stress testing or Asset Liability Management (ALM). They manage the same balance sheet, the same cashflows and the same liquidity resources. The difference lies in the timeframe being analysed.

This distinction matters because many banks have historically approached intraday liquidity as a separate discipline, often driven by payment operations or regulatory reporting requirements. As a result, intraday liquidity monitoring has frequently evolved outside the core Treasury and ALM framework.

That approach becomes increasingly difficult to justify as payment flows move towards real-time settlement and supervisors place greater emphasis on intraday liquidity risk. A liquidity position at 11:00 a.m. is not disconnected from tomorrow’s funding requirements, next week’s cash flow forecasts or the bank’s overall liquidity risk profile. It is part of the same picture.

Consider a bank expecting a large incoming payment during the afternoon. If that payment is delayed, the immediate impact may be an intraday liquidity shortfall that requires Treasury action. However, the same event may also increase overnight funding requirements, reduce liquidity buffers and alter near-term liquidity forecasts. Treasury is not dealing with different liquidity risks. It is dealing with the same liquidity event viewed across different time horizons.

The challenge for banks, therefore, is not whether they can monitor liquidity within the day. The challenge is whether intraday liquidity is connected to the broader liquidity management framework.

The Visibility Trap

When banks evaluate intraday liquidity capabilities, the first requirement is often visibility.

Questions such as these are common:

  • Can we see our account balances in near real time?
  • Can we monitor payment flows as they occur?
  • Can we generate the required regulatory metrics?
  • Can we forecast, i.e. identify potential liquidity pressures before they become critical?

These are legitimate requirements. However, visibility alone is not liquidity management.

A dashboard showing current balances may answer what is happening now. Treasury also needs to understand what happens next.

How do today’s payment flows affect tomorrow’s funding needs? How does intraday liquidity usage compare with expected cash flows? What happens if a large incoming payment is delayed? How do intraday developments affect the bank’s wider liquidity position?

Without these connections, banks risk creating yet another source of liquidity information that operates independently from the rest of the treasury and risk management framework.

One Liquidity Position, Multiple Time Horizons

The same liquidity resources support operational payments, short-term liquidity management and longer-term balance sheet planning.

Consider a simple example.

During the morning, a bank experiences significantly higher payment outflows than expected. From an intraday perspective, this may appear to be an operational issue requiring immediate action.

However, the same development may also affect:

  • Funding requirements for the following business day
  • Liquidity buffer utilisation
  • Cash flow forecasts
  • Internal liquidity risk limits
  • Regulatory reporting metrics

The event itself has not changed. Only the time horizon through which it is being viewed has changed.

This is why intraday liquidity should not be treated as a separate discipline. It is simply part of a broader liquidity management continuum.

The Growing Impact of Instant Payments

Instant payments have made this connection even more important.

Historically, payment activity followed relatively predictable processing windows. Treasury teams had more time to assess positions, redistribute liquidity and respond to changing conditions.

Today, payment activity increasingly occurs in real time.

Funds can move immediately. Liquidity positions can change rapidly. Operational decisions that were previously made over hours may now need to be made within minutes.

This does not create a new type of liquidity risk. Rather, it increases the need for timely information and effective controls.

As a result, the quality of integration between payments, Treasury and liquidity risk management becomes increasingly important.

The Missing Link Between Intraday Liquidity and ALM

One of the most common organisational challenges is the separation between intraday liquidity management and Asset Liability Management.

In many institutions, these functions are supported by different systems, owned by different teams and operated through different processes.

From a liquidity risk perspective, however, the connection is obvious.

Intraday liquidity influences:

  • Liquidity buffers
  • Funding decisions
  • Short-term liquidity forecasts
  • Limit monitoring
  • Liquidity stress testing
  • Regulatory reporting

Each of these activities relies on the same underlying balance sheet and many of the same cash flow assumptions.

When these processes operate separately, institutions often face:

  • Duplicate data
  • Reconciliation challenges
  • Conflicting liquidity views
  • Increased operational complexity

The objective should be to establish a consistent view of liquidity across both operational and strategic time horizons.

A Unified Approach to Liquidity Management

At MORS, intraday liquidity is implemented as part of the Asset Liability Management environment rather than as a standalone application.

The solution supports operational intraday liquidity management, regulatory reporting and multi-day liquidity forecasting within the same framework.

Near-real-time updates of nostro accounts and payment activity provide treasury teams with timely visibility into evolving liquidity positions. Supported interfaces include SWIFT MT, SWIFT CAMT (ISO 20022), Open Banking and generic account interfaces.

The solution includes regulatory reporting metrics such as:

  • Daily maximum intraday liquidity usage
  • Available intraday liquidity at the start of the business day
  • Total payments processed

These metrics are generated from the same underlying data used for monitoring and management activities.

The framework also supports multi-day liquidity forecasting based on known committed flows, FX settlements and maturing instruments, helping treasury teams connect current positions with expected future liquidity requirements.

In addition, real-time limit monitoring can be configured at account, account group and currency level, providing a consistent control framework across daily liquidity operations.

From Monitoring to Management

The industry discussion around intraday liquidity often focuses on monitoring.

However, the next stage of maturity is management.

Monitoring tells a bank where liquidity stands right now.

Management provides the ability to:

  • Connect current positions to future cash flows
  • Understand developing risks
  • Apply liquidity limits consistently
  • Support operational and regulatory requirements from a common dataset
  • Link intraday developments to broader treasury decision-making

This requires more than a standalone monitoring solution. It requires a framework that treats liquidity consistently across different business horizons.

Conclusion

Intraday liquidity is often presented as a specialised liquidity discipline created by regulatory requirements or faster payment systems.

In reality, it is simply liquidity viewed through a shorter time horizon.

 Many banks are still working to improve access to timely intraday liquidity data. Yet even where visibility has been achieved, a separate monitoring solution is rarely enough. The greater challenge is connecting intraday developments with forecasting, stress testing, funding decisions, liquidity risk management and Asset Liability Management.

As instant payments volumes continue to grow, trading settlement windows continue to shrink  and supervisory expectations evolve, the case for treating intraday liquidity as a standalone process becomes increasingly difficult to justify.

The strongest liquidity frameworks are likely to be those that provide a single, consistent view across operational, tactical and strategic liquidity management, enabling treasury teams to make decisions based on one liquidity position rather than several.