The Strategic Treasury Function: Trends Shaping APAC in 2025-26

The treasury function is at an inflection point. What was once an operational back-office function is rapidly becoming a strategic nerve centre, enabled by automation, real-time data, and modern platform architecture.

What Has Changed for APAC Treasury in 2026?

Three developments have carried the 2025 agenda forward. First, the ISO 20022 migration reached its decisive milestone: SWIFT retired the legacy MT format for cross-border payment instructions in November 2025, making rich, structured payment data the default for correspondent flows. Treasuries that completed the migration are already using the enhanced remittance data to automate reconciliation that previously required manual matching, while those that leaned on translation services are managing degraded data quality in both directions.

Second, supervisors have begun testing how the frameworks operate in practice. APRA's operational risk standard CPS 230 came into force on 1 July 2025 and its first full supervisory cycle runs through 2026 — treasury platforms, bank connectivity, and the service providers behind them now sit inside the "critical operations" perimeter, with tolerance settings and mapped dependencies expected on request. MAS and HKMA continue to sharpen intraday liquidity expectations along the same lines.

Third, AI-assisted cash forecasting has reached production in the region's larger corporate treasuries. The pattern that works pairs machine-learning forecast models with the connected data foundations described below — institutions that skipped the data-plumbing stage are finding that model quality cannot compensate for stale or fragmented position data.

Why Is Treasury Shifting From Operational to Strategic?

Industry surveys consistently show that finance professionals expect treasury to take on a more strategic mandate. This shift is being enabled by the automation of routine operational tasks, freeing treasury teams to focus on capital optimisation, risk strategy, and business partnering.

The 80% of finance professionals who anticipate greater treasury strategic influence are not simply being optimistic. They are responding to structural change driven by technology. (Source: AFP Treasury in Practice Survey, 2024)

For APAC institutions, this transition is occurring in the context of a uniquely complex monetary and regulatory environment. The treasury function that can model multiple scenarios simultaneously, execute hedging strategies dynamically, and provide real-time liquidity insight to the business has a demonstrable competitive advantage over one still constrained by manual processes and end-of-day reporting.

What Regulatory Drivers Are Shaping APAC Treasury?

The regulatory environment for treasury operations across APAC has become significantly more demanding:

Australia - APRA CPS 190 (Recovery and Resolution Planning): requires banks to maintain detailed treasury contingency planning and liquidity buffers - APRA APS 210 (Liquidity): tightened liquidity coverage ratio and net stable funding ratio requirements following global banking stress events in 2023 - ASIC requirements for robust treasury governance in corporate treasury operations

Singapore - MAS Notice 649 (Liquidity Coverage Ratio) and MAS Notice 651 (Net Stable Funding Ratio): continuous monitoring requirements that demand real-time liquidity positions - MAS Technology Risk Management (TRM) Guidelines 2021: operational resilience requirements for treasury platforms, including recovery time objectives for critical treasury systems

Hong Kong - HKMA Supervisory Policy Manual LM-2: liquidity monitoring standards that require continuous intraday liquidity reporting for larger institutions

These regulatory requirements are the primary driver of treasury platform investment across the region. Institutions that cannot generate compliant, real-time liquidity positions are carrying regulatory risk that will only increase as supervisory focus intensifies.

What Does Real-Time Treasury Look Like in Practice?

The concept of real-time treasury, characterised by 24/7 cash movements, instant liquidity visibility, and automated execution, is moving from aspiration to operational reality in leading APAC institutions.

Key enablers include: - ISO 20022 adoption: Richer payment data enabling smarter cash management - API connectivity: Real-time bank connectivity replacing batch file processing - Cloud platforms: Scalable architecture supporting always-on operations

The shift to real-time is not simply a technology choice. It represents a fundamental change in how treasury manages intraday liquidity risk. In a T+0 environment, the treasury team needs continuous visibility into positions across currencies and entities, something that overnight batch processes fundamentally cannot provide.

Early adopters of real-time treasury in APAC are reporting material reductions in trapped liquidity, with some institutions reporting 15-25% improvements in working capital efficiency following real-time treasury implementation.

How Does Monetary Policy Complexity Affect APAC Treasury?

