[Due for payment 2026-02-17] Time - Default hourly rate shows decimals in VND when VND does not support decimals

[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.11-17
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: #80331
Email or phone of affected tester (no customers): applausetester+s2d2d@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

• Log in with Expensifail account.

1. Go to staging.new.expensify.com
2. Create a workspace with VND as default currency.
3. Go to workspace settings > More features.
4. Enable Time.
5. Go to Time.

Expected Result:

Default hourly rate will show ₫50 because VND does not support decimals.

Actual Result:

Default hourly rate shows ₫50.00 when VND does not support decimals.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7063593_1769957210475.0.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @kadiealexander

[melvin-bot]

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

[melvin-bot]

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

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

[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: #80331 - "Create Time Tracking settings page" by @mhawryluk (High confidence)
Related Issues: N/A

Recommendation: ROLL FORWARD

The fix is straightforward - replace convertAmountToDisplayString() with convertToDisplayString() in the time tracking rate display. This is simpler than reverting the entire Time Tracking feature PR.

Labels: Removing DeployBlocker (backend label). Keeping DeployBlockerCash (this is a frontend App bug that requires an App PR fix).

📋 Detailed Analysis

Evidence

PR #80331 introduced the Time Tracking settings page, which is a new feature that does not exist in production. The bug is reproducible on staging only, and melvin-bot correctly identified this PR as the cause.

The issue appears in the display of the default hourly rate on the Time Tracking settings page (/home/runner/work/App/App/src/pages/workspace/timeTracking/WorkspaceTimeTrackingDefaultRateSection.tsx).

Verification

Affected file: src/pages/workspace/timeTracking/WorkspaceTimeTrackingDefaultRateSection.tsx (line 37)
Created by: PR #80331

The file uses:

title={policy ? convertAmountToDisplayString(getDefaultTimeTrackingRate(policy), policy?.outputCurrency) : '}

This PR introduced these files as part of the Time Tracking feature implementation.

Root Cause

The bug is in src/libs/CurrencyUtils.ts in the convertAmountToDisplayString() function (lines 164-172):

function convertAmountToDisplayString(amount = 0, currency: string = CONST.CURRENCY.USD): string {
    const convertedAmount = amount / 100.0;
    return format(IntlStore.getCurrentLocale(), convertedAmount, {
        style: 'currency',
        currency,
        minimumFractionDigits: CONST.MIN_TAX_RATE_DECIMAL_PLACES,  // = 2
        maximumFractionDigits: CONST.MAX_TAX_RATE_DECIMAL_PLACES,  // = 4
    });
}

The function uses hardcoded decimal places (MIN_TAX_RATE_DECIMAL_PLACES = 2) instead of respecting the currency's actual decimal configuration. VND has 0 decimal places, but the function forces a minimum of 2, resulting in ₫50.00 instead of ₫50.

The fix: Replace convertAmountToDisplayString() with convertToDisplayString() which properly uses getCurrencyDecimals(currency) to respect each currency's decimal places.

Alternative locations to fix:

1. In WorkspaceTimeTrackingDefaultRateSection.tsx line 37 (use convertToDisplayString instead)
2. Modify convertAmountToDisplayString() to accept currency decimals as a parameter or use getCurrencyDecimals()