Expense - Mark as paid button appears for sender after merging IOU expenses

[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.2.9-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 TestRail: #68204
Email or phone of affected tester (no customers): yonghongkok2+110902@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to 1:1 DM with user that has Expensify account.
3. Submit two expenses to the user.
4. Open the expense report.
5. Select one of the expenses via checkbox.
6. Click dropdown button > Merge.
7. Select the other expense > Continue.
8. Select any detail > Continue.
9. Click Merge expenses.

Expected Result:

Mark as paid button will not appear for sender after merging expenses.

Actual Result:

Mark as paid button appears for sender after merging expenses.
The report name also changes to "Sender owes x" instead of "Receiver owes x".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6941039_1757550451271.Screen_Recording_2025-09-11_at_08.26.06.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

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

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

[hoangzinh]

@youssef-lr this issue can be demoted as it's related to IOU