APAC treasury teams are navigating an unusually complex monetary policy environment, with divergent central bank trajectories across the region. This places a premium on sophisticated scenario modelling and dynamic hedging capabilities.

In 2024-2025, APAC treasury teams have faced: - The Reserve Bank of Australia's rate normalisation cycle and subsequent easing path - The Bank of Japan's historic shift away from yield curve control, with significant implications for cross-currency swap markets - The MAS's continued use of exchange rate management (rather than interest rates) as its primary monetary policy tool, requiring Singapore-based treasuries to model FX impacts differently from rate-focused peers - RBI's balancing act between supporting growth and managing inflation in India

No two APAC treasury functions face the same risk profile. Platform capabilities that allow scenario-specific modelling, rather than generic "rate up/rate down" frameworks, are increasingly the differentiator between institutions that manage this complexity proactively and those reacting after the fact.

What Technology Stack Does a Modern APAC Treasury Need?

The modern APAC treasury function typically requires the following platform capabilities:

• Multi-currency cash management: Consolidated global cash position across all operating currencies
• Real-time bank connectivity (SWIFT, API): Intraday liquidity management without manual reconciliation
• Financial instrument coverage (FX, IRD, bonds): Full mark-to-market visibility for hedging and investment portfolios
• Regulatory reporting automation: Continuous LCR/NSFR computation and reporting
• Scenario modelling: Stress testing and policy scenario analysis

What Is the AST360 Opportunity for Treasury Teams?

ACS's AST360 platform was designed specifically for this environment, combining real-time liquidity management, multi-currency financial instruments, and trade lifecycle management in a modular, cloud-ready architecture.

AST360 addresses the core requirements of modern APAC treasury operations: full multi-currency capability, API-first bank connectivity, comprehensive financial instrument coverage, and a regulatory reporting layer designed for the specific requirements of APRA, MAS, and HKMA frameworks. The modular design allows institutions to deploy the capabilities most critical to their immediate needs and scale over time.

What Is a Modular Treasury Management System and Why Does It Matter for APAC?

A modular treasury management system is one where individual capabilities (liquidity management, financial instruments, trade lifecycle, regulatory reporting) are deployed independently and integrated through standardised interfaces. This architectural approach contrasts with monolithic enterprise treasury platforms that require all-or-nothing implementations and impose long, expensive go-live timelines.

For APAC institutions, modularity matters for three specific reasons:

1. Phased deployment matches phased business need. Most APAC treasury transformations have an immediate regulatory driver (LCR/NSFR compliance, MAS Notice 649, APRA APS 210) alongside longer-term strategic ambitions (real-time treasury, intraday liquidity optimisation). Modular platforms allow institutions to deploy compliance capability first, validate the value, and add strategic modules as priorities firm up, rather than committing to a 12-18 month enterprise implementation before seeing any benefit.

2. APAC currency and regulatory diversity demands flexibility. A treasury platform serving operations across Australia, Singapore, the Philippines, India, and Thailand needs to handle distinct regulatory regimes, payment infrastructures, and currency conventions. Modular systems with configurable rule engines accommodate this diversity without expensive customisation. Monolithic platforms designed for single-jurisdiction use require costly retrofitting.

3. Cost scales with usage, not licence size. Traditional enterprise TMS pricing reflects the full platform footprint regardless of which modules are actually used. Modular pricing, common in cloud-native platforms, lets institutions pay only for the capability they deploy, with predictable scaling as usage grows.

ACS's AST360 modular treasury management system was designed on this principle from inception, with liquidity management, financial instruments, and trade lifecycle deployable as independent modules across cloud-ready infrastructure. Combined with API-first integration to existing core banking systems, this architecture lets APAC institutions stage their treasury transformation in line with their regulatory calendar and budget cycle, rather than reshape both around a vendor's implementation timeline.

What Should Your Organisation Do About Treasury Modernisation?

The strategic treasury function is not a future destination, it is available today, to organisations willing to invest in the platform capabilities that enable it. The institutions that will lead their markets in the next five years are building those capabilities now.

For corporate treasuries, the priority is typically moving from spreadsheet-based cash management to a platform that provides consolidated, real-time positions and automates the routine tasks that currently consume the treasury team's time. For banking treasuries, the priority is usually regulatory compliance first, ensuring LCR, NSFR, and intraday liquidity reporting is automated and audit-ready, before addressing strategic capability gaps.

