Reads AoR state before release
Every disbursement reads the engagement readiness record. Holds are computed from gate state, not free-form notes.
For finance, AP, and compliance partners
Release money only when AoR state is readable.
Payout runs read AoR hold state before disbursement, attach reason codes to every paused release, and fail closed when the readiness record cannot be read.
Reads AoR stateReason codes on holdsFail-closed behaviorMaker-checker overrides
The control point
Holds belong on the engagement, not in someone’s inbox.
Payout holds keep finance, compliance, and ops looking at the same record. AoR derives the hold state from the readiness record so the run reads engagement truth before money moves.
- Hold reasons attached to every blocked release.
- Fail-closed behavior when state is unreadable.
- Override path that records the second approver.
- Retry-safe replays that respect existing holds.
Classification hold
Engagement assessment is missing, expired, indeterminate, or returned a stop outcome.
Document hold
A required launch-country document or registration is missing, expired, or rejected by reviewer.
Paper hold
Signed agreement is unsigned or stale after reclassification or rule update.
Coverage hold
Coverage is suspended, ineligible, or no longer in scope for the launch program.
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
Six controls behind every release decision.
Each control writes state to the engagement and the run, so audits never have to reconstruct intent from log files.
Reason codes on every hold
Held releases carry the reason code, owner, and action path so the next person picking up the run does not start from zero.
Fails closed on unreadable state
If AoR hold state cannot be read for an engagement, payout creation stops rather than moving without compliance context.
Concentration and threshold signals
Payout concentration changes can trigger reassessment and downstream holds before money moves.
Maker-checker overrides
Override requests pass through a second approver with the decision and reasoning recorded against the engagement.
Retry-safe behavior
Retries replay the same payout intent. Held releases stay held until the underlying gate clears.
Where payout hold controls earn their keep.
Programs reach for AoR holds when the cost of a release that should not have happened keeps showing up in finance reviews and audit findings.
Compliance-led payout controls
Replace ad-hoc finance pauses with reason-coded holds tied to engagement state.
Programs spanning launch countries
Apply consistent hold rules across markets while honoring jurisdiction overlays.
Audit-driven finance reviews
Give auditors hold reasons, owners, and action paths attached to every paused release.
High-volume contractor runs
Process bulk payouts knowing each disbursement reads the readiness record before release.
After payout holds
Keep watching the engagement after activation.
Monitoring re-runs classification on expiry, law update, payout concentration change, and assessment update. Holds read that signal too.
Frequently Asked Questions
What does it mean to fail closed?+
If the AoR hold summary cannot be read for an engagement, payout creation stops rather than guessing. The control prefers a paused run over a release that ignored compliance state.
What reasons can hold a payout?+
Pending classification, missing or expired documents, unsigned or stale paper, ineligible coverage, suspended coverage, and policy or beneficiary state failures can all hold release. 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 documents and paper, finance reviews policy and beneficiary holds. The action path is recorded with the hold record.
How do concentration changes interact with holds?+
Payout concentration threshold changes can trigger reassessment. AoR records the trigger, requests a recheck, and can hold downstream releases until the recheck completes.
Can finance override a hold?+
Override requests follow a maker-checker path with a second approver. The approval, rejection, and reasoning are recorded against the engagement and the run rather than being lost to a thread.
How does this interact with retries?+
Retries respect the hold state. A previously held release stays held until the underlying gate clears. Retries are designed as replays, not duplicate disbursements.
Ready to scope payout hold controls?
Bring your payout runs, hold owners, and override approvers. Gruv can scope the reason codes and recovery paths your team needs before money moves.