01
Reads state
Before every disbursement
Classification, W-8BEN, signed agreement, sanctions, tax. All checked.
For finance, AP, and compliance partners
The payout waits until every compliance gate is green
Every payout run checks classification, W-8BEN, signed agreement, sanctions clearance, and tax readiness before release. Any gate is red? The payout holds with a reason code. State unreadable? The payout waits. Finance and compliance see the same record.
Reads five AoR gates before releaseReason code on every held payoutThe payout waits when state is unreadableMaker-checker override path
Operating tokens
What payout holds on Gruv look like
02
Reason-coded
On every hold
Owner, action path, and reason attach automatically.
03
Payout waits
When state is unreadable
The payout holds. Nothing moves blind.
04
Override-aware
Maker-checker path
Second approver and reasoning recorded on the engagement.
Hold by default
When state is unreadable, the payout holds
Finance, compliance, and ops look at the same record. AoR derives hold state from the readiness record, so the payout run reads engagement truth before release. If state is unreadable, nothing moves.
- Reason code attaches to every blocked release.
- Override path records the second approver.
- Retry-safe replays respect existing holds.
- No silent disbursements when state is missing.
Unreadable state blocks release
The readiness record is unreadable for an engagement? Payout creation stops. The run prefers a paused release over a payout going out without compliance context.
Why it matters
No release without engagement truth
Audits stop asking why a payout went out when the readiness record was empty. Override path records the second approver if finance still needs to push.
Six controls behind every release decision
Each control writes state to the engagement and the run. Audits never reconstruct intent from log files.
Reads five AoR gates before release
Classification, documents (W-8BEN, passport), signed agreement, tax readiness, and sanctions clearance. All checked on every payout run.
Reason code on every hold
Held releases carry the reason code, owner, and action path. The next person picking up the run knows exactly what to fix.
The payout waits when state is unreadable
AoR state unreadable? Payout creation stops. The run prefers a paused release over a payout going out without compliance context.
Concentration threshold triggers
A US contractor crosses 80% revenue from one client. Payout concentration change triggers reassessment and a downstream hold before the payout goes out.
Maker-checker overrides
Finance needs to push? Override requests pass through a second approver. Decision and reasoning record on the engagement.
Retry-safe behavior
Retries replay the same payout intent. Held releases stay held until the underlying gate clears. No duplicate disbursements.
How it works
How a payout decision moves through the gate
Four steps. The hold or release decision is reproducible from the engagement record.
gruv.app › payouts › release gates
payoutseng_3f4agates
Cleared for releaseEngagement state read
Pending payout
$8,500.00 · USD
pyt_8a91 · scheduled 2026-05-15T18:00Z
EligibleWithin policy
Five gates5 / 5
Classification fresh
expires 2027-05-04
Documents complete
Signed paper attached
aor_3f4a
Tax readiness
W-9 + DE-4 on file
Sanctions re-screen
cleared 2026-05-03
Hold operations
Stop releases before AoR state can be read.
Payout runs read AoR hold state on every disbursement. If a required gate is blocked, the run pauses with a reason code. If the hold summary cannot be read at all, payout creation stops rather than guessing.
- Hold reasons attached to every blocked release
- Failure-to-read state stops payout creation outright
- Concentration and threshold changes flagged before money moves
Hold log
Run #PAY-2026-05-24
Aria Patel
TXN-7711 · Coverage active, paper signed
£2,450.00Released
Mason Lee
TXN-7712 · Insurance proof expired 02 May
£4,500.00Held
Studio Pink
TXN-7713 · Coverage suspended after recheck
HK$4,883.50Review
Missing classification
Documents expired
Unsigned or stale paper
Coverage suspended
Four hold paths every payout reads
Holds derive from the engagement record. Each path carries the gate, the owner, and the action.
Classification hold
Assessment missing or stale
Your German contractor's classification expired last month. The payout holds until the recheck completes and a fresh result binds.
Document hold
W-8BEN or right-to-work blocked
W-8BEN expired? Indian right-to-work rejected? The payout holds until the document is resubmitted and approved.
Paper hold
Agreement unsigned or stale
Signed agreement is stale after reclassification. The payout holds until a refreshed agreement countersigns via DocuSign.
Coverage hold
Coverage suspended or out of scope
Coverage is suspended or no longer in scope for the launch program. The payout holds until coverage is restored.
Where payout hold controls earn their keep
Teams reach for AoR holds when bad releases show up in finance reviews, audit findings, and compliance escalations.
Compliance-led payout controls
Replace ad-hoc finance pauses with reason-coded holds tied to W-8BEN status, classification, and signed agreements.
Programs spanning the US, UK, Germany, India
Apply consistent hold rules across every market while honoring jurisdiction-specific overlays.
Audit-driven finance reviews
Give auditors hold reasons, owners, and action paths attached to every paused release. No spreadsheet archaeology.
High-volume contractor runs
Pay 500 contractors in one batch. Each disbursement reads the readiness record before release. Compliant ones flow. Held ones wait.
After payout holds
Keep watching the engagement after activation
Germany updates its rules. A right-to-work expires. A payout concentration threshold crosses. Monitoring re-runs classification and holds read the new signal.
Frequently Asked Questions
What happens when AoR state is unreadable?+
Money waits. If the readiness record is unreadable for an engagement, payout creation stops. The system prefers a paused release over a payout that ignored compliance state.
What reasons can hold a payout?+
Expired W-8BEN, missing classification, stale signed agreement, failed sanctions screening, suspended coverage, and beneficiary verification failure. Each hold carries a reason code attached to the payout.
Who clears a hold?+
Hold ownership follows the gate that triggered it. Compliance reviews classification holds. Program ops handles W-8BEN and document holds. Finance reviews beneficiary and policy holds. The action path records with the hold.
Can finance override a hold?+
Yes, through a maker-checker path. A second approver reviews the request. The approval, rejection, and reasoning record on the engagement and the payout run. Nothing lost to email.
How do retries interact with holds?+
Retries respect the hold state. A previously held release stays held until the underlying gate clears. Retries replay the same intent. No duplicate disbursements.
Ready to scope payout hold controls?
Bring your payout schedule, hold owners, and override approvers. Gruv scopes the reason codes and recovery paths your team needs before the first batch releases.
Many teams start with a narrow launch in weeks.