Mass payouts: paying your whole contractor base in one batch

When you have five contractors, paying them one by one is fine. When you have fifty, it is an afternoon lost to copying account details and a real chance of a typo. Mass payouts solve this by letting you send many payments together as a single batch instead of one transfer at a time.

This guide covers how batch payouts work, the file-upload and API routes, sending different currencies in one run, what to do when a single payment in a batch fails, and how to keep records clean enough to reconcile later.

What a batch payout actually is

A batch payout is a list of individual payments submitted together. Each line still has its own recipient, amount and reference, but you prepare and approve them as one set rather than entering each transfer by hand.

The benefit is not only speed. Reviewing one list before you send is easier to control than approving fifty separate transfers, and a single approval step gives you one clear moment to check totals before money moves. For a growing contractor base, this is the difference between payouts being a chore and payouts being a five-minute routine.

Two ways to send a batch: file upload or API

There are two common ways to get a batch into the system, and the right one depends on how you already work.

• File upload. You prepare a structured file, usually a spreadsheet or CSV with one row per contractor, listing recipient details, amount, currency and a reference. You upload it, the system checks the rows, and you approve the run. This suits most teams and needs no engineering work.
• API. If payouts are tied to something else, such as completed work logged in your own tool, an API lets you submit batches programmatically without anyone touching a spreadsheet. This suits platforms and teams that want payouts triggered by their own systems.

Many teams start with file upload and move to the API later as volume grows. The underlying batch is the same either way.

Mixed-currency batches

Your contractors are rarely all in one currency, so a useful batch lets you mix currencies in a single run. One line pays a contractor in EUR, the next in GBP, the next in USD, all from the same upload or API call.

A couple of practical points keep mixed batches clean:

• State the currency per line. Each row should say which currency it is paying in, so there is no ambiguity about what a contractor receives.
• Hold the currencies you pay out where you can. If you keep balances in the currencies that come up most, more lines pay out without a fresh conversion, and your pricing on the run is easier to read.

When one payment in a batch fails

In a large batch, the most common outcome is that nearly everything goes through and one or two lines do not, usually because of a wrong account number, a name that does not match, or a missing detail. The goal is to fix the few without disturbing the many.

• Find it. A clear payout view marks each line as sent or failed, with a reason, so you can spot the problem rows immediately rather than re-checking the whole list.
• Fix the details. Correct the recipient information for the failed line, often by checking it with the contractor directly.
• Resend just that line. Re-submit only the corrected payments. There is no need to re-run the whole batch, and the contractors who were already paid are not affected.

Treating a failed line as a small follow-up rather than a reason to redo everything keeps payouts calm even at volume.

Keeping a clear record

Every payout run is something you will need to explain later, to a co-founder, an accountant or yourself at the end of the quarter. Build the record as you go rather than reconstructing it afterwards.

Give each batch a meaningful reference, keep the file or API payload you submitted, and use a per-line reference that ties a payment back to the contractor and the work it covers. With clear references and a status on every line, reconciling a month of contractor payments becomes a matter of matching a list rather than chasing individual transfers.

How Altery fits

Altery supports batch payouts so you can pay your whole contractor base together rather than one transfer at a time, by file upload or via API as your volume grows. Batches can mix currencies, each line carries its own reference, and a clear payout view shows the status of every payment so you can find and resend any that need attention. The record stays in one place for reconciliation.

Frequently asked questions