The batch surface in the current product is called Payment Runs. A run begins with a CSV that references existing beneficiaries. Uploading the file creates the batch record; processing, approving, and executing eligible disbursements are separate actions controlled by workspace availability and permissions.
Create beneficiaries before the CSV
Open Finance > Beneficiaries and create the destination records needed by the run. A talent ID or email is not a substitute for a beneficiary ID. The upload screen rejects a new client account until the referenced beneficiaries exist.
Use the exact CSV fields
Download the template from the upload dialog. Its header is beneficiary_id,amount_minor,currency,external_ref,memo. Enter the amount in the currency's smallest unit: for example, 150000 represents 1,500.00 USD. Keep the file in CSV format, include at least one data row, and keep it within the 1 MB upload limit.
Upload and inspect the run
- Open Finance > Payment Runs and choose Upload CSV.
- Select the active team when requested, then upload the completed template. Only users with the available Payment Runs capability can upload the file.
- Open the run. Review each row's beneficiary ID, amount, currency, reference, memo, status, status explanation, and reason codes.
- If the run is Imported and the action is available, choose Process Batch. Processing evaluates the uploaded rows and creates the next item states.
Keep approval and execution separate
- Pending approval means an approver decision is still required.
- Approve or Approve all is shown only when the role can approve those items.
- Approved means the item is eligible for a separate execution action.
- Execute approved initiates real payments and requires an explicit confirmation. Do not treat Process Batch as execution.
- Held, failed, or completed-with-failures items need their displayed reason or explanation reviewed before another attempt.