The FinOps page in Manage → Organization → FinOps is the dedicated operator workflow for payment and payout follow-through.
It builds on the Finance board, but it is designed for active operations work rather than passive monitoring.
Use it when you need to:
- work blocked payouts
- monitor retry backlog
- review payout-readiness blockers
- assign ownership to a finance issue
- add operator notes to an issue
- open the employee's Stripe account details directly from the work item
What the Workbench Shows
The page combines four types of information in one place:
- Payout Queue - blocked, retrying, and transfer-ready payout items
- Account Readiness - employee payout blockers such as missing wallets or incomplete onboarding
- Signals Snapshot - current finance alerts and rolling SLO health
- Operator History - audit notes and recent actions taken by operators
Payout Queue
The Payout Queue section is where finance teams triage payout execution problems.
Each payout item includes:
- employee and property context
- amount at risk
- current queue state
- retry count
- next retry timing when applicable
- the most recent error or failure class
- current case assignment, if one exists
Queue states
| State | Meaning |
|---|---|
| Blocked | Automatic recovery is exhausted or the payout has a hard blocker |
| Retrying | A retry is still scheduled or in progress |
| Ready | The dividend is transfer-ready but still uncompleted |
Account Readiness
This section surfaces the employee-side blockers that often explain why payouts fail.
It highlights issues such as:
- missing linked users
- missing wallet records
- missing Stripe account IDs
- incomplete onboarding
- missing bank accounts
- inactive Stripe capabilities
Action Console
When you select a work item, the Action Console lets you take controlled operator actions.
Available actions
| Action | What it does |
|---|---|
| Acknowledge | Marks the issue as seen and records who acknowledged it |
| Assign To Me | Takes ownership of the case using your operator identity |
| Assign To | Assigns the issue to a named operator |
| Add Note | Writes an audit note into the issue history |
| Retry Now | Triggers an immediate payout retry for payout queue items |
| Open Stripe | Opens the employee's connected Stripe account details in a new tab |
Operator History
Every assignment, note, acknowledgment, retry result, and Stripe-open action is written to the operator history stream.
This gives finance teams a lightweight audit trail without needing to reconstruct actions from chat or memory.
Use this history when:
- handing work from one operator to another
- checking whether a payout was already reviewed
- confirming whether a retry was manual or automatic
- documenting why a payout stayed blocked
Recommended Workflow
- Start with Blocked payout items.
- Check whether the blocker is queue-related or readiness-related.
- Open the related Stripe account when the issue appears to be banking or capability based.
- Add a short note before handing off or escalating.
- Assign ownership so the same issue does not get worked twice.
When to Stay on the Finance Board Instead
Use the standard Finance page when you want portfolio-wide visibility and trend monitoring.
Use the FinOps page when you are actively working operational issues and need assignments, notes, retries, and history.