[Due for payment 2026-07-06] [$250] Invoice - After reselecting the same user, RHP opens manual expense confirm page

[applause-bot]

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.4.17-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 BrowserStack: #94134
Email or phone of affected tester (no customers): sdjnoisdjdosijsonssjo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Enable Invoice.

1. Go to staging.new.expensify.com
2. Open FAB > Send invoice.
3. Enter amount > Next.
4. Select a user.
5. On confirm page, click To field.
6. Click on the same user.

Expected Result:

After reselecting the same user, RHP will return to invoice confirm page.

Actual Result:

After reselecting the same user, RHP opens manual expense confirm page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7188091_1782171983610.19.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7188091

Issue Owner

Current Issue Owner: @mallenexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022070362656170293428
• Upwork Job ID: 2070362656170293428
• Last Price Increase: 2026-06-26
• Automatic offers:
• thelullabyy | Reviewer | 111834580

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/042c3f2b0d469b7d190054028384e0c4f272c845dbbbbbc06ef3214a42c66943

[melvin-bot]

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

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

[MelvinBot]

Proposal

What is the root cause of that problem?

On the invoice confirmation page, the To field now opens the inline ParticipantPicker (this picker used to be gated behind the NEW_MANUAL_EXPENSE_FLOW beta, which PR #94134 removed, so it now always renders).

When you (re)select a participant in that picker, handleParticipantsAdded runs and unconditionally rewrites the route's iouType to create for any type that isn't split or create:

Code reference

IOURequestStepConfirmation.tsx:314-316

if (iouType !== CONST.IOU.TYPE.SPLIT && iouType !== CONST.IOU.TYPE.CREATE) {
    navigation.setParams({iouType: CONST.IOU.TYPE.CREATE});
}

Full handler: IOURequestStepConfirmation.tsx:304-324

For the invoice flow iouType === 'invoice', so this branch fires and switches the route param from invoice → create. The confirmation page then re-renders as a manual expense (create) confirm page instead of the invoice confirm page — exactly the reported symptom. The same bug affects the Pay someone flow (pay), which is also neither split nor create.

The conversion to create is only correct for the manual-expense flows (submit/track) — the sibling participantPickerIOUType already encodes that intent (submit/track → create, otherwise keep iouType). The handleParticipantsAdded guard does not match it, so non-manual types get clobbered.

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

In handleParticipantsAdded, only convert to create for the manual-expense flows, mirroring participantPickerIOUType. Change the guard at IOURequestStepConfirmation.tsx:314 from:

iouType !== CONST.IOU.TYPE.SPLIT && iouType !== CONST.IOU.TYPE.CREATE

to only fire for submit/track:

iouType === CONST.IOU.TYPE.SUBMIT || iouType === CONST.IOU.TYPE.TRACK

This preserves iouType for invoice and pay, so reselecting a participant returns to the correct confirm page.

What alternative solutions did you explore? (Optional)

None needed — the fix is a one-line guard correction. Regression test: cover the invoice (and pay) confirm → To → reselect path to assert iouType is not rewritten.

How it reproduces

1. FAB → Send invoice → enter amount → Next → select a user → on the confirm page click To → click the same user.
2. MoneyRequestConfirmationList's onOpenParticipantPicker sets manuallyOpenedParticipantPickerForTransactionID → the inline ParticipantPicker becomes visible.
3. Tapping the user fires onParticipantsAdded → handleParticipantsAdded → navigation.setParams({iouType: 'create'}) → confirm page renders as a manual expense.

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/94263) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.