Expense - IOU expenses can be changed to 0 amount by bulk editing

[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.21-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: #76264
Email or phone of affected tester (no customers): sodijnsojndsojsioj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to 1:1 DM with any user.
3. Submit two expenses.
4. Open the report.
5. Select both expenses.
6. Click dropdown button > Edit multiple.
7. Click Amount.
8. Enter zero > Save > Save.

Expected Result:

Error will show up on amount page because IOU expenses cannot be changed to 0 amount.

Actual Result:

No error shows up on amount page when changing 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

Bug7080964_1771376966185.11.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @marcaaron

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @twisterdotcom (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: #76264 - "Feat: bulk edit multiple" by @waterim (High confidence)
Related Issues: None

Recommendation: REVERT

The bulk edit feature is missing critical validation logic that prevents zero-amount IOU expenses. Reverting #76264 will restore proper validation until a fix can be implemented.

Labels: Keeping DeployBlockerCash (Frontend bug - App PR needs revert), Removing DeployBlocker (no backend fix needed)

📋 Detailed Analysis

Evidence

PR #76264 introduced the bulk edit multiple expenses feature and was merged on 2026-02-17 at 21:17:18 UTC. The bug report indicates:

• Version: 9.3.21-0
• Reproducible in staging: Yes
• The issue is specific to bulk editing IOU expenses to amount 0
• The error validation that should prevent this is not showing up

Verification

Affected file: src/pages/Search/SearchEditMultiple/SearchEditMultipleAmountPage.tsx

Lines 116-130 show the MoneyRequestAmountForm component being called without the isP2P parameter:

<MoneyRequestAmountForm
    amount={amountForForm}
    currency={selectedCurrency}
    isEditing
    isCurrencyPressable={false}
    hideCurrencySymbol
    ref={(e: BaseTextInputRef | null) => {
        textInput.current = e;
    }}
    onCurrencyButtonPress={showCurrencyPicker}
    onSubmitButtonPress={saveAmount}
    allowFlippingAmount={allowNegative}
/>

Comparison with working code: src/pages/iou/request/step/IOURequestStepAmount.tsx (line 463) properly passes isP2P:

<MoneyRequestAmountForm
    // ... other props
    isP2P={isParticipantP2P(getMoneyRequestParticipantsFromReport(chatReportForP2PCheck, currentUserPersonalDetails.accountID).at(0))}
/>

Root Cause

In src/pages/iou/MoneyRequestAmountForm.tsx, the validation logic (lines 66-68) requires both the correct iouType AND the isP2P flag to validate zero amounts for IOU requests:

if ((iouType === CONST.IOU.TYPE.REQUEST || iouType === CONST.IOU.TYPE.SUBMIT) && parseFloat(amount) < 0.01 && isP2P) {
    return true;
}

Since SearchEditMultipleAmountPage.tsx does not pass the isP2P parameter, it defaults to false (line 98 in MoneyRequestAmountForm), causing the validation to fail and allowing zero amounts to be saved for IOU expenses.

The bulk edit flow needs to:

1. Pass the isP2P parameter to MoneyRequestAmountForm
2. Determine if the selected expenses are P2P requests (checking if participants are not policy expense chats)