The Singapore-to-India corridor is one of the most active in APAC for B2B payments. Singapore is among India's top ten trading partners in services, and the corridor carries a distinctive mix of payment types: IT services billing from Indian software firms with Singapore holding companies, SaaS subscription revenue for Indian-origin products, supply-chain settlement for manufactured goods, and cross-border payroll for Indian professionals in Singapore-domiciled teams. Each of these use cases has different optimal routing logic.
The core choice facing treasury teams on this corridor is whether to route via SWIFT correspondent banking or via local rail clearing through an Authorized Dealer (AD) bank in India. Understanding why that choice matters — and when each is appropriate — requires a working understanding of how INR actually settles.
Why SWIFT Underperforms on SGD → INR
SWIFT for SGD-to-INR works like this: your Singapore bank sends an MT103 payment instruction to a correspondent bank, which typically holds a USD nostro account at an Indian bank. The correspondent converts USD (or SGD) to INR and instructs the Indian bank to credit the beneficiary. In a clean scenario, this chain takes 2–3 business days. In practice, correspondent banking on the India corridor has several friction points that drive actual settlement times higher:
- Correspondent selection: Different Singapore banks route via different correspondents, and the India-leg correspondent's relationship with the beneficiary's bank determines how quickly final credits appear. If the correspondent does not have a direct relationship with, say, a Kotak Mahindra branch in Pune, an additional hop is required.
- FEMA documentation: The Reserve Bank of India requires that inbound foreign currency remittances comply with FEMA (Foreign Exchange Management Act). Authorized Dealer banks are required to collect purpose code and supporting documentation for remittances above certain thresholds. A SWIFT payment that arrives without proper purpose code designation can sit at the AD bank for additional scrutiny.
- Intermediary charges: Each correspondent bank in the chain deducts its own charges from the principal, so the beneficiary receives less than the invoiced amount. This is structurally different from a fee-transparent local rail transfer where the sender pays a known fee and the beneficiary receives the full converted amount.
UPI for Cross-Border B2B: What Is Actually Possible
UPI is India's dominant domestic real-time payment rail, processing several billion transactions monthly across consumer and business use cases. The question cross-border operators frequently ask is: can I send an international payment that arrives at a UPI VPA (Virtual Payment Address) directly?
The short answer is yes, with regulatory structure. The RBI has progressively enabled inward remittances to credit to UPI-linked accounts. The mechanism works through an Authorized Dealer bank: the cross-border payment provider (licensed in the originating jurisdiction) delivers INR-equivalent funds to the AD bank's nostro/vostro settlement account; the AD bank then credits the beneficiary via IMPS (Immediate Payment Service) or UPI within the Indian banking network. From the beneficiary's perspective, the credit appears as a domestic IMPS or UPI credit — typically within 30–120 minutes of the originating payment instruction, during Indian banking hours.
For B2B use cases specifically, most Indian businesses receiving payments from Singapore counterparts have a GST-registered company bank account. Payments into these accounts for services rendered require the remittance to include a valid FEMA purpose code (the most commonly applicable codes for IT services are P0802 — computer services — and P1007 — business services). An AD bank receiving a well-structured remittance instruction with purpose code can process same-day; one receiving a bare SWIFT message without purpose code goes into a compliance queue.
NEFT, RTGS, and When to Use Each
Not all B2B payments on the India corridor are appropriately routed to UPI or IMPS. Transaction size matters.
IMPS/UPI: For payments up to approximately INR 5–10 lakh per transaction (roughly SGD 8,000–16,000 at current rates), IMPS offers real-time settlement 24/7. This covers most contractor payments, smaller supplier invoices, and SaaS subscription receipts.
NEFT (National Electronic Funds Transfer): Batch clearing in half-hourly cycles during RBI operating hours. No transaction cap per transfer. Settles within the same business day if submitted before the last clearing cycle. Appropriate for mid-range B2B invoices that do not need immediate finality.
RTGS (Real Time Gross Settlement): Available for transactions above INR 2 lakh. Settlement is immediate and irrevocable during RBI RTGS operating hours (typically 7:00 AM to 6:00 PM IST on banking days). For large B2B settlements — purchase orders, advance payments on manufacturing contracts, large IT project milestone payments — RTGS is the appropriate rail. No cap on transaction size.
A mid-size Singapore engineering services firm billing a Hyderabad-based manufacturing client for a INR 18 lakh project milestone used SWIFT for the first two payments in 2023, each taking 3–4 days to settle and arriving short by the correspondent bank's intermediary charges. Switching to RTGS routing via an AD bank partner cut settlement to same-day and made the net received amount fully predictable. The documentation overhead of providing FEMA purpose codes was offset within two transactions by the savings on intermediary charges alone.
RBI Compliance: What the AD Bank Needs
Every inbound cross-border B2B payment to India touches an Authorized Dealer bank, which is the RBI-regulated gatekeeper. The AD bank's compliance requirements are not arbitrary friction — they implement the RBI's FDI and current account transaction tracking under FEMA. Understanding what the AD bank needs helps structure payments to avoid delays.
Standard documentation for a B2B services payment includes: the FEMA purpose code (A0103 for goods imports, P0802 for computer services, P1007 for business services — the correct code depends on the nature of the transaction), a brief purpose description, and for transactions above USD 10,000 equivalent, typically a reference to an underlying contract or invoice. Payments below the small value threshold (USD 10,000 or equivalent) are often processed with minimal documentation; above that threshold, documentation is not optional.
We are not saying the RBI documentation requirements make India a difficult corridor — they make it a well-regulated one. Treasury teams that treat FEMA purpose coding as routine operational hygiene rather than one-time compliance find that the India corridor runs smoothly. The issues arise when businesses apply SWIFT's relatively unstructured messaging conventions to a corridor that has structured domestic requirements on the receiving end.
FX Rate Considerations on SGD → INR
SGD/INR is not a directly traded major pair in the interbank FX market. The standard pricing route is SGD/USD then USD/INR, with two spreads applied. Payment providers that maintain direct bilateral SGD/INR settlement through integrated nostro positions with Indian AD banks can offer tighter spreads than the double-conversion route — typically 0.3–0.8% tighter on the total conversion cost for mid-size transactions.
For businesses with predictable monthly INR payment volumes — recurring IT services fees, monthly payroll disbursements — forward contracts on SGD/INR (or effectively a USD/INR forward hedged back to SGD) provide cost predictability. The cost of a 3-month forward on INR trades within a manageable range relative to the spot rate. For companies with more than SGD 150,000/month in India corridor exposure, the case for a hedging programme is straightforward on unit economics alone.
The SGD-to-India corridor will likely improve further as NPCI expands its international payment partnerships and as the MAS–RBI bilateral framework for cross-border payment linkages develops. Singapore already has a real-time payment linkage with India via the PayNow-UPI corridor for retail transfers; the extension of structured commercial payment flows into that framework is a logical next development that treasury teams should track.