01
Configured
Hold states
Your program defines when a hold should be recorded.
For compliance, operations, and finance teams
Give every configured payout hold a reason
Define the hold states your program uses, record why an engagement is held, and assign the review. Finance can see the owner, current status, and decision context before a release handoff.
Configured hold statesReason recordedReview owner assignedFinance decision context
Payout hold record
Engagement ENG-9824
- Hold status
- Under review
- Owner
- Finance operations
- Reason
- Document status review
- Next step
- Record decision
A finance-readable hold record
The context behind a payout decision
02
Reasoned
Hold context
The record explains why finance should pause.
03
Assigned
Review owner
The team can see who owns resolution.
04
Recorded
Release review
The decision and reviewer notes stay with the hold.
What the hold record carries
Payout review without missing context
Make the hold, its owner, and the release decision legible to compliance, operations, and finance.
Configured hold state
Use the hold statuses and policy reasons your payout program defines.
Reason and source
Record why the hold was added and which engagement status informed it.
Resolution owner
Assign the team responsible for gathering context or resolving the issue.
Current status
Show whether the hold is open, under review, retained, or cleared by the responsible team.
Release review
Record the reviewer, decision, reason, and notes before the finance handoff.
Finance handoff
Give finance the reviewed hold status and the context behind the decision.
A hold workflow finance can trace
Your payout policy defines the hold conditions and who may clear them. Gruv keeps that work on the record.
01
Record
Add the configured hold state and its reason to the engagement.
02
Assign
Give the hold to the team responsible for resolution.
03
Review
Save the decision, reason, and reviewer notes.
04
Hand off
Share the reviewed hold status with finance.
Where configured payout holds help
Use the record when finance needs more than a bare pause flag.
Incomplete engagement review
Record the hold reason and owner while another team completes its work.
Document status question
Keep the document reason and payout hold connected for review.
Finance exception review
Give finance the engagement context and named resolution owner.
Release decision record
Retain the reviewer, decision, reason, and notes with the hold.
After hold review
Keep later engagement changes in a shared queue
Send reported changes through an assigned monitoring review and carry the resulting status back to finance.
Frequently Asked Questions
What can create a payout hold?+
Your team configures the statuses and reasons that should produce a hold record under its payout policy.
Who owns a hold?+
The record can assign the compliance, operations, or finance owner responsible for the next review step.
What is recorded when a hold is reviewed?+
The record can retain the reviewer, decision, reason, notes, and resulting hold status.
What does finance receive?+
Finance receives the reviewed hold status and the context behind the decision as part of its release workflow.
Scope payout holds around your policy
Bring your hold states, reason codes, resolution owners, release reviewers, and finance handoff needs. We will use them to map the workflow.
Many teams start with a narrow launch in weeks.