Reports - No connected bank account list when selecting Pay with business account on Reports

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.2.20-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from TestRail: #69437
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• User has a workspace connected to business bank account.

1. Go to staging.new.expensify.com
2. Create a new USD workspace.
3. Go to workspace chat.
4. Create an expense in workspace chat.
5. Click Submit and Approve.
6. Click Pay button.
7. Click Pay with business account.
   → Existing connected bank account list opens.
8. Close the RHP.
9. Go to Reports > Expenses.
10. Click Pay button.
11. Click Pay with business account.

Expected Result:

Existing connected bank account list will open when selecting Pay with business account on Reports.

Actual Result:

Bank account setup opens when selecting Pay with business account on Reports.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6959908_1759189521494.Screen_Recording_2025-09-30_at_07.42.10.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @zanyrenney (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

Triggered auto assignment to @Beamanator (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[dominictb]

cc @MrMuzyk We missed this case.

[MrMuzyk]

Looking into this