The best and cheapest way to pay international contractors
The cheapest way to pay international contractors, and how to pay 50 in one batch: six methods compared on total cost, speed, tax forms and delivery.
By Valeria VahorovskaUpdated 30 September 2026
The cheapest way to pay international contractors is in their own currency, over a local payment rail, at an exchange rate close to the mid-market rate. The transfer fee is rarely the biggest cost; the FX margin is. For more than a handful of contractors, pay them in one batch from one balance, and have every payment reconcile back to its invoice.
Four things decide the method: total cost, speed, the tax paperwork the relationship creates, and whether the contractor receives what you sent. Most comparisons cover the first and ignore the fourth, which is the one that generates the support email.
The four decision criteria
| Criterion | What to actually measure |
|---|---|
| Cost | What left your account vs what arrived in theirs, not the fee line |
| Speed | Time to available funds, not time to “sent” |
| Paperwork | Whether tax forms are collected at onboarding or chased at year end |
| Delivery | Whether the contractor can receive it in their country, in their currency |
The cheapest way to pay international contractors
The cheapest method is the one with the lowest total landed cost on your corridors. Total landed cost is the fee, plus the exchange-rate margin, plus any deductions in transit. The margin is applied to the whole amount, so on payments of any size it dominates the fee.
The scale of the problem is measured. The World Bank puts the global average cost of sending money abroad at 6.36% of the amount sent (Remittance Prices Worldwide, September 2025). That’s consumer remittances, not business payouts. It still shows how much of a cross-border payment disappears into margins and fees when nobody compares the rate.
A worked example: one monthly run of 50 contractors at $1,000 each ($50,000). The figures are illustrative; plug in the rates you’re quoted.
| Method | Fee | FX margin | Deductions in transit | Cost of the run |
|---|---|---|---|---|
| Bank wire, converted by the receiving bank | $25 × 50 = $1,250 | ~2.5% = $1,250 | $15 × 50 = $750 | ~$3,250 |
| Payment platform, paid one by one | $5 × 50 = $250 | ~0.6% = $300 | none | ~$550 |
| Batch payout in local currency, near mid-market | 0.5% = $250 | ~0.5% = $250 | none | ~$500 |
The wire costs more than six times the batch payout. Almost none of that is visible on the bank’s fee line.
Test it once: take a real payment and note the rate you received. Compare it against the mid-market rate at that timestamp. The difference, as a percentage, is your actual FX cost, and it is frequently several times the fee.
How to pay 50 international contractors in one batch
Paying contractors in one batch means one funded balance, one approval, and one payment per contractor, each in the contractor’s own currency on the rail for their country. Done properly, it takes one approval a month instead of fifty transfers.
- Collect details and tax forms at onboarding. Bank details, payout currency and the W-9 or W-8BEN go in once, while the contractor is keen to be paid. Year end is too late.
- Pick the currency and rail per country, not per run. A contractor in Poland gets zloty, one in Mexico gets pesos, each over their local rail. Keep SWIFT for the corridors that have no local option.
- Fund the run from one balance. Convert once, at a quoted rate, instead of fifty times at fifty rates.
- Approve the run once. The run shows each payment, its rate and its cost before any money moves.
- Reconcile against the invoices. Each payment should post to your books against the contractor invoice it settles. Anything that fails should come back as an exception to fix.
Speed depends on the rail. Local rails often settle the same or the next day. On SWIFT, nearly 60% of gpi payments are credited to the end beneficiary within 30 minutes, and almost 100% within 24 hours. Credited is not the same as arrived in full, though: the amount can still shrink in transit.
The methods
Bank wire (SWIFT)
How: your bank sends to theirs, hopping through correspondent banks. Cost: a quoted fee, plus an exchange margin, plus intermediary deductions taken in transit that nobody quotes. Speed: from minutes to days, depending on the banks in the chain. Best fit: occasional large payments to a contractor with a stable bank relationship. Worst fit: anything recurring. The unpredictable deductions mean the contractor receives a different amount each time, which produces a monthly conversation. How SWIFT differs from SEPA.
Payout layer (Fynex)
How: Fynex routes each payment over whichever rail is cheapest for that corridor: local rails where they exist, SWIFT where they don’t. The whole run goes out in the contractors’ own currencies. Fynex is not a new rail; it runs the payouts over the rails and accounts you keep. Cost: Fynex’s fee is 0.5% per payout, $1 minimum, plus $100 a month (pricing). The FX and rail cost is shown per payment before you approve the run. Speed: rail-dependent, so often same or next day on local rails. Best fit: dozens to hundreds of contractors, where the payout run and its reconciliation are someone’s monthly job. Each payment carries the invoice it settles, so the run lands in your ledger as settled invoices, not one debit to decompose. Watch: for five contractors it is more than you need; a payment platform and a spreadsheet will do. Payouts.
Multi-currency business account
How: hold balances in several currencies, pay locally in each. Cost: conversion margin when you convert; low or nil when you pay from an existing balance. Speed: local rails, so often same or next day. Best fit: paying regularly into a small number of currencies, where you can hold balances and time conversions. Watch: the benefit comes from holding, not from the account existing. Converting per payment gets you the margin anyway.
Payment platform (Wise, Payoneer and similar)
How: send in your currency, they deliver in theirs. Cost: transparent fee; the margin varies by provider, and some quote it against the mid-market rate explicitly. Speed: hours to days, by corridor. Best fit: a handful of contractors, paid individually, where simplicity matters more than integration. Watch: contractor-side account requirements vary by country, and this is where “the payment failed” usually starts.
Mass payout platform
How: upload or push a batch; the platform handles the delivery method per recipient. Cost: per-payment pricing plus FX. Speed: rail-dependent. Best fit: dozens to hundreds of contractors, especially with tax-form collection built in. Watch: built for volume, so heavy for five contractors.
Contractor management platform
How: contracts, invoices, compliance and payment in one product. Cost: per-contractor subscription plus payment costs. Best fit: you want the agreement, the invoice and the payment in one place, and you’re prepared to pay per head. Watch: you are buying the paperwork layer. If you already have contracts and invoicing, you pay for them twice.
Employer of Record
How: they employ the person locally on your behalf. Cost: substantially more per head than contractor payment. Best fit: the relationship is functionally employment, and misclassification is the risk you are buying down. Not: a cheaper way to move money. It’s a different instrument for a different problem.
The comparison
| Method | Total cost | Speed | Tax forms | Batch payouts | Scales to |
|---|---|---|---|---|---|
| Bank wire | High, partly hidden | Minutes–days | Manual | No | ~5 |
| Payout layer (Fynex) | Low: 0.5% per payout + quoted FX | Rail-dependent | KYC built in; tax forms via your onboarding | Yes, reconciled to invoices | Hundreds |
| Multi-currency account | Low if you hold | 1–2 days | Manual | Limited | ~20 |
| Payment platform | Moderate, transparent | Hours–days | Manual | Limited | ~30 |
| Mass payout platform | Moderate | Rail-dependent | Built in | Yes | Hundreds |
| Contractor platform | Higher per head | Days | Built in | Yes | Dozens |
| Employer of Record | Highest | Payroll cycle | Employment | Payroll | Any |
The mistake that gets expensive
Optimising the fee and ignoring the margin.
The advertised transfer fee is usually the smaller number. The FX markup is the difference between the rate you received and the mid-market rate at that moment. It is applied to the whole amount, so on any payment of size it dominates.
The second version of the same mistake is sending in your currency and letting the receiving bank convert. You’ve handed the margin to a bank with no relationship to you and no reason to compete, and the contractor absorbs it silently. In the worked example above, that single choice is most of the difference between $3,250 and $275.
The paperwork, done once
Collect tax forms at onboarding, not at year end.
A contractor who is working with you now returns a form in a day. A contractor you stopped working with in March may never return it, and you have a filing obligation and no document.
For a US business the forms are:
- W-9 from US persons
- W-8BEN (or another W-8) from non-US persons
- 1099-NEC where the reporting threshold is met. For payments made after December 31, 2025, that threshold is $2,000, up from $600, and it’s adjusted for inflation from 2027 (IRS, Instructions for Forms 1099-MISC and 1099-NEC).
Other countries have their own equivalents. The operational rule is the same everywhere: the form is easy to get while the relationship is live and hard afterwards.
This is the strongest argument for the tools that build it in. Collection isn’t technically difficult. The point is that it happens at the right moment, automatically.
What breaks at scale
Paying five contractors is an administrative task. Paying eighty is an operational process, and three things start to hurt:
- Reconciliation. A batch of eighty payments leaves your account as one debit, or as eighty lines with unhelpful references. Matching them back to eighty contractor invoices becomes a monthly job.
- Failed payments. With eighty recipients, a few fail every cycle: details changed, an account closed, a country-specific requirement missed. Someone has to notice, chase and re-send.
- Amount drift. Where intermediary fees are deducted in transit, contractors receive slightly different amounts than they invoiced. Each difference is a small conversation and a small unreconciled balance.
This is the point where contractor payouts stop being administration, and where a payout layer earns its place. With Fynex, the run of eighty goes back into your ledger as eighty settled invoices. The applied rate travels with each payment, so a gap between invoiced and sent is explained at the time. A failed payment surfaces as an exception, not as a contractor’s email three weeks later.
Related: Partner payouts across borders · Payoneer vs Tipalti · cross-border payment · Payouts