{"id":739,"date":"2026-02-05T04:50:31","date_gmt":"2026-02-05T04:50:31","guid":{"rendered":"https:\/\/nawadata.com\/blog\/?p=739"},"modified":"2026-02-05T04:50:31","modified_gmt":"2026-02-05T04:50:31","slug":"navigating-ilaap-the-next-chapter-of-integrated-risk-and-liquidity-reporting-in-indonesian-banking","status":"publish","type":"post","link":"https:\/\/nawadata.com\/blog\/navigating-ilaap-the-next-chapter-of-integrated-risk-and-liquidity-reporting-in-indonesian-banking\/","title":{"rendered":"Navigating ILAAP: The Next Chapter of Integrated Risk and Liquidity Reporting in Indonesian Banking"},"content":{"rendered":"\n<p>As the financial sector continues to mature under the guidance of <strong>OJK\u2019s POJK 19\/2024<\/strong> and <strong>Bank Indonesia\u2019s liquidity framework<\/strong>, banks in Indonesia are now preparing for a new layer of regulatory expectation: <strong>ILAAP (Internal Liquidity Adequacy Assessment Process)<\/strong>.<\/p>\n\n\n\n<p>ILAAP is not just another report.<br>It represents a holistic view of a bank\u2019s liquidity governance, requiring alignment between <strong>risk management, finance, and treasury<\/strong>, all supported by <strong>data consistency and traceability across systems<\/strong>.<\/p>\n\n\n\n<p><strong>Why ILAAP Matters Now<\/strong><\/p>\n\n\n\n<p>Starting in <strong>2025<\/strong>, OJK and Bank Indonesia are progressively socializing the requirement for banks to document, stress-test, and demonstrate liquidity adequacy under varying conditions.<\/p>\n\n\n\n<p>This means banks must:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Integrate liquidity data across multiple systems (core banking, treasury, ALM, risk).<\/li>\n\n\n\n<li>Provide quantitative and qualitative reports that are fully auditable.<\/li>\n\n\n\n<li>Demonstrate clear governance, controls, and scenario management.<\/li>\n<\/ul>\n\n\n\n<p>For many banks, this is not merely a compliance challenge \u2014 it is a <strong>data and process orchestration challenge<\/strong>.<\/p>\n\n\n\n<p><strong>The Technology Gap: From Data to Governance<\/strong><\/p>\n\n\n\n<p>Based on our observations of current regulatory reporting practices (e.g., <strong>Apolo, SCV\/LPS, KPMM, and RWA\/ATMR<\/strong>), many banks still rely heavily on fragmented spreadsheets and manual consolidation between risk and finance units.<\/p>\n\n\n\n<p>When ILAAP reporting is introduced, this manual approach will no longer scale.<\/p>\n\n\n\n<p>Banks will require:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A unified data model for liquidity and risk parameters.<\/li>\n\n\n\n<li>Workflow orchestration for review and approval cycles.<\/li>\n\n\n\n<li>Versioning and traceability for every stress-testing scenario.<\/li>\n\n\n\n<li>An audit and governance layer aligned with OJK standards.<\/li>\n<\/ul>\n\n\n\n<p><strong>Building the Bridge: Our Approach to ILAAP Readiness<\/strong><\/p>\n\n\n\n<p>While ILAAP is new within the Indonesian regulatory landscape, our experience in <strong>regulatory reporting automation<\/strong> (including <strong>Apolo, IFRS 9, and RWA<\/strong>) provides a strong foundation to extend our platform capabilities for ILAAP in the near future.<\/p>\n\n\n\n<p>We are currently:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Designing ILAAP data models aligned with OJK and Basel frameworks.<\/li>\n\n\n\n<li>Building integration connectors for liquidity, risk, and treasury data sources.<\/li>\n\n\n\n<li>Preparing modular reporting templates for both quantitative and qualitative disclosures.<\/li>\n\n\n\n<li>Enabling full traceability and scenario versioning through our <strong>NF10 architecture<\/strong>.<\/li>\n<\/ul>\n\n\n\n<p>Our goal is to ensure that when ILAAP reporting becomes mandatory, banks can transition smoothly \u2014 supported by technology that is already trusted for existing OJK and BI reporting requirements.<\/p>\n\n\n\n<p><strong>Partnering with Banks for Co-Development<\/strong><\/p>\n\n\n\n<p>We believe the most effective regulatory solutions are built in close collaboration with practitioners.<\/p>\n\n\n\n<p>That is why we are opening opportunities for early co-development with <strong>risk, finance, and IT teams<\/strong> from leading banks that are preparing their ILAAP roadmap.<\/p>\n\n\n\n<p>Together, we can co-create:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A compliant, flexible, and scalable ILAAP reporting solution.<\/li>\n\n\n\n<li>Seamless integration with existing Apolo, RWA, and liquidity systems.<\/li>\n\n\n\n<li>Configurable workflows and dashboards tailored to each bank\u2019s governance model.<\/li>\n<\/ul>\n\n\n\n<p>If your bank is exploring ILAAP implementation, we would be delighted to collaborate \u2014 ensuring compliance, transparency, and readiness from day one.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As the financial sector continues to mature under the guidance of OJK\u2019s POJK 19\/2024 and Bank Indonesia\u2019s 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\u2019s liquidity governance, requiring alignment [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":740,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/posts\/739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/comments?post=739"}],"version-history":[{"count":1,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/posts\/739\/revisions"}],"predecessor-version":[{"id":741,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/posts\/739\/revisions\/741"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/media\/740"}],"wp:attachment":[{"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/media?parent=739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/categories?post=739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nawadata.com\/blog\/wp-json\/wp\/v2\/tags?post=739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}