Cannot Enter Decimal Amounts for COP Currency in New Expensify

[m-natarajan]

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-53
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @Liz-Canary
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Navigate to workspace chat or click global +
2. create a new expense
3. Set the currency to COP
4. Attempt to enter an amount that includes a decimal value (e.g., 1234.56)

Expected Result:

The expense amount should accept and display 2 decimal values, consistent with Expensify Classic behavior.

Actual Result:

New Expensify does not register any input after the decimal point.
The user cannot enter the full amount as intended.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Recording.2350.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (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.

[trjExpensify]

Response from the frontend:

"COP": {
        "symbol": "Col$",
        "name": "Colombian Peso",
        "decimals": 0
      },

Looks like this currency has decimals: 0 in the backend in places like here and here.

Not entirely sure why, given that we allow 2 decimal entry for COP in Classic. See below:

2026-02-05_18-46-08.mp4

[abbasifaizan70]

Allow Decimal Input for COP in New Expensify

Proposal

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

When creating a new expense in New Expensify and selecting COP, the amount input rejects any digits after the decimal separator (e.g., 1234.56 becomes 1234.). In Expensify Classic, COP accepts two decimal places. We want New Expensify to accept and display 2 decimal values for COP to match Classic behavior.

What is the root cause of that problem?

COP is coming from the backend currency list with decimals: 0, so getCurrencyDecimals() returns 0 and the money request input uses that value to validate the amount. The validation rejects decimal input when decimals === 0, so typing after the decimal point is ignored.

Current frontend flow:

• getCurrencyDecimals() reads the currencyList decimals and returns 0 for COP
  

  App/src/libs/CurrencyUtils.ts

  Lines 29 to 32 in 56e8c77

  	function getCurrencyDecimals(currency: string = CONST.CURRENCY.USD): number {
  	const decimals = currencyList?.[currency]?.decimals;
  	return decimals ?? 2;
  	}

• MoneyRequestAmountInput passes that decimals value into the input
  

  App/src/components/MoneyRequestAmountInput.tsx

  Lines 176 to 213 in 56e8c77

  	const decimals = getCurrencyDecimals(currency);
  	useEffect(() => {
  	if ((!currency || typeof amount !== 'number' || (formatAmountOnBlur && isTextInputFocused(textInput))) ?? shouldKeepUserInput) {
  	return;
  	}
  	const frontendAmount = onFormatAmount(amount, currency);
  	// Only update selection if the amount prop was changed from the outside and is not the same as the current amount we just computed
  	// In the line below the currentAmount is not immediately updated, it should still hold the previous value.
  	if (frontendAmount !== numberFormRef.current?.getNumber()) {
  	numberFormRef.current?.updateNumber(frontendAmount);
  	}
  	// we want to re-initialize the state only when the amount changes
  	// eslint-disable-next-line react-hooks/exhaustive-deps
  	}, [amount, shouldKeepUserInput]);
  	const formatAmount = useCallback(() => {
  	if (!formatAmountOnBlur) {
  	return;
  	}
  	const formattedAmount = onFormatAmount(amount, currency);
  	if (maxLength && formattedAmount.length > maxLength) {
  	return;
  	}
  	numberFormRef.current?.updateNumber(formattedAmount);
  	}, [amount, currency, onFormatAmount, formatAmountOnBlur, maxLength]);
  	const inputOnBlur = (e: BlurEvent) => {
  	props.onBlur?.(e);
  	formatAmount();
  	};
  	return (
  	<NumberWithSymbolForm
  	value={onFormatAmount(amount, currency)}
  	decimals={decimals}
  	onSymbolButtonPress={onCurrencyButtonPress}

• NumberWithSymbolForm uses validateAmount() with the provided decimals, which blocks decimals for 0
  https://github.com/Expensify/App/blob/main/App/src/components/NumberWithSymbolForm.tsx#L224-L233
  

  App/src/libs/MoneyRequestUtils.ts

  Lines 44 to 53 in 56e8c77

  	function validateAmount(amount: string, decimals: number, amountMaxLength: number = CONST.IOU.AMOUNT_MAX_LENGTH, shouldAllowNegative = false): boolean {
  	const regexString =
  	decimals === 0
  	? `^${shouldAllowNegative ? '-?' : ''}\\d{1,${amountMaxLength}}$` // Don't allow decimal point if decimals === 0
  	: `^${shouldAllowNegative ? '-?' : ''}\\d{1,${amountMaxLength}}(\\.\\d{0,${decimals}})?$`; // Allow the decimal point and the desired number of digits after the point
  	const decimalNumberRegex = new RegExp(regexString, 'i');
  	if (shouldAllowNegative) {
  	return amount === '' || amount === '-' || decimalNumberRegex.test(amount);
  	}
  	return amount === '' || decimalNumberRegex.test(amount);

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

Add a small frontend override so COP is treated as having 2 decimals when getCurrencyDecimals() is called. This keeps backend data unchanged while aligning New Expensify input behavior with Classic.

1. Add a currency decimals override map in CurrencyUtils:

App/src/libs/CurrencyUtils.ts

Lines 29 to 32 in 56e8c77

	function getCurrencyDecimals(currency: string = CONST.CURRENCY.USD): number {
	const decimals = currencyList?.[currency]?.decimals;
	return decimals ?? 2;
	}

(new TypeScript code)

const CURRENCY_DECIMALS_OVERRIDE: Record<string, number> = {
    COP: 2,
};

function getCurrencyDecimals(currency: string = CONST.CURRENCY.USD): number {
    const override = CURRENCY_DECIMALS_OVERRIDE[currency];
    if (typeof override === 'number') {
        return override;
    }

    const decimals = currencyList?.[currency]?.decimals;
    return decimals ?? 2;
}

This makes all places that rely on getCurrencyDecimals() (input validation, formatting, etc.) accept two decimals for COP without changing backend currency metadata.

What alternative solutions did you explore? (Optional)

• Updating the backend currency list to set COP.decimals = 2. This is cleaner long-term but requires backend changes and coordinated release. The frontend override is low-risk and unblocks users immediately.