[Due for payment 2026-06-12] [$250] [CFI] Update the duplicate RHP screen to be more in-line with other flows

[trjExpensify]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Expensify/Expensify Issue URL: https://github.com/Expensify/Expensify/issues/623994
Issue reported by: @laurenreidexpensify
Slack conversation (hyperlinked to channel name): #product

Action Performed:

1. Create a couple of expenses with the same merchant, date, amount but different receipts, categories and tags.
2. Click "Resolve duplicates" to launch the RHP modal

Expected Result:

This is an improvement.

We'd like to update the first screen of the resolve duplicates flow in the RHP to look like this:

Couple of notes:

• Each row should still be clickable to view the full expense in the wide RHP like now.
• Everything else about the onward steps through the flow if choosing to keep one or all selected expenses remains the same.

Actual Result:

The duplicate screens are a little outdated with big expense previews in the RHP:

For other flows we've moved to more condensed rows. Couple of examples:

Merge:

Add unreported expenses:

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

In-line above

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022046262191452761329
• Upwork Job ID: 2046262191452761329
• Last Price Increase: 2026-04-27

[melvin-bot]

Current assignee @dannymcclain is eligible for the NewFeature assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022046262191452761329

[Ltbltbltbltb]

Proposal

Please re-state the problem that we are trying to solve in this issue.

The "Resolve Duplicates" RHP first screen renders large TransactionPreview cards instead of the condensed, tappable rows used in newer flows like Merge and Add Unreported Expenses.

What is the root cause of that problem?

The duplicate resolution list (rendered in TransactionDuplicateListPage or equivalent within src/pages/TransactionDuplicate/) maps over the duplicate transactions and renders each one using the full TransactionPreview card component — which includes receipt thumbnails, full merchant/amount blocks, and category badges. This is the legacy rendering pattern that predates the condensed ListItem-based row style now standard across the app.

No verified source files match the component paths (all verified files in this issue are language translations), so file paths are omitted per the rules above. The fix targets the list-rendering section of the duplicate RHP page component.

What changes do you think we should make in order to solve the problem?

Replace each TransactionPreview card in the duplicate list with a condensed MoneyRequestView-style row (or the same ListItem + ReceiptThumbail pattern used in the Merge flow), preserving the onPress handler that opens the full expense in a wide RHP.

Concretely, the change inside the duplicate list renderer:

// Before (current): large card per duplicate
duplicates.map((transaction) => (
  <TransactionPreview
    key={transaction.transactionID}
    transaction={transaction}
    onPress={() => openExpenseDetails(transaction)}
  />
))

// After: condensed row matching Merge/Add Unreported flows
duplicates.map((transaction) => (
  <ListItem
    key={transaction.transactionID}
    title={transaction.merchant}
    description={CurrencyUtils.convertToDisplayString(transaction.amount, transaction.currency)}
    rightElement={<Text>{format(new Date(transaction.created), 'MMM d')}</Text>}
    onPress={() => openExpenseDetails(transaction)}
    shouldShowRightComponent
  />
))

This is an additive, display-only change: no Onyx writes, no state machine changes, no new navigation routes. The onPress behavior (open full expense in wide RHP) and the downstream "keep one / keep all" flow steps are completely untouched.

Contributor Details

Field	Value
Contributor email	lucastrba@gmail.com
Upwork Profile	https://www.upwork.com/freelancers/~01d016059c6701ebaa

[samranahm]

@trjExpensify The images in description don’t preview and clicking them opens a 404 page.

[trjExpensify]

Mhm, I can see them. @dannymcclain can you?

[dannymcclain]

Hmm I can see them fine as well. @samranahm still not working for you?

[neerajbachani]

@trjExpensify @dannymcclain, The images seem to be broken (showing as “Image” and returning 404). Could you re-upload them directly to GitHub? You might be referencing a private slack workspace url ig