Expense - Failed scan expense shows $0.00 amount after being submitted to a workspace

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: V9.4.54-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96772
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: Money Requests

Action Performed:

1. Launch the app
2. Go to the self DM
3. Create a failed scan expense
4. Wait for the scan to complete/fail
5. Open the expense details
6. Verify that the missing amount violation is displayed and the Amount field is empty
7. Use Submit to friend
8. Submit/move the expense to a workspace
9. Open the expense details
10. Observe the Amount field

Expected Result:

The Amount field should remain empty and the missing amount violation should continue to be displayed.

Actual Result:

After submitting the expense to a workspace, the Amount field displays $0.00 instead of showing the missing amount error.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7235135_1786901211290.Screenrecorder-2026-08-16-22-50-32-621.1.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @jjcoffee

[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/451909a7af09c0a6b137a9183b8a4e79ac5562e44136958e7ab21f86103ce08e

[melvin-bot]

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

[melvin-bot]

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

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

[melvin-bot]

@arosiclair @Ollyws you have been assigned to this deploy blocker because you reviewed the offending PR: #96772

[melvin-bot]

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