[$250] Expense - Invisible report is created after submit scan expense from self DM to workspace chat

[jponikarchuk]

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.2.15-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: https://test-management.browserstack.com/projects/2219752/test-runs/TR-827/folder/13176877/41237362/899331471
Email or phone of affected tester (no customers): applausetester+sdonjisjods@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Log in with Expensifail account.
• Account has self DM.

1. Go to staging.new.expensify.com
2. Create a workspace.
3. Go to workspace chat.
4. Create an expense.
5. Go to self DM.
6. Create a scan expense in self DM.
7. Click Submit it to someone.
8. Select workspace chat.
9. Click Create expense.
10. Open the expense report.
11. Open any expense row.
12. Click Report field.

Expected Result:

No new report will be created after submitting scan expense from self DM to workspace chat.

Actual Result:

A new, invisible report (can't be found anywhere except from Report field) is created after submitting scan expense from self DM to workspace chat.
When trying to move an expense to the invisible report, the expense cannot be moved.

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

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021969056613504776398
• Upwork Job ID: 1969056613504776398
• Last Price Increase: 2025-10-03
• Automatic offers:
• truph01 | Contributor | 109024371
• thelullabyy | Contributor | 109046004

Issue Owner

Current Issue Owner: @chuckdries

[melvin-bot]

Triggered auto assignment to @sakluger (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.

[thelullabyy]

Proposal

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

A new, invisible report (can't be found anywhere except from Report field) is created after submitting scan expense from self DM to workspace chat.
When trying to move an expense to the invisible report, the expense cannot be moved.

What is the root cause of that problem?

A new, invisible report (can't be found anywhere except from Report field) is created after submitting scan expense from self DM to workspace chat.

• This issue appears because when submitting a track expense to workspace chat, we incorrectly create new report rather than moving the track expense to the existing report in the workspace chat. In detail, in here:

App/src/libs/actions/IOU.ts

Line 3444 in 79f111b

const shouldCreateNewMoneyRequestReport = isSplitExpense ? false : shouldCreateNewMoneyRequestReportReportUtils(iouReport, chatReport, isScanRequest);

App/src/libs/ReportUtils.ts

Line 10003 in 79f111b

return !existingIOUReport || hasIOUWaitingOnCurrentUserBankAccount(chatReport) || !canAddTransaction(existingIOUReport) || (isScanRequest && isASAPSubmitBetaEnabled);

shouldCreateNewMoneyRequestReport is true because (isScanRequest && isASAPSubmitBetaEnabled) is true.

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

• We should update part isScanRequest && isASAPSubmitBetaEnabled in:
  

  App/src/libs/ReportUtils.ts

  Line 10003 in 79f111b

  return !existingIOUReport || hasIOUWaitingOnCurrentUserBankAccount(chatReport) || !canAddTransaction(existingIOUReport) || (isScanRequest && isASAPSubmitBetaEnabled);

  
  to:

action !== 'submit' && isScanRequest && isASAPSubmitBetaEnabled

• The action is the 4th param we need to introduce in

  App/src/libs/ReportUtils.ts

  Line 9997 in 79f111b

  function shouldCreateNewMoneyRequestReport(existingIOUReport: OnyxInputOrEntry<Report> | undefined, chatReport: OnyxInputOrEntry<Report>, isScanRequest: boolean): boolean {

  and it will be passed down in where we call that function. It is easy to handled in PR

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

• NA

What alternative solutions did you explore? (Optional)

[melvin-bot]

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

[melvin-bot]

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