Navigating ILAAP: The Next Chapter of Integrated Risk and Liquidity Reporting in Indonesian Banking

As the financial sector continues to mature under the guidance of OJK’s POJK 19/2024 and Bank Indonesia’s liquidity framework, banks in Indonesia are now preparing for a new layer of regulatory expectation: ILAAP (Internal Liquidity Adequacy Assessment Process).

ILAAP is not just another report.
It represents a holistic view of a bank’s liquidity governance, requiring alignment between risk management, finance, and treasury, all supported by data consistency and traceability across systems.

Why ILAAP Matters Now

Starting in 2025, OJK and Bank Indonesia are progressively socializing the requirement for banks to document, stress-test, and demonstrate liquidity adequacy under varying conditions.

This means banks must:

• Integrate liquidity data across multiple systems (core banking, treasury, ALM, risk).
• Provide quantitative and qualitative reports that are fully auditable.
• Demonstrate clear governance, controls, and scenario management.

For many banks, this is not merely a compliance challenge — it is a data and process orchestration challenge.

The Technology Gap: From Data to Governance

Based on our observations of current regulatory reporting practices (e.g., Apolo, SCV/LPS, KPMM, and RWA/ATMR), many banks still rely heavily on fragmented spreadsheets and manual consolidation between risk and finance units.

When ILAAP reporting is introduced, this manual approach will no longer scale.

Banks will require:

• A unified data model for liquidity and risk parameters.
• Workflow orchestration for review and approval cycles.
• Versioning and traceability for every stress-testing scenario.
• An audit and governance layer aligned with OJK standards.

Building the Bridge: Our Approach to ILAAP Readiness

While ILAAP is new within the Indonesian regulatory landscape, our experience in regulatory reporting automation (including Apolo, IFRS 9, and RWA) provides a strong foundation to extend our platform capabilities for ILAAP in the near future.

We are currently:

• Designing ILAAP data models aligned with OJK and Basel frameworks.
• Building integration connectors for liquidity, risk, and treasury data sources.
• Preparing modular reporting templates for both quantitative and qualitative disclosures.
• Enabling full traceability and scenario versioning through our NF10 architecture.

Our goal is to ensure that when ILAAP reporting becomes mandatory, banks can transition smoothly — supported by technology that is already trusted for existing OJK and BI reporting requirements.

Partnering with Banks for Co-Development

We believe the most effective regulatory solutions are built in close collaboration with practitioners.

That is why we are opening opportunities for early co-development with risk, finance, and IT teams from leading banks that are preparing their ILAAP roadmap.

Together, we can co-create:

• A compliant, flexible, and scalable ILAAP reporting solution.
• Seamless integration with existing Apolo, RWA, and liquidity systems.
• Configurable workflows and dashboards tailored to each bank’s governance model.

If your bank is exploring ILAAP implementation, we would be delighted to collaborate — ensuring compliance, transparency, and readiness from day one.