[Due for payment 2026-07-08] Search - Bank account changes to ID in search field

[applause-bot]

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.4.25-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: #90791
Email or phone of affected tester (no customers): nsjoijojosdjosjosj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Search

Action Performed:

Precondition:

• Workspace has business bank account.

1. Go to staging.new.expensify.com
2. Open search.
3. Type bank-account:
4. Select bank-account:"Bank xx1111" from the suggestion.
5. Press Enter.
6. Open search again.

Expected Result:

Search query will remain as bank-account:"Bank xx1111".

Actual Result:

Search query changes to bank-account:9789681

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7195343_1782821668457.3.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7195343

Issue Owner

Current Issue Owner: @Eskalifer1

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/796781fc2581eff9a973a61cd87c7cf5beacabc7b30e203294f5210716b86300

[melvin-bot]

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

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