CURRENCY in Zoho Sheet: Syntax and Data Limitations

CURRENCY requests conversion of an amount between two currencies. Its answer depends on the exchange-rate data available to the service, so a formula’s syntax alone does not determine a permanent numerical result.

=CURRENCY(100;"USD";"EUR")

This expresses a conversion of 100 US dollars into euros. If, hypothetically, the applicable rate were 0.90 EUR per USD, the converted amount would be 90 EUR. That rate is invented solely to explain the units. It is not a current quote, historical observation or prediction of what Zoho will return.

=CURRENCY(value; "from"; "to")

The three arguments are the amount, its source currency code and the destination currency code. The official CURRENCY reference lists codes including USD, EUR, GBP and INR. Use quoted code strings or cells containing those strings. A display symbol such as $ is not the currency code used in these examples.

Zoho describes the data as informational and says it may be delayed by up to 30 minutes. That delay notice is not a refresh schedule, an uptime commitment or a promise that every displayed result is fresh. The article does not establish a guaranteed query cadence, quote source timestamp or execution-time availability for these examples.

A simple worksheet layout is:

For the fictional rate of 0.90 EUR/USD, the dimensional check is 100 USD × 0.90 EUR/USD = 90 EUR. Do not multiply by 100 again merely because a rate is displayed alongside a monetary amount. Conversely, dividing by 0.90 would reverse the rate’s direction.

The cell-based formula above is an illustration of the documented request. It was not submitted to Zoho during preparation of this guide. There is no observed output for D2 here.

Each row below supplies an explicitly fictional rate. The expected arithmetic is conditional on that assumption, not an asserted function result from a live service.

The first two invented rates are reciprocal, making a useful unit check: 250×0.80 = 200, followed mathematically by 200×1.25 = 250. Two real service requests need not form this exact round trip if their data differ in time or precision. This arithmetic is not evidence about Zoho caching, spreads or update behavior.

Suppose a fictional budget contains 250 USD and 100 EUR, and the analyst deliberately chooses the scenario rate 0.80 EUR/USD. Independent arithmetic gives 250×0.80+100 = 300 EUR.

That is a fixed scenario calculation. A worksheet that instead calls CURRENCY uses the service’s returned conversion, whose value may differ. Label the report accordingly: source amounts, destination currency, whether the rate is a deliberate assumption or externally obtained, and the time at which the report was prepared. If a rate timestamp is unavailable, say so rather than treating the report timestamp as proof of quote freshness.

For reproducible comparisons, retain the explicitly chosen rate in a visible assumption cell and calculate from it. This is a modeling alternative, not a claim that CURRENCY has a historical-date argument: its documented signature has none. Do not treat a rounded display as the full stored numerical value when reconciling a total.

The help page supplies generic error descriptions but does not establish a comprehensive result contract for unavailable currency pairs, unsupported codes, service outages or text-number coercion. Do not convert an unrecognized error to zero in a total without investigating it: zero is a monetary value and would silently change the report.

A returned conversion also does not establish the amount a bank or payment provider would deliver. A real transaction can involve a separately quoted rate, fees or other terms. This guide explains a spreadsheet request and hypothetical arithmetic; it does not recommend a currency transaction.

CONVERT changes measurement units such as meters and feet. It does not provide the external exchange-rate relationship needed here. SUM can combine amounts only after their currencies have been consistently normalized.

The rolling official reference was checked on October 18, 2026. No currency service request, authored Zoho workbook or calculation-engine execution was performed. All numerical examples above are conditional on clearly labeled fictional rates. The source does not identify a first introduction version or establish mobile/import parity, retirement or deprecation history.