Singapore sits at the intersection of seven major bilateral trade relationships, yet the mechanics of B2B money movement across those relationships remain poorly understood — even by treasury teams that execute APAC payments every week. SWIFT MT103 messages arrive at correspondent banks in Manila or Jakarta, get hit with intermediary fees somewhere in the chain, and settle two to four days later at a rate nobody quoted upfront. The problem is not that cross-border infrastructure does not exist. It is that most businesses are still using 1990s correspondent banking architecture to move money across corridors that have built entirely new rails over the last decade.
This guide covers the five corridors that matter most to Singapore-based B2B businesses — SGD to PHP, SGD to INR, SGD to MYR, SGD to IDR, and SGD to THB — and the specific settlement infrastructure available on each.
How Corridor Architecture Actually Works
Every cross-border payment involves at minimum three entities: the sending institution, a correspondent or intermediary bank, and the receiving institution. SWIFT is the messaging layer — it transmits payment instructions, not funds. The actual movement of funds requires nostro-vostro account relationships at each node. That chain introduces fees (typically USD 10–30 per hop in the APAC region), unpredictable settlement timing, and FX conversion at whatever rate the intermediary bank decides to apply.
Local settlement rails short-circuit that chain. Instead of routing SGD → correspondent → recipient country → beneficiary bank, a local-rail payment routes SGD → FX conversion → local clearing system → beneficiary bank. The clearing happens inside the destination country's domestic rails, which means one fewer intermediary, faster settlement, and a quoted rate at time of instruction rather than a surprise rate at time of settlement.
We are not saying SWIFT is bad for APAC B2B payments. There are corridors — particularly to smaller markets without developed domestic rails, and for very large transactions requiring MT202 cover messages and AML documentation chains — where SWIFT remains the correct choice. What we are saying is that for the five high-volume APAC corridors, local rails now offer meaningfully better unit economics and settlement predictability than correspondent banking, and most businesses have not updated their payment stack to reflect this.
The SGD → PHP Corridor: InstaPay and PESONet
The Philippines-Singapore corridor carries substantial B2B volume: BPO firms billing Singapore clients, e-commerce platform seller payouts, and remittances from the large Filipino professional workforce in Singapore. The Philippine payment system offers two relevant domestic rails.
InstaPay is the real-time gross settlement rail for lower-value transactions, operated by BancNet and PESO under the BSP's National Retail Payment System framework. Individual transaction caps apply (PHP 50,000 per transaction as of late 2024), making it suitable for salary disbursements to individual employees or smaller supplier payments but not large single-invoice settlements. Settlement is near-instantaneous during processing hours.
PESONet handles larger values via batch clearing — typically one to three clearing cycles per banking day. For B2B supplier payments exceeding the InstaPay cap, PESONet settles same-day if submitted before the clearing cutoff, typically around 2:00 PM Philippine time.
Consider a Singapore-based staffing firm with 80 contractors in Cebu and Manila. On SWIFT, payroll disbursement took 2–3 days with USD 15–25 in intermediary fees per beneficiary. Routing via PESONet through a licensed payment service provider cut settlement to same-day and reduced per-transfer overhead to a flat corridor fee, materially improving cash flow predictability for both the firm and its contractors.
The SGD → INR Corridor: RBI-Compliant UPI Routing
India is the highest-volume B2B corridor from Singapore by several measures. Singapore-India bilateral trade in services alone exceeds USD 10 billion annually, and the IT outsourcing, SaaS subscription, and supply-chain settlement flows that constitute B2B payment volume are large and growing.
UPI — the Unified Payments Interface operated by NPCI — has become the dominant domestic settlement rail in India by transaction count. For cross-border B2B applications, the relevant question is not whether UPI is fast (it is, settling in seconds during network hours) but whether inbound international payments can route to UPI addresses compliantly.
The answer is yes, with structure. The Reserve Bank of India regulates inbound cross-border receipts under its Foreign Exchange Management Act (FEMA) framework. Inward remittances in INR require RBI-compliant routing through a licensed Authorized Dealer bank. Payment service providers who have established bilateral settlement arrangements with Authorized Dealer partners in India can offer a path that looks like this: SGD converted at mid-market rate → transferred to an AD bank account → disbursed to beneficiary UPI VPA or bank account via IMPS/UPI within the same business day in most cases.
NEFT and RTGS remain relevant for larger transaction sizes. RTGS (Real Time Gross Settlement) handles transactions above INR 2 lakh (roughly SGD 3,200 at current rates) with immediate finality during RBI operating hours. For large B2B invoice settlements, RTGS via an AD partner bank remains the most reliable same-day path.
The SGD → MYR Corridor: DuitNow and IBG
Malaysia is Singapore's closest trading partner and the APAC corridor with the highest proportion of same-day settlement already achieved via traditional banking. The proximity and SGD/MYR rate stability (both pegged loosely to USD, with relatively low bilateral volatility) make this a corridor where the primary gain from rail optimization is fee reduction rather than speed improvement.
PayNet's DuitNow platform handles both real-time payments (DuitNow Transfer) and request-to-pay flows. The Interbank GIRO (IBG) system processes batch transactions for payroll and bulk supplier payments. For Singapore entities paying Malaysian suppliers, DuitNow Transfer offers confirmation within seconds during banking hours, with a transaction limit of MYR 50,000 per transfer for retail use cases — larger B2B flows typically route via Interbank Fund Transfer (IBFT) or RENTAS (Real-time Electronic Transfer of Funds and Securities) for high-value settlements.
The SGD → IDR Corridor: BI-FAST
Bank Indonesia launched BI-FAST in December 2021 as a retail real-time payment infrastructure layer, replacing the older RTGS-dominated architecture for smaller transactions. BI-FAST operates 24/7 with a transaction ceiling of IDR 250 million per transfer (approximately USD 15,000–16,000 at current rates). For B2B seller payouts on Indonesian e-commerce platforms and smaller supplier payments, BI-FAST settles in real time.
Larger B2B transactions in IDR — procurement payments, offshore payroll for larger teams, foreign investment-related flows — typically route via Bank Indonesia's RTGS (BI-RTGS) system, which has no value cap but operates within defined banking hours. Important compliance note: inbound USD or SGD must be converted to IDR through an authorized foreign exchange bank in Indonesia (Bank Devisa) before domestic distribution. This conversion step adds one operational node but does not materially slow settlement if properly structured.
The SGD → THB Corridor: PromptPay
Thailand's PromptPay is operated by the National ITMX consortium and has achieved near-universal bank coverage among Thai financial institutions. Registered to national ID numbers, passport numbers, or tax IDs, PromptPay addresses allow B2B payments to route to the correct beneficiary without requiring precise bank account number entry — reducing payment error rates on this corridor substantially.
For cross-border payments arriving in THB, the Bank of Thailand requires that conversions comply with Foreign Exchange regulations, particularly for amounts above THB 50,000 (approximately SGD 2,000). Payments above this threshold typically require a supporting purpose declaration — invoice reference, contract number, or similar documentation. Structured correctly, inbound cross-border payments can reach PromptPay-registered Thai businesses within the same business day.
Choosing the Right Rail: A Decision Framework
No single rail is optimal across all use cases on a given corridor. The practical framework looks like this:
- Transaction size: Real-time retail rails (InstaPay, BI-FAST, PromptPay) carry per-transaction caps. Large B2B invoices need RTGS or batch IBG equivalents.
- Settlement timing requirement: Same-day settlement requires instruction submission before the destination country's clearing cutoff — which varies by rail and may differ from Singapore business hours by 1–3 hours depending on time zone.
- Documentation requirements: Higher-value corridors to India (FEMA) and Thailand (BOT FX regulations) require purpose documentation. Failing to attach documentation does not delay payment in every case, but it creates compliance exposure.
- Beneficiary type: Individual recipients (payroll, contractor payments) can use UPI VPA, PromptPay national ID, or InstaPay account. Corporate beneficiaries need bank account routing for compliance documentation purposes.
The corridors described above are not static. Bank Negara Malaysia's ongoing retail payment modernization, the BSP's continued expansion of PESONet clearing cycles, and NPCI's push to expand UPI to more international markets mean the optimal routing for a given payment type will shift over the next two to three years. Payment infrastructure that worked optimally in 2022 may have a better alternative in 2024, and treasury teams that re-evaluate corridor routing annually rather than locking in a single SWIFT-only workflow will capture meaningful cost and speed improvements over time.