Skip to main content
Gruv.ai logo
Payout automation

Keep approved payouts moving. Know what needs attention.

Use a configured workflow to execute eligible approved payments and follow provider updates. Keep holds and payment errors visible for the person who can resolve them.

Discuss your payout routineFollow a payout run

September run · USD 3,000 requested

USD 1,500

Approved

Ready for execution

USD 600

Held

Review required

USD 900

Processing

Awaiting provider update

One run. Three different next steps.

With the execution workflow enabled, eligible approved payments can move forward. A held payment still needs review, while a processing payment needs a provider update.

This run contains USD 3,000 in requests. The amount requested does not tell you how much has reached recipients.

  1. Maya Rao · USD 1,500

    Approved

    Execute the eligible payment through the configured payment path. Approval alone does not confirm delivery.

  2. Jon Bell · USD 600

    Held

    Resolve the screening review before taking the next payment step. The execution workflow does not clear the hold.

  3. Lena Ortiz · USD 900

    Processing

    Follow the provider status using the payment reference. Delivery has not yet been confirmed.

Decide what needs another attempt and what needs a correction

A temporary request failure and invalid payment details need different responses. Keep the reason with the payment so the next action is clear.

Retryable request

The configured workflow limits each request’s retry attempts and adds a delay between them. Each retry still needs a successful response before the payment can move forward.

Invalid request

An invalid execution request is excluded from automatic execution attempts. Review and correct the details before resuming the payment process.

What if the provider reference is invalid?

Status polling can also stop on an invalid request. Check the provider reference and resolve the error before resuming status checks. A missing update does not confirm payment delivery.

More in Payouts

Explore more in Payouts

Universal connectors

Check recipient IDs, amounts and references before processing an import.

Vendor portal

Let payees maintain their details and follow their payment status.

Accounts payable

Carry invoice decisions and source references into payment preparation.

Frequently Asked Questions

What needs to be configured before automation runs?+
Agree the account, supported execution path, approval steps and follow-up process during setup. The execution workflow must be enabled for the account before it can move eligible payments forward.
Can we schedule our payouts?+
Scheduling depends on the workflow and payment setup. Confirm the available cadence, preparation steps and release requirements for your account before committing to a payout calendar.
Will every failed payment be retried?+
No. Retryable requests use bounded retry rules. Invalid execution requests or invalid provider references need correction and review; repeatedly sending the same invalid request does not fix it.
Does processing mean the payee has received the money?+
Processing means the payment is still in progress. Follow the provider status and any resulting exception before treating delivery as confirmed.

Build a payout routine your team can follow

Talk through your approval steps, execution setup and the exceptions that need a person’s attention.

Discuss your payout routine