Reports - Existing linked account is not shown when paid via dropdown button

[nlemma]

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.97-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+khcategory20@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:

• User has created a USD workspace and add business bank account.

1. Go to staging.new.expensify.com
2. Create another USD workspace.
3. Go to workspace chat.
4. Create an expense.
5. Click Submit and Approve on the expense preview.
6. Go to Reports > Reports.
7. Click Pay button > Pay with business account.
   → Existing linked account is shown.
8. Close the RHP.
9. Select the report via checkbox.
10. Click dropdown button > Pay > Pay with business account.

Expected Result:

Existing linked account will be shown.

Actual Result:

Existing linked account is not shown when paid via dropdown button.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7044753_1767985257673.7.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #77751

[melvin-bot]

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

[melvin-bot]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #77751 - "feat: Show page to link existing account when attempting to pay" by @MrMuzyk (High confidence)
Related Issues: Originally fixed #65912

Recommendation: REVERT

This PR should be reverted to unblock the deploy. The issue is a critical regression in the payment flow when using bulk actions from the Reports page.

📋 Detailed Analysis

Evidence

The issue explicitly references PR #77751 in the bug report description, and I have confirmed this is the causing PR by analyzing the code changes.

The PR introduced changes to how existing business bank accounts are detected and shown during the payment flow. Specifically, it added logic in BaseKYCWall.tsx to check for eligible existing business bank accounts based on currency matching.

Root Cause

The bug occurs in the bulk action payment flow on the Reports page. When paying via the dropdown button:

1. In ActionCell.tsx (line 86), the currency is extracted from iouReport:

   const {currency} = iouReport ?? {};

2. This currency is then explicitly passed to SettlementButton (line 160):

   currency={currency}

3. The Problem: If iouReport is not fully loaded or missing currency data in the bulk action context, currency becomes undefined. When explicitly passed as undefined, it overrides the default parameter value of CONST.CURRENCY.USD in SettlementButton.

4. In BaseKYCWall.tsx (line 122), the code checks:

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

5. The function getEligibleExistingBusinessBankAccounts in WorkflowUtils.ts (line 498) returns an empty array when currency is undefined:

   if (!bankAccountList || policyCurrency === undefined) {
       return [];
   }

6. This causes the existing bank account screen to NOT be shown, even though eligible accounts exist.

Why It Works in Report Preview

When paying directly from the report preview (MoneyRequestReportPreviewContent.tsx line 601), the full iouReport is available with complete currency data, so the check passes correctly.

Why It Was Missed in Testing

The PR included Scenario D which matches this exact flow, but the test may not have caught the case where the iouReport data is incomplete/loading in the bulk action context, or the testing was done with a fully loaded report where currency was always present.