[$250] Bank - Partially set up bank account is not visible when business BA already exists.

[jponikarchuk]

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: V9.3.53-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-16382/folder/43918362/97878675/1309880636
Email or phone of affected tester (no customers): dreamnitethedragon+vegst@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: Workspace Settings

Action Performed:

1. Launch app
2. Add a VBA ( Region Bank ending 1111)
3. Add a member with admin role
4. Go to wallet - Add BA - Make payment - United states - Login bank
5. Add a business bank account with ( Region Bank ending 0000) and exit the steps after reaching personal information page [ first name as first and last name as last]
6. Note in wallet page, bank account with action required badge is shown
7. Go to workspace - workflows - payments
8. Tap bank account and note partially added bank set up is not shown

Expected Result:

Partially set up bank account must be visible even when business BA already exists.

Actual Result:

Partially set up bank account is not visible when business BA already exists.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @shubham1206agra

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022043743578183974847
• Upwork Job ID: 2043743578183974847
• Last Price Increase: 2026-04-20

[MelvinBot]

Proposal

What is the root cause of that problem?

The Workspace > Workflows > Payments section in WorkspaceWorkflowsPage.tsx:256-267 is designed to display only one bank account. It uses a two-step lookup:

1. Check if policy.achAccount is fully set up (state OPEN or LOCKED)
2. Fall back to searching bankAccountList for an entry where additionalData.policyID matches the current workspace

When a verified bank account already exists, isBankAccountFullySetup is true, so shouldShowBankAccount is true and the page renders a single MenuItem for that verified account. There is no code path to also display a second partially set up account — the page was built for a single-account model.

The partially set up account (state SETUP) either:

• Has no additionalData.policyID yet (policyID is assigned later in the setup flow), so even the fallback lookup can't find it
• Or has a different policyID, so it doesn't match this workspace

Meanwhile, the Wallet page shows it because formatPaymentMethods() iterates over all entries in bankAccountList with no state or policy filtering, and PaymentMethodListItem adds the "action required" badge via isBankAccountPartiallySetup().

What changes do you think we should make in order to solve the problem?

In WorkspaceWorkflowsPage.tsx, after the existing bank account lookup logic, add a secondary check for any partially set up bank account linked to this workspace (via additionalData.policyID). When both a verified account and a partially set up account exist for the same workspace, render both — the verified account as the connected bank, and the partially set up account as an additional item with the "action required" badge (using the existing getBadgeText logic at line 275).

Alternatively, if showing two accounts in the single-account UI is too disruptive, at minimum the bankAccountConnectedToWorkspace lookup should also consider accounts in SETUP/VERIFYING/PENDING states (currently it finds the first match via .find() but doesn't prioritize showing accounts that need user action). The partially set up account should be surfaced with its "action required" badge so the user knows to complete setup.

What alternative solutions did you explore? (Optional)

An alternative would be to change the "Add bank account" button flow. Currently, hasValidExistingAccounts (line 137) is computed with shouldIncludePartiallySetup=true via getEligibleExistingBusinessBankAccounts(), but this is only used when shouldShowBankAccount is false (i.e., when no bank account is connected yet). This path is never reached when a verified account exists. However, reworking just the button flow wouldn't solve the visibility problem — the user needs to see the partially set up account without having to tap "Add bank account."

Related issues

• [Due for payment 2026-04-23] [Due for payment 2026-04-20] Initial page shows log in/connect button instead of Continue setup for partially set up bank #87610 — "Initial page shows log in/connect button instead of Continue setup for partially set up bank" (related partial-setup UX issue)

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (External)