India's services exports reached USD 421.3 billion in FY 2025-26, up from USD 387.5 billion the year before, according to the Ministry of Commerce and Industry. Behind that number sit thousands of exporters, SaaS companies, agencies and freelancers who have done the hard part already: won the client, delivered the work, raised the invoice. Then they wait. Not for the buyer, who paid on time, but for the money to finish crawling through the banking system.
That wait is usually three days or more when you collect through a bank wire, and it comes with a foreign exchange rate you did not negotiate, fees you cannot itemise, and a stretch of silence where nobody, including your bank, can tell you where your money is.
Cutting international payment settlement time to 24 hours removes most of that. Here is why bank collection takes as long as it does, what 24 hour settlement actually means and when the clock starts, and what can still slow it down.
- International payment settlement time through a bank wire is typically three days or longer, while PayGlocal's multi-currency account flow settles within 24 hours of invoice approval.
- The biggest delay often happens after the payment reaches the receiving bank, during invoice matching, purpose code declaration and compliance processing.
- Local collection accounts let overseas buyers pay domestically in their own currency, removing the correspondent banking chain from the collection leg.
- Faster settlement improves working capital, reduces FX exposure and makes reconciliation and export documentation easier to manage.
The short answer: International payment settlement time through a bank wire is typically three days or longer. Through a cross-border payment aggregator using a multi-currency account, it is within 24 hours of invoice approval. The bottleneck was never the wire. It is the compliance and matching work at the receiving end.
Why does an international payment take three days to settle?
The usual explanation is that SWIFT is slow. That explanation is wrong, and believing it means you fix the wrong problem.
SWIFT's own published network data shows that 90% of cross-border payments reach the destination bank within an hour. But only 43% reach the end customer's account within an hour. The message travels fast. The money lands at the beneficiary bank fast. Then it stops.
The gap is the real answer. Your payment arrives at your Authorised Dealer bank, the AD bank licensed to handle foreign exchange on your behalf, as an unallocated inward remittance. Before it can be credited, the bank has to match it to an underlying transaction, obtain a purpose code declaration under FEMA (the Foreign Exchange Management Act, which governs how foreign currency moves in and out of India), verify your invoice, and clear its own compliance queue. Much of this is manual, it runs on banking hours, and it sits behind every other remittance that arrived that morning.
Then there is the correspondent chain. A payment from a buyer in the United States may pass through two or three intermediary banks before it reaches India, and each one is entitled to take a cut. The World Bank's Remittance Prices Worldwide data has consistently found banks to be the most expensive channel. Industry analysis of B2B flows puts typical cross-border settlement at three to five days at an average all-in cost of roughly 6.3% of transaction value once foreign exchange markups, correspondent fees and compliance charges are counted.
And through all of it, you have no visibility. The buyer says they sent it. Your bank statement says nothing. You cannot tell your CFO whether the money is stuck at an intermediary in Frankfurt or in your own bank's compliance queue in Mumbai. So you email your relationship manager and wait some more.
Where the delay actually sits:
- The wire is not the bottleneck. The last mile inside the receiving country is.
- Purpose code declaration and invoice matching are what gate the credit.
- Each correspondent bank can deduct a fee you never see quoted upfront.
- No transaction-level tracking, so finance cannot forecast the receipt.
What does settlement in 24 hours mean, and when does the clock start?
Settlement in 24 hours means funds reach your account within one business day of the transaction becoming settlement-ready. Under the PayGlocal flow, a transaction becomes settlement-ready the moment your invoice for it is approved. The clock starts at invoice approval, not when your buyer clicks send.
That distinction matters more than it first appears.
A settlement promise measured from the buyer's payment is a promise about things nobody controls: the buyer's bank, the corridor, the correspondent chain, the weekend. A promise measured from invoice approval covers the part that is actually in the payment aggregator's hands, and that is where your three days were going.
It is also a ceiling rather than an average. Most settlements land faster than 24 hours. 24 hours is the outer boundary, assuming no compliance issue needs resolution. That framing is deliberate. A partner who quotes you an average is quoting you the good days. A partner who quotes you a ceiling is telling you what to plan around.
The practical consequence: the timeline becomes something you control. Upload the invoice promptly and settlement follows predictably. Sit on it for four days and the delay is yours, not the system's.
What a three day wait actually costs you
Two extra days sounds like a rounding error. It is not, and the cost lands in four places.
Working capital. Collect USD 500,000 a month with every rupee arriving two days late and you are permanently funding two days of your own revenue. On a working capital line, that is real interest paid for no reason. Bootstrapped, it is payroll timing anxiety every month.
Foreign exchange exposure. Money in transit is money exposed. The rupee moves while your funds sit in a correspondent chain, and you control neither the moment of conversion nor the rate. You are running an unhedged position you never chose to take.
The reconciliation tax. Unidentified credits, part-settlements, fees deducted mid-route, and no transaction reference to match against your invoice ledger. Someone spends hours every week matching money to invoices that should have arrived pre-matched.
Audit exposure. Under FEMA, export proceeds must be realised within 15 months of the invoice date, a window the RBI raised from 9 months with effect from November 2025. Fast settlement keeps that clock nowhere near a risk and your EDPMS entries closing cleanly. EDPMS is the RBI's Export Data Processing and Monitoring System, which tracks export transactions against the money actually realised. Slow, poorly documented settlement is how exporters end up chasing extensions.
How a multi-currency account changes the collection route
A multi-currency account is a set of local currency collection accounts held in your business's name, so your overseas buyer can pay you the way they pay a domestic supplier instead of initiating an international wire.
This is the structural change, and it removes the correspondent chain rather than merely speeding it up. When your US buyer pays into a US dollar collection account, that leg is domestic to them. There is no chain of intermediary banks taking a cut, because there is no chain. The money is collected locally, then moved through a regulated route into India.
With PayGlocal you can open a multi-currency account, get access to major currency accounts, and start accepting payments in your buyer's local currency straight away. Your buyer's experience improves too, which is not a small thing when you are closing an enterprise contract with a procurement team that dislikes international wires. Collection reaches 180+ countries, so one account structure serves clients across the United States, the United Kingdom, the European Union, Singapore and beyond.
What changes on the collection leg:
- Your buyer pays locally, in their own currency, on their normal domestic rails.
- No correspondent chain means no intermediary deductions on the way.
- The transaction appears on your dashboard when it lands, not days later on a statement.
- Conversion happens once, at a point you can see, rather than invisibly in transit.
Bank wire compared with PA-CB collection
PA-CB stands for Payment Aggregator - Cross Border, the RBI's authorisation category for entities that collect or disburse money across India's borders on behalf of buyers and sellers. Here is what an exporter actually experiences on each route.
| What you experience | Bank wire collection | PA-CB multi-currency collection |
|---|---|---|
| Typical settlement time | Three days or longer, commonly three to five days for B2B flows | Within 24 hours of invoice approval, often faster |
| When the clock starts | Unclear, dependent on corridor and correspondent chain | At invoice approval, a point you control |
| How your buyer pays | International wire from their bank | Local payment in their own currency |
| Intermediary deductions | Each correspondent bank may deduct a fee | No correspondent chain on the collection leg |
| Foreign exchange rate | Bank's rate for a single small ticket, applied at its discretion | Pooled conversion across merchants through an AD bank |
| Cost transparency | Fees often visible only after the credit lands | Pricing known in advance of settlement |
| Visibility | None until the credit appears on your statement | Transaction-level tracking on a unified dashboard |
| Foreign exchange documentation | FIRC often requested manually after the fact | FIRA and FIRC generation automated |
| Reconciliation | Manual matching of unidentified credits to invoices | Settlement already mapped to the underlying invoice |
FIRA and FIRC are the Foreign Inward Remittance Advice and Certificate: your documentary proof that funds arrived in convertible foreign exchange, and what your GST refund and export status claims rest on.*Banner CTA note: place the multi-currency account banner immediately after this table, not at the foot of the page. This is where the reader forms intent.*
From buyer payment to INR: the five steps
The journey is short enough to describe completely, which is itself the point. If a process cannot be explained in five steps, it probably has places for your money to get lost.
Steps one and two happen without you doing anything. Step three is the only action required from you, and it starts the settlement clock. Steps four and five complete within 24 hours.
- Collect. Your buyer pays into your multi-currency account in their local currency, on domestic rails in their own market.
- See it. The transaction appears on your PayGlocal dashboard as soon as funds arrive, with transaction-level visibility of where it stands.
- Upload the invoice. You upload the commercial invoice for that transaction, as required under RBI guidelines for cross-border collections.
- Approval. PayGlocal reviews and approves the invoice against the transaction. The transaction becomes settlement-ready and the 24 hour clock starts.
- Convert and settle. The transaction joins a pooled foreign exchange conversion, is converted through an Authorised Dealer bank, and settles to your Indian account within 24 hours of approval.
One constraint to plan around. The Payment Aggregator Directions, 2025 set a maximum of INR 25 lakh per transaction for inward or outward transactions processed by a PA-CB. This is a regulatory limit that applies to every PA-CB, not a restriction specific to any provider. If your typical invoice sits above that threshold, work out the route with your provider and your AD bank before you build a process around it.
Why pooled FX conversion beats converting alone
This is the part almost nobody explains to merchants, and it is why an aggregator can beat the rate your bank offers you directly.
When you convert USD 20,000 by yourself, you are a small ticket arriving at an unremarkable moment. You get the rate the bank chooses to show a small ticket. No bargaining position, no timing advantage, and no reason for anyone to sharpen a pencil for you.
An aggregator is not converting your USD 20,000. It is converting your transaction alongside a large number of settlement-ready transactions belonging to many other merchants, in a single pooled conversion executed with an Authorised Dealer bank. Size changes the pricing you can command, and that improved rate flows back to the merchants in the pool, including you.
Timing is the other half. Each settlement has a known deadline, so transfers can be sequenced deliberately and converted at chosen moments rather than whenever a payment happens to clear a correspondent bank at 2am.
If funds are pooled, who holds the float?
Fair question, and the RBI has already answered it. Under the Payment Aggregator Directions, 2025, a PA-CB is prohibited from pre-funding its collection account, and every payment aggregator must maintain a day-end balance in the escrow account equal to the amount realised but not yet settled to merchants. Inward flows sit in an Inward Collection Account, with no co-mingling or netting off against outward transactions permitted.
A PA-CB is also prohibited from dealing in foreign currency with any entity other than an Authorised Dealer bank, so your conversion always runs through a regulated AD bank. The aggregator pools, times and routes the conversion. It is not the counterparty to it.
Pooling is a conversion mechanism, not a licence to sit on your money, and the regulator has ring-fenced it accordingly.
What can still delay your settlement
No honest provider should tell you settlement is never delayed. It is more useful to know the four things that cause delays, because three of them are entirely within your control.
A late invoice upload
The most common cause, and the most avoidable. Since the clock starts at invoice approval, a transaction sitting on your dashboard for three days without an uploaded invoice has not started its clock.
An invoice that does not reconcile
If the invoice does not match the transaction on amount, currency or reference, approval stalls while it is sorted out. Invoicing discipline removes this category permanently.
An incorrect purpose code
Every inward remittance carries a purpose code under FEMA classifying what the payment is for. The wrong code creates downstream reconciliation and EDPMS problems, so it is worth taking seriously rather than picking the closest-looking option. If your services vary across clients, your codes can legitimately vary too.
A genuine compliance review
Cross-border payments are screened, and occasionally a transaction needs additional checks before release. That is the system working as intended. The reasonable expectation is not that reviews never happen, but that you are told when one does.
Which businesses gain most from faster settlement
Any Indian business with recurring overseas revenue: software and SaaS exporters, IT and business services firms, agencies, D2C brands selling internationally, and freelancers billing foreign clients.
The benefit scales with frequency. If you collect monthly, faster settlement is convenient. If you collect weekly or daily, it materially changes your working capital position, because the gap between delivering the work and holding the cash stops compounding across every invoice in the cycle.
For your specific business, tax or regulatory circumstances, speak with a qualified professional or with the PayGlocal team rather than relying on general guidance.
If your export collections are still arriving on someone else's timetable, it is worth seeing what the alternative looks like on your own transaction volumes.Related reads:
- Multi-currency accounts
- How PayGlocal handles international payment settlement time end to end
- Payment solutions for exporters
- Why exporters choose PayGlocal.