The key questions to assess your readiness: - Can your treasury system generate a real-time, consolidated cash position across all entities and currencies? - How long does it take your team to produce the LCR and NSFR reports required by your regulator? - Do you have dynamic scenario modelling capability, or do you rely on spreadsheet-based analysis for strategy decisions? - What is the cost (in headcount and error rate) of your current manual treasury processes? - Is your treasury platform cloud-ready, with API-first connectivity to your banking partners?

If the answer to any of these questions reveals a significant gap, the case for treasury transformation is already present, it simply needs to be quantified. ACS's treasury advisory team has guided institutions across Australia, Singapore, Hong Kong, and India through this analysis. Contact us to begin that conversation. For related reading, see our analysis of APAC lending transformation and explore our AST360 platform.

What Are the Typical Stages of a Treasury Transformation Journey?

Based on ACS engagements across the APAC region, treasury transformation typically progresses through recognisable stages:

Stage 1: Compliance Baseline: The immediate priority for most institutions is ensuring the treasury platform can generate the LCR, NSFR, and intraday liquidity reports required by the relevant regulator. This stage is non-negotiable and should anchor the transformation roadmap.

Stage 2: Operational Automation: Once compliance reporting is automated, the next priority is eliminating manual processes in core treasury operations, cash positioning, bank reconciliation, deal confirmation, and settlement. Each of these processes, when manual, creates both operational risk and a direct cost that can be quantified and eliminated through automation.

Stage 3: Real-Time Capability: With compliance and automation foundations in place, the institution can begin building real-time treasury capability, intraday liquidity management, API-based bank connectivity, and real-time FX exposure tracking. This stage typically requires platform upgrade or replacement if the existing system does not support API connectivity.

Stage 4: Strategic Treasury: The final stage is the genuine strategic function, scenario modelling, capital optimisation, and business partnering at board level. This is only achievable when treasury teams are freed from the manual and compliance workload that consumes most of their time in Stages 1-2.

How Do Leading Firms Achieve End-to-End Treasury Automation?

End-to-end treasury automation is rarely the product of a single platform replacement. Across the APAC engagements ACS has supported, leading institutions consistently reach automation maturity through five layered capabilities, each addressing a specific manual touchpoint in the treasury process chain.

1. Multi-bank cash visibility through standardised connectivity. Treasury operations stuck in spreadsheet-based reconciliation are typically constrained by inconsistent bank data formats. Modern treasury platforms consolidate bank statements from SWIFT MT940/MT942, host-to-host feeds, and increasingly bank API channels into a single normalised position view. ISO 20022 migration is accelerating this capability, institutions on richer XML formats are recovering hours per day previously spent on manual reconciliation between bank portals.

2. Automated cash forecasting driven by ERP and AR/AP integration. Manual rolling forecasts built in Excel produce stale, error-prone numbers within 24 hours. Connected forecasting integrates accounts receivable, accounts payable, and ERP scheduled cash flows directly into the treasury platform, refreshing positions continuously. Leading APAC corporate treasuries are building 13-week, multi-entity forecasts that update automatically as underlying business data changes.

3. Straight-through deal capture and confirmation. Automated trade confirmation through SWIFT MT3xx, eConfirms, or modern matching platforms eliminates the manual reconciliation between trade execution and settlement. Combined with automated regulatory reporting (EMIR, MAS reporting, ASIC trade reporting), this removes the operational risk that comes with manual settlement breaks.

4. Real-time intraday liquidity management. API-based bank connectivity enables intraday position monitoring and automated sweep execution, letting treasury teams deploy trapped cash within the operating day rather than reconciling positions overnight. For institutions operating across multiple APAC currencies and entities, the working capital uplift from intraday optimisation typically exceeds the platform investment within 18-24 months.

5. Continuous regulatory reporting. Automated LCR, NSFR, and intraday liquidity reporting against APRA, MAS, and HKMA frameworks transforms compliance from a recurring manual burden into a by-product of normal treasury operations. Reports that previously consumed days of effort each month-end are generated continuously and audit-ready.

The institutions that achieve genuine end-to-end automation typically treat these five capabilities as an integrated stack rather than discrete projects, sequencing implementation according to regulatory urgency, immediate operational pain, and the compounding ROI from each layer.

How Do You Build the Business Case?

The ROI case for treasury transformation is typically anchored in three measurable value drivers:

Direct cost reduction: Manual treasury processes typically consume significant FTE headcount. Automation of cash positioning, bank reconciliation, and regulatory reporting can reduce this headcount requirement by 40-60%, depending on the complexity of the current state.

Working capital efficiency: Real-time liquidity visibility enables institutions to deploy trapped cash more effectively. Institutions that have implemented real-time treasury report 15-25% improvements in working capital efficiency, a benefit that compounds over time as the treasury team develops greater confidence in intraday position data and begins actively optimising cash deployment across entities, currencies, and time zones.

Regulatory risk mitigation: The cost of a regulatory breach or supervisory action related to inadequate liquidity reporting far exceeds the cost of the platform investment required to prevent it. For APAC institutions, where supervisory expectations around liquidity management are tightening across all major jurisdictions, this risk quantification is increasingly important in building board-level support for treasury transformation programmes. A single supervisory requirement to remediate liquidity reporting deficiencies can consume more resources than a proactive platform investment would have required.

How Do You Choose Treasury Management Software for APAC?

Selecting treasury management software for APAC operations involves trade-offs that look different from the Western European or North American market. ACS has supported treasury platform selection across institutions in Australia, Singapore, the Philippines, and India, and the criteria that matter most consistently fall into five categories.

1. APAC regulatory coverage out of the box. The platform should support APRA, MAS, HKMA, RBI, and BSP regulatory reporting frameworks without requiring custom development. Verify that LCR, NSFR, and intraday liquidity report templates exist for your specific jurisdiction. Globally-marketed TMS platforms often advertise APAC support but require expensive localisation projects to meet specific regulatory expectations.

2. Multi-currency and cross-entity capability. APAC operations typically involve multiple operating currencies (AUD, SGD, PHP, INR, THB, JPY, HKD) and multi-entity structures with intercompany funding flows. The platform should handle multi-currency consolidation, FX translation, and intercompany netting natively, not as a regional add-on.

3. Bank connectivity depth. Treasury platforms vary widely in their pre-built bank connectivity for APAC institutions. Tier 1 banks across the region (NAB, ANZ, DBS, OCBC, Standard Chartered, Maybank, BPI) have varying levels of API maturity and SWIFT capability. Verify that the platform connects directly to your specific bank panel without manual file processing as the primary integration path.

4. Cloud and data residency posture. APAC data residency requirements are tightening. MAS Outsourcing Guidelines, APRA CPS 234, and HKMA cloud risk requirements all impose specific controls on financial services data storage. The platform should support deployment in the data residency jurisdictions your regulators require, typically AWS, Azure, or Google Cloud regions in Sydney, Singapore, or Mumbai.

5. Total cost of ownership over 5 years, not licence cost. Treasury platform decisions are often driven by initial licence cost, but the dominant TCO drivers over five years are implementation cost, ongoing customisation, and platform support overhead. Modular, cloud-native platforms typically deliver lower 5-year TCO than enterprise alternatives, but only when sized appropriately for the institution's actual usage.

ACS's tailored treasury solutions practice combines AST360 as a modular platform option with independent advisory on alternative platforms, including Murex, Calypso, Kyriba, and ION, for institutions whose requirements suggest a different fit. The starting point for any treasury platform decision should be a structured business requirements analysis, not a vendor demo. Speak with our treasury advisory team for an independent assessment of your platform options.

References

• Association for Financial Professionals, [AFP Treasury in Practice Survey 2024](https://www.afponline.org/publications-data-tools/reports/survey-research-economic-data/details/treasury-in-practice)
• Australian Prudential Regulation Authority, [APS 210 Liquidity](https://www.apra.gov.au/sites/default/files/2023-11/Prudential_Standard_APS_210_Liquidity_0.pdf)
• Monetary Authority of Singapore, [Notice 649 Liquidity Coverage Ratio](https://www.mas.gov.sg/regulation/notices/notice-649)
• Hong Kong Monetary Authority, [Supervisory Policy Manual LM-2](https://www.hkma.gov.hk/media/eng/doc/key-functions/banking-stability/supervisory-policy-manual/LM-2.pdf)