Distance - Rate changes from $0.70 / mile to $0.725 / mile

[lanitochka17]

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.3-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-2989/folder/18717689/49855697/1128449367
Email or phone of affected tester (no customers): sdjnsodijisjsodjso@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Create a default USD workspace.

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, Rate is $0.70 / mile.
6. Click Create expense.
7. Open the expense.

Expected Result:

In Step 5, on confirm page Rate should be $0.725 / mile.

Actual Result:

In Step 5, on confirm page Rate is $0.70 / mile.
In Step 7, after the expense is created, it changes to $0.725 / mile.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7050333_1768499709195.7.mp4

View all open jobs on GitHub

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

[melvin-bot]

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

[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: #79197 - "[BETA] Allow zero-amount expenses - ROUND 5" by @Gonals (High confidence)
Related Issues: Part of zero-amount expenses beta feature

Recommendation: ROLL FORWARD

This bug is behind the zero_expenses beta and affects the display of distance rates on the confirmation page. The bug shows $0.70/mile instead of $0.725/mile before the expense is created, but displays correctly after creation.

Given that:

1. This functionality is behind a beta flag
2. The PR is part of a series (ROUND 5) with multiple dependencies
3. The bug is a display issue that self-corrects after expense creation
4. Reverting would impact the zero-amount expenses feature rollout

A forward fix is more appropriate than a revert. The fix should address the rate display truncation in the confirmation flow.

Labels:

• REMOVE DeployBlockerCash - This is a beta-only bug that does not affect general users
• KEEP Bug label

Detailed Analysis

Evidence

PR #79197 was merged on 2026-01-15 and is in the staging deploy (9.3.3-0). The PR modified:

• src/libs/DistanceRequestUtils.ts - Changed distance display logic to allow zero distances
• src/components/MoneyRequestConfirmationList.tsx - Updated amount display logic for zero amounts

Verification

The bug affects distance rate display on the money request confirmation page:

• Affected file: src/components/MoneyRequestConfirmationListFooter.tsx (line 530)
• Rate calculation: src/libs/DistanceRequestUtils.ts (getRateForDisplay function)
• Display logic: src/libs/PolicyUtils.ts (getUnitRateValue and getRateDisplayValue functions)

The PR modifies distance handling logic which likely exposes an existing truncation issue in rate display where rates are incorrectly truncated before the transaction is fully persisted.

Root Cause

The rate display issue occurs in the confirmation flow where:

1. On the confirmation page, the rate shows truncated (e.g., $0.70 instead of $0.725)
2. After expense creation, the backend returns the correct rate which displays properly

The PR's changes to allow zero-distance/zero-amount expenses may have altered the timing or state of transaction data during the confirmation flow, exposing this display bug.

Beta-Only Impact

According to PR #79197's description: "most of its functionality is behind a beta" (the zero_expenses beta). Users not in the beta will not encounter this issue.