[Due for payment 2025-11-26] [Merge] Expense - Different distance can be selected when merging expense but it is not kept

[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.1.91-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: #65596
Email or phone of affected tester (no customers): jsdknjsoisd@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 workspace chat.
3. Submit two distance expenses with different waypoints.
4. Open expense report.
5. Open any transaction thread.
6. Click More > Merge.
7. Select the other distance expense > Continue.
8. On receipt page, select the original receipt > Continue.
9. Select the original amount.
10. Select the "Merchant" from the other distance expense.
11. Click Continue.
12. Note that the Distance field still shows the original distance instead of the selected distance.
13. Click Merge expense.
14. The merged expense also shows the original distance instead of the selected distance.

Expected Result:

The distance we use in the merged expense should come from the expense with the selected merchant.

Actual Result:

In Step 10, merchant is selectable if it cannot keep the distance details from another distance expense.
In Step 12, Distance field still shows the original distance instead of the selected distance.
In Step 14, the merged expense also shows the original distance instead of the selected distance.

*The same issue also happens when we merge distance expense with same waypoints but different distance rate. The original rate is kept despite choosing a different rate.

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

Bug6911046_1754623994090.Screen_Recording_2025-08-08_at_11.28.40.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (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 @aldo-expensify (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.