The Finance Board (Manage → Organization → Finance) now includes a Payout Readiness section that scans employee payout accounts across the selected organization.
This view is designed for operators who need to answer three questions quickly:
- Which employees are fully payout-ready?
- Which employees need follow-up before they can withdraw?
- Which records can Aplauso repair automatically without manual cleanup?
What the Readiness Scan Checks
For each employee in scope, Aplauso checks:
- Whether the employee is linked to a user account
- Whether a live or sandbox wallet record exists
- Whether the wallet has a valid Stripe Connect account ID
- Whether Stripe onboarding is complete
- Whether a payout bank account is connected
- Whether Stripe payouts are enabled
- Whether Stripe transfer and payment capabilities are active
Readiness States
| State | Meaning | Typical Next Step |
|---|---|---|
| Ready | Wallet exists and Stripe account is payout-ready | No action needed |
| Needs Attention | The employee has a wallet, but onboarding or banking is incomplete | Ask the employee to finish Stripe setup |
| Blocked | A hard blocker exists, such as no linked user or Stripe disabling payouts | Manual operator follow-up required |
Common Blockers
You may see tags such as:
- No linked user account
- Wallet not provisioned
- Stripe account missing
- Wallet needs recreation
- Stripe onboarding incomplete
- Bank account missing
- Payouts disabled in Stripe
- Transfers capability inactive
These tags come directly from the current wallet record and Stripe account state.
Provision Missing Wallets
The Provision Missing Wallets action is intended for legacy cleanup and self-healable account gaps.
When you run it, Aplauso will only attempt safe remediation for employees who:
- already have a linked user account, and
- are missing a wallet record, missing a Stripe account ID, or need a wallet recreated
It does not bypass Stripe onboarding and it does not repair employees who are not linked to a user account.
Property Hotspots
The left side of the section groups readiness issues by property so regional operators can see where the concentration of payout blockers is highest.
Use this when:
- onboarding a newly launched property
- cleaning up older records after data migration
- checking whether a portfolio is ready before going live
Employee Blockers
The blocker list shows each affected employee with:
- employee name
- property name
- current severity (Attention or Blocked)
- whether the issue is auto-provisionable
- the exact readiness tags for that employee
Operational Guidance
Use auto-provision first for missing wallets and recoverable legacy account gaps.
Use manager follow-up when onboarding is incomplete or the employee has not linked a bank account.
Escalate to support or operations when Stripe has disabled payouts or the employee record has no linked user account.