[Due for payment 2026-09-09] Expense- Auto categorize new expense is not applied for concierge created expense.

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: v9.4.66-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: #98030
Email or phone of affected tester (no customers): dreamnitethe@gmal.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: win 10 chrome
App Component: Money Requests

Action Performed:

1. Go to
2. Open workspace settings - categories - settings
3. Verify Auto categorize new expense is toggled on
4. open workspace chat
5. Create a manual expense via concierge by sending a message - Create expense for home depot $400
6. Open the expense and note missing category is shown

Expected Result:

Auto categorize new expense must be applied for concierge created expense.

Actual Result:

Auto categorize new expense is not applied for concierge created expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7248618_1788320145218.bandicam_2026-09-02_08-57-26-981.mp4

View all open jobs on GitHub

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

Issue Owner

Current Issue Owner: @mallenexpensify

[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/5cb730030d226623dd79ba6e824b0333e61d4f1fafc8703efd34aad4273581e0

[melvin-bot]

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

[melvin-bot]

@heyjennahay @jasperhuangg @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #98030

[melvin-bot]

@dukenv0307 you have been assigned to this deploy blocker because you authored the offending PR: #98030

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