[Due for payment 2026-06-18] Payment issue for E/App PR#92297

[melvin-bot]

Issue created to compensate the Contributor+ member for their work on #92297
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/643487.
Contributor+ member who reviewed the PR - @daledah.

Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

@daledah The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

@daledah Whoops! This issue is 2 days overdue. Let's get this updated quick!

[daledah]

BugZero Checklist:

• [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

  Link to the comment on the PR: N/A refactor
  Link to the comment on the Issue: N/A refactor

• [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

  Link to discussion:

• [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

• [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

  Link to issue: https://github.com/Expensify/Expensify/issues/650516

Regression Test Proposal

Precondition: account with several reports ready for payment

Test:

1. Navigate to Spend
2. Select the reports ready for payment
3. Pay the reports
4. Verify that it works.

Do we agree 👍 or 👎

Zapier Logs

Run ID: 00040eee-b3f2-ab52-cc97-a0e9fbcd64b4

[daledah]

@luacmartins may I request an increase in the bounty for this issue? The PR involved a large number of changes across 19 files. This added considerable extra effort to the review and testing process across all platforms

Proposed amount to increase the price to: 500

Multiple PRs - Link to all PRs

Main PR: #92297
Follow up PR: #93308

[luacmartins]

I think that one was pretty standard, so the regular bounty seems fair in this case.