Skip to main content
Gruv.ai logo
Universal connectors

Turn your payout export into a usable batch

Bring recipient IDs, amounts and references into Gruv through CSV or structured imports. Check the data before moving the batch into payout processing.

Talk through payout setupFollow the import fields
A professional working with a laptop and printed records
The payout run starts with the records your team already prepares.

Keep the meaning of each field

Northstar is preparing Maya’s September commission. Its export says USD 1,500. The import needs the recipient’s ID, the amount in the right units and a reference finance can trace.

Northstar · September commission · Portal CSV

Recipient in your export
Maya Rao
beneficiary_id
ben_maya_01

Use the ID of Maya’s existing Gruv beneficiary record.

Amount in your export
USD 1,500.00
amount_minor
150000

The portal CSV uses minor units: 1,500 dollars × 100 cents.

Currency in your export
US dollars
currency
USD

Keep the currency code beside the amount it describes.

Source reference in your export
September commission 041
external_ref
COMM-SEP-041

Keep a reference that leads back to the source record.

Prepare the file against the CSV template. The optional memo field adds context for your team.

Resolve the error before the import

A missing beneficiary ID leaves the recipient unresolved. If validation finds invalid input, the import is rejected before the batch is saved. Correct the source and submit it again.

See how to correct the recipient field

Find Maya’s existing beneficiary record and place its ID in beneficiary_id. If she has no record yet, complete recipient setup first.

Recheck the amount and currency, then resubmit the corrected file. The rejected import has not saved the other rows as a partial batch.

After the corrected import succeeds

The batch is imported

IMPORTED

The records are staged for the next step. Review the batch, then start processing through a separate action.

An imported batch is still awaiting processing. Follow the resulting payout records to check payment progress.

More in Payouts

Explore more in Payouts

Payout automation

Continue from imported records to the decisions that start a payout run.

Vendor portal

Keep recipient details ready for the next payout batch.

Accounts payable

Connect invoice preparation with the review that comes before payment.

Frequently Asked Questions

Which import formats can we use?+
Use the portal CSV template for file uploads. Structured items[] imports provide a programmatic path. Confirm the endpoint and amount format for your integration during setup; the worked example here uses the portal CSV format.
Can we import recipient names instead of IDs?+
The payout CSV requires an existing beneficiary ID. Match each source recipient to their Gruv record before importing. A name in a spreadsheet alone does not identify the payout recipient.
What if our source export changes?+
Check the changed columns against the import template before the next upload. Recheck recipient IDs, amount units and currency codes together, then correct the source file before importing.
Is there a native connector for our accounting system?+
Connector availability and field mappings are confirmed during setup. Tell us where payout records live and how your team prepares a run so we can agree the import path.

Connect the source to your payout workflow

Tell us where your payout records live. We’ll work through the import path, recipient setup and review steps with your team.

Talk through payout setup