Rules - Track expense submitted to WS is always set to "Reimbursable" despite opposite rule.

[mitarachim]

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.31.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: #83005
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has a workspace with "Rules" enabled.
Prerequisite 2: Account has Self DM.

1. Open the staging.new.expensify.com website.
2. Navigate to "Workspaces" > "Rules"
3. Scroll down to "Merchant" section.
4. Click on "Add Merchant Rule"
5. In "For expenses with" add any merchant name. (For example: Test)
6. In "Apply these updates", add any category, any description, and set reimbursable field to "No".
7. Save the just created rule.
8. Navigate to Self DM.
9. Create a manual expense.
10. Click on "Submit it to someone"
11. Add the merchant used for the created rule and submit the expense to the workspace where rule was created.
12. Open the expense report.
13. Note that all updates were correclty applied, but expense is still displayed as "Reimbursable"
14. Note that system message shows "Marked the expense as non-reimbursable" despite expense being displayed as reimbursable.

Expected Result:

After submitting a track expense to a workspace, with a merchant used for a rule, all the fields included on the rule should be automatically updated.

Actual Result:

Track expenses are always set to "Reimbursable" when submitted to workspace, despite a rule being created setting the expense to "Non-reimbursable". The rest of the fields are correctly updated.
Also, system message after expense creation, displays a "Marked the expense as non-reimbursable" despite expense being displayed as "Reimbursable".

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7094168_1772666692582.Reimbursable.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @JS00001

[melvin-bot]

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

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

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