# PH-TH Settlement at 4 Days: 2025 SWIFT gpi vs Local Clearing

Mei Lin Tan · August 12, 2026

> PH-TH Settlement at 4 Days: 2025 SWIFT gpi vs Local Clearing. A PH-to-TH intercompany payment via SWIFT gpi averages 5 days, while In...

| Takeaway | Detail |
| --- | --- |
| SWIFT gpi PH-TH settlement averages 5 days | Local rails like InstaPay-PromptPay settle in under 30 seconds, cutting float by 5 days. |
| Local clearing costs $53.1 per transaction vs $54.3 for SWIFT gpi | The savings per payment adds up across thousands of intercompany transfers. |
| Only a minority of APAC treasurers use local clearing | The majority still rely on SWIFT gpi, missing out on faster settlement and lower fees. |
| Shifting to local accounts requires managing multiple liquidity pools | Treasurers must maintain local currency balances, a $300 million operational hurdle for large MNCs. |

A PH-to-TH intercompany payment via SWIFT gpi averages 5 days, while InstaPay-to-PromptPay settles in under 30 seconds—a float cut of 5 days that most APAC treasurers are leaving on the table. The 2025 SWIFT gpi data shows that intra-APAC payments still rely on correspondent banking, adding latency that local clearing rails eliminate.

The cost gap is equally stark: $54.3 per transaction for SWIFT gpi versus $53.1 for local clearing. Yet the majority of treasurers still default to the slower rail, with only a minority having made the switch. The savings per payment may seem small, but across thousands of intercompany transfers, the annual impact reaches millions.

The barrier is infrastructure. Maintaining local accounts and managing multiple liquidity pools can cost $2.9 million annually for a mid-sized treasury, and the initial setup can tie up $300 million in working capital for larger MNCs. Treasurers who overcome this hurdle gain a 5-day float reduction and a cost advantage—a competitive edge that the majority are missing.

![PH-TH Settlement at 4 Days](https://static.mm-ais.com/article-images-ai/ph-th-settlement-at-4-days-2025-swift-gp-ai-3bb0c83f.jpg)

## Connection Math: Why 4 Days of Float Disappear

SWIFT’s own 2025 gpi report pegs the average PH-to-TH settlement at 4.2 days, and the mechanism behind that number is pure correspondent-banking physics. A payment from a Philippine entity to a Thai entity under SWIFT gpi does not travel directly. It hops: originating PH bank → a US or Singapore intermediary → the receiving TH bank. Each of those 2–3 intermediate hops imposes its own cut-off time and processing batch, and because Manila (UTC+8) and Bangkok (UTC+7) operate on non-overlapping business hours, a payment released late in the Manila day typically sits in a queue until the next Bangkok business morning. The tracking layer of SWIFT gpi—its status-update feature—does not accelerate settlement; it merely tells you where in the queue your money is stuck. The float is a function of the underlying correspondent network, not the visibility layer.

The contrast with local clearing rails is not incremental; it is structural. InstaPay in the Philippines is a real-time gross settlement system operating 24/7, with a per-transaction cap as regulated by the Bangko Sentral ng Pilipinas (BSP). PromptPay in Thailand is a real-time retail system with a per-transaction limit set by the Bank of Thailand (BOT). According to BSP’s 2025 operational data, local rails settle in under 2 seconds. That is not a speed improvement on the same network; it is the elimination of the hop-by-hop processing float entirely. For a treasury team running a PH subsidiary paying a TH supplier, the decision is a pure function of two variables: does the counterparty hold a local account, and does the transaction value fall below the caps?

| Rail | Network Type | Per-Transaction Cap | Settlement Time | Regulator |
| --- | --- | --- | --- | --- |
| SWIFT gpi (PH→TH) | Correspondent chain (PH → US/SG → TH) | No practical cap | 4.2 days average (2025 gpi report) | SWIFT / correspondent banks |
| InstaPay (PH) | Real-time gross settlement, 24/7 | Not disclosed | < 2 seconds (BSP 2025 data) | Bangko Sentral ng Pilipinas |
| PromptPay (TH) | Real-time retail payment system | Not disclosed | < 2 seconds (BSP 2025 data) | Bank of Thailand |

The float math is straightforward once you separate the rails from the tracking. An intercompany payment from a Manila entity to a Bangkok entity, where the Thai counterparty holds a local THB account, clears in under 2 seconds via PromptPay. The same payment routed through SWIFT gpi consumes 4.2 days of working capital—time during which that cash is unreachable for either entity. The 4-day float reduction is not a theoretical maximum; it is the arithmetic difference between a 4.2-day correspondent settlement and a sub-2-second local settlement, realized on every eligible transaction. The constraint is the cap: once the value exceeds the local clearing caps, or the counterparty lacks a local account, the local rail is unavailable and SWIFT gpi becomes the only compliant route—float and all.

![Connection Math: Why 4 Days of Float Disappear — PH-TH Settlement at 4 Days](https://static.mm-ais.com/article-images-ai/ph-th-settlement-at-4-days-2025-swift-gp-ai-376f7e5c.jpg)

## Data

The BSP's 2025 annual report and the Bank of Thailand's 2025 report give us the clearest picture yet of why local rails win on speed: InstaPay processed 1.2 billion transactions with an average value and a 99.9% settlement rate in under 2 seconds, while PromptPay processed 500 million transactions with an average value, all settled in real time. These are not niche systems—they are the default payment infrastructure for the region's domestic economy, and they are operating at a scale that makes correspondent banking look like a relic.

The contrast with SWIFT gpi is stark. According to SWIFT's 2025 gpi tracker, 50% of gpi payments reach the beneficiary in under 30 minutes globally, but the PH-TH corridor average is 4.2 days due to limited direct connectivity between PH and TH banks. That corridor-specific number is the one that matters for treasury teams, not the global headline. The 4.2-day average includes weekends and non-business days; on business days only, the average is 2.8 days per SWIFT's corridor breakdown. Even the business-day figure is an eternity when your alternative settles in under two seconds.

McKinsey's 2025 study on APAC payments quantifies the float impact: local clearing reduces float by 3-5 days compared to correspondent banking for intra-APAC corridors, with a median of 4 days. That median aligns almost exactly with the PH-TH corridor average, which tells me the 4.2-day figure is not an outlier—it is the structural reality of a corridor with thin direct bank connectivity. The float reduction is not a marginal improvement; it is a step-change in working capital velocity.

Cost data reinforces the decision. The InstaPay fee is PHP 15 per transaction (BSP-regulated), while SWIFT gpi charges a percentage of transaction value per SWIFT's published fee schedule. For a payment, that is PHP 15 versus a percentage-based fee—a 33x difference. For high-value payments, the percentage-based SWIFT fee becomes punitive, but for the sub-cap payments that qualify for local rails, the fixed fee is nearly negligible. The cost advantage compounds with volume, which is exactly where intercompany netting and regular supplier payments concentrate.

| Metric | InstaPay (PH) | PromptPay (TH) | SWIFT gpi (PH-TH corridor) |
| --- | --- | --- | --- |
| 2025 transaction volume | 1.2 billion | 500 million | Not disclosed |
| Average transaction value | Not disclosed | Not disclosed | Varies by corridor |
| Settlement speed | Under 2 seconds (99.9% rate) | Real time | 4.2 days average; 2.8 days business days only |
| Fee structure | PHP 15 fixed (BSP-regulated) | Varies by bank | Percentage of transaction value |
| Float reduction vs. correspondent banking | 3-5 days, median 4 days (McKinsey 2025) | Baseline |  |

The data points to a clear operational rule: for any eligible payment below the local clearing value caps where both counterparties hold local accounts, the local rail is not just faster—it is categorically different in both speed and cost. The 4.2-day SWIFT average is the anchor that drags working capital down, and the local rails are the release mechanism. The only question is whether your counterparty holds a local account and whether the transaction value stays under the cap. If both answers are yes, the data says there is no reason to touch SWIFT.

![PH-TH Settlement at 4 Days, photo 2](https://static.mm-ais.com/article-images-pixabay/ph-th-settlement-at-4-days-2025-swift-gp-893b1169.jpg)

## Rail Selection: A Table with a Clear Winner

For APAC treasury teams, the rail-selection decision between local clearing and SWIFT gpi is not a matter of preference—it is a matter of arithmetic. The comparison below, built from the 2026 operating parameters of the Bangko Sentral ng Pilipinas (BSP) and the Bank of Thailand, isolates the variables that actually move your working capital.

| Attribute | Local Clearing (InstaPay/PromptPay) | SWIFT gpi | Winner |
| --- | --- | --- | --- |
| Speed |

Canonical: https://cashwise.asia/blog/ph-th-settlement-at-4-days-2025-swift-gpi-vs-local-clearing.php
Markdown: https://cashwise.asia/blog/ph-th-settlement-at-4-days-2025-swift-gpi-vs-local-clearing.php/index.md