A bad row is hard to find
Missing beneficiaries, malformed amounts, and incomplete currency fields are easy to miss in a long payout file.
Overview
Catch payout problems before you send
Upload a CSV or send the batch through the API. Check required fields and beneficiaries, review the draft, process accepted rows, and export the results.
CSV or API intakeRow-level validationStatus and CSV export
Payout batchstaged
Batch review
Ready to review
Uploading creates a draft before payouts move forward.
Source rows
ImportedRequired fields
CheckedBeneficiaries
CheckedProcess the batch
NextReady for the next step
Process batch
Where batch payouts stop being simple
Import and release get mixed together
Uploading data should not silently release money. Operators need a clear step between a staged batch and payment processing.
Finance loses the item-level story
A batch total is not enough when someone needs the source reference, payout status, or reason an item needs attention.
Batch flow
One batch from upload to results
Keep each imported row with its payout status and reason, from the original upload through the current CSV result.
Upload CSV or send from your system
Start with a CSV containing the beneficiary, amount, and currency, or send the batch through the API.
Catch invalid rows
Find missing fields, invalid values, and beneficiary references that do not match.
Review before sending
Uploading creates a draft. Someone must process it, and approval may also be required before payouts move forward.
See status and export results
Review each payout status, reason code, and explanation, then download the current results as CSV.
How it works
From payout file to current results
More in Mass Payouts
Explore more in Mass Payouts
Payout risk review
See which payout instructions need attention, understand the reason, record the decision, and execute only approved item
Batch review
Review payment-run status, inspect individual payouts and reason codes, take the actions available to you, and download
Tax readiness
See which payees need tax information, what is holding them up, and what to do next before you prepare a payout.
Frequently Asked Questions
Which fields does a payout batch need?+
A CSV needs a beneficiary, amount, and currency. You can also include an external reference and memo for each payout.
Does importing a batch release payments?+
No. Import creates a draft batch. An operator must process it, and approval or execution may still apply before payouts move forward.
What happens when the import finds an issue?+
Gruv returns the CSV line, field, and error message instead of silently creating an incomplete item. Correct the source data, then submit the batch again.
What is included in the batch export?+
The CSV can include the source line, external reference, beneficiary, amount, currency, memo, current status, reason codes, and status explanation.
Next step
See where Gruv fits
Tell us what you are trying to do, where it needs to work, and how your team handles it today.
Contact the team