[Due for payment 2026-05-11] Expense - Expense with negative account is not displayed on "Existing Expenses" list.

[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.3.65-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: #85225
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the staging.new.expensify.com website.
2. Open any workspace chat.
3. Create a manual expense with negative amount.
4. Create an empty report.
5. Click on "Add Expense" > "Add existing expense"
6. Note that the expense created on step 3, is not visible on existing expenses list.

Expected Result:

Expense with negative amount should be displayed on existing expenses list and user should be able to add it to another report.

Actual Result:

Expense with negative amount is not displayed on existing expenses list and can´t be added to another report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7142469_1777599960840.Existing_1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @sobitneupane

[melvin-bot]

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

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