Expense - Track map distance amount & rate is shown incorrectly

[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: V9.3.4-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/folder/18717689/test-cases/49855697
Email or phone of affected tester (no customers): dreamnitethedragon+yydyd373@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Login with new gmail account
3. Tap fab - track distance
4. Enter 1 km
5. Select self dm
6. Note amount and rate is incorrect different from production

Expected Result:

Track map distance amount & rate must not be shown incorrectly.

Actual Result:

Track map distance amount & rate is shown incorrectly.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7052378_1768732050001.Screenrecorder-2026-01-18-15-53-57-699.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @kadiealexander (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 @MariaHCD (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: Not a bug - Expected behavior
Causing PR: #79051 - "[No QA] Update mileage rate mapping for new year" by @neil-marcellini (High confidence)
Related Issues: None

Recommendation: DEMOTE

This is not a bug. The mileage rates were intentionally updated for the 2025 tax year. The difference between staging and production is expected and correct.

Rationale:

• PR [No QA] Update mileage rate mapping for new year #79051 updated default mileage rates for 2025 (e.g., USD rate changed from $0.70/mi to $0.725/mi)
• The issue reports "amount & rate is incorrect different from production" - but this difference is intentional
• Production still has 2024 rates, staging has 2025 rates
• This is standard annual maintenance to comply with updated IRS mileage rates
• The PR references an internal Expensify issue (Expensify/Expensify#572804) about updating rates via an internal tool

Labels: No label changes needed - this should be closed as "Working as intended" rather than being treated as a deploy blocker.

📋 Detailed Analysis

Evidence

PR #79051 modified src/CONST/index.ts to update the CURRENCY_TO_DEFAULT_MILEAGE_RATE mapping. For example:

• USD rate: 70 → 72.5 (cents per mile, which displays as $0.725/mi)
• EUR rate: unchanged at 0.30
• Many other currencies updated

The PR was merged on 2026-01-16 and deployed to staging in version 9.3.4-0.

Verification

The affected code is in:

• /home/runner/work/App/App/src/CONST/index.ts (line 5970-6250)
• /home/runner/work/App/App/src/libs/DistanceRequestUtils.ts (uses these rates for P2P distance calculations)

The getRateForP2P function (line 245-257 in DistanceRequestUtils.ts) uses CONST.CURRENCY_TO_DEFAULT_MILEAGE_RATE to determine the rate for peer-to-peer (self-DM) distance expenses.

Root Cause

There is no bug. The QA tester is correctly observing that staging shows different rates than production. However, this is the intended behavior when mileage rates are updated for a new year. The rates should be different between staging and production until the production deploy occurs.

[OSBotify]

🔍 Investigation Summary - UPDATE

Classification: Likely expected behavior, but needs verification
Causing PR: #79051 - "[No QA] Update mileage rate mapping for new year" by @neil-marcellini (High confidence)
Related Issues: None

Recommendation: NEEDS INVESTIGATION

While PR #79051 is clearly the causing PR, I need clarification on whether this is an actual bug or expected behavior.

The issue: PR #79051 updated default mileage rates for 2025 (e.g., USD rate changed from $0.70/mi to $0.725/mi). This causes staging to show different rates than production.

Two possible scenarios:

1. Expected behavior: The rates are displaying correctly with the new 2025 values, and the tester is simply noting they differ from production (2024 values). In this case, this should be DEMOTED as "working as intended."

2. Actual bug: There is a calculation or display error introduced by the rate update (e.g., wrong decimal places, incorrect currency formatting, backend sync issue). In this case, PR [No QA] Update mileage rate mapping for new year #79051 should be REVERTED.

Question for @lanitochka17 or QA team: Can you clarify what "incorrect" means in the issue description?

• Are the rates just different from production (expected)?
• Or are they incorrectly calculated/displayed (e.g., showing wrong decimal places, wrong currency symbol, etc.)?

If you can share specific examples (e.g., "1 km should show $X but shows $Y"), that would help determine if this is a bug.

Labels: Keeping both labels until clarified.

📋 Detailed Analysis

Evidence

PR #79051 modified src/CONST/index.ts to update CURRENCY_TO_DEFAULT_MILEAGE_RATE. Examples:

• USD: 70 → 72.5 (cents per mile = $0.725/mi display)
• AED: 414 → 428.5 (cents per km)
• EUR: 30 → 30 (unchanged)

Merged: 2026-01-16 13:30:42Z
Deployed to staging: v9.3.4-0

Verification

Affected files:

• /home/runner/work/App/App/src/CONST/index.ts (rate constants)
• /home/runner/work/App/App/src/libs/DistanceRequestUtils.ts (rate calculation logic)

The getRateForP2P function uses CONST.CURRENCY_TO_DEFAULT_MILEAGE_RATE for P2P/self-DM distance calculations.
The getUnitRateValue function divides the rate by 100 (CUSTOM_UNIT_RATE_BASE_OFFSET) to convert from cents to dollars for display.

Root Cause Analysis

If this is expected behavior: The rates were intentionally updated for 2025 tax year. No bug exists.

If this is a bug: Possible causes could include:

• Backend API not updated with new rates, causing mismatch
• Display formatting issue with new rate values
• Calculation error in amount computation

The code comments (lines 240 & 357 in DistanceRequestUtils.ts) emphasize that frontend and backend logic must stay in sync. If the backend wasn't updated simultaneously, there could be a discrepancy.

[OSBotify]

Update: Recommendation Changed to DEMOTE

After further analysis, I believe this should be DEMOTED rather than blocking the deploy.

Reasoning:

1. PR [No QA] Update mileage rate mapping for new year #79051 was explicitly marked [No QA] because updating annual mileage rates is routine maintenance
2. The rates were updated for 2025 tax year compliance (e.g., IRS mileage rate for USD increased from $0.70 to $0.725 per mile)
3. The issue description says "different from production" - which is expected and correct
4. No evidence of calculation or display errors in the code review
5. This is not a regression - it's an intentional configuration update

If there IS an actual bug (wrong decimal places, incorrect calculation, etc.) beyond just the rates being different, please provide specific details and I'll re-evaluate. Otherwise, this is working as intended and should not block the deploy.

cc @MariaHCD @kadiealexander