Liquidity risk has evolved from a technical consideration within risk teams into a central regulatory and strategic priority. Under AIFMD II, it is no longer sufficient to monitor liquidity periodically. Firms are now expected to manage it continuously, systematically, and in a fully demonstrable manner.

However, it is critical to understand what AIFMD II is not. It is not a new tool that can be layered on top of existing systems. It is not a standalone risk engine, nor a compliance add-on designed to support the current operating model.

Instead, AIFMD II requires something far more fundamental: the core back-office infrastructure itself must become capable of supporting liquidity management tools (LMTs) and the decisions surrounding them.
This is not another regulatory project running alongside others. It is a structural shift that begins at the very heart of the back office. Liquidity management under AIFMD II is not simply a risk management function, it is an operational capability that must be embedded directly into core processes, data flows, and system architecture.

Let’ explores what has changed under AIFMD II, why existing approaches to liquidity management are no longer sufficient, and what fund managers must do to adapt their operating models accordingly.

Liquidity: From Structural Challenge to Daily Priority

Liquidity management has always required balancing two inherently conflicting dynamics: illiquid or long-term assets on one side, and investor redemption expectations on the other.

What has changed is the context in which this balance must be maintained. Increased market volatility, shifting interest rate environments, and evolving investor behavior have made liquidity stress more frequent and more complex. At the same time, the continued growth of the alternative investment sector has increased its systemic importance.

As a result, liquidity risk is a continuous operational concern with direct implications for financial stability and investor protection

The Operational Reality: Fragmentation and Delay

Despite its growing importance, liquidity management in many organisations remains operationally fragmented.

Common challenges include:

• reliance on manual, spreadsheet-based processes
• delayed insights driven by batch or end-of-day data
• disconnected systems across risk, portfolio management, and compliance

Although stress testing has been a regulatory requirement, it is often conducted periodically and remains insufficiently integrated into decision-making processes.
This creates a structural disconnect: risks may be identified, but responses are neither timely nor consistently executed.

The implications are significant:

• Inefficient decision-making, particularly under stressed conditions
• Increased exposure to liquidity events, with potential investor impact
• Rising compliance pressure, driven by limited auditability and reactive reporting

At its core, this is not a question of expertise. It is a limitation of system design.

The Limitations of AIFMD I

AIFMD I established the foundation for liquidity risk management, requiring firms to monitor liquidity, align it with investment strategies, and conduct stress testing.

However, it provided limited guidance on how these requirements should be operationalised. The absence of standardised tools, frameworks, and processes resulted in inconsistent implementations across the industry.

Liquidity management remained largely interpretative and, in many cases, reactive.

AIFMD II: From Principle to Prescription

AIFMD II represents a clear shift from principles-based oversight to a more prescriptive and harmonised framework.

The focus moves from ensuring liquidity is managed to demonstrating that it is managed through defined tools, governance, and processes.

Harmonised Liquidity Management Tools

For the first time, the directive introduces a standardised set of Liquidity Management Tools (LMTs), including mechanisms such as redemption gates, swing pricing, and side pockets.
For open-ended funds, the use of LMTs is mandatory, with at least two tools required. This introduces a new level of operational complexity, as these tools must be fully integrated into systems and workflows.

Enhanced Governance and Accountability

Liquidity management must now be supported by:

• Clearly defined policies
• Documented activation and calibration rules
• Robust governance frameworks

Decisions must be explainable, consistently applied, and fully auditable.

Stress Testing as a Decision Tool

Stress testing is no longer a standalone exercise. It must be forward-looking, structured, and directly linked to operational actions.
Firms are expected to demonstrate how stress scenarios inform decisions, particularly regarding the activation of LMTs.

Continuous Alignment Requirements

AIFMD II reinforces the need for ongoing alignment between:

• Investment strategies
• Asset liquidity profiles
• Investor redemption terms

This alignment must be monitored continuously, rather than assessed periodically.

A Shift to Continuous, System-Driven Liquidity Management

The practical implication of AIFMD II is clear: liquidity management becomes a daily operational capability rather than a periodic reporting exercise.

Firms must be able to:

• Monitor liquidity conditions in near real time
• Maintain operational readiness of liquidity tools
• Make data-driven, defensible decisions under varying market conditions

This introduces new complexity, particularly for organisations managing multiple funds with differing liquidity profiles and tool configurations.

Without integrated systems, this complexity is difficult to manage at scale.

Implications for Operating Models

To meet these requirements, firms must evolve across three dimensions:

Systems

Infrastructure must support:

• Real-time data integration
• Scenario-based stress testing
• LMT simulation and execution
• Consistent regulatory reporting

Processes

Operational processes must transition from:

• Periodic to continuous
• Reactive to predictive
• Manual to automated

Organisational Alignment

Liquidity management now requires close coordination across risk, portfolio management, and compliance functions, reflecting its expanded role within the organisation.

Towards a More Integrated Approach

AIFMD II necessitates a fundamental shift in how liquidity is managed.
Rather than treating it as a reporting function, firms must establish liquidity as an integrated, system-wide capability. This requires:

• Centralised and consistent data across funds
• Automated monitoring and alerting mechanisms
• Embedded compliance within operational workflows
• Forward-looking, scenario-based analysis

Such an approach enables not only regulatory compliance but also more informed and timely decision-making.

Strategic Implications

For decision makers, liquidity management is no longer only a purely operational concern, but it has become a strategic priority.

At the same time, technology has transitioned from a supporting function to a critical enabler. Without appropriate infrastructure, firms will struggle to meet regulatory expectations or manage the associated complexity.

Conclusion

AIFMD II is not simply a regulatory update—it is a structural shift that requires liquidity management to be embedded at the core of the back office.

It cannot be addressed through standalone tools or incremental changes. The directive demands integrated systems, continuous oversight, and operationally embedded decision-making.

For many firms, this exposes a clear gap between regulatory expectations and existing infrastructure.Addressing it requires rethinking liquidity not as a function, but as a core operational capability. Firms that do so will be better positioned to meet regulatory demands and operate with greater resilience in an increasingly complex environment.

Is your infrastructure ready for the new reality of mandatory LMTs and continuous liquidity oversight?

Our latest whitepaper provides an actionable roadmap for fund managers to bridge the gap between regulatory pressure and operational resilience under AIFMD II.

Read the whitepaper here.