Cross-border payroll is the payment use case where the friction of traditional banking is most visible, because it is recurring, predictable, and welfare-critical. Unlike supplier payments that can absorb a 2-day settlement delay, payroll delays directly affect employees' ability to pay rent and meet financial obligations. Despite that criticality, many Singapore SMBs with APAC teams are still running payroll disbursements on SWIFT correspondent banking infrastructure — paying 2–4% in combined fees and FX spread on every payroll run, and accepting 1–3 day settlement windows that are entirely unnecessary given the local rail alternatives now available.
This article covers the mechanics and cost structure of cross-border payroll for the four APAC corridors that matter most to Singapore SMBs: Malaysia, the Philippines, India, and Indonesia.
The Real Cost Structure of SWIFT Payroll
When treasury teams say they are "paying X% on payroll disbursements," the number they cite is usually the FX spread they can see. The full cost structure typically has four components:
- FX spread at conversion: The difference between mid-market and the rate the bank or SWIFT correspondent quotes. At retail commercial banking rates, this is typically 1.5–2.5% for SGD/PHP, SGD/INR, and SGD/IDR pairs.
- SWIFT messaging fee: Your bank's outgoing wire fee, typically SGD 15–40 per transaction depending on the bank and amount.
- Correspondent bank charges: The intermediary bank(s) in the SWIFT chain deduct their own charges from the principal, meaning employees receive less than the payroll amount. These charges are often labelled OUR/SHA/BEN but the practical outcome for SHA payments is that the beneficiary bears unknown intermediary deductions.
- Currency risk on timing: SWIFT settlement takes 1–3 days, during which the FX rate may move. The rate quoted at instruction may differ from the rate at settlement if conversion happens at the correspondent bank rather than the originator.
A Singapore-based digital services firm with 18 staff in the Philippines — primarily designers and project managers — calculated their 2023 payroll disbursement cost on SWIFT. Monthly PHP payroll of approximately PHP 900,000 (roughly SGD 22,000) was arriving to employees 2 days after initiation, with average SGD/PHP conversion at 1.9% over mid-market plus SGD 20 per wire. Annual payroll overhead: approximately SGD 5,200 in spread plus SGD 4,800 in wire fees = SGD 10,000 per year on a SGD 264,000 annual payroll. That is 3.8% total overhead on disbursement — a number that largely disappears when moved to local rail routing.
Malaysia: DuitNow Payroll Disbursement
The SGD-to-MYR corridor is the most straightforward for payroll optimization, partly because of the geographic and commercial proximity of Singapore and Malaysia and partly because Malaysian banking infrastructure is well-developed with high DuitNow coverage.
Malaysian employees with DuitNow-registered bank accounts can receive payroll credits via DuitNow Transfer in near-real-time. For batch payroll disbursements — a file of 10, 30, or 100 employee payments submitted as a single batch instruction — PayNet's Interbank Fund Transfer (IBFT) processes same-day with settlement within a few hours during banking hours. The MYR/SGD spread via a local-rail payment provider with direct PayNet connectivity is typically 0.3–0.7% over mid-market, compared to 1.5–2.5% via SWIFT correspondent banking.
Compliance note for Malaysia payroll: payments classified as employee salaries are treated as current account transactions under Malaysia's foreign exchange administration rules and do not require BNM approval for standard amounts. Employment Pass or contract documentation may be requested for large recurring transfers to individual recipients.
Philippines: PESONet Batch Payroll
Philippine payroll disbursement via PESONet is now the dominant approach for Singapore companies with BPO and IT services teams in Manila, Cebu, and other cities. PESONet batch files support multiple beneficiaries in a single submission with individual bank account details or InstaPay addresses.
The practical requirement: a PESONet file in the BSP-specified format, submitted to a PSP with Philippine banking connectivity before the clearing cutoff (typically early afternoon Singapore time to catch the primary Philippine clearing cycle). Employees receive credits in their Philippine bank accounts by end of business day in most cases.
BSP regulations require that inbound cross-border payments to Philippine individuals include a brief purpose declaration. Payroll disbursements from a registered employer are a standard, low-scrutiny purpose category — the documentation overhead is minimal if the remitting entity can demonstrate an employment relationship to the beneficiaries.
For Philippine teams larger than 50 people, a proper batch payroll file workflow — with beneficiary details validated, amounts reconciled against payroll run, and a single submission rather than individual transfers — dramatically reduces operational overhead compared to wire-by-wire SWIFT instructions and eliminates the per-beneficiary fee structure of individual wires.
India: IMPS/NEFT Payroll Routing
India payroll via local rails requires the AD bank compliance step described in the SGD-to-INR corridor guide. For recurring payroll disbursements to the same employee beneficiaries each month, the AD bank documentation burden reduces significantly after the first cycle: purpose code P0802 (computer services) or equivalent service category, with supporting employment contracts or assignment letters for the initial transaction set.
IMPS for Indian payroll handles payments up to INR 5 lakh per transfer with near-real-time settlement. For employees at mid-to-senior level with monthly salaries above the IMPS ceiling, NEFT batch clearing provides same-day settlement for the full amount without per-transaction caps.
One genuine complication on the India corridor for payroll specifically: FEMA classifies outward remittances and inward remittances differently. A Singapore company disbursing to Indian employees who are Indian tax residents is in a different regulatory position than disbursing to Indian employees on assignment in Singapore. Tax-at-source and TDS (Tax Deducted at Source) obligations under Indian income tax law add a compliance layer for Indian-resident employees receiving foreign remittances that does not apply to offshore payroll. Companies with large India teams typically work with a local Indian payroll provider or accountant to ensure TDS compliance — this is outside the payment rail question but affects payroll structure design.
Indonesia: BI-FAST for Smaller Teams, RTGS for Larger Amounts
Indonesian payroll disbursement via BI-FAST works well for individual payments up to IDR 250 million per transaction (approximately USD 15,000–16,000). For most SMB payroll use cases — contractor payments, smaller salary disbursements — BI-FAST's per-transaction cap is not a constraint.
For larger disbursements to individual employees or for batch payroll to multiple employees in a single instruction, BI-RTGS handles higher values during RBI operating hours with immediate finality. BI-FAST settlement is near-real-time 24/7; BI-RTGS is business hours only.
We are not saying Indonesian payroll compliance is simple — Indonesian tax law requires PPh 21 withholding on employment income, and foreign companies paying Indonesian employees who are Indonesian tax residents need to understand their withholding obligations. The payment rail optimization is the easier part; the tax compliance layer is where most companies working with Indonesia payroll need local expertise.
Building the Operational Workflow
The operational pattern that works for Singapore SMBs with 10–100 APAC employees across multiple markets:
- Maintain a payroll calendar that accounts for local clearing cutoffs in each destination market. Philippine clearing cutoffs are 1–2 hours earlier (relative to Singapore time) than Malaysian cutoffs due to time zones.
- Submit batch payroll files rather than individual transfers. A 30-beneficiary batch file costs the same in submission overhead as a single transfer but requires only one compliance review and one FX conversion.
- Hold working currency balances for payroll currencies. Running the Philippine PHP payroll from a pre-funded PHP balance eliminates conversion urgency and allows the conversion to be executed at a planned time rather than on payroll day.
- Validate beneficiary bank accounts before the first payroll run. A returned payment to an incorrect Philippine account number or a mistyped Indian IFSC code delays salary payment and creates a support burden. Most payment service providers offer pre-validation tools for APAC bank accounts.
The total cost saving from shifting APAC payroll from SWIFT to local-rail disbursement typically pays back within the first two to three payroll cycles. For a company with SGD 50,000/month in combined APAC payroll disbursements, the annualised saving on spread and fees alone is in the range of SGD 12,000–24,000, depending on the corridor mix. That is before accounting for the operational benefit of same-day settlement predictability — which, for payroll specifically, matters as much as cost.