Skip to main content
Gruv.ai logo
Mass payments

From your payout list to each payment’s result

Keep the run together as individual payments move forward. Import the list, review the next steps and give finance a clear result for every item.

Talk through a payment runFollow one payment run
Colleagues reviewing work together at their laptops
Your team prepares the run. Each payment keeps its own result.

September · RUN-214

Follow the list through to its results

Your team has approved three payments totaling USD 1,300. Import the recipient IDs, amounts and source references, then keep the same run in view as the payments move forward.

What if a row fails the import checks?

The import returns the line, field and error. Correct the source and submit it again. A file with validation errors does not become a partly imported run.

  1. Imported

    Three items · USD 1,300

    The list is staged with its original references. Importing has not sent the payments.

  2. Process the run

    Create the payment records

    Processing connects each imported item to a payment. Complete any required approval and execution steps before following the payment result.

  3. Review the result

    Keep each item in view

    A completed payment and a failed payment remain separate results, even when they started in the same list.

The run is finished. One payment still needs follow-up.

RUN-214 now has two completed payments and one failed payment. Finance can see what happened to the full USD 1,300 without treating the whole amount as paid.

Maya RaoINV-214-A

USD 600

Completed

Jon BellINV-214-B

USD 450

Completed

Lena OrtizINV-214-C

USD 250

Failed

Instructed
USD 1,300
Completed
USD 1,050
Failed
USD 250

Keep INV-214-C with the follow-up

Open the failed payment’s reason and explanation before deciding the next step. Export the current results with the source references so finance can distinguish the USD 1,050 completed from the USD 250 that needs attention.

Will processing the run again retry the failed payment?

No. Processing creates payment records for items that still lack one. It does not retry an already linked failed payment. Review that payment separately and agree the appropriate follow-up.

More in Mass Payouts

Explore more in Mass Payouts

Payout risk review

Review payout decisions and the items that need attention before execution.

Payout review

Inspect a payment’s source reference, current status and reason details.

Tax readiness

Confirm which recipient and tax information your workflow needs before preparing a payout.

Frequently Asked Questions

Does importing a batch send the payments?+
No. Importing stages the items. Processing creates the payment records, and required approval or execution steps still apply before you follow the payment result.
What do we include in the payout list?+
Include the beneficiary ID, amount and currency, with an external reference or memo when useful. Use the template for your import path: the portal CSV uses amounts in the currency’s smallest unit, while the public API uses decimal amounts.
Can a finished batch include failed payments?+
Yes. When every payment has reached a final status, the batch can be completed with failures. Review individual results before treating an amount as paid.
What can finance download?+
The current CSV result includes source fields, payment status, reason codes and explanations. Keep the original reference with each item when following up on a failed payment.

Plan a payment run your team can follow

Talk through your payout list, review steps and finance records. We’ll help map the workflow for your team.

Talk through a payment run