Expense - Bank setup page opens instead of linked account page after changing currency to USD

[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.99-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 BrowserStack: #77751
Email or phone of affected tester (no customers): applausetester+sdnsd11o@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create a USD workspace.
• Create a non-USD workspace.
• USD workspace is set up with business bank account.

1. Go to staging.new.expensify.com
2. Go to non-USD workspace chat.
3. Create an expense.
4. Click Submit and Approve,
5. Go to non-USD workspace settings > Overview.
6. Click Default currency and change it to USD.
7. Go back to non-USD workspace chat.
8. Click Pay > Pay with business account.

Expected Result:

Linked account page will open.

Actual Result:

Bank setup page opens instead of linked account page after changing currency to USD.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7046021_1768155976993.4.mp4

View all open jobs on GitHub

[melvin-bot]

@srikarparsi recently merged #77751, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

Triggered auto assignment to @brianlee-expensify (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.

[melvin-bot]

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

[melvin-bot]

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

[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.

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug (App repo)
Causing PR: #77751 - "feat: Show page to link existing account when attempting to pay" by @MrMuzyk (High confidence)
Related Issues: N/A

Recommendation: REVERT

PR #77751 introduced a bug in the KYCWall component that causes it to use the wrong currency when checking for eligible business bank accounts. When a workspace currency is changed, the code checks for existing bank accounts using the expense/transaction currency instead of the updated policy currency, resulting in the bank setup flow being triggered incorrectly.

📋 Detailed Analysis

Evidence

1. Timing: PR feat: Show page to link existing account when attempting to pay #77751 merged on 2026-01-08 and is included in the staging deploy 9.2.99-0. The issue is reproducible on staging but not production (new feature), which matches the deployment timeline.

2. Code Changes: The PR added logic in BaseKYCWall.tsx (line 122) that determines whether to show the "link existing account" page:

   const canLinkExistingBusinessBankAccount = getEligibleExistingBusinessBankAccounts(bankAccountList, currency, true).length > 0;

3. Bug Scenario:

   • When a workspace currency is changed from non-USD to USD
   • The currency prop passed to KYCWall is from the expense/transaction, not the policy's outputCurrency
   • After currency change, canLinkExistingBusinessBankAccount evaluates to false even though valid USD bank accounts exist
   • The code then skips the existing account linking flow and goes straight to bank setup

Root Cause

The canLinkExistingBusinessBankAccount variable in BaseKYCWall.tsx uses the currency prop (which comes from the expense/transaction currency), but it should be using the policy's outputCurrency instead. When the policy currency is changed, the check for eligible bank accounts still uses the old or wrong currency, causing the wrong flow to be triggered.

The correct logic should check for eligible accounts using the policy's current currency since:

1. The policy currency has been updated to USD
2. There are valid USD business bank accounts available
3. The user should be shown the "link existing account" page, not the setup flow