Use safe non-production guide accounts to verify request creation, the SettleWise notification, and both resolution paths without exposing private data.
Before you start
- Guide
- A sample guide with an active season account
- Finance
- A reviewer with an active USD funding source and the guide's debt account
Run the scenario
- 1GuideTrailhead Mobile · Profile > Account > Request personal advance
Submit a safe USD amount and reason once, then return to Account.
Expected evidence
The guide receives confirmation, the pending card appears, the request-history badge increases, and no account movement or debt is created yet.
- 2AccountsSettleWise · Notifications and Payouts > Guide Advances
Open the unread notification and locate the request in the table.
Expected evidence
The notification opens the actionable request and Fund and Reject are available with the correct request details.
- 3AccountsSettleWise · Payouts > Guide Advances
Fund the request using the default bank-transfer method and confirm the body summary.
Expected evidence
The request becomes Funded, its pending mobile card disappears, and a USD payout and guide-debt movement are recorded separately from earnings and expenses.
- 4AccountsSettleWise · Payouts > Guide Advances
With a separate safe request, choose Reject and confirm the standard rejection dialog.
Expected evidence
The request becomes Rejected, its pending mobile card disappears, and no payout or financial movement is created.
Scenario completed
Finance has funded or rejected the request.
- Advance request
- Not submitted→Requested with no financial movement
- Advance request
- Requested→Funded with guide debt recorded
- Advance request
- Requested→Rejected with no financial movement
If it does not match
- Do not fund when the USD funding source or the guide's debt account is missing; resolve that setup before retrying.
- After an ambiguous timeout, reopen Guide Advances and Account movements before taking the action again.