[$250] Expense - Unable to create expense in the report after Concierge joins the report

[lanitochka17]

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.3.51-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-14589/folder/22315296/56016282/1295549084?sort=-identifier
Email or phone of affected tester (no customers): jsodinjsodjoisnjonsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense.
4. Open the report.
5. Click +.
   → Create expense and Track distance option are available.
6. Send "Create an expense" message in the report.
7. Wait for Concierge message to show up.
8. After Concierge replies, click +.
9. Click More menu > Add expense > Create expense.

Expected Result:

After Concierge replies, + menu will show Create expense and Track distance option. Create expense button will open expense creation page.

Actual Result:

After Concierge replies, + menu is missing Create expense and Track distance option. Create expense button opens not here page.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7119114_1775059456769.27.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @thesahindia

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022043625199019032314
• Upwork Job ID: 2043625199019032314
• Last Price Increase: 2026-04-20

[MelvinBot]

Proposal

What is the root cause of that problem?

When Concierge replies in a report, the server adds Concierge to the report's participants. The + menu options are determined by getMoneyRequestOptions, which checks whether any EXPENSIFY_ACCOUNT_IDS are among the report's participants. Since Concierge is in EXPENSIFY_ACCOUNT_IDS, the function returns [] — removing all expense options ("Create expense", "Track distance") from the menu.

The "not here" page occurs for the same reason: canCreateRequest delegates to getMoneyRequestOptions, which returns empty, so AccessOrNotFoundWrapper renders NotFoundPage.

The participant list is built at ReportActionCompose.tsx:267-273 from all report.participants keys — it only filters out the current user, not hidden/system participants like Concierge.

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

Filter out EXPENSIFY_ACCOUNT_IDS from reportParticipantIDs in ReportActionCompose.tsx before passing them to getMoneyRequestOptions. This way, Concierge being added as a participant won't trigger the Expensify-account check that blocks all expense options.

Alternatively, the filter could be applied inside getMoneyRequestOptions itself — only consider non-system-account participants when deciding whether to block expense creation. The Expensify-account check at ReportUtils.ts:10022 would then use a filtered list that excludes participants with notificationPreference: 'hidden', since system accounts added by the server (like Concierge) typically have this preference.

What alternative solutions did you explore? (Optional)

Removing Concierge from EXPENSIFY_ACCOUNT_IDS is not viable — that constant is used for other legitimate checks. The fix should be scoped to the participant filtering for expense option determination.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

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