Fix/79181 - "Pay with business account" option reappears in IOU preview after user re-login. #80330

dmkt9 · 2026-01-23T11:29:01Z

Explanation of Change

When the IOU report has not yet been loaded (due to a fresh login and the report not being opened), the "Pay with Business Account" option will always appear on the Pay button in the preview report within the chat report, even though we have expenses from both sides.
This PR ensures the correct display in this case.

Fixed Issues

$ #79181
PROPOSAL: #79181 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Prerequisites:

Create two new accounts: User A (Creator) and User B (Participant), with USD as the payment currency.
User A has created two IOUs with User B.

Steps:

Navigate to staging.new.expensify.com.
Log in as User B (Participant).
Navigate to the IOU submitted by User A.
Submit an IOU to User A with an amount less than the owed amount.
Tap the Pay button and note that "Pay with business account" is NOT displayed.
Log out and log back in as User B, or navigate to Account > Troubleshoot > "Clear cache and restart."
Go to the 1:1 chat with User A.
Tap the Pay button.
Verify that the "Pay with business account" option is NOT displayed.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.native.mp4

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

ios.nativ.mp4

iOS: mWeb Safari

ios.mweb.mp4

MacOS: Chrome / Safari

mac.safari.mp4

… user re-login.

melvin-bot · 2026-01-23T11:29:09Z

@situchan Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

melvin-bot · 2026-01-23T11:29:15Z

@justinpersaud Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

src/libs/ReportActionsUtils.ts

situchan · 2026-01-23T11:34:53Z

src/libs/ReportActionsUtils.ts

+    const getTransactionAmount = (transaction?: Transaction) => Number(transaction?.modifiedAmount || transaction?.amount || 0);
+
+    const firstNonZeroTransaction = reportTransactions.find((transaction) => getTransactionAmount(transaction) !== 0);
+    if (reportTransactions.length === 0 || !firstNonZeroTransaction) {


if (reportTransactions.length === 0)
For optimization, move this condition just below const reportTransactions =

I've changed to use doesReportContainRequestsFromMultipleUsers instead of creating a new helper, for consistency with the suggestion by ChatGPT.

hasRequestFromCurrentAccount is also for IOU reports only, so using it will be fine.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7379429698

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

src/libs/ReportActionsUtils.ts

trjExpensify

Confirming that it's expected you can't pay with business account and thus convert the IOUReport to an expense report on the workspace when the IOUReport contains expenses from both parties. 👍

… user re-login.

situchan · 2026-01-23T13:52:16Z

src/libs/ReportUtils.ts


-function doesReportContainRequestsFromMultipleUsers(iouReport: OnyxEntry<Report>): boolean {
-    const transactions = getReportTransactions(iouReport?.reportID);
+function doesReportContainRequestsFromMultipleUsers(iouReport: OnyxEntry<Report>, shouldExcludeDeletedTransactions = false): boolean {


Please add unit test for this updated function.

A unit test has been added for hasRequestFromCurrentAccount, and it also covers the updated part of the doesReportContainRequestsFromMultipleUsers function.

codecov · 2026-01-23T13:54:19Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/libs/ReportActionsUtils.ts	`54.54% <100.00%> (+0.02%)`	⬆️
src/libs/ReportUtils.ts	`72.01% <50.00%> (+0.10%)`	⬆️
... and 11 files with indirect coverage changes

dmkt9 · 2026-01-23T14:01:08Z

It appears that the ESLint check is encountering an error; I will re-trigger the checks later.

situchan · 2026-01-25T17:43:56Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-01-25.at.11.48.37.PM.mov

situchan · 2026-01-25T17:52:57Z

Please merge main and fix lint

justinpersaud

need to fix lint

… user re-login.

dmkt9 · 2026-01-27T14:33:42Z

@justinpersaud It is ready.

OSBotify · 2026-01-28T20:36:11Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2026-01-28T23:22:01Z

🚀 Deployed to staging by https://github.com/justinpersaud in version: 9.3.11-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Fix - "Pay with business account" option appears in IOU preview after…

7379429

… user re-login.

dmkt9 requested review from a team as code owners January 23, 2026 11:29

melvin-bot bot assigned dmkt9 Jan 23, 2026

melvin-bot bot requested review from a team, situchan and trjExpensify and removed request for a team January 23, 2026 11:29

melvin-bot bot requested review from justinpersaud and removed request for a team January 23, 2026 11:29

github-actions bot reviewed Jan 23, 2026

View reviewed changes

src/libs/ReportActionsUtils.ts Outdated Show resolved Hide resolved

situchan reviewed Jan 23, 2026

View reviewed changes

chatgpt-codex-connector bot reviewed Jan 23, 2026

View reviewed changes

src/libs/ReportActionsUtils.ts Outdated Show resolved Hide resolved

trjExpensify previously approved these changes Jan 23, 2026

View reviewed changes

Fix - "Pay with business account" option appears in IOU preview after…

044ab10

… user re-login.

dmkt9 dismissed trjExpensify’s stale review via 044ab10 January 23, 2026 13:44

situchan reviewed Jan 23, 2026

View reviewed changes

situchan approved these changes Jan 25, 2026

View reviewed changes

justinpersaud reviewed Jan 27, 2026

View reviewed changes

dmkt9 added 3 commits January 27, 2026 20:55

Merge branch 'main' into fix/79181

64e66a3

Fix - "Pay with business account" option appears in IOU preview after…

cc8e086

… user re-login.

fix lint

255fdc0

justinpersaud approved these changes Jan 28, 2026

View reviewed changes

justinpersaud merged commit a9b7843 into Expensify:main Jan 28, 2026
29 checks passed

OSBotify mentioned this pull request Jan 28, 2026

Deploy Checklist: New Expensify 2026-01-28 #80808

Open

Fix/79181 - "Pay with business account" option reappears in IOU preview after user re-login. #80330

Fix/79181 - "Pay with business account" option reappears in IOU preview after user re-login. #80330

Uh oh!

Conversation

dmkt9 commented Jan 23, 2026

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jan 23, 2026

Uh oh!

melvin-bot bot commented Jan 23, 2026

Uh oh!

Uh oh!

Uh oh!

situchan Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

dmkt9 Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

This comment was marked as off-topic.

Uh oh!

dmkt9 Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

situchan Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

dmkt9 Jan 23, 2026

Choose a reason for hiding this comment

Uh oh!

codecov bot commented Jan 23, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

dmkt9 commented Jan 23, 2026

Uh oh!

situchan commented Jan 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

situchan commented Jan 25, 2026

Uh oh!

justinpersaud left a comment

Choose a reason for hiding this comment

Uh oh!

dmkt9 commented Jan 27, 2026

Uh oh!

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

OSBotify commented Jan 28, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

codecov bot commented Jan 23, 2026 •

edited by github-actions bot

Loading

situchan commented Jan 25, 2026 •

edited

Loading