[Due for payment 2025-12-04] [$250] Upgrade Option Has Incorrect Amount Listed

[CortneyOfstad]

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.2.55-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers): cortney@expensify.com
Issue reported by: @CortneyOfstad
Device used: Web
App Component: Workspace Settings

Action Performed:

1. Open expense
2. Click on associated Report
3. get pop-up message "Upgrade, unlock this feature."

Expected Result:

The text should read $5, not $9 when updating from Free to Collect

Actual Result:

The amount is listed as $9

##Workaround:
Unknown

Platforms:

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

Videos or Screenshots

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021990498183073560547
• Upwork Job ID: 1990498183073560547
• Last Price Increase: 2025-11-17

Issue Owner

Current Issue Owner: @CortneyOfstad

[CortneyOfstad]

Originally created under the Expensify/Expensify repo after an SRAM reported the issue. QA was able to recreate here

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021990498183073560547

[melvin-bot]

Current assignee @CortneyOfstad is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

[ShridharGoel]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a Free user taps an expense’s associated report, the upgrade modal shows the Collect plan at $9/month instead of the correct $5/month.

What is the root cause of that problem?

The upgrade intro view picks the corporate (Control) annual price unless the flow is categorizing or distance-rate related, so the reporting upgrade path falls through to the higher $9 price.

App/src/pages/workspace/upgrade/UpgradeIntro.tsx

Lines 48 to 55 in 4c1d026

	const formattedPrice = useMemo(() => {
	const upgradeCurrency = Object.hasOwn(CONST.SUBSCRIPTION_PRICES, preferredCurrency) ? preferredCurrency : CONST.PAYMENT_CARD_CURRENCY.USD;
	return `${convertToShortDisplayString(
	// eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
	CONST.SUBSCRIPTION_PRICES[upgradeCurrency][isCategorizing || isDistanceRateUpgrade ? CONST.POLICY.TYPE.TEAM : CONST.POLICY.TYPE.CORPORATE][CONST.SUBSCRIPTION.TYPE.ANNUAL],
	upgradeCurrency,
	)} `;
	}, [preferredCurrency, isCategorizing, isDistanceRateUpgrade]);

What changes do you think we should make in order to solve the problem?

Treat the reporting upgrade path like categorizing/distance upgrades by using the team (Collect) pricing when formatting the upgrade price.

Updated code snippet:

const formattedPrice = useMemo(() => {
    const upgradeCurrency = Object.hasOwn(CONST.SUBSCRIPTION_PRICES, preferredCurrency) ? preferredCurrency : CONST.PAYMENT_CARD_CURRENCY.USD;
    const shouldUseTeamPricing = isCategorizing || isDistanceRateUpgrade || isReporting;
    return `${convertToShortDisplayString(
        // eslint-disable-next-line @typescript-eslint/prefer-nullish-coalescing
        CONST.SUBSCRIPTION_PRICES[upgradeCurrency][shouldUseTeamPricing ? CONST.POLICY.TYPE.TEAM : CONST.POLICY.TYPE.CORPORATE][CONST.SUBSCRIPTION.TYPE.ANNUAL],
        upgradeCurrency,
    )} `;
}, [preferredCurrency, isCategorizing, isDistanceRateUpgrade, isReporting]);

We can check if there are some other scenarios also which should use the Collect pricing.

[PiyushChandra17]

🚨 Edited by proposal-police: This proposal was edited at 2025-11-17 20:28:19 UTC.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Upgrade Option Has Incorrect Amount Listed

What is the root cause of that problem?

Subscription Price Update

What changes do you think we should make in order to solve the problem?

1. We are setting the amount listed in formattedPrice here

2. In upgrade into page, we are setting the formattedPrice logic in useMemo block here, the price value comes from CONST.SUBSCRIPTION_PRICES

3. We need to update the SUBSCRIPTION_PRICES > USD > corporate > yearly2018: 500 here

[this.SUBSCRIPTION.TYPE.ANNUAL]: 500,

What alternative solutions did you explore? (Optional)

n/A

Result

[dukenv0307]

@ShridharGoel @PiyushChandra17 Do you guys know how to reproduce?

[PiyushChandra17]

@dukenv0307 Yes,

1. Go to "Workspaces" tab
2. Go to "Reports"
3. Toggle "Report field"