Creator payout · PAY-248
Contractor payout
- Recorded reason
- No current signed agreement
- Payout status
- HELD
- Execution
- Blocked · Approved status required
Held is a payment stop. It is not a completed review or a release decision.
AoR payout readiness
See why an AoR payout stops before execution
Gruv copies the workspace’s AoR readiness reasons into the creator payout. When no separate payout override applies, a copied reason can put the payout in Held. Execution stays closed unless its status reaches Approved.
Held
PAY-248 · Worked payout
One readiness reason changes the payout path
The reason is copied from the workspace readiness summary when the payout is created. Gruv checks it before ordinary payout approval rules.
- 01
Readiness reason
No current signed agreement
The workspace summary returns the fixed agreement reason.
- 02
Payout decision
Status becomes Held
The recorded AoR reason is evaluated before the ordinary approval policy.
- 03
Execution boundary
Execution request is rejected
The payout must have Approved status before execution can begin.
Fixed AoR readiness reasons
Read the reason behind the stop
The workspace summary uses a fixed set of AoR reason codes. They describe unfinished engagement or coverage work.
The summary can combine reasons across AoR-managed engagements. Creating this payout then requires exactly one linked engagement for tax readiness; zero or multiple matches fail before the payout is created. The resulting payout reason set does not identify which engagement contributed each reason and has no engagement ID.
Engagement readiness
- AOR_CLASSIFICATION_PENDING
- Classification is not complete
- AOR_DEPENDENT_CONTRACTOR_REVIEW
- Dependent-contractor review is still open
- AOR_DOCUMENTS_MISSING
- Required documents are still missing
- AOR_CONTRACT_UNSIGNED
- There is no current signed AoR agreement
Coverage readiness
- AOR_COVERAGE_INELIGIBLE
- Classification coverage is not eligible
- AOR_COVERAGE_SUSPENDED
- Classification coverage is suspended
- AOR_INSURANCE_NOT_BOUND
- Required insurance coverage is not bound
After engagement evidence changes
Fixing the cause does not rewrite the held payout
A current agreement can improve a later readiness summary. The existing payout still carries the reason set copied when that payout was created.
Engagement evidence
Current agreement signed
A later workspace readiness summary can reflect the resolved agreement requirement.
Existing payout
Reason still recorded
The payout keeps the agreement reason; unchanged reasons can return it to Held when release checks run.
Changed engagement evidence
Why did signing not update this payout?
The readiness summary can change after a current agreement is signed, but the existing payout retains the AoR reasons copied into it when it was created.
Existing payout check
What happens if a hold release is requested?
The release path reruns payout checks using the existing payout information. If the agreement reason remains recorded there, the payout can return to Held.
Next review
What should operations review next?
Review the updated engagement evidence and the existing held payout with Gruv before another execution attempt.
AoR payout hold questions
What puts an AoR payout in Held?+
Fixed AoR readiness reasons copied from the workspace summary can place a creator payout in Held before ordinary approval rules, when no separate payout override applies.
Are AoR hold reasons configurable?+
The AoR readiness summary uses a fixed reason set for classification, dependent-contractor review, required documents, a current signed agreement, coverage and insurance.
Is the hold tied to one engagement?+
The summary evaluates all AoR-managed engagements and can combine their reasons. The payout carries that combined set without a specific engagement ID. Creating this payout then requires exactly one engagement with client and worker identity links for tax readiness; otherwise it fails before creating the payout. This example uses that single-engagement case.
Can a Held payout execute?+
No. Payout execution requires an Approved disbursement. An execution request for a Held disbursement is rejected before the payment can proceed.
Does fixing the engagement release the existing payout?+
No. Updated engagement evidence can change a later readiness summary, but the existing held payout keeps the AoR reasons recorded when it was created. Review the updated evidence and the existing payout with Gruv.
Plan the AoR payout check
Plan the hold check
Review the enabled AoR payout path, readiness inputs and the operational response when a payout is Held.