Bulk contractor payouts: pay your bench in one run on Fynex

To pay your contractor bench in one bulk payout run on Fynex, add each contractor once as a payee with their bank details, fund your USD, GBP and EUR balances, and let Fynex build the run each cycle. You approve it once. Each contractor is paid separately over their local rail, and each payment is reconciled to its invoice.

This guide is for agencies and creative studios paying a bench of freelancers and contractors across several countries. It covers the Fynex setup. If you are still deciding how contractors should be paid at all, read how to pay your contractor bench across borders and the best way to pay international contractors first.

How to set up bulk contractor payouts on Fynex: the steps

Steps 1 to 4 happen once per contractor. Steps 5 to 8 are the monthly run, and they take minutes once the bench is in place.

1. Create a Fynex account. The setup dock walks you through a first payee, a commission rule, an invoice and a test payment; you can explore in sandbox before verification. How to get started with Fynex walks through every screen.
2. Add each contractor as a payee. Enter the business or trading name, email, role (Contractor), tax ID, address, bank country, account number and BIC or routing number. A wallet for the contractor is set up automatically.
3. Record what each contractor is owed. A fixed monthly rate, a day rate against a timesheet, or a milestone. This is the figure Fynex checks each payment against.
4. Fund your currency balances. Your Fynex account holds USD, GBP and EUR. Top up the currencies you owe, so payouts draw from a balance rather than a conversion on every line.
5. Let Fynex build the run. One line per contractor: amount, currency, rail and the invoice it settles. Lines that don’t match the agreed rate are flagged before you see the total.
6. Approve once. Review the run, hold a line if you need to, then approve. Nothing moves before approval.
7. Each payout goes out on its own rail. Every line is a separate payment with its own reference and status.
8. The run reconciles itself. Each settled payout is matched to the contractor’s invoice and booked to QuickBooks or Xero.

What do you need from each contractor before the first run?

Collect the details once, at onboarding, and the monthly run never stops to ask for them. A contractor with missing bank details is held out of the run with the reason shown, rather than paid late or paid wrong.

Ask each contractor to invoice in the currency they are paid in. It keeps the invoice, the payment and the ledger entry in one currency, and it removes the conversion question from the contractor’s side.

Which rail does each contractor get paid on?

Fynex picks the rail from the payout currency and the contractor’s bank details. Where a domestic scheme reaches the contractor, the payment uses it instead of an international wire. That is where most of the saving on a bench run comes from.

Pay each contractor in the currency they invoice in. A designer in Lisbon invoicing in EUR is paid in EUR over SEPA, from your EUR balance, with no conversion on arrival. The rail terms themselves are explained in SEPA vs SWIFT.

What does a bulk payout run cost on Fynex?

Fynex’s fee is 0.05% per transaction on money in and money out, plus $20 a month for the plan, which includes 40,000 agent credits. On a $40,000 monthly bench run, the Fynex fee is $20. Full details are on the pricing page.

Two costs matter more than the fee line on most contractor platforms:

• The FX spread. A low transfer fee can hide a wide rate. Fynex earns no spread on your flow; hold the currencies you owe and convert deliberately rather than per payment.
• The rail. A domestic payment usually costs far less than an international wire to the same contractor.

Price any platform on all three at once. FX markup explains how to spot the spread.

How does one approval become forty separate payments?

A bulk payout on Fynex is one approval over many payments, not one payment split later. When you approve the run, each line is sent as its own payout, drawn from the contractor’s wallet in that currency.

Every payout moves through the same statuses: pending, processing, then completed, failed or cancelled. A failed line returns its amount to your balance and shows the reason. The other lines carry on.

Each payout carries a description of up to 140 characters, which reaches the contractor’s bank statement as remittance information. Put the invoice number in it, for example “INV-0931 September design retainer”, and neither side has to ask which payment was which.

If you run the bench through the API instead of the dashboard, the same run is one POST /payees/{payee_id}/payouts per contractor, with payoutMethodId, amount, description and an idempotencyKey. The Payouts docs have the full request.

How do contractor payouts land in QuickBooks or Xero?

Each settled payout is matched to the invoice it pays and to the contractor, so month-end starts from forty settled invoices, not one lump to untangle. The applied rate travels with each foreign-currency payment, so a difference between invoiced and sent amounts is explained when it happens.

This is the agentic finance layer on top of the run: the agents check each line against the agreed rate, route it, and reconcile it, and you approve the result. Your cash position already shows the run against the client payments landing that week, so payday never collides with a low balance.

Where to go next

• Payouts: one approval, every contractor on their best rail.
• Fynex for agencies: how studios run billing, bench payouts and reconciliation in one place.
• Payees and Payout methods in the docs.
• Partner payouts across borders: the same run for referral and revenue-share partners.
• How to automate accounts payable in QuickBooks: the supplier-bill side of the same books.