---
title: "How to pay international contractors in one batch"
description: "To pay multiple international contractors in one batch, verify details once, fund each currency, route every line to a local rail and approve one run."
url: "/blog/pay-your-contractor-bench/"
date: "2026-07-13"
updated: "2026-09-29"
author: "Valeria Vahorovska"
tags: ["Guides","Payouts"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page is an article from the Fynex blog: “How to pay international contractors in one batch”. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when the reader runs the money workflow this article describes and wants to understand how it works, what it costs and where it breaks.

# How to pay international contractors in one batch

To pay multiple international contractors in one batch, collect each contractor's verified bank details and currency once, then run every pay cycle as a single payout batch. Amounts come from approved invoices or timesheets, each currency is funded from a matching balance, and each line goes out over the contractor's local rail after one approval.

That is the whole method. This guide covers the steps, what paying 50 contractors actually costs, why batch lines fail, and how a bulk payout compares with a wire per person. For a method-by-method comparison of providers, see [the best way to pay international contractors](/blog/best-way-to-pay-international-contractors/).

If you run a [software company](/saas/), the contractor bench is probably your second-biggest cost after payroll: a designer in Porto, engineers in Warsaw and Belgrade, a QA contractor in Manila. Each adds a currency, a corridor and a fee. Operators describe the result bluntly: card and transfer fees adding up to *"3% of my gross margin."*

## How to pay international contractors in one batch: the steps

A batch payout replaces one transfer per contractor with one approved run. The work moves from payday to setup: details, rates and currencies are captured once, then reused every cycle.

1. **Onboard each contractor once.** Legal name, local bank details (IBAN, sort code, ACH routing and account number), payout currency, tax form and signed rate.
2. **Build the batch from source documents.** Pull each amount from the approved [invoice](/features/invoicing/) or timesheet, not from a spreadsheet retyped on Friday.
3. **Check every line against the contract.** Rate, hours and milestone are verified before money moves, which catches the double-billed week [before it's paid](/blog/where-is-your-business-losing-money/).
4. **Fund each currency once.** Hold a EUR or GBP balance and top it up in one deliberate conversion, instead of converting per payment. That is the case for [multi-currency balances](/blog/how-nested-accounts-work/).
5. **Route each line to its cheapest rail.** SEPA for euro payees, Faster Payments for the UK, ACH for the US, SWIFT only where no local rail reaches.
6. **Approve once.** One person signs off the whole [mass payment](/glossary/mass-payment/), with totals per currency.
7. **Reconcile automatically.** Every payout books to Xero or QuickBooks against its invoice and contractor.

## Batch payouts vs one wire per contractor

A bulk payout over local rails beats a SWIFT wire per contractor on approvals, FX, fees and reconciliation. The difference is structural, not a better price on the same method.

| | One SWIFT wire per contractor | Transfer tool, one payment at a time | Batch payout over local rails |
|---|---|---|---|
| **Approvals per cycle** | One per contractor | One per contractor | One for the whole run |
| **FX** | Bank's rate on every wire | Spread on every payment | Deliberate conversions from held balances |
| **Fees** | Sending, correspondent and receiving fees | Per-transfer fee | Local-rail cost per line |
| **Contractor receives** | Often short-paid by intermediaries | The quoted amount | The full amount, in their currency |
| **Reconciliation** | Manual, wire by wire | Export and match | Books itself per invoice |
| **Tax paper trail** | Kept separately | Kept separately | An invoice behind every line |

The FX row is where most of the money sits. In its [2025 progress report on cross-border payments](https://www.fsb.org/uploads/P091025-1.pdf), the Financial Stability Board found business-to-person payments cost 1.8% on average, and that FX made up 74.5% of that cost. A method that only lowers the fee line leaves three-quarters of the bill untouched.

## What paying 50 contractors costs: a worked example

At the global average, paying 50 international contractors $4,000 each costs about $3,600 a month. Most of it is exchange-rate margin, which is why the fix is how you hold and convert currency, not a cheaper transfer fee.

Say your bench is 50 contractors averaging $4,000 a month, so $200,000 leaves every month across a dozen currencies. The FSB measures its business-to-person average on a $5,000 transfer, close to this bench's typical line.

| Line | Monthly | Yearly |
|---|---:|---:|
| Payout volume | $200,000 | $2,400,000 |
| Total cost at the 1.8% average | $3,600 | $43,200 |
| of which FX (74.5%) | $2,682 | $32,184 |
| of which fees | $918 | $11,016 |

Two habits push the FX line up. Converting per payment pays the spread 50 times, at whatever rate that morning offers. Wiring over SWIFT adds correspondent deductions, and the contractor asks you to top up the difference. Holding a balance per currency, converting in one sized amount and paying over local rails removes both.

Price every provider on the rate, not the fee line: compare its conversion against the [mid-market rate](/glossary/mid-market-rate/) at the same moment.

## Why batch payout lines fail or arrive late

Batch lines bounce on data: a name that doesn't match the account, a malformed IBAN, a missing address field. Speed is the second problem, because cross-border business payments are still slow.

The same FSB report found only 44.3% of business-to-person payment services credit the recipient within one business day. For a contractor who invoices on the 1st and pays rent on the 3rd, that gap separates a reliable client from one they quietly drop.

Three controls keep a batch clean:

- **Validate details at onboarding, not on payday.** Check the IBAN format, the name match and the structured address before the first run.
- **Verify every destination change.** A "new bank details" email is the classic fraud entry point, and [instant payments are irrevocable](/blog/instant-means-irrevocable/).
- **Pay on a fixed date.** One run, same day every month. The bench that gets paid like clockwork doesn't drift to clients who pay faster.

## Where contractor payouts leak

Four leaks sit behind contractor payout costs. None is hard to fix, and all of them compound every month.

- **The wire premium.** A sending fee, often a receiving fee, correspondent deductions in between, and a short-paid contractor.
- **The hidden spread.** Consumer transfer tools advertise low fees and earn on the rate. On one $4,000 payment, a 2% spread is $80.
- **The convert-per-payment habit.** Dozens of small conversions pay dozens of spreads.
- **The three-tools tax.** One tool for Europe, another for Asia, wires for the rest, and a spreadsheet reconciling all three.

## How Fynex runs the batch

This is a rules problem, and rules are what agents are for. In Fynex you define the bench once: contractor, rate or timesheet source, schedule. Each cycle, the agents build the run, verify each payout against the contract terms, [pay it by ACH or Faster Payments](/features/payouts/) for contractors in the US and the UK, and queue the whole batch for one approval. Contractors outside those two countries still need one of the routes above.

Money goes out on schedule through the [payouts API](https://docs.fynex.ai/payments-api/v1/docs/payouts), and every payment reconciles itself to your books behind the run. Because Fynex is unconflicted, owning no rails and earning no spread on your flow, the run optimises your cost rather than a network's volume. Your [cash position](/features/cash/) already knows the run is coming, so payday never collides with a cash-floor surprise.

Related: [payment platforms for freelancers who can't afford a freeze](/blog/freelance-payment-platforms-freezes/) is the bench's own view of the same run; [mass payouts to international partners](/blog/partner-payouts-across-borders/) and [multi-currency accounts for SaaS companies](/blog/multi-currency-accounts-software-companies/) cover the neighbouring problems.

The bench is how a software company scales without hiring ahead of revenue. Paying it should take one approval, not 3% of gross margin and a Friday afternoon.