1
Upload the payouts
Add your payees, then upload a CSV with one row per payout. You can also create the batch through the API.
Mass Payouts
Prepare a payout batch before you send it
Bring contractor and vendor payments into one run. Give your team a clear list to review, keep approvals with the right people and see how each payout turns out.
Start with CSV or connect through the API.
Contractor and vendor payments
One run. A whole team counting on it.
A clear review before the payments go out.
What happens between upload and payout
The upload creates a draft. Review it, process the payment items, and complete the required approvals before execution.
2
Catch bad rows
Review the line and field for each import error, such as an invalid amount or missing payee reference. Correct the source and upload again.
3
Review, approve and execute
Check the draft totals and process the batch. Complete the required approvals, then execute eligible payments with the right permissions.
4
See results and export
Follow each payment status and review any hold or failure reason. Export the results with their original references for finance.
When someone asks “Have I been paid?”
Find their payment. Have an answer.
A batch total cannot tell you whether one contractor received their payment. Open the individual result, with the original amount and invoice reference beside it.
Completed
Use the payment result and reference to answer the payee.
Needs attention
Read the reason before correcting details or taking another action.
Ready for finance
Export row-level results to reconcile against the source invoices.
September contractor run
Every payment has a result.
USD 5,400 · 3 payments
Mason Lee
$1,800
INV-1042Completed
Asha Nair
$2,400
INV-1043Completed
Jules Rivera
$1,200
INV-1044Needs review
Follow up on the payment that needs attention. Keep the completed results for reconciliation.
A few checks before you approve
A valid upload is a good start. A complete payment list is what your approver needs.
01
Make sure nobody is missing
Compare the count and totals by currency with the payments due. An invoice left out of the file cannot show up as a failed row.
02
Keep late approvals visible
Check invoices approved after the export. Decide whether they belong in this run or the next, and let the payee know.
03
Split runs where it helps
Different paying businesses, approval owners or schedules may need separate runs. Give each run a clear owner and cutoff.
Every mass payout feature
Explore batch preparation, payment review and the records your finance team needs.
The batch, upload to export
Walk through import fields, validation, approvals and the results export. See what to check before your first run.
Payout Risk Review
See why an instruction needs attention and record the next decision.
Inside one payment run
Learn how to review payment statuses, work through held items and hand the results to finance.
Tax Readiness
See who needs tax information before you prepare a payout batch.
Payment destinations
Review the countries, currencies and payment routes your run needs.
Currency Planning
Review payout totals, balances, and FX quotes before the run.
Payout batch API
Connect your system to batch creation, processing and results exports.
Self-Billing Setup
Plan the source data, invoice review, document, and payout handoff.
Payment run questions
What is a payment run?+
A payment run groups the payouts you want to process together. It keeps the source rows, approval actions and payment results in one place. Open the run to check a payment or download its results as CSV.
Can I start with a CSV?+
Yes. Add your payees first, then use the CSV template with their beneficiary references, amounts and currencies. Include your own invoice reference and memo to make the results easier to reconcile. You can also submit a batch from your system through the API.
Does uploading a batch send the payments?+
No. Uploading creates a draft batch for review. Processing prepares its payment items; the required approvals and execution follow as separate actions. Only users with the right permissions can take those steps.
What can the team review and download?+
Review each payee, amount, currency, reference and current status. Payments that need attention include a reason code and explanation. Download the results as CSV so finance can match them against the invoices or ledger entries that started the run.
What happens if one payment is held or fails?+
Open the affected row to check its reason and the original payee details. Follow the review steps required for that item before approving or sending it again. Keep the other results in the same run so finance can see what completed and what still needs follow-up.
Which countries and currencies can we pay?+
Share the countries, currencies and payment methods your team needs. We confirm the available routes and funding requirements for your account before the first run, then include them in your launch plan.
Make the next payment run easier
Tell us who you pay and how your team approves payments. We can walk through a run together, from the first upload to the finance export.
Plan your first payment run