[Due for payment 2026-08-05] Payment issue for E/App PR#96503

[melvin-bot]

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

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]

@eVoloshchak 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]. If no checklist is needed for this issue, you can click: [no checklist button]

[melvin-bot]

@eVoloshchak Huh... This is 4 days overdue. Who can take care of this?

[eVoloshchak]

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, this wasn't implemented originally
  Link to the comment on the Issue:

• [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: regression wasn't critical

• [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/669352

Regression Test Proposal

Test:

1. Sign in as a workspace admin whose member has a different email domain from the managed-card workspace domain.
2. Open the member's unreported managed-card expense.
3. Move the expense to a new report.
4. Verify the report is created and the expense remains on it without an error.

Do we agree 👍 or 👎

Zapier Logs

Run ID: 00040eee-2c0f-aafb-03c5-7b222f471fa4

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Awaiting Payment)