[Due for payment 2026-01-20] Expense - IOU expense amount can be edited to 0

[lanitochka17]

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.96-1
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: #77238
Email or phone of affected tester (no customers): applausetester+sjdiosn2djois2j2d@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:

• Log in with Expensifail account.

1. Go to staging.new.expensify.com
2. Open 1:1 DM with User B.
3. Click + > Create expense > Manual.
4. Enter 0 > Next.
   → User cannot proceed with 0 amount for IOU expense - Expected.
5. Enter any amount except 0 and create the expense.
6. Open the expense.
7. Click Amount.
8. Change the amount to 0 and save it.

Expected Result:

User cannot edit IOU expense amount to 0.

Actual Result:

User cannot submit IOU expense without 0 amount, but they can edit IOU expense amount to 0.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7043826_1767890059513.5.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @stephanieelliott

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[arosiclair]

Revert was CP'd. This is waiting on QA: https://expensify.slack.com/archives/C09V78U42D8/p1767909520115659