Expense - Tax rate and category selected in expense thread is not preserved on confirm page

[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.2.18-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 TestRail: #70821
Email or phone of affected tester (no customers): sosdpsosnjojs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM and a workspace.
• Taxes are enabled on the workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Create a track expense.
4. Open the expense thread.
5. Click Category and select a category.
6. Click Taxes.
7. Select Tax Rate 1 (5%).
8. Go back to self DM.
9. Click Submit it to someone.
10. Select the workspace.

Expected Result:

On confirm page, the category and 5% tax rate selected in expense thread (Step 6) will be shown.

Actual Result:

On confirm page, the category and 5% tax rate selected in expense thread (Step 6) is not shown. It shows no category selected and 0% rate instead.

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

Bug6954971_1758758010254.Screen_Recording_2025-09-25_at_07.52.22.mp4

View all open jobs on GitHub

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @MonilBhavsar (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

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