[$250] Expense - Tax field is blank after merging with expense with invalid tax rate

[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.24-1
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: #71244
Email or phone of affected tester (no customers): sjdsoijsoidjsndoinjsdoi@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:

Precondition:

• Taxes are enabled.
• Workspace has two tax rates - 5% and 10 %.

1. Go to staging.new.expensify.com
2. Go to workspace chat.
3. Create an expense with 5% tax rate.
4. Create an expense with 10% tax rate.
5. Go to workspace settings > Taxes.
6. Delete 10% tax rate.
7. Go back to workspace chat.
8. Open expense with 5% tax rate.
9. Click More > Merge.
10. Select the expense with 10% tax rate > Continue.
11. Select all the details from the expense with 10% tax rate (select all the second options) > Next.
12. Click Merge expenses.

Expected Result:

Tax field will show 10% with violation.

Actual Result:

Tax field is blank.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7083642_1771605033256.2.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @aimane-chnaif

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022024891872992580751
• Upwork Job ID: 2024891872992580751
• Last Price Increase: 2026-02-20

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #71244 - "[Merge] Merging tax rates" by @dominictb (High confidence)
Related Issues: None

Recommendation: REVERT

This PR introduced a regression in how deleted tax rates are displayed after merging expenses. The issue is isolated to this PR and reverting will restore the previous working behavior.

Labels: Removed DeployBlocker (backend label not needed - this is a frontend bug in App)

📋 Detailed Analysis

Evidence

• The issue explicitly references PR [Merge] Merging tax rates #71244 in the reproduction steps
• The bug is staging-only and reproducible with the new merge tax rates feature
• The PR was merged on 2026-02-19 and is included in the current staging deploy (9.3.24-1)
• The bug occurs specifically when merging expenses where one has a deleted tax rate

Verification

PR #71244 modifies the exact files and code paths related to the reported issue:

• src/components/ReportActionItem/MoneyRequestView.tsx - Changed tax display logic
• src/libs/MergeTransactionUtils.ts - Added tax rate handling during merge
• src/types/onyx/Transaction.ts - Added taxName field

Root Cause

The PR introduced a new taxName field on transactions and changed the display priority in MoneyRequestView.tsx (line 605):

// After PR #71244
const taxRateValue = transaction?.taxName ?? taxRateTitle ?? fallbackTaxRateTitle;

The Problem:

1. When merging expenses with a deleted tax rate, the code sets transaction.taxName using getTaxName(policy, transaction) ?? transaction?.taxValue ?? ""
2. If the tax rate is deleted from the policy, getTaxName() returns undefined (it cannot find the rate)
3. The fallback to transaction.taxValue should work, but the field ends up empty
4. In MoneyRequestView.tsx, the new priority checks transaction?.taxName first, which may be an empty string, causing the field to display blank instead of falling through to taxRateTitle or showing the violation with the rate name

Expected behavior: The tax field should show "10%" with a violation indicator when the tax rate is deleted.

Actual behavior: The tax field is completely blank because transaction.taxName is checked first but contains an empty/invalid value.