The Finance Operations Signals section on Manage → Organization → Finance turns payout telemetry into operator-facing signals.
It is intended to answer three practical questions:
- Do we have payout issues that need attention now?
- Are payment and payout flows meeting operational targets?
- Do our internal totals still reconcile with Stripe?
Active Alerts
The alert list surfaces the highest-priority finance conditions in the current organization scope.
You may see alerts such as:
- Blocked payouts are aging
- Automatic retries are overdue
- Payout amount at risk
- Daily reconciliation drift detected
Each alert shows:
- how many records are affected
- the dollar amount at risk when applicable
- the age of the oldest affected payout if the issue is time-based
Alert severity
| Severity | Meaning |
|---|---|
| Warning | The issue is active and should be reviewed soon |
| Critical | The issue is old enough or large enough that it should be treated as an immediate operational problem |
SLO Compliance
The finance board now tracks two service-level objectives:
| SLO | Target | What it means |
|---|---|---|
| Payment Finalization | 15 minutes | How quickly tips move from creation to finalized payment state |
| Payout Completion | 6 hours | How quickly dividends move from transfer-ready to completed transfer |
For each SLO, the dashboard shows:
- the percentage of records that met the target
- how many records were eligible for the SLO window
- how many completed within target
- a health label: healthy, warning, or breached
Use this to spot operational degradation before it becomes a backlog problem.
Daily Reconciliation
The reconciliation table compares internal totals against Stripe totals by day.
It includes separate views for:
- Charges - guest payments captured through Stripe
- Transfers - employee payout transfers sent to connected accounts
For each day, the board shows:
- internal amount
- Stripe amount
- the daily delta
How to Use It Operationally
If blocked payouts are aging: Start with the Payout Readiness section to find employees with disabled payouts, missing onboarding, or missing linked users.
If retries are overdue: Treat this as a queue-health issue. A small overdue retry count is tolerable for brief Stripe disruption, but an increasing count means recovery is not keeping up.
If SLOs fall into warning or breached: Look at the specific side that degraded first:
- Payment Finalization issues usually point to webhook delivery, payment-intent handling, or charge state drift.
- Payout Completion issues usually point to blocked wallets, retry backlog, or Stripe transfer friction.
If reconciliation drift appears: Use the daily table to isolate the day where the delta started, then review recent payout issues and transfer records for that same window.
What This Section Does Not Do
The Finance Operations section is a monitoring and triage surface. It does not:
- bypass Stripe onboarding requirements
- force-complete failed transfers
- modify bank-account settings directly inside Stripe
Those actions still require follow-up through the payout readiness workflow, employee action, or Stripe account updates.