Reports- Nothing happens after clicking bank account when paying non-reimbursable 0.00 expense

[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.3.52-3
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: #83329
Email or phone of affected tester (no customers): applausetester+khcategory20@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Workspace is set up with bank account.
• Admin invites member to the workspace.

1. Go to staging.new.expensify.com
2. [Member] Go to workspace chat.
3. [Member] Create an expense with 0.00 amount and make it non-reimbursable.
4. [Member] Click Submit on the expense preview.
5. [Admin] Go to Reports > Reports.
6. [Admin] Click Approve on the report row from Step 4.
7. [Admin] Click dropdown button next to Pay button > click bank account.

Expected Result:

"Cannot pay via Expensify" modal will open.

Actual Result:

Nothing happens after clicking bank account when attempting to pay non-reimbursable 0.00 expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7120847_1775234271352.15.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[OSBotify]

Investigation Summary: Classification: Frontend bug. Causing PR: #83329 by @samranahm (High confidence). Recommendation: ROLL FORWARD. Root cause: In src/components/Search/SearchList/ListItem/ActionCell/PayActionCell.tsx, the confirmPayment function returns early when !amount is true. For a 0.00 expense, amount===0 which is falsy in JS, so the function exits before reaching shouldBlockDirectPayment and the error modal is never shown. Fix: change !amount to amount==null in the guard condition. Labels: DeployBlockerCash kept, no changes made.