[Due for payment 2026-04-16] [Due for payment 2026-04-14] Distance - Tax rate and amount do not update after selecting distance rate 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.3.53-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: #84136
Email or phone of affected tester (no customers): sjoinjojsodidsjodjso@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:

• Enable Distance rates and Taxes.
• Enable Track tax in Distance settings.
• Create a distance rate with 5% tax rate and any reclaimable amount.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Click + > Track distance > Manual.
4. Enter amount > Next.
5. On confirm page, click Rate.
6. Select the rate with with 5% tax rate and any reclaimable amount.
7. Scroll down to tax rate and tax amount section.

Expected Result:

Tax rate and amount will update to the correct value.

Actual Result:

Tax rate shows 0% and tax amount shows 0.00 after selecting distance rate with 5% tax on confirm page.

It only shows the correct tax rate and amount after creating the expense.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7123249_1775525941670.6.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

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

[OSBotify]

Investigation Summary. Classification: Frontend bug. Causing PR: #84136 (PR 84136) - Feat: Add distance rate to the distance expenses tracked in selfDM by @FitseTLT (High confidence). Recommendation: REVERT. The regression is directly introduced by PR 84136 in the distance rate step logic. Reverting this PR would restore the correct tax rate/amount display behavior on the confirmation page. Labels: DeployBlockerCash kept (frontend App regression). DeployBlocker removed (no backend fix needed). Evidence: The bug is staging-only (new feature not yet in production), and PR 84136 is in the StagingDeployCash checklist (merged 2026-04-06T18:28:53Z). melvin-bot assigned PR 84136 as the causing PR. Bug appears when selecting a distance rate with tax on confirm page: tax shows 0% and 0.00 until after expense is created. Verification: Affected files are src/pages/iou/request/step/IOURequestStepDistanceRate.tsx and src/components/MoneyRequestConfirmationList.tsx. PR 84136 modifies both files directly. Root Cause: In IOURequestStepDistanceRate.tsx line 84, shouldShowTax is computed using isTaxTrackingEnabled with policy from usePolicyForTransaction. For a track distance expense in selfDM, this policy is undefined at rate-selection time (expense is unreported/draft). With policy undefined, isTaxTrackingEnabled returns false, so the tax update block (setMoneyRequestTaxAmount, setMoneyRequestTaxRate, setMoneyRequestTaxValue) is skipped when the user selects a rate. The draft transaction retains 0% / $0.00 tax values and only gets corrected after submission.