Bulk International Payments
Bulk international payments: send hundreds of overseas payments in one run, validated and approved.
One file or one API call, funded by a single pay-in, with beneficiary validation and layered sign-off built in. The run that eats a finance day, absorbed.
The market, in numbers
What are bulk international payments?
They exist because keying hundreds of overseas payments into your bank one at a time does not scale. Done by hand, the errors are predictable: a transposed account number, a missed cut-off, a salary bounced back with a return fee.
The alternative is to create and fund many payments in one operation, from a file or through your systems, with validation and approvals built in. In bulk payments, your business instructs payments from its own account.
That is different from a paying agent, an independent party that receives funds and distributes them on behalf of a transaction, and different again from escrow, which holds money until conditions are met.
If you are the one paying your own suppliers, staff or partners, bulk payments is your lane.
When bulk payments are useful
The case appears the moment your list of payees outgrows your patience. These are the runs a batch platform is built to absorb.
- ◆Supplier runs. Paying dozens or hundreds of overseas suppliers on terms, in their own currencies.
- ◆Payroll and contractors. Monthly runs to staff and freelancers abroad, where a late payment is a people problem. Our international payroll guide covers that case in depth.
- ◆Marketplaces and platforms. Paying out to many sellers, creators or partners on a cycle.
- ◆Commissions, pensions, expenses and refunds. Any recurring many-to-one payout that currently eats a finance day.
File upload, or API?
There are two ways to get a batch into a provider. The right one depends on how often you run it and whether you want it wired into your systems.
- ◆A finance team runs a periodic batch by hand, monthly or weekly, rather than continuously.
- ◆You can export a CSV of payees and amounts and upload it. Wise takes a file of up to 1,000 transfers across multiple currencies.
- ◆One pay-in covers the whole batch, so you fund once rather than payment by payment.
- ◆You want to start simple and move to the API later as volume grows.
- ◆Your own software, an ERP or a billing system, should create and submit the payments directly.
- ◆Volume is high, runs are frequent, or payouts are triggered by events rather than a monthly cycle.
- ◆You want the run wired into existing systems. Our ERP and API integration guide goes deeper.
How a batch works
One file in. Many validated payments out.
Load the batch
Upload a CSV of payees and amounts, or let your ERP submit them through the API. Wise takes up to 1,000 transfers across multiple currencies in one file.
Validate payees
Good providers check payee data before you pay, not after it bounces. Ebury runs pre-payment validation and country-specific account checks that catch format errors.
Approve and fund
A six-figure run should not go out on one click. Ebury supports up to five levels of authorisation. One pay-in then covers the whole batch.
Pay and reconcile
The provider pays each recipient, in their own currency where needed. Exportable reports tie every line back to your ledger, with status you can see rather than guess.
How bulk payment providers handle FX
When a batch pays people in several currencies, each line is an FX conversion, and the margin on those conversions is where the real cost sits, not the per-payment fee.
Approaches differ. Wise converts each transfer at the mid-market rate with a fee from around 0.33% and lets you send exact amounts in the recipient’s currency.
Broker-style providers such as Ebury and moneycorp price the margin into the rate and quote case by case. Ask for the rate against the mid-market on your currencies before committing.
Compare the rate, not the headline fee
On a large monthly run, a fraction of a per cent across every line adds up faster than the headline fees. Compare the rate the same way you would for any corporate FX decision.
Beneficiary management and approval workflows
Three controls separate a proper batch tool from a bank’s payments screen.
- ◆Beneficiary validation. Good providers check payee data before you pay, not after it bounces. Ebury runs pre-payment validation and country-specific account checks that catch the format errors that cause rejections.
- ◆Approval controls. A batch worth six figures should not go out on one click. Ebury supports up to five levels of authorisation, so a run can require sign-off from the people who should see it.
- ◆Stored beneficiaries. Holding validated payees means you are not re-uploading the same details every month, which is where duplicate-payment errors creep in.
Reconciliation, failed payments and reporting
The failure modes are predictable, which means you can screen for them when you choose a provider.
A name or account mismatch causes an automatic rejection, and the return can carry a fee. Miss a currency’s local cut-off time and the payment slips to the next business day.
Intermediary banks on the SWIFT route add delay, and a sanctions or KYC flag pulls a payment into manual review.
What protects you is validation up front, clear per-currency cut-offs, exportable reports that tie each payment back to your ledger, and status you can see rather than guess. Ask a provider to show you exactly what happens to a line that fails, and how you find out.
UK bulk payment providers, side by side
Verified from provider websites. Capabilities and pricing change, so confirm directly for your currencies and volumes.
| Provider | Batch method | Published pricing | Worth knowing |
|---|---|---|---|
| Wise Business | File upload (to 1,000/batch) and API | From 0.33% per transfer, mid-market rate; batch tool free | Recipients paid in home currency, no Wise account needed; clearest published pricing; spot only, no hedging. |
| Ebury | File upload and API | Quote-based | Pre-payment validation, up to 5 approval levels, Faster Payments/SEPA/ACH/SWIFT; hedging available alongside. |
| moneycorp | File upload and API | Quote-based | Its own figures cite 190 countries and 120+ currencies, 1 to 3 business days; forwards and options on the same account. |
| Currencies Direct | BatchPay file upload and API | No transfer fees; margin quote-based | 40+ currencies, no ERP integrations named (upload or API only); forwards to 24 months. |
Important — read before you fund a batch
Safeguarding is not the same as FSCS protection.
Bulk payment providers are almost always payment or e-money institutions, not banks. The float you hold with them to fund a batch is safeguarded, kept separate so it can be returned if the firm fails, but it is not covered by the deposit scheme.
The FSCS deposit guarantee, £120,000 per person, covers bank and building society deposits, not a balance at a payments provider, whatever the amount. The FCA is tightening safeguarding from May 2026, adding daily reconciliations and audits.
Do not leave more float sitting with a provider than a batch needs, and check its safeguarding wording.
How to compare bulk payment providers
Six checks that do most of the filtering before you park float with anyone.
- 01
Get the exchange-rate margin against the mid-market on your actual currencies, not just the per-payment fee.
- 02
Confirm the batch method you want, file upload, API, or both, and the maximum payments per batch.
- 03
Check pre-payment beneficiary validation and how many approval levels you can require.
- 04
Ask for per-currency cut-off times and what happens to a failed or returned line.
- 05
Confirm the reporting export ties back to your accounting system cleanly.
- 06
Check the FCA authorisation and safeguarding wording before you park float with it.
Common questions
What is the difference between bulk payments and a paying agent? +
In bulk payments your business instructs many payments from its own account. A paying agent is an independent regulated party that receives funds and distributes them on behalf of a transaction, such as a company sale. Different job, different provider.
How many payments can I send in one batch? +
It varies by provider. Wise takes up to 1,000 transfers in one uploaded file across multiple currencies; broker-style providers set their own limits. Banks are often far more restrictive, and Wise reports that some business accounts cap batches at around 25 payments.
How do I pay for a batch? +
Typically with one pay-in that covers the whole batch, rather than funding each payment separately. With Wise you upload the file, make a single transfer to cover it, and confirm payment; the provider then pays each recipient.
What happens if one payment in the file has wrong details? +
A name or account mismatch usually causes that line to be rejected, and a returned payment can carry a fee. Providers that validate beneficiary data before payment catch most of these, which is why pre-payment validation is worth paying for on large runs.
Is my money safe with a bulk payment provider? +
The float you hold to fund batches is safeguarded in segregated accounts under FCA rules, and those rules tighten from May 2026. It is not FSCS-protected like a bank deposit. Keep only what a batch needs with the provider and read its safeguarding statement.
Tell us about your run.
Share how many payees you pay, in which currencies, and how often, and we will introduce you to the provider that fits your volumes, and be straight about the one that does not. No cost, no obligation